Suspicious container runtime connection from within 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	XDR Agent
Detector Tags	Kubernetes - AGENT, Containers
ATT&CK Tactic	Execution (TA0002)
ATT&CK Technique	Container Administration Command (T1609), Deploy Container (T1610)
Severity	Informational

Description

A process from within a Kubernetes Pod communicated with the container runtime daemon using the runtime socket. This may indicate an adversary attempting to escape from the Kubernetes Pod to the host.

Attacker's Goals

Escape from a container to the host machine and expand the foothold in the network.

Investigative actions

• Change the container socket configuration.
• Check if the default Docker daemon binding to TCP changed. If so, non-root users may gain access to the container.

Variations

Suspicious container runtime connection from within a Kubernetes Pod using the curl client

Synopsis

Field	Value
ATT&CK Tactic	Execution (TA0002)
ATT&CK Technique	Container Administration Command (T1609), Deploy Container (T1610)
Severity	Low

Description

A process from within a Kubernetes Pod communicated with the container runtime daemon using the runtime socket. This may indicate an adversary attempting to escape from the Kubernetes Pod to the host.

Attacker's Goals

Escape from a container to the host machine and expand the foothold in the network.

Investigative actions

• Change the container socket configuration.
• Check if the default Docker daemon binding to TCP changed. If so, non-root users may gain access to the container.

Suspicious container runtime connection from within a Kubernetes Pod using the docker client

Synopsis

Field	Value
ATT&CK Tactic	Execution (TA0002)
ATT&CK Technique	Container Administration Command (T1609), Deploy Container (T1610)
Severity	Medium

Description

A process from within a Kubernetes Pod communicated with the container runtime daemon using the runtime socket. This may indicate an adversary attempting to escape from the Kubernetes Pod to the host.

Attacker's Goals

Escape from a container to the host machine and expand the foothold in the network.

Investigative actions

• Change the container socket configuration.
• Check if the default Docker daemon binding to TCP changed. If so, non-root users may gain access to the container.