5156 Security log · Filtering Platform Connection low severity very-high volume

Windows Event ID 5156 — The Windows Filtering Platform has permitted a connection

WFP permitted an outbound/inbound network connection. ProcessName, Direction, SourceAddress, DestAddress, DestPort are key.

Why event 5156 matters

C2 communication detection. Beacon traffic from unexpected processes. Data exfiltration patterns. Processes making connections to unusual ports or external IPs. High volume — focus on specific process+destination combinations.

How to detect it

Alert: ProcessName is cmd.exe, PowerShell, mshta, or other unusual processes making external connections. Alert: internal processes connecting to external IPs on unusual ports. High volume — aggregate and alert on anomalies, not individual events.

Log source
Security
Advanced Audit Policy — enable the 'Filtering Platform Connection' subcategory (Success and/or Failure).
Fields to pivot on
ApplicationSourceAddressDestAddressDestPortDirection

MITRE ATT&CK mapping

Tactic Technique
Command and Control Application Layer Protocol (T1071)

Detection queries

Starting points — adapt the log source, projected fields and thresholds for your environment.

Sigma rule
title: Suspicious Process Making External Network Connection
status: experimental
description: Unexpected process making outbound connection
author: theadminstack.com
date: 2026/05/16
logsource:
    product: windows
    service: security
detection:
    selection:
        EventID: 5156
        Direction: '%%14593'
        Application|endswith:
            - '\\cmd.exe'
            - '\\powershell.exe'
            - '\\mshta.exe'
            - '\\wscript.exe'
    condition: selection
falsepositives:
    - Legitimate admin scripts making web requests
level: medium
tags:
    - attack.command_and_control
    - attack.t1071
Sentinel / Defender KQL
SecurityEvent
| where EventID == 5156   // The Windows Filtering Platform has permitted a connection
| project TimeGenerated, Computer, Application, SourceAddress, DestAddress, DestPort, Direction
| sort by TimeGenerated desc
Splunk SPL
index=* sourcetype="WinEventLog:Security" EventCode=5156
| stats count earliest(_time) as first_seen latest(_time) as last_seen by ComputerName
| sort - count   `# The Windows Filtering Platform has permitted a connection — add EventData fields: Application, SourceAddress, DestAddress, DestPort`
Hunt event 5156 in Sentinel/Defender →
Build a KQL query for this event in the KQL Query Builder.
Search all event IDs →
Open the interactive Windows Event ID lookup.

Related Filtering Platform Connection events

5154 The Windows Filtering Platform has permitted an application to listen on a port 5155 The Windows Filtering Platform has blocked an application from listening on a port 5157 The Windows Filtering Platform has blocked a connection 5158 The Windows Filtering Platform has permitted a bind to a local port

Frequently asked questions

What is Windows Event ID 5156?

The Windows Filtering Platform has permitted a connection. WFP permitted an outbound/inbound network connection. ProcessName, Direction, SourceAddress, DestAddress, DestPort are key.

Which log records event 5156?

Event 5156 is written to the Security channel by Microsoft-Windows-Security-Auditing. Advanced Audit Policy — enable the 'Filtering Platform Connection' subcategory (Success and/or Failure).

What MITRE ATT&CK techniques map to event 5156?

Event 5156 is associated with: Application Layer Protocol (T1071).

How do you detect activity around event 5156?

Alert: ProcessName is cmd.exe, PowerShell, mshta, or other unusual processes making external connections. Alert: internal processes connecting to external IPs on unusual ports. High volume — aggregate and alert on anomalies, not individual events.