Windows Vulnerable Driver Blocklist Registry Tampering via PowerShell or REG.EXE

Flags PowerShell/REG.EXE command lines that change the VulnerableDriverBlocklistEnable registry setting under \Control\CI\Config.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2026-01-26
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 process executions using PowerShell or REG.EXE where command-line activity modifies the registry configuration path \Control\CI\Config, specifically targeting the VulnerableDriverBlocklistEnable setting. Tampering with the Vulnerable Driver Blocklist can weaken Windows driver protections, potentially enabling the use of malicious or vulnerable drivers. It relies on Windows process creation telemetry including the executing image name and command-line arguments.

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 Vulnerable Driver Blocklist Registry Tampering via PowerShell or REG.EXE
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.