huntrule

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

Alerts when Windows event logs are cleared, based on Microsoft-Windows-Eventlog Event ID 104 from System telemetry.

FreeReviewedSigma · Medium · v2
Product
windows
Service
system
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-01-10
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 Event Log is cleared by matching Microsoft-Windows-Eventlog events with EventID 104. Clearing event logs can help attackers reduce forensic visibility and hinder incident investigation. It relies on Windows System telemetry for the EventID and Provider_Name fields and excludes specific channels already covered elsewhere, focusing on remaining event log channels.

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 (Microsoft-Windows-Eventlog EventID 104)
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.