For the complete documentation index, see llms.txt. This page is also available as Markdown.

Kubernetes Privileged Pod Creation

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 privileged container. This may indicate an adversary attempting to access that host's filesystem or gain root access to the host.

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 Privileged Pod Creation 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 privileged container. This may indicate an adversary attempting to access that host's filesystem or gain root access to the host.

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 Privileged Pod Creation 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 privileged container. This may indicate an adversary attempting to access that host's filesystem or gain root access to the host.

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 Privileged Pod Creation 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 privileged container. This may indicate an adversary attempting to access that host's filesystem or gain root access to the host.

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.

Was this helpful?