huntrule

Windows Event Log Cleared (EventID 104, Microsoft-Windows-Eventlog)

Alerts when Microsoft-Windows-Eventlog reports Event ID 104 for core event log channels, indicating log clearing.

FreeReviewedSigma · High · v2
Product
windows
Service
system
Author
Florian Roth (Nextron Systems), Tim Shelton, Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-05-17
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

  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 when a Windows Core Event Log is cleared by matching EventID 104 from the Microsoft-Windows-Eventlog provider. Clearing event logs can help an attacker reduce visibility by removing forensic evidence and weakening detection opportunities. It relies on System logs capturing EventID 104, including the affected Channel information (e.g., Security, System, PowerShell operational logs).

Reporting behind it

Related detections9 linkedT1685.005 — drag to rearrange
Suspicious Windows Event Log Clearing via wevtutil (via process_creation)
Malicious USN Change Journal Deletion via Fsutil for Anti-Forensics
Suspicious Windows Event Log Clearing via wevtutil
Suspicious Windows Event Log Cleared via wevtutil during Ransomware Staging (via process_creation)
Suspicious Deletion of Terminal Server Client History via reg by UNC1549
Suspicious Windows Event Log Clearing via process_creation
Malicious Windows Event Log Clearing via wevtutil
Suspicious Event Log Clearing via Renamed Log Utility
Suspicious Event Log Clearing via PowerShell Invoke-Expression
Windows Event Log Cleared (EventID 104, Microsoft-Windows-Eventlog)
Pivot detection · T1685.005 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.