> 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-exec-into-a-kubernetes-pod.md).
# Unusual exec into a Kubernetes Pod
### 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 | Execution (TA0002) |
| ATT\&CK Technique | Container Administration Command (T1609) |
| Severity | Informational |
### Description
An identity initiated a shell session within a Kubernetes pod using the exec command. The command allows an identity to establish a temporary shell session and execute commands in the pod. This may indicate an attacker attempting to gain an interactive shell, which will allow access to the pod's data.
### Attacker's Goals
* Execute commands within the Kubernetes Pod.
* Access any resource the Kubernetes Pod has access to.
### Investigative actions
* Check the identity's role designation in the organization.
* Inspect for any additional suspicious activities inside the Kubernetes Pod.
### Variations
Failed exec attempt into a Kubernetes Pod
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Container Administration Command (T1609) |
| Severity | Informational |
**Description**
An identity initiated a shell session within a Kubernetes pod using the exec command. The command allows an identity to establish a temporary shell session and execute commands in the pod. This may indicate an attacker attempting to gain an interactive shell, which will allow access to the pod's data.
**Attacker's Goals**
* Execute commands within the Kubernetes Pod.
* Access any resource the Kubernetes Pod has access to.
**Investigative actions**
* Check the identity's role designation in the organization.
* Inspect for any additional suspicious activities inside the Kubernetes Pod.
First time execution into Kubernetes Pod at the cluster-level
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Container Administration Command (T1609) |
| Severity | Medium |
**Description**
An identity initiated a shell session within a Kubernetes pod using the exec command. The command allows an identity to establish a temporary shell session and execute commands in the pod. This may indicate an attacker attempting to gain an interactive shell, which will allow access to the pod's data.
**Attacker's Goals**
* Execute commands within the Kubernetes Pod.
* Access any resource the Kubernetes Pod has access to.
**Investigative actions**
* Check the identity's role designation in the organization.
* Inspect for any additional suspicious activities inside the Kubernetes Pod.
Identity executed into Kubernetes Pod for the first time
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Container Administration Command (T1609) |
| Severity | Low |
**Description**
An identity initiated a shell session within a Kubernetes pod using the exec command. The command allows an identity to establish a temporary shell session and execute commands in the pod. This may indicate an attacker attempting to gain an interactive shell, which will allow access to the pod's data.
**Attacker's Goals**
* Execute commands within the Kubernetes Pod.
* Access any resource the Kubernetes Pod has access to.
**Investigative actions**
* Check the identity's role designation in the organization.
* Inspect for any additional suspicious activities inside the Kubernetes Pod.
Identity executed into a Kubernetes namespace for the first time
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Container Administration Command (T1609) |
| Severity | Low |
**Description**
An identity initiated a shell session within a Kubernetes pod using the exec command. The command allows an identity to establish a temporary shell session and execute commands in the pod. This may indicate an attacker attempting to gain an interactive shell, which will allow access to the pod's data.
**Attacker's Goals**
* Execute commands within the Kubernetes Pod.
* Access any resource the Kubernetes Pod has access to.
**Investigative actions**
* Check the identity's role designation in the organization.
* Inspect for any additional suspicious activities inside the Kubernetes Pod.
Identity executed into a Kubernetes Pod for the first time
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002) |
| ATT\&CK Technique | Container Administration Command (T1609) |
| Severity | Low |
**Description**
An identity initiated a shell session within a Kubernetes pod using the exec command. The command allows an identity to establish a temporary shell session and execute commands in the pod. This may indicate an attacker attempting to gain an interactive shell, which will allow access to the pod's data.
**Attacker's Goals**
* Execute commands within the Kubernetes Pod.
* Access any resource the Kubernetes Pod has access to.
**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 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/unusual-exec-into-a-kubernetes-pod.md?ask=&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.