Windows Event Forwarding (WEF) and Collection
You'll learn how to centralize Windows event logs from multiple systems into a collector server for enterprise-wide monitoring and analysis.
The Core Idea
Windows Event Forwarding (WEF) is Microsoft's built-in solution for sending event logs from source computers to one or more central collector systems. Instead of manually checking logs on hundreds of servers, you configure machines to automatically forward critical security events to a centralized location where analysts can monitor, correlate, and respond to threats across your entire infrastructure.
Think of it like a newsroom: instead of reporters writing stories that stay in their notebooks, they send their articles (event logs) to a central editor (collector) who compiles everything into one newspaper (centralized log repository).
How WEF Works
WEF operates on a subscription model:
- Collector server: Runs the Windows Event Collector service and defines subscriptions (which events to collect from which computers)
- Source computers: Forward events matching subscription criteria using the Windows Remote Management (WinRM) protocol
- Subscriptions: Define filtering rules—what events to collect, from where, and how often
There are two delivery modes:
- Source-initiated: Computers push logs to the collector (scalable for large environments)
- Collector-initiated: Collector pulls logs from specified computers (simpler for small networks)
Configuration Workflow
Enable WinRM on source machines, configure the Event Collector service on your collector, create subscriptions specifying event criteria (like Critical Windows Security Event IDs you've learned), and apply group policy to direct sources to the collector. The forwarded events appear in the collector's "Forwarded Events" log.
Key Takeaway: Windows Event Forwarding centralizes security monitoring by automatically collecting events from distributed systems into a collector using subscriptions and WinRM, enabling enterprise-scale detection and response.