Windows Security 5156 — Filtering Platform connection permitted

Source and collection

Windows Event Log: Security; archived .evtx is binary, while this fixture is an XML event export.

Configure Audit Filtering Platform Connection. Read with Get-WinEvent and preserve provider, event ID, version, computer and record ID.

Native example and provenance

publisher documentation example. Published example; no independent capture provenance claimed.

Original publisher / pinned upstream fixture — preformatted example 1

Removed Event Viewer tree expansion markers before XML tags; field values unchanged.

Download the exact sample · Offline research kit

SHA-256: 369d43181bb8c75cccacf8b564c7150d8210747c445db0b7c4ff84b4d3333361

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
 <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" /> 
 <EventID>5156</EventID> 
 <Version>1</Version> 
 <Level>0</Level> 
 <Task>12810</Task> 
 <Opcode>0</Opcode> 
 <Keywords>0x8020000000000000</Keywords> 
 <TimeCreated SystemTime="2015-09-22T05:24:22.622090200Z" /> 
 <EventRecordID>308129</EventRecordID> 
 <Correlation /> 
 <Execution ProcessID="4" ThreadID="3712" /> 
 <Channel>Security</Channel> 
 <Computer>DC01.contoso.local</Computer> 
 <Security /> 
 </System>
<EventData>
 <Data Name="ProcessID">4556</Data> 
 <Data Name="Application">\\device\\harddiskvolume2\\documents\\listener.exe</Data> 
 <Data Name="Direction">%%14592</Data> 
 <Data Name="SourceAddress">10.0.0.10</Data> 
 <Data Name="SourcePort">3333</Data> 
 <Data Name="DestAddress">10.0.0.100</Data> 
 <Data Name="DestPort">49278</Data> 
 <Data Name="Protocol">6</Data> 
 <Data Name="FilterRTID">70201</Data> 
 <Data Name="LayerName">%%14610</Data> 
 <Data Name="LayerRTID">44</Data> 
 <Data Name="RemoteUserID">S-1-0-0</Data> 
 <Data Name="RemoteMachineID">S-1-0-0</Data> 
 </EventData>
 </Event>

Structure and field interpretation

System/EventID

Event identifier within the named provider.

System/Version

Version of this event layout.

System/TimeCreated/@SystemTime

Event timestamp in UTC.

EventData

Named fields; use names, not positional array indices.

Relevant fields

Application, Direction, SourceAddress, DestAddress, Protocol

Investigation uses

• Correlate process/application, direction and five-tuple with endpoint and network evidence.
• Compare event time with ingestion time and retain the original XML for a reviewable evidence trail.

Validation boundaries

Permit is a filtering decision, not proof of a completed application exchange; collection can be high volume. This sample uses event version 1.

This sample passed byte-integrity and JSON/XML parsing checks, including the catalogue’s specified event discriminators. This is not a complete vendor-schema validation or a tested detection.

For a simulation, first parse this fixture offline, then create a separately labelled synthetic variant and test it against the intended collector in an isolated lab. Never replay public example identities or destinations into production.

Related sources

• Windows Security 4624 — Successful logon
• Windows Security 4625 — Failed logon
• Windows Security 4688 — Process creation
• Windows Security 4698 — Scheduled task created
• Windows Security 4720 — User account created
• Windows Security 4732 — Member added to local security group

Ecosystem connections

• Telemetry Library — ATT&CK data components
• Detection Rules — candidate detection content
• Threat hunting — from intelligence to validated defense
• Practical security learning paths
• AdversaryGraph — evidence-led investigation

References

• 5156(S) The Windows Filtering Platform has permitted a connection. - Windows 10 | Microsoft Learn

Sample provenance is linked above. Field availability and product behavior must be checked against the deployed version.