This article includes a list of references, related reading, or external links, but its sources remain unclear because it lacks inline citations. Please help improve this article by introducing more precise citations. (March 2025) (Learn how and when to remove this message)

Windows Filtering Platform (WFP) is a set of system services in Windows Vista and later that allows Windows software to process and filter network traffic. Microsoft intended WFP for use by firewalls, antimalware software, and parental controls apps. Additionally, WFP is used to implement NAT and to store IPSec policy configuration.

WFP relies on Windows Vista's Next Generation TCP/IP stack. It provides features such as integrated communication and per-application processing logic. Since Windows 8 and Windows Server 2012, WFP allows filtering at the MAC layer of the second layer of the TCP/IP suite, increasing control beyond IP-level filtering.^[1] Since Windows 8 also integrated Hyper-V into the client OS, support was also added for Virtual Switch (vSwitch) Filtering.^[1]

The filtering platform includes the following components:

• Shims, which expose the internal structure of a packet as properties. Different shims exist for protocols at different layers. WFP comes with a set of shims; users can register shims for other protocols using the API. The in-built set of shims includes:
  • Application Layer Enforcement (ALE) shim
  • Transport Layer Module (TLM) shim
  • Network Layer Module (NLM) shim
  • RPC Runtime shim
  • Internet Control Message Protocol (ICMP) shim
  • Stream shim

• Filtering engine, which spans both kernel-mode and user-mode, providing basic filtering capabilities. It matches the data within a packet – as exposed by the shims – against filtering rules, and either blocks or permits the packet. A callout (see below) may implement any other action as required. The filters operate on a per-application basis. To mitigate conflicts between filters, they are given weights (priorities) and grouped into sublayers, which also have weights. Filters and callouts may be associated to providers which may be given a name and description and are essentially associated to a particular application or service.
• Base filtering engine, the module that manages the filtering engine. It accepts filtering rules and enforces the security model of the application. It also maintains statistics for the WFP and logs its state.
• Callout, a callback function exposed by a filtering driver. The filtering drivers provide filtering capabilities other than the default block/allow. Administrators specify a callout function during registration of a filter rule. When the filter matches, the system invokes the callout, which handles a specified action.

Starting with Windows 7, the netsh command can diagnose of the internal state of WFP.

Microsoft released three out-of-band hotfixes for WFP in Windows Vista and Windows 7 to address issues that could cause a memory leak, loss of connectivity during a Remote Desktop Connection session, or a blue screen of death. Later, these hotfixes were rolled up into one package.^[2]

• Kresten, Proteus Valre (May 2012). Windows Filtering Platform. VolutPress. ISBN 978-620-1-65842-4. Retrieved 25 March 2025.

• Windows Filtering Platform Architecture Overview