Security event 4947
A change has been made to Windows Firewall exception list. A rule was modified
Channel: Security. Category: Audit MPSSVC Rule-Level Policy Change.
What it records
Generated when an existing local Windows Firewall rule is modified. Records the affected profile(s) and the modified rule's unique ID (GUID) and name. Does not generate when a rule is modified via Group Policy.
Why it matters
Modifying an existing rule (for example, loosening its action from Block to Allow, or widening its scope) is functionally equivalent to adding a new hole but can be stealthier, since it reuses a rule an analyst might assume is already benign. Worth reviewing alongside 4946/4948 whenever unexpected network behavior is observed.
What triggers it
Legitimately: an admin or installer updating an existing rule's ports, program path, or profile scope. Maliciously: an attacker altering a rule's action or scope to permit traffic that was previously blocked.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Profile Changed | Which firewall profile(s) the modified rule applies to, which indicates the scope of the change. |
| Rule Name | The display name of the modified rule. Check whether a previously-restrictive rule was loosened. |
| Rule ID | The rule's GUID: pivot into the FirewallRules registry key to see exactly what changed, since the event itself doesn't record before/after values. |
In practice
A 4947 showing Profile Changed Public and Rule Name "Remote Desktop - User Mode (TCP-In)" with its Rule ID indicates that built-in RDP rule was modified; because the event carries no before/after values, the analyst pulls the FirewallRules registry entry for that Rule ID to check whether the action was loosened from Block to Allow, correlating the timestamp against any new inbound RDP sessions on the host.
Sample record
A change has been made to Windows Firewall exception list. A rule was modified.
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.