Kubernetes Audit: Deleted Events

Identifies Kubernetes audit log entries where the events resource is deleted via the delete verb.

FreeReviewedSigma · Medium · v5
Product
kubernetes
Category
application
Author
Leo Tsaousis (@laripping) (SigmaHQ), DRL 1.1
Published
2024-03-26
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies Kubernetes API activity where the resource type is events and the verb is delete. Deleting events can be used to reduce visibility and hinder incident investigation by removing recorded event data. It relies on Kubernetes audit logs capturing the request verb and the targeted resource reference (events).

Related detections9 linkedT1070 — drag to rearrange
Suspicious Browser History Wipe via Rundll32 ClearMyTracksByProcess (via process_creation)
USN Change Journal Deletion via Fsutil (via process_creation)
Suspicious Salesforce Query History Deletion Anti-Forensics
Suspicious Browser History Clearing via RunDll32 InetCpl ClearMyTracksByProcess (via process_creation)
Suspicious Clearing of hosts.deny Access Restrictions on Linux
Windows Process Creation: Command-Line Deletion of IIS Logs
Linux Package Removal via yum, apt, dpkg, or rpm Commands
Windows Tomcat Log File Deletion Indicating Possible Forensic Evidence Destruction
Windows Event Log EVTX File Deletion in winevt\Logs
Kubernetes Audit: Deleted Events
Pivot detection · T1070 · 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.