Skip to content
StratQuad

Windows security event IDs

3 min read

The Windows event IDs that matter most in investigations and detection, grouped by what they tell you.

At a glance

Owner
StratQuad
Version
November 2026
Applies to
Windows Server and Windows client, Active Directory
Mandatory
Reference

Key points

  • Most of these events are only written if the matching advanced audit policy subcategory is enabled. Check audit policy before relying on an absence of events.
  • Security log events below are in the Security channel unless stated.
  • Logon type in 4624 and 4625 is often the most useful field: it separates interactive, network, service and remote desktop sign ins.
  • Clearing the Security log (1102) is itself logged and is a strong indicator of tampering.

Logon and authentication

Event IDMeaningNotes
4624An account successfully logged onCheck Logon Type and source address
4625An account failed to log onStatus and Sub Status codes give the reason
4634 / 4647Logoff / user initiated logoffPair with 4624 by Logon ID for session length
4648Logon attempted with explicit credentialsCommon with runas and some lateral movement
4672Special privileges assigned to new logonAdministrator equivalent sign ins
4768Kerberos ticket granting ticket requestedOn domain controllers
4769Kerberos service ticket requestedRC4 encryption (0x17) requests are worth reviewing for Kerberoasting
4771Kerberos pre authentication failedPassword spraying against Kerberos
4776Domain controller attempted to validate credentials (NTLM)NTLM authentication; logged on the computer holding the account, so local accounts appear on member hosts

Logon types (4624 and 4625)

TypeMeaning
2Interactive (at the console)
3Network (for example SMB file access)
4Batch (scheduled task)
5Service
7Unlock
8Network cleartext
9New credentials (runas /netonly)
10Remote interactive (Remote Desktop)
11Cached interactive

Accounts and groups

Event IDMeaning
4720A user account was created
4722 / 4725A user account was enabled / disabled
4723 / 4724Password change attempt / password reset attempt
4726A user account was deleted
4728 / 4732 / 4756Member added to a global / local / universal security group
4738A user account was changed
4740A user account was locked out
4767A user account was unlocked

Persistence and execution

Event IDChannelMeaning
4688SecurityA new process was created (enable command line logging to capture arguments)
4697SecurityA service was installed on the system
7045SystemA new service was installed
4698 / 4702SecurityA scheduled task was created / updated
4104Microsoft-Windows-PowerShell/OperationalPowerShell script block logging

Tampering and policy

Event IDChannelMeaning
1102SecurityThe audit log was cleared
104SystemAn event log was cleared
4719SecuritySystem audit policy was changed
4657SecurityA registry value was modified (requires auditing on the key)

Practitioner note

On endpoints with Microsoft Defender for Endpoint or Sysmon, process, network and registry telemetry from those tools is richer than 4688 and 4657. Keep the Windows events anyway: they are what remains on servers without an agent, and they are what investigators ask for first.

Sources

Suggest a correction