Suspicious Anonymous Access to Kubernetes API Server via Audit Log

PremiumReviewedSigma · High · v1
Product
kubernetes
Service
audit
Author
HuntRule
Published
2026-06-16
Updated
2026-08-28

ATT&CK techniques

Discovery
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects Kubernetes API server requests authenticated as system:anonymous or belonging to the system:unauthenticated group. Adversaries query an unauthenticated API server to enumerate pods, secrets, and other cluster resources for reconnaissance and initial access. Anonymous access to the control plane indicates a misconfigured cluster exposed to untrusted callers.

Related detections9 linkedT1613 — drag to rearrange
Suspicious Azure OpenAI Model Enumeration and Deployment Creation (via azure)
Suspicious Container Image Export via ctr in Cloud Model Exfiltration
Suspicious Kubernetes Enumeration via kubectl in Cloud Compromise
Malicious AzureHound Cloud Reconnaissance via User Agent (via azure)
Suspicious S3 Access from Desktop File Transfer Clients by Bling Libra
Suspicious Kubernetes Permission Enumeration via kubectl auth can-i
Suspicious Kubernetes SelfSubjectAccessReview Permission Enumeration
Malicious Kubernetes Reconnaissance Tooling Activity
Suspicious Container Environment Reconnaissance in Serverless Build
Suspicious Anonymous Access to Kubernetes API Server via Audit Log
Pivot detection · T1613 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.