Skip to content

Windows Log Channels and Providers

Browse Windows event IDs by log channel and provider: the Security audit log, Sysmon, the System log and PowerShell operational logging.

18 events

Authentication, authorization and account-management auditing

The Security log holds Windows audit events: logons and logoffs, privilege use, account and group changes, Kerberos and NTLM authentication, object access and the audit log's own integrity. It is the primary source for logon forensics and account-abuse detection, and most of its events are governed by the Advanced Audit Policy.

View events
7 events

Rich endpoint telemetry for threat hunting

System Monitor (Sysmon) is a configurable logging driver and service that records process creation, network connections, image loads, file and registry changes, and more — each correlated by a per-process GUID. It adds the fields the native Windows logs leave out, which makes it the backbone of endpoint detection and hunting.

View events
1 event

Service, driver and operating-system events

The System log records operating-system and service-control activity: service and driver installation, service state changes, and startup and shutdown. Several of its events are logged by default, which makes them reliable persistence and lateral-movement artifacts even where audit policy is sparse.

View events
1 event

Script block and module logging

PowerShell's operational log captures what scripts and commands actually ran: script block logging records the deobfuscated code, and module logging records pipeline activity. Together they turn PowerShell — a favourite of attackers — into one of the most useful detection sources on a host.

View events