> 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-admission-controller-activity.md).
# Kubernetes admission controller activity
### 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 | Persistence (TA0003), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts (T1078), Unsecured Credentials: Container API (T1552.007) |
| Severity | Informational |
### Description
A Kubernetes admission controller has been created or modified.
### Attacker's Goals
* Intercept the requests to the Kubernetes API sever, records secrets, and other sensitive information.
* Modify requests to the Kubernetes API sever.
### Investigative actions
* Verify whether the identity should use Kubernetes admission controllers.
* Examine the role of the Kubernetes admission controller and its intended function.
* Investigate other operations that were performed by the identity within the cluster.
### Variations
Kubernetes validating admission controller was used in the organization for the first time
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------ |
| ATT\&CK Tactic | Persistence (TA0003), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts (T1078), Unsecured Credentials: Container API (T1552.007) |
| Severity | Low |
**Description**
A validating Kubernetes admission controller has been created or modified.
**Attacker's Goals**
* Intercept the requests to the Kubernetes API sever, records secrets, and other sensitive information.
* Modify requests to the Kubernetes API sever.
**Investigative actions**
* Verify whether the identity should use Kubernetes admission controllers.
* Examine the role of the Kubernetes admission controller and its intended function.
* Investigate other operations that were performed by the identity within the cluster.
Kubernetes mutating admission controller was used in the organization for the first time
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------ |
| ATT\&CK Tactic | Persistence (TA0003), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts (T1078), Unsecured Credentials: Container API (T1552.007) |
| Severity | Medium |
**Description**
A mutating Kubernetes admission controller has been created or modified.
**Attacker's Goals**
* Intercept the requests to the Kubernetes API sever, records secrets, and other sensitive information.
* Modify requests to the Kubernetes API sever.
**Investigative actions**
* Verify whether the identity should use Kubernetes admission controllers.
* Examine the role of the Kubernetes admission controller and its intended function.
* Investigate other operations that were performed by the identity within the cluster.
Kubernetes validating admission controller was used in the cluster for the first time
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------ |
| ATT\&CK Tactic | Persistence (TA0003), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts (T1078), Unsecured Credentials: Container API (T1552.007) |
| Severity | Low |
**Description**
A validating Kubernetes admission controller has been created or modified.
**Attacker's Goals**
* Intercept the requests to the Kubernetes API sever, records secrets, and other sensitive information.
* Modify requests to the Kubernetes API sever.
**Investigative actions**
* Verify whether the identity should use Kubernetes admission controllers.
* Examine the role of the Kubernetes admission controller and its intended function.
* Investigate other operations that were performed by the identity within the cluster.
Kubernetes mutating admission controller was used in the cluster for the first time
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------ |
| ATT\&CK Tactic | Persistence (TA0003), Credential Access (TA0006) |
| ATT\&CK Technique | Valid Accounts (T1078), Unsecured Credentials: Container API (T1552.007) |
| Severity | Medium |
**Description**
A mutating Kubernetes admission controller has been created or modified.
**Attacker's Goals**
* Intercept the requests to the Kubernetes API sever, records secrets, and other sensitive information.
* Modify requests to the Kubernetes API sever.
**Investigative actions**
* Verify whether the identity should use Kubernetes admission controllers.
* Examine the role of the Kubernetes admission controller and its intended function.
* Investigate other operations that were performed by the identity within the cluster.
---
# 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/kubernetes-admission-controller-activity.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.