Windows Etw Base

Windows Base ETW Model #

This model is designed to follow ETW event sources.

ETW events are provided by various ETW Providers in the Windows Kernel. These events can provide security critical information which can be detected using Sigma Rules.

This is a real time monitoring profile which allows live monitoring of Windows systems using Sigma rules.

Log Sources #

Following is a list of recognized log sources.

Log SourceDesc
etw/windows/kernelEvents from the `NT Kernel Logger` provider
etw/windows/fileLog source based on the `Microsoft-Windows-Kernel-File` provider.
etw/windows/registryLog source based on the `Microsoft-Windows-Kernel-Registry` provider.
etw/windows/processLog source based on the `Microsoft-Windows-Kernel-Registry` provider
etw/windows/sysmonLog source to read Sysmon events via ETW
etw/windows/etwLog source to monitor ETW system states
etw/windows/wmiLog source to monitor WMI activity
etw/windows/dnsLog source to monitor DNS Lookups

Field Mappings #

The following field mappings can be used to access fields within the event. Note that it is also possible to access the fields directly (e.g. EventData.AccessMask)

View all Field Mappings

etw/windows/kernel #

Events from the NT Kernel Logger provider

The NT Kernel Logger ETW source is a special purpose ETW provider that reports details about network/registry and file.

This provider enriches events with process information from the process tracker.

This provider is special: Enabling this provider implicitly triggers many other ETW providers such as File, Process, Registry and Network monitoring. Velociraptor’s ETW subsystem recognizes the Kernel Logger provider automatically and performs additional processing:

  • Resolves full files paths from kernel space (uses device notation) to regular filesystem paths (e.g. C:\Windows).

  • Collects rundown events to determine the initial system state. This allows Velociraptor to resolve file and registry paths from events that refer to kernel object addresses.

For these reasons it is preferable to use this provider over the Microsoft-Windows-Kernel-File or Microsoft-Windows-Kernel-Registry providers.

Details

etw/windows/file #

Log source based on the Microsoft-Windows-Kernel-File provider.

See etw/windows/kernel for a better ETW provider.

Details

etw/windows/registry #

Log source based on the Microsoft-Windows-Kernel-Registry provider.

See etw/windows/kernel for a better ETW provider.

Details

etw/windows/process #

Log source based on the Microsoft-Windows-Kernel-Registry provider

See etw/windows/kernel for a better ETW provider.

Details

etw/windows/sysmon #

Log source to read Sysmon events via ETW

This is better than reading the log files since it does not use the event log service.

Details

etw/windows/etw #

Log source to monitor ETW system states

Details

etw/windows/wmi #

Log source to monitor WMI activity

Details

etw/windows/dns #

Log source to monitor DNS Lookups

See full description here

Details