Windows Firewall Exception List Rule Deletion via Windows Event 2006/2052

Flags deletion of Windows Defender Firewall exception rules using EventID 2006 or 2052 with modifying application context.

FreeReviewedSigma · Medium · v4
Product
windows
Service
firewall-as
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-02-19
Updated
2026-10-21

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 Windows Defender Firewall exception list changes where firewall rules are deleted, using event IDs 2006 and 2052. Removing exception list rules can impair defensive connectivity and may be used to hinder or revert prior access allowances. The detection relies on Windows firewall auditing telemetry that records the deleting process via ModifyingApplication and the ModifyingUser context, while filtering common system and installer-related actors to reduce false positives.

Related detections9 linkedT1686.003 — drag to rearrange
Windows Registry: AuthorizedApplications List Enabled Firewall Exceptions
Windows Registry Modification: Re-enable Microsoft Defender Firewall Exceptions (DoNotAllowExceptions=0)
Windows Firewall Allow Rule Added via WmiPrvSE.exe
Windows Firewall Exception Rule Added for Application in Suspicious Path
Windows Firewall Rules Deleted (Windows Defender Firewall) via Firewall-as Events
Windows Registry: Disable Firewall via EnableFirewall DWORD Policies
Windows Firewall rule deleted via netsh.exe command line
Windows Firewall Settings Change Events (Windows Firewall/Defender Firewall-AS)
Windows Defender Firewall Reset to Default Configuration (Firewall-as Service)
Windows Firewall Exception List Rule Deletion via Windows Event 2006/2052
Pivot detection · T1686.003 · 9 related

Changelog

v4
  1. v4
    Candidate ingested via manual entry.2026-10-21
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. 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.