> 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/write-access-to-sensitive-host-files-from-within-a-kubernetes-pod.md).

# Write access to sensitive host files from within a Kubernetes pod

### 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 with eXtended Threat Hunting (XTH) |
| Detector Tags        | Kubernetes - AGENT                           |
| ATT\&CK Tactic       | Privilege Escalation (TA0004)                |
| ATT\&CK Technique    | Escape to Host (T1611)                       |
| Severity             | Low                                          |

### Description

A process wrote to sensitive host files from within a Kubernetes pod, indicating a potential container escape or host compromise attempt.

### Attacker's Goals

Modify sensitive host files for persistence, privilege escalation, or container escape.

### Investigative actions

* Look for additional suspicious activities from the same pod.
* Verify if the written files were modified maliciously (e.g., backdoor accounts in /etc/shadow).
* Investigate the bind mount configuration that allowed host filesystem write access.
* Check if the container has elevated privileges or capabilities.

### Variations

<details>

<summary>Write access to sensitive host files from within a Kubernetes pod via an interactive shell</summary>

**Synopsis**

| Field             | Value                         |
| ----------------- | ----------------------------- |
| ATT\&CK Tactic    | Privilege Escalation (TA0004) |
| ATT\&CK Technique | Escape to Host (T1611)        |
| Severity          | High                          |

**Description**

A process wrote to sensitive host files from within a Kubernetes pod, indicating a potential container escape or host compromise attempt.

**Attacker's Goals**

Modify sensitive host files for persistence, privilege escalation, or container escape.

**Investigative actions**

* Look for additional suspicious activities from the same pod.
* Verify if the written files were modified maliciously (e.g., backdoor accounts in /etc/shadow).
* Investigate the bind mount configuration that allowed host filesystem write access.
* Check if the container has elevated privileges or capabilities.

</details>

<details>

<summary>Write access to sensitive host files from within a Kubernetes pod in a privileged or scanning context</summary>

**Synopsis**

| Field             | Value                         |
| ----------------- | ----------------------------- |
| ATT\&CK Tactic    | Privilege Escalation (TA0004) |
| ATT\&CK Technique | Escape to Host (T1611)        |
| Severity          | Medium                        |

**Description**

A process wrote to sensitive host files from within a Kubernetes pod, indicating a potential container escape or host compromise attempt.

**Attacker's Goals**

Modify sensitive host files for persistence, privilege escalation, or container escape.

**Investigative actions**

* Look for additional suspicious activities from the same pod.
* Verify if the written files were modified maliciously (e.g., backdoor accounts in /etc/shadow).
* Investigate the bind mount configuration that allowed host filesystem write access.
* Check if the container has elevated privileges or capabilities.

</details>

<details>

<summary>Unusual write access to sensitive host files from within a Kubernetes pod</summary>

**Synopsis**

| Field             | Value                         |
| ----------------- | ----------------------------- |
| ATT\&CK Tactic    | Privilege Escalation (TA0004) |
| ATT\&CK Technique | Escape to Host (T1611)        |
| Severity          | Medium                        |

**Description**

A process wrote to sensitive host files from within a Kubernetes pod, indicating a potential container escape or host compromise attempt.

**Attacker's Goals**

Modify sensitive host files for persistence, privilege escalation, or container escape.

**Investigative actions**

* Look for additional suspicious activities from the same pod.
* Verify if the written files were modified maliciously (e.g., backdoor accounts in /etc/shadow).
* Investigate the bind mount configuration that allowed host filesystem write access.
* Check if the container has elevated privileges or capabilities.

</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/write-access-to-sensitive-host-files-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.
