> 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/unusual-identity-and-access-management-iam-activity.md).
# Unusual Identity and Access Management (IAM) activity
### Synopsis
| Field | Value |
| -------------------- | ---------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 5 Days |
| Required Data | Requires one of the following data sources:
AWS Audit Log OR Gcp Audit Log
|
| Detection Modules | Cloud |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation: Additional Cloud Credentials (T1098.001), Valid Accounts: Cloud Accounts (T1078.004) |
| Severity | Informational |
### Description
A cloud identity performed an unusual IAM operation.
### Attacker's Goals
Manipulate IAM configuration to strengthen the foothold in the cloud environment of the organization, by creating new accounts, modifying credentials, and permissions. Using the modified accounts, the attacker may perform additional activities in an evasive manner.
### Investigative actions
* Check the identity's role designation in the organization.
* Verify that the identity did not perform any sensitive IAM operation that it shouldn't.
### Variations
Unusual Identity and Access Management (IAM) activity executed from a cloud Internet facing instance
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation: Additional Cloud Credentials (T1098.001), Valid Accounts: Cloud Accounts (T1078.004) |
| Severity | Medium |
**Description**
A cloud Internet facing instance performed an unusual IAM operation.
**Attacker's Goals**
Manipulate IAM configuration to strengthen the foothold in the cloud environment of the organization, by creating new accounts, modifying credentials, and permissions. Using the modified accounts, the attacker may perform additional activities in an evasive manner.
**Investigative actions**
* Check the identity's role designation in the organization.
* Verify that the identity did not perform any sensitive IAM operation that it shouldn't.
Unusual Identity and Access Management (IAM) activity
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Account Manipulation: Additional Cloud Credentials (T1098.001), Valid Accounts: Cloud Accounts (T1078.004) |
| Severity | Low |
**Description**
A cloud non-user identity performed an unusual IAM operation.
**Attacker's Goals**
Manipulate IAM configuration to strengthen the foothold in the cloud environment of the organization, by creating new accounts, modifying credentials, and permissions. Using the modified accounts, the attacker may perform additional activities in an evasive manner.
**Investigative actions**
* Check the identity's role designation in the organization.
* Verify that the identity did not perform any sensitive IAM operation that it shouldn't.
---
# 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/unusual-identity-and-access-management-iam-activity.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.