huntrule

Windows Registry Changes Disabling Windows Defender Event Log Channel

Detects registry changes that disable the Windows Defender Operational event log channel by setting its Enabled DWORD to 0.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-07-04
Updated
2026-07-30
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 flags registry updates that set the Enabled value to 0 for the Windows Defender Operational event log channel (Microsoft-Windows-Windows Defender/Operational). Disabling security event logging can reduce visibility and hinder incident detection after compromise. It relies on registry_set telemetry capturing writes to the specific WINEVT Channels path and the associated DWORD Enabled value.

Reporting behind it

Related detections9 linkedT1685 — drag to rearrange
Suspicious Vulnerable Intel Ethernet Driver Load for BYOVD via SCATTERED SPIDER (via driver_load)
Malicious Defender Disable And Executable Exclusion Via Registry
Malicious UAC Disable via EnableLUA Registry Modification (via registry_set)
Malicious AMSI and ETW Patching via PowerShell Script
Malicious PowMix AMSI Bypass via amsiInitFailed
Suspicious ThrottleStop Driver Abuse for Defense Evasion in Ransomware Attacks
Malicious Disabling of Microsoft Defender Real-Time Protection via SystemSettingsAdminFlows by DeadLock Ransomware
Suspicious Security Software Uninstallation via WMIC Product Call Uninstall (Chaos Ransomware)
Suspicious Security Product Uninstall via wmic product call uninstall
Windows Registry Changes Disabling Windows Defender Event Log Channel
Pivot detection · T1685 · 9 related

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