Windows Process Creation: PowerShell or sc.exe Disabling Windows Defender Behavior Monitoring

Detects PowerShell flags or sc.exe service actions that disable WinDefend monitoring on Windows.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
ok @securonix invrep-de, oscd.community, frack113 (SigmaHQ), DRL 1.1
Published
2020-10-12
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 flags process executions on Windows where PowerShell is used to disable Windows Defender behavior and runtime monitoring. It also detects use of sc.exe to stop, delete, or reconfigure the WinDefend service to start in a disabled state. Disabling these protections is a common attacker step to reduce detection and persistence by weakening endpoint security monitoring. The detection relies on process creation telemetry including the executable path/name and command-line arguments.

Related detections9 linkedT1685 — drag to rearrange
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
Malicious PowMix AMSI Bypass via amsiInitFailed
Windows Process Creation: PowerShell or sc.exe Disabling Windows Defender Behavior Monitoring
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.