> 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/cloud-impersonation-attempt-by-unusual-identity-type.md).
# Cloud impersonation attempt by unusual identity type
### 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 | Initial Access (TA0001) |
| ATT\&CK Technique | Valid Accounts (T1078), Trusted Relationship (T1199) |
| Severity | Informational |
### Description
A suspicious identity type has attempted to impersonate another identity.
### Attacker's Goals
* Escalate privileges to bypass access controls
* Avoid detection throughout their compromise.
### Investigative actions
* Check the identity's designation.
* Verify that the identity did not perform sensitive operation on behalf of the impersonated identity.
### Variations
Cloud impersonation attempt of a management role by unusual identity type
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Valid Accounts (T1078), Trusted Relationship (T1199) |
| Severity | Informational |
**Description**
An unusual cloud identity type attempted to impersonate a management role.
**Attacker's Goals**
* Escalate privileges to bypass access controls
* Avoid detection throughout their compromise.
**Investigative actions**
* Check the identity's designation.
* Verify that the identity did not perform sensitive operation on behalf of the impersonated identity.
Successful cloud impersonation by an unusual identity type
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001) |
| ATT\&CK Technique | Valid Accounts (T1078), Trusted Relationship (T1199) |
| Severity | Medium |
**Description**
A suspicious identity type has successfully impersonated another identity.
**Attacker's Goals**
* Escalate privileges to bypass access controls
* Avoid detection throughout their compromise.
**Investigative actions**
* Check the identity's designation.
* Verify that the identity did not perform sensitive operation on behalf of the impersonated identity.
---
# 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/cloud-impersonation-attempt-by-unusual-identity-type.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.