Security event 4946
A change has been made to Windows Firewall exception list. A rule was added
Channel: Security. Category: Audit MPSSVC Rule-Level Policy Change.
What it records
Generated when a new rule is added locally to Windows Firewall (e.g., via `netsh`, PowerShell's `New-NetFirewallRule`, or the Windows Firewall with Advanced Security console); records the affected profile(s) (Domain/Private/Public/All) plus the new rule's unique ID (GUID) and name. Does not generate when a rule is added via Group Policy.
Why it matters
Firewall rule changes are a documented defense-evasion technique (an attacker or piece of malware that opens an inbound/outbound hole enables C2 callback, lateral movement, or exfiltration the host firewall would otherwise block), so an unexpected new rule is worth correlating with process-creation and network telemetry around the same timestamp.
What triggers it
Legitimately: software installers adding firewall exceptions for their own services, or an admin opening a port for a new application. Maliciously: malware or an attacker locally adding a permissive allow rule to enable inbound access or outbound C2.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Profile Changed | Which firewall profile(s) the new rule applies to (Domain/Private/Public/All), which indicates the scope of exposure the new rule creates. |
| Rule Name | The display name of the added rule: the field to check against expected software/admin activity for an unexpected new allow rule. |
| Rule ID | The rule's GUID: use it to pivot into the FirewallRules registry key for the rule's full definition (port, program, direction) beyond what the event itself carries. |
In practice
A 4946 fired locally might show Profile Changed All and Rule Name "Allow Remote Support" with a Rule ID GUID for the newly added rule; since the event doesn't record who made the change or the rule's port/direction, an unfamiliar new All-profile allow rule appearing outside a known change window is worth pivoting into the FirewallRules registry key by that Rule ID to see exactly what it opens.
Sample record
A change has been made to Windows Firewall exception list. A rule was added.
Profile Changed: Domain
Rule ID: {7793E274-A697-4E6D-8F6E-C012BA6486DE}
Rule Name: Custom TCP Port 8080ATT&CK techniques
- T1562.004: T1562.004
Sources
Paste a record into Event XML or open a log in EVTX Reader.