Windows ETW Trace Evasion via Clearing/Disabling Logs or Providers

Identifies command-line attempts to clear/disable ETW traces or remove/modify ETW providers on Windows.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
@neu5ron, Florian Roth (Nextron Systems), Jonhnathan Ribeiro, oscd.community (SigmaHQ), DRL 1.1
Published
2019-03-22
Updated
2026-07-30

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 flags Windows process creation commands attempting to clear or disable ETW trace logs, as well as remove or modify ETW trace providers. Such actions can reduce or impair forensic visibility and are commonly used as defense-impairment and stealth techniques. It relies on process creation telemetry with command-line fields matching indicative wevtutil-style parameters, logman trace updates, and PowerShell ETW provider cmdlets.

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
Kubernetes Audit: Deleted Events
Linux Package Removal via yum, apt, dpkg, or rpm Commands
Windows Tomcat Log File Deletion Indicating Possible Forensic Evidence Destruction
Windows ETW Trace Evasion via Clearing/Disabling Logs or Providers
Pivot detection · T1070 · 9 related

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