expert

WFP & BFE (deep dive)

How filters are stored, enforced, and hooked into the packet path.

What you should already know

This topic is marked expert. Skim these first if any of them feel unfamiliar.

Related labs

Hands-on exercises for this area — in the browser or on a Windows machine.

View all labs

Guided paths in this branch

Follow a short sequence step by step. Each path links to the first topic; use Read next on each page to continue.

Official Microsoft docs

Closest official references related to this topic on Microsoft Learn.

Why it matters

Modern Windows firewalls and endpoint security build on WFP. Understanding BFE explains persistent policies, boot-time filtering, and callout registration.

Mental model

WFP is a set of layers + a filter engine; BFE is the user-mode service that coordinates configuration, storage, and security of that filtering system.

How it works

  1. 1Kernel shims hand packets/streams to the filter engine at specific layers.
  2. 2Filters are matched and actions are chosen; callouts can run for deep inspection/modification.
  3. 3BFE manages filter objects (persistent/dynamic/boot-time) and plumbs configuration to kernel components.

Key terms

BFE
Base Filtering Engine service coordinating WFP configuration and security.
Layer
A WFP classification point in the networking stack.
Filter
A rule attached to a layer, possibly invoking callouts or permitting/blocking.

Why some filtering works before logon

WFP supports boot-time filtering in kernel mode until BFE starts and persistent policy is fully plumbed.

Common misconception

People assume firewall rules are only user-mode settings. They are enforced in the kernel packet path via WFP layers and callouts.

You should read next

Ranked from your current topic, related links, branch depth, and any active guided path.

Related topics