> 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-cloud-instance-metadata-service-imds-access.md).
# Unusual cloud Instance Metadata Service (IMDS) access
### Synopsis
| Field | Value |
| -------------------- | -------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | XDR Agent |
| Detection Modules | Cloud |
| Detector Tags | Kubernetes - AGENT, Kubernetes Credentials Theft Analytics |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Unsecured Credentials: Cloud Instance Metadata API (T1552.005) |
| Severity | Informational |
### Description
A request to cloud Instance Metadata Service (IMDS) was made by an unusual process. This process does not usually access the Instance Metadata Service. An attacker may extract cloud compute tokens to gain access to a cloud environment.
### Attacker's Goals
Extract sensitive cloud compute tokens to access restricted cloud resources.
### Investigative actions
* Determine whether a web service was involved and if it was exploited to execute this technique.
* Identify any additional commands that were executed.
* Review the permissions assigned to the target machine to identify which resources may be affected.
* Examine related compute activity in the cloud audit logs.
### Variations
Unusual cloud Instance Metadata Service (IMDS) access from an unusual known Windows web service
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Unsecured Credentials: Cloud Instance Metadata API (T1552.005) |
| Severity | Medium |
**Description**
A request to cloud Instance Metadata Service (IMDS) was made by an unusual process. This process does not usually access the Instance Metadata Service. An attacker may extract cloud compute tokens to gain access to a cloud environment.
**Attacker's Goals**
Extract sensitive cloud compute tokens to access restricted cloud resources.
**Investigative actions**
* Determine whether a web service was involved and if it was exploited to execute this technique.
* Identify any additional commands that were executed.
* Review the permissions assigned to the target machine to identify which resources may be affected.
* Examine related compute activity in the cloud audit logs.
Unusual cloud Instance Metadata Service (IMDS) access from an unusual known web service
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Unsecured Credentials: Cloud Instance Metadata API (T1552.005) |
| Severity | Medium |
**Description**
A request to cloud Instance Metadata Service (IMDS) was made by an unusual process. This process does not usually access the Instance Metadata Service. An attacker may extract cloud compute tokens to gain access to a cloud environment.
**Attacker's Goals**
Extract sensitive cloud compute tokens to access restricted cloud resources.
**Investigative actions**
* Determine whether a web service was involved and if it was exploited to execute this technique.
* Identify any additional commands that were executed.
* Review the permissions assigned to the target machine to identify which resources may be affected.
* Examine related compute activity in the cloud audit logs.
Unusual cloud Instance Metadata Service (IMDS) access from an unusual known Windows shell process
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Unsecured Credentials: Cloud Instance Metadata API (T1552.005) |
| Severity | Medium |
**Description**
A request to cloud Instance Metadata Service (IMDS) was made by an unusual process. This process does not usually access the Instance Metadata Service. An attacker may extract cloud compute tokens to gain access to a cloud environment.
**Attacker's Goals**
Extract sensitive cloud compute tokens to access restricted cloud resources.
**Investigative actions**
* Determine whether a web service was involved and if it was exploited to execute this technique.
* Identify any additional commands that were executed.
* Review the permissions assigned to the target machine to identify which resources may be affected.
* Examine related compute activity in the cloud audit logs.
Unusual cloud Instance Metadata Service (IMDS) access from an unusual known shell process
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Unsecured Credentials: Cloud Instance Metadata API (T1552.005) |
| Severity | Medium |
**Description**
A request to cloud Instance Metadata Service (IMDS) was made by an unusual process. This process does not usually access the Instance Metadata Service. An attacker may extract cloud compute tokens to gain access to a cloud environment.
**Attacker's Goals**
Extract sensitive cloud compute tokens to access restricted cloud resources.
**Investigative actions**
* Determine whether a web service was involved and if it was exploited to execute this technique.
* Identify any additional commands that were executed.
* Review the permissions assigned to the target machine to identify which resources may be affected.
* Examine related compute activity in the cloud audit logs.
Unusual cloud Instance Metadata Service (IMDS) access from an unusual known Windows scripting process
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Unsecured Credentials: Cloud Instance Metadata API (T1552.005) |
| Severity | Medium |
**Description**
A request to cloud Instance Metadata Service (IMDS) was made by an unusual process. This process does not usually access the Instance Metadata Service. An attacker may extract cloud compute tokens to gain access to a cloud environment.
**Attacker's Goals**
Extract sensitive cloud compute tokens to access restricted cloud resources.
**Investigative actions**
* Determine whether a web service was involved and if it was exploited to execute this technique.
* Identify any additional commands that were executed.
* Review the permissions assigned to the target machine to identify which resources may be affected.
* Examine related compute activity in the cloud audit logs.
Unusual cloud Instance Metadata Service (IMDS) access from an unusual known scripting process
**Synopsis**
| Field | Value |
| ----------------- | -------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Unsecured Credentials: Cloud Instance Metadata API (T1552.005) |
| Severity | Low |
**Description**
A request to cloud Instance Metadata Service (IMDS) was made by an unusual process. This process does not usually access the Instance Metadata Service. An attacker may extract cloud compute tokens to gain access to a cloud environment.
**Attacker's Goals**
Extract sensitive cloud compute tokens to access restricted cloud resources.
**Investigative actions**
* Determine whether a web service was involved and if it was exploited to execute this technique.
* Identify any additional commands that were executed.
* Review the permissions assigned to the target machine to identify which resources may be affected.
* Examine related compute activity in the cloud audit logs.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/unusual-cloud-instance-metadata-service-imds-access.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.