> 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/kubernetes-pod-created-with-sensitive-volume.md).
# Kubernetes Pod Created With Sensitive Volume
### Synopsis
| Field | Value |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 5 Days |
| Required Data | Requires one of the following data sources:
AWS Audit Log OR Azure Audit Log OR Gcp Audit Log OR Kubernetes Audit Logs
|
| Detection Modules | Cloud |
| Detector Tags | Kubernetes - API |
| ATT\&CK Tactic | Privilege Escalation (TA0004), Execution (TA0002) |
| ATT\&CK Technique | Escape to Host (T1611), Deploy Container (T1610) |
| Severity | Informational |
### Description
An identity created a Kubernetes Pod with a sensitive volume, allowing the Pod to have read or write permissions on the host's filesystem This could suggest an effort by an adversary to access sensitive files on the host and employ techniques for escalating privileges.
### Attacker's Goals
* Gain access to the host's filesystem.
* Gain root access to the host.
### Investigative actions
* Check the identity's role designation in the organization.
* Inspect for any additional suspicious activities inside the Kubernetes Pod.
### Variations
Kubernetes Pod Created With Sensitive Volume for the first time in the cluster
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------- |
| ATT\&CK Tactic | Privilege Escalation (TA0004), Execution (TA0002) |
| ATT\&CK Technique | Escape to Host (T1611), Deploy Container (T1610) |
| Severity | Low |
**Description**
An identity created a Kubernetes Pod with a sensitive volume, allowing the Pod to have read or write permissions on the host's filesystem This could suggest an effort by an adversary to access sensitive files on the host and employ techniques for escalating privileges.
**Attacker's Goals**
* Gain access to the host's filesystem.
* Gain root access to the host.
**Investigative actions**
* Check the identity's role designation in the organization.
* Inspect for any additional suspicious activities inside the Kubernetes Pod.
Kubernetes Pod Created With Sensitive Volume for the first time in the namespace
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------- |
| ATT\&CK Tactic | Privilege Escalation (TA0004), Execution (TA0002) |
| ATT\&CK Technique | Escape to Host (T1611), Deploy Container (T1610) |
| Severity | Low |
**Description**
An identity created a Kubernetes Pod with a sensitive volume, allowing the Pod to have read or write permissions on the host's filesystem This could suggest an effort by an adversary to access sensitive files on the host and employ techniques for escalating privileges.
**Attacker's Goals**
* Gain access to the host's filesystem.
* Gain root access to the host.
**Investigative actions**
* Check the identity's role designation in the organization.
* Inspect for any additional suspicious activities inside the Kubernetes Pod.
Kubernetes Pod Created With Sensitive Volume for the first time by the identity
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------- |
| ATT\&CK Tactic | Privilege Escalation (TA0004), Execution (TA0002) |
| ATT\&CK Technique | Escape to Host (T1611), Deploy Container (T1610) |
| Severity | Low |
**Description**
An identity created a Kubernetes Pod with a sensitive volume, allowing the Pod to have read or write permissions on the host's filesystem This could suggest an effort by an adversary to access sensitive files on the host and employ techniques for escalating privileges.
**Attacker's Goals**
* Gain access to the host's filesystem.
* Gain root access to the host.
**Investigative actions**
* Check the identity's role designation in the organization.
* Inspect for any additional suspicious activities inside the Kubernetes Pod.
---
# 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/kubernetes-pod-created-with-sensitive-volume.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.