Windows Registry: Exploit Guard ProtectedFolders Value Deleted

Alerts on deletion of registry values under Exploit Guard Controlled Folder Access ProtectedFolders.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_delete
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-05
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 registry value deletions where the TargetObject path contains the Windows Defender Exploit Guard Controlled Folder Access ProtectedFolders list. Removing entries from this list can reduce protection for selected folders, potentially enabling processes an attacker wants to run. It relies on Windows Registry delete-value events (EventType=DeleteValue) with the affected TargetObject containing the ProtectedFolders registry location.

Related detections9 linkedT1685 — drag to rearrange
Suspicious Windows Defender Exclusion of User Profile via PowerShell (via process_creation)
Malicious Vulnerable Driver Service Creation for BYOVD (via process_creation)
Malicious Microsoft Defender Disabled via Registry DisableAntiSpyware (via process_creation)
Suspicious Termination of Defender Tray Process via Taskkill
Malicious Windows Defender Disablement via MpCmdRun RemoveDefinitions
Malicious Unsigned VIB Installation on ESXi Host via esxcli (via process_creation)
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Malicious EDR Evasion Driver Load from AnyDesk Directory via k.sys (via image_load)
Malicious Zemana Vulnerable Driver Load for EDR Termination (via image_load)
Windows Registry: Exploit Guard ProtectedFolders Value Deleted
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.