Windows Registry Event Log Tampering by Disabling WINEVT Channel Enabled Key

Flags registry changes that set WINEVT channel Enabled to 0x00000000 to disable Windows event logging.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
frack113, Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-07-04
Updated
2026-07-30

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 registry modifications where a WINEVT channel’s Enabled value is set to DWORD 0x00000000, effectively disabling event logging for a specific Windows event channel. Attackers may use this to evade detection by reducing the availability of audit and telemetry from targeted event sources. It relies on registry_set telemetry capturing the TargetObject path under WINEVT\Channels and the value Details indicating the Enabled key was disabled, with exclusions for common system processes that can legitimately touch these paths.

Related detections9 linkedT1685.001 — drag to rearrange
Malicious Security Event Log Disabled via wevtutil
Malicious SQL Server Auditing Deactivated (via application)
Malicious Event Log Deactivation or Size Reduction - Command (via process_creation)
Malicious Audit Policy Disabled by Command Line (via process_creation)
Suspicious IIS Logging Disabled via appcmd
Malicious SQL Server Database Auditing Deactivated (via application)
Malicious Audit Policy Disabled by Command Line (via security)
Malicious Event Log Tampering via wevtutil Channel Disable by FunkSec Ransomware (via process_creation)
OCSP Responder Auditing Settings Changed or Disabled (via security)
Windows Registry Event Log Tampering by Disabling WINEVT Channel Enabled Key
Pivot detection · T1685.001 · 9 related

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