SecureAEye LAB ONLINE · SIG 657 · DET ~41s

← All attacks / Cloud, container and supply chain attacks

Kubernetes API server abuse

Over-permissive or unauthenticated API access creates workloads or reads secrets

categoryCloud, container and supply chain attacksseverityVery HighdetectabilityHighlabnot yet measured

Detection opportunity what to watch for

A benign emulation of this technique’s linchpin behaviour — the command an attacker runs, and where we’ve detonated it in the lab, exactly what the SIEM saw, what caught it, and what it missed.

What the attacker runs

ATT&CK T1552.007 · Cat the contents of a Kubernetes service account token file · Atomic Red Team
sudo /opt/lab/detonate.sh --technique T1552.007 --tool atomic --run-id <run-id> -- pwsh -c 'Import-Module invoke-atomicredteam; Invoke-AtomicTest T1552.007 -TestGuids 788e0019-a483-45da-bcfe-96353d46820f -GetPrereqs -PathToAtomicsFolder /opt/AtomicRedTeam/atomics; Invoke-AtomicTest T1552.007 -TestGuids 788e0019-a483-45da-bcfe-96353d46820f -PathToAtomicsFolder /opt/AtomicRedTeam/atomics -TimeoutSeconds 120'

Queued for lab measurement — not yet detonated.

Classification

26 values: 16 reviewed, 8 imported, 2 derived. What do these mean?

Exploitability

Attack vectorCredential attacksMisconfiguration
Reach (CVSS)Network
Attack complexityLow
Privileges requiredLow
User interactionNone
Attacker skill requiredMedium
Resources requiredLow
Likelihood / prevalenceHigh
MaturityEstablished

Impact & scope

SeverityVery High
ImpactAvailabilityConfidentialityIntegrity
PlatformContainers
EnvironmentCloudOn-premises
Target asset classIdentityServer
Kill-chain phase (tactic)Credential Access

Detection & telemetry

DetectabilityHigh
TestabilityAtomic Red Team test
Data sources (ATT&CK data components)Application Log ContentCommand ExecutionProcess Creation

Detection & response

Mitigated by 13

  • M1018 attack-mitigation
  • M1026 attack-mitigation
  • M1030 attack-mitigation
  • M1035 attack-mitigation
  • D3-ANCI d3fend
  • D3-CCSA d3fend
  • D3-CH d3fend
  • D3-CR d3fend
  • D3-CRO d3fend
  • D3-CTS d3fend
  • D3-DUC d3fend
  • D3-MFA d3fend
  • D3-RIC d3fend

Detected by 5

  • DET0198 attack-detection-strategy
  • 6ad91e31-53df-4826-bd27-0166171c8040 sigma
  • a61a3c56-4ce2-4351-a079-88ae4cbd2b58 sigma
  • eeb3e9e1-b685-44e4-9232-6bb701f925b5 sigma
  • eed82177-38f5-4299-8a76-098d50d225ab sigma

Tested by 3

  • 31e794c4-48fd-4a76-aca4-6587c155bc11 atomic
  • 43c3a49d-d15c-45e6-b303-f6e177e44a9a atomic
  • 788e0019-a483-45da-bcfe-96353d46820f atomic

Attack relationships

Framework references

Evidence & sources

  • ev-0001 (Cyber Attack Taxonomy) — Name, definition and Example/ID taken verbatim from the 'Cloud, container and supply chain attacks' table, line 409 of Cyber-Attack-Taxonomy.md
  • ev-0002 (MITRE Enterprise ATT&CK v19.2 (STIX 2.1)) — ATT&CK usage prevalence: 3 groups/software/campaigns reference this technique (ATT&CK enterprise v19.2)