Skip to content
.ca
3 minlow

Kernel eviction notice: What wesp.sys reveals about the Windows Endpoint Security Platform

Microsoft's WESP framework moves EDR out of the Windows kernel via wesp.sys, but preview binaries show user-mode clients cannot block process creation yet. WESP uses a file system mini-filter (wesp.sys) at altitude 329500 communicating with user-mode clients via espclient.dll over a FilterCommunicationPort named \EspFilterPort. The client DLL imports FilterGetMessage and FilterSendMessage but not FilterReplyMessage, indicating one-way notification without blocking capability. EDR vendors must wait for Microsoft to add reply functionality before migrating blocking logic to user mode.

Sens:LowConf:highAnalyzed:2026-11-05Z.ai

Authors: Pavel Yosifovich

Source:Elastic Security Labs

Improve this report

Send corrections, useful missing information, or quality feedback. It is private and will not appear as a comment.

Feedback type

Detection / HunterZ.ai

Immediate Actions

  • Track WESP binary presence on Windows Insider ring hosts to prepare for migration

Key Takeaways

  • wesp.sys is a file system mini-filter at altitude 329500, dependent on FltMgr.sys
  • espclient.dll exports 120 functions with Esp prefix for rules, filters, and event queues
  • FilterReplyMessage absent from espclient.dll imports, preventing user-mode process blocking
  • WESP clients will likely need Protected Process Light signing by Microsoft
  • Driver registers via PsSetCreateProcessNotifyRoutineEx2, PsSetCreateThreadNotifyRoutineEx, PsSetLoadImageNotifyRoutineEx

Attack Chain

  1. Kernel Notifications: wesp.sys registers for process, thread, image load, registry, and file system notifications via PsSet*NotifyRoutine APIs
  2. User-Mode Communication: Notifications sent to espclient.dll clients through \EspFilterPort FilterCommunicationPort
  3. Event Filtering: Client configures rules and filters via Esp* API to drop uninteresting events at the kernel source
  4. Processing Limitation: User-mode client receives messages but cannot reply with block or allow decisions

Affected Systems

  • Windows Insider builds with WESP binaries
  • EDR vendor products targeting Windows kernel migration
  • Elastic Defend and other XDR solutions preparing for WESP

Detection Engineering Assessment

Hunting Hypotheses

copy:
HypothesisTelemetryStageFP Risk
Processes connecting to \EspFilterPort communication port indicate WESP client registration activity (T1106)Object manager handle creation eventsDefense EvasionLow — only EDR clients expected to connect
Absence of FilterReplyMessage in espclient.dll imports means process creation blocking is not functional (T1059)PE import table analysis of espclient.dllExecutionLow — deterministic binary analysis

Required Log Sources

  • Kernel debug logs
  • fltmc mini-filter listings
  • Registry service key entries
  • PE import tables
  • FilterCommunicationPort objects

Control Gaps

  • User-mode clients cannot block process creation without FilterReplyMessage
  • No documented filtering API for dropping noisy events at kernel source
  • WESP lacks WFP callout support in current preview binaries
  • No public documentation for EDR vendor integration

Recommendations

Infrastructure Hardening

  • Test EDR product compatibility with WESP in Insider preview rings before broad deployment
  • Maintain existing kernel-mode EDR drivers until WESP supports process blocking

MITRE ATT&CK Mapping

MITRE ATT&CK Mapping5 techniques