Maintaining security visibility across modern enterprise endpoints requires timely aggregation of critical security audit logs—including failed logon attempts, privilege escalations, and process creations. Windows Event Forwarding (WEF) provides a native, agentless architecture built directly into Windows 11 that forwards event telemetry from source workstations to central collector servers via Windows Remote Management (WinRM). Configuring subscriptions via PowerShell automates pipeline deployment without requiring third-party telemetry agents.
Understanding Windows Event Forwarding Architecture
WEF operates through a client-pull or collector-initiated subscription model:
- Source Computers: Client workstations (Windows 11 endpoints) that generate Windows Event Logs (such as
Security,System, orMicrosoft-Windows-Sysmon/Operational). - Collector Server: The central server configured to host event subscriptions and store forwarded records inside its
Forwarded Eventslog repository. - WinRM & Kerberos Transport: Event payloads travel across port 5985 (HTTP) or 5986 (HTTPS) encrypted using native Kerberos authentication within domain environments.
Configuring WinRM and the Windows Event Collector Service
Before creating subscriptions, enable required services on the collector workstation using an elevated PowerShell console:
# Enable Windows Remote Management service
winrm quickconfig -quiet
# Configure Windows Event Collector service for automatic launch
wecutil qc /q
# Verify Windows Event Collector status
Get-Service -Name Wecsvc | Select-Object Name, Status, StartType
This automated sequence configures Windows firewall exceptions for WinRM and initializes the Windows Event Collector (Wecsvc) background service.
Granting Network Service Log Permissions on Endpoints
For client workstations to forward security event logs successfully, the local Network Service account must possess read permissions on the Security log channel:
# Add Network Service to Event Log Readers local security group
$group = "Event Log Readers"
$account = "NT AUTHORITY\Network Service"
Add-LocalGroupMember -Group $group -Member $account
Creating and Deploying WEF Subscriptions
Subscriptions can be defined using structured XML configuration files and registered with wecutil:
- Author an XML subscription document specifying event IDs (such as Process Creation Event ID 4688 or Account Lockout Event ID 4740).
- Import the subscription into the collector:
wecutil cs "C:\Deploy\SecuritySubscription.xml" - Verify subscription health and active client connection count using:
wecutil gr "SecuritySubscription"
Implementing native Windows Event Forwarding delivers robust, tamper-evident telemetry pipelines across corporate Windows 11 estates.