Synopsis
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
|
Detection Modules |
Cloud |
Detector Tags |
Kubernetes - API |
ATT&CK Tactic |
|
ATT&CK Technique |
|
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
ATT&CK Tactic |
|
ATT&CK Technique |
|
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
ATT&CK Tactic |
|
ATT&CK Technique |
|
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
ATT&CK Tactic |
|
ATT&CK Technique |
|
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
ATT&CK Tactic |
|
ATT&CK Technique |
|
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.