Windows PowerShell sets Microsoft Defender threat severity default actions to Allow/NoAction

Alerts when PowerShell Set-MpPreference sets Defender threat-severity default actions to Allow or NoAction.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Matt Anderson (Huntress) (SigmaHQ), DRL 1.1
Published
2025-07-11
Updated
2026-07-31

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 process creation events where PowerShell runs Set-MpPreference to change Microsoft Defender threat severity default actions to Allow (including value 6) or NoAction (including value 9). Such configuration changes can reduce Defender’s ability to automatically mitigate threats for specified severity levels. The detection relies on command-line telemetry that includes Set-MpPreference and the relevant default-action parameters and values.

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 PowerShell sets Microsoft Defender threat severity default actions to Allow/NoAction
Pivot detection · T1685 · 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.