> 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/a-compute-attached-identity-executed-api-calls-outside-the-instance-s-region.md).
# A compute-attached identity executed API calls outside the instance's region
### Synopsis
| Field | Value |
| -------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 5 Days |
| Required Data | AWS Audit Log |
| Detection Modules | Cloud |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts: Cloud Accounts (T1078.004), Steal Application Access Token (T1528), Unsecured Credentials (T1552) |
| Severity | Informational |
### Description
A compute-attached identity performed actions outside the compute instance region.
### Attacker's Goals
Exfiltrate token and abuse it remotely.
### Investigative actions
* Verify whether the compute-attached identity's credentials were intentionally used remotely.
* Check what API calls were executed using instance's attached role.
* Check if the suspected instance is compromised.
### Variations
A compute-attached identity executed API calls outside the Lambda function's region
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts: Cloud Accounts (T1078.004), Steal Application Access Token (T1528), Unsecured Credentials (T1552) |
| Severity | Informational |
**Description**
A compute-attached identity performed actions outside the Lambda function region.
**Attacker's Goals**
Exfiltrate token and abuse it remotely.
**Investigative actions**
* Verify whether the compute-attached identity's credentials were intentionally used remotely.
* Check what API calls were executed using instance's attached role.
* Check if the suspected instance is compromised.
A compute-attached identity executed API calls outside the instance's region from an unusual geolocation and ASN
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts: Cloud Accounts (T1078.004), Steal Application Access Token (T1528), Unsecured Credentials (T1552) |
| Severity | High |
**Description**
A compute-attached identity performed actions outside the compute instance region.
**Attacker's Goals**
Exfiltrate token and abuse it remotely.
**Investigative actions**
* Verify whether the compute-attached identity's credentials were intentionally used remotely.
* Check what API calls were executed using instance's attached role.
* Check if the suspected instance is compromised.
A compute-attached identity executed API calls outside the instance's region from an unusual geolocation
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts: Cloud Accounts (T1078.004), Steal Application Access Token (T1528), Unsecured Credentials (T1552) |
| Severity | Medium |
**Description**
A compute-attached identity performed actions outside the compute instance region.
**Attacker's Goals**
Exfiltrate token and abuse it remotely.
**Investigative actions**
* Verify whether the compute-attached identity's credentials were intentionally used remotely.
* Check what API calls were executed using instance's attached role.
* Check if the suspected instance is compromised.
A compute-attached identity executed API calls outside the instance's region from an unusual ASN
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts: Cloud Accounts (T1078.004), Steal Application Access Token (T1528), Unsecured Credentials (T1552) |
| Severity | Low |
**Description**
A compute-attached identity performed actions outside the compute instance region.
**Attacker's Goals**
Exfiltrate token and abuse it remotely.
**Investigative actions**
* Verify whether the compute-attached identity's credentials were intentionally used remotely.
* Check what API calls were executed using instance's attached role.
* Check if the suspected instance is compromised.
A compute-attached identity executed API calls outside the instance's region
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts: Cloud Accounts (T1078.004), Steal Application Access Token (T1528), Unsecured Credentials (T1552) |
| Severity | Low |
**Description**
A compute-attached identity performed actions outside the compute instance region.
**Attacker's Goals**
Exfiltrate token and abuse it remotely.
**Investigative actions**
* Verify whether the compute-attached identity's credentials were intentionally used remotely.
* Check what API calls were executed using instance's attached role.
* Check if the suspected instance is compromised.
A compute-attached identity failed to execute API calls outside the instance's region
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Initial Access (TA0001), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts: Cloud Accounts (T1078.004), Steal Application Access Token (T1528), Unsecured Credentials (T1552) |
| Severity | Informational |
**Description**
A compute-attached identity performed actions outside the compute instance region.
**Attacker's Goals**
Exfiltrate token and abuse it remotely.
**Investigative actions**
* Verify whether the compute-attached identity's credentials were intentionally used remotely.
* Check what API calls were executed using instance's attached role.
* Check if the suspected instance is compromised.
---
# 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/a-compute-attached-identity-executed-api-calls-outside-the-instance-s-region.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.