> 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-imds-access-followed-by-remote-token-usage.md).

# Cloud IMDS access followed by remote token usage

### Synopsis

| Field                | Value                                                                    |
| -------------------- | ------------------------------------------------------------------------ |
| Activation Period    | 14 Days                                                                  |
| Training Period      | 30 Days                                                                  |
| Test Period          | 1 Hour                                                                   |
| Deduplication Period | 1 Hour                                                                   |
| Required Data        | <p>Requires all of the following:<br>AWS Audit Log<br>XDR Agent</p>      |
| Detection Modules    | Cloud                                                                    |
| ATT\&CK Tactic       | Initial Access (TA0001), Credential Access (TA0006)                      |
| ATT\&CK Technique    | Exploit Public-Facing Application (T1190), Unsecured Credentials (T1552) |
| Severity             | Medium                                                                   |

### Description

A request was made to the cloud Instance Metadata Service (IMDS) followed by a remote usage of EC2 role token.

### Attacker's Goals

Gain unauthorized access by leveraging valid cloud credentials.

### Investigative actions

* Identify the process that accessed the IMDS on the cloud instance.
* Examine the AWS API calls made by the stolen token, focusing on unusual or sensitive actions.
* Assess the role's permissions and rotate credentials if compromise is confirmed.


---

# 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-imds-access-followed-by-remote-token-usage.md?ask=<question>&goal=<user_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.