> 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/harvesting-multiple-kubernetes-pod-tokens-from-within-a-kubernetes-pod.md).

# Harvesting multiple Kubernetes pod tokens from within a Kubernetes pod

### Synopsis

| Field                | Value                                                                                  |
| -------------------- | -------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                |
| Training Period      | 30 Days                                                                                |
| Test Period          | 15 Minutes                                                                             |
| Deduplication Period | 1 Day                                                                                  |
| Required Data        | XDR Agent with eXtended Threat Hunting (XTH)                                           |
| Detector Tags        | Kubernetes - AGENT, Kubernetes Credentials Theft Analytics                             |
| ATT\&CK Tactic       | Credential Access (TA0006)                                                             |
| ATT\&CK Technique    | Unsecured Credentials (T1552), Unsecured Credentials: Credentials In Files (T1552.001) |
| Severity             | Medium                                                                                 |

### Description

A process within a Kubernetes pod accessed the service account tokens of multiple other pods by traversing the host filesystem.

### Attacker's Goals

Harvest service account tokens from other pods to impersonate their identities and perform lateral movement or privilege escalation within the Kubernetes cluster.

### Investigative actions

* Verify if the pod has a legitimate reason for a hostPath mount.
* Check if the harvested tokens were used to access the Kubernetes API server.
* Investigate which operations were performed with the stolen credentials.
* Look for additional suspicious activities from the same pod.

### Variations

<details>

<summary>Harvesting multiple Kubernetes pod tokens from within a Kubernetes pod via an interactive shell</summary>

**Synopsis**

| Field             | Value                                                                                  |
| ----------------- | -------------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006)                                                             |
| ATT\&CK Technique | Unsecured Credentials (T1552), Unsecured Credentials: Credentials In Files (T1552.001) |
| Severity          | High                                                                                   |

**Description**

A process within a Kubernetes pod accessed the service account tokens of multiple other pods by traversing the host filesystem.

**Attacker's Goals**

Harvest service account tokens from other pods to impersonate their identities and perform lateral movement or privilege escalation within the Kubernetes cluster.

**Investigative actions**

* Verify if the pod has a legitimate reason for a hostPath mount.
* Check if the harvested tokens were used to access the Kubernetes API server.
* Investigate which operations were performed with the stolen credentials.
* Look for additional suspicious activities from the same pod.

</details>


---

# 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/harvesting-multiple-kubernetes-pod-tokens-from-within-a-kubernetes-pod.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.
