huntrule

Windows Security and Eventlog Cleared via Event IDs 517 or 1102

Flags Windows event log clearing using Security Event ID 517 and Microsoft-Windows-Eventlog Event ID 1102.

FreeReviewedSigma · High · v2
Product
windows
Service
security
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 Windows log activity where the Security log is cleared or the Eventlog service records that event logs were cleared, based on Event ID 517 from Provider "Security" or Event ID 1102 from Provider "Microsoft-Windows-Eventlog". Clearing or impairing logs can help an attacker reduce forensic visibility after suspicious activity. The detection relies on Windows Security and Eventlog telemetry capturing these specific event records, including the EventID and Provider_Name fields.

Reporting behind it

Related detections9 linkedT1685.005 — drag to rearrange
Malicious Security Event Log Disabled via wevtutil
Suspicious Event Log Clearing via Wevtutil (via process_creation)
Suspicious Mass Windows Event Log Clearing via PowerShell (via ps_script)
Malicious Event Log Clear Attempt - Wmi (via process_creation)
Malicious Event Log Clear Attempt - Command (via process_creation)
Malicious Event Log Cleared Using Diagnostics - Via PowerShell (via powershell)
Malicious Clearing of Windows Event Logs (via process_creation)
Suspicious Event Log Clearing via wevtutil During Ransomware Activity
Suspicious Event Log Clearing via Get-WinEvent ClearLog (Qilin)
Windows Security and Eventlog Cleared via Event IDs 517 or 1102
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.