Analytics BIOC Informational
✕

Kubernetes Pod Created With Sensitive Volume

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.

Module:
Cortex Cloud
Licensed by:
Cloud Runtime Security (CRS)
Data source:
AWS Audit Log, Azure Audit Log, Gcp Audit Log, Kubernetes Audit Logs
ATT&CK tactics: Privilege Escalation (TA0004) Execution (TA0002)
ATT&CK techniques: Escape to Host (T1611) Deploy Container (T1610)
Detector tags: Kubernetes - API
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.

Test period:
N/A (single event)
Deduplication:
5 Days
3 variations:
  • Kubernetes Pod Created With Sensitive Volume for the first time in the cluster Low (parent: Informational)
  • Kubernetes Pod Created With Sensitive Volume for the first time in the namespace Low (parent: Informational)
  • Kubernetes Pod Created With Sensitive Volume for the first time by the identity Low (parent: Informational)