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.
Security
18 eventsAuthentication, 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 eventsSysmon
7 eventsRich 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 eventsSystem
1 eventService, 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 eventsPowerShell
1 eventScript 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