Kubernetes vulnerability scanning tool usage

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	Execution (TA0002), Discovery (TA0007)
ATT&CK Technique	Deploy Container (T1610), Container and Resource Discovery (T1613)
Severity	Medium

Description

A known vulnerability scanning tool was used within a Kubernetes cluster.

Attacker's Goals

Usage of known tools and frameworks to exploit Kubernetes clusters.

Investigative actions

• Check if this activity is expected (e.g. penetration testing).
• Determine which Kubernetes resources were affected.
• Review additional events for any suspicious activity within the cluster.

Variations

Kubernetes vulnerability scanning tool usage within a pod

Synopsis

Field	Value
ATT&CK Tactic	Execution (TA0002), Discovery (TA0007)
ATT&CK Technique	Deploy Container (T1610), Container and Resource Discovery (T1613)
Severity	Medium

Description

A known vulnerability scanning tool was used from a pod within a Kubernetes cluster.

Attacker's Goals

Usage of known tools and frameworks to exploit Kubernetes clusters.

Investigative actions

• Check if this activity is expected (e.g. penetration testing).
• Determine which Kubernetes resources were affected.
• Review additional events for any suspicious activity within the cluster.

External Kubernetes vulnerability scanning tool usage

Synopsis

Field	Value
ATT&CK Tactic	Execution (TA0002), Discovery (TA0007)
ATT&CK Technique	Deploy Container (T1610), Container and Resource Discovery (T1613)
Severity	Medium

Description

A known vulnerability scanning tool was used within a Kubernetes clusteroutside the cloud environment.

Attacker's Goals

Usage of known tools and frameworks to exploit Kubernetes clusters.

Investigative actions

• Check if this activity is expected (e.g. penetration testing).
• Determine which Kubernetes resources were affected.
• Review additional events for any suspicious activity within the cluster.