> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/aws-user-creation.md).
# AWS user creation
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | AWS Audit Log |
| Detection Modules | Cloud |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Create Account: Cloud Account (T1136.003) |
| Severity | Informational |
### Description
An AWS user creation was attempted.
### Attacker's Goals
Maintaining persistence by creating backdoor users or malicious resources, ensuring ongoing access even if their initial entry is detected.
### Investigative actions
* Check which user was created.
* Investigate the created user role and permissions.
* Verify the user who created the new identity is aware of this action.
* Review the recent history of IAM user creation performed by {identity\_name} — a spike may indicate scripted persistence.
* Determine the typical role of {identity\_name} (e.g., IT/DevOps) and whether user creation is expected for this identity.
* Be aware of any suspicious activity originating from the new user.
### Variations
AWS user creation from an unfamiliar IP address
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Create Account: Cloud Account (T1136.003) |
| Severity | Low |
**Description**
An AWS user creation was attempted.
**Attacker's Goals**
Maintaining persistence by creating backdoor users or malicious resources, ensuring ongoing access even if their initial entry is detected.
**Investigative actions**
* Check which user was created.
* Investigate the created user role and permissions.
* Verify the user who created the new identity is aware of this action.
* Review the recent history of IAM user creation performed by {identity\_name} — a spike may indicate scripted persistence.
* Determine the typical role of {identity\_name} (e.g., IT/DevOps) and whether user creation is expected for this identity.
* Be aware of any suspicious activity originating from the new user.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/aws-user-creation.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.