Kubernetes audit log signals potential tool and shell enumeration/execution activity

Finds allowed Kubernetes API audit requests with URI-encoded/visible shells or recon tool user agents that may indicate enumeration or secret scanning.

FreeReviewedSigma · Medium · v5
Product
kubernetes
Service
audit
Author
uniqu3-us3r (SigmaHQ), DRL 1.1
Published
2026-04-28
Updated
2026-07-31

ATT&CK techniques

Execution → Discovery
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags Kubernetes API audit events that are allowed and whose request URI contains references to common shells and CLI utilities, or encoded tool paths. It also matches user agents indicative of reconnaissance or secret/scanning tools such as access_matrix (Rakkess) and trufflehog. Attackers often use these requests to enumerate cluster capabilities, harvest secrets, or invoke exec-like workflows, and the detection relies on Kubernetes audit telemetry including response status code, requestURI, and userAgent.

Related detections9 linkedT1613 — drag to rearrange
Malicious Ingress-nginx Configuration Injection via Kubernetes Audit (via kubernetes)
Suspicious Container Image Export via ctr in Cloud Model Exfiltration
Suspicious Kubernetes Enumeration via kubectl in Cloud Compromise
Suspicious Kubernetes Permission Enumeration via kubectl auth can-i
Suspicious Direct etcd Database Access via etcdctl With Server Certificates (via process_creation)
Suspicious Kubernetes SelfSubjectAccessReview Permission Enumeration
Malicious Kubernetes Reconnaissance Tooling Activity
Suspicious Container Environment Reconnaissance in Serverless Build
Suspicious Command Execution Inside a Kubernetes Pod (via audit)
Kubernetes audit log signals potential tool and shell enumeration/execution activity
Pivot detection · T1613 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

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