Windows Registry: Tamper Protection Disabled in Microsoft Defender Features

Flags registry changes that set Microsoft Defender Tamper Protection to disabled (DWORD 0x0), excluding expected MsMpEng update activity.

FreeReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2021-08-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 changes to the registry value controlling Microsoft Defender Tamper Protection by matching the TamperProtection feature key and a DWORD value of 0x00000000. Disabling Tamper Protection can weaken host protections and may allow malicious security settings to persist or be modified. The detection relies on registry-set telemetry capturing the targeted key path and the associated DWORD value, with exclusions for MsMpEng.exe scenarios that occur during updates.

Related detections9 linkedT1685 — drag to rearrange
Suspicious WMI Query Against Windows Defender Namespace via wmic (via process_creation)
Malicious Microsoft Defender Tampering via PowerShell Preference Cmdlets
Suspicious Windows Defender Exclusion via Add-MpPreference (via process_creation)
Malicious Windows Defender Service Tampering via PowerShell (via process_creation)
Windows Defender Disabled via DisableAntiSpyware Registry Key
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
Windows Registry: Tamper Protection Disabled in Microsoft Defender Features
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.