Critical Windows Security Event IDs
What you'll learn: You'll discover the most important Windows event IDs that signal security-relevant activities like logins, privilege changes, and policy modifications.
Understanding Security Event IDs
Windows logs thousands of events, but a focused set of Event IDs act as security tripwires — they reveal critical actions that attackers perform or legitimate changes administrators make. Knowing these IDs lets you build effective monitoring rules without drowning in noise.
Think of Event IDs like alarm codes in a building: not every sensor matters equally. Fire alarms (critical logins) deserve instant attention; door sensors (routine events) can wait.
Key Event IDs by Category
Authentication Events
- 4624: Successful logon (check logon type: 3=network, 10=remote desktop)
- 4625: Failed logon attempt (watch for brute-force patterns)
- 4634/4647: Logoff events
- 4648: Logon using explicit credentials (RunAs or credential theft indicator)
Privilege Use
- 4672: Special privileges assigned to new logon (Administrator-level access)
- 4673: Sensitive privilege use attempted
- 4674: Operation attempted on privileged object
Account Management
- 4720: User account created
- 4722/4723: Account enabled / password reset
- 4732/4733: User added/removed from security-enabled group
- 4738: User account changed (password policy, permissions)
Policy Changes
- 4719: System audit policy changed (attackers may disable logging)
- 4739: Domain policy changed
- 4657: Registry value modified (monitor sensitive keys)
Monitoring Strategy
Prioritize monitoring failed logins (4625) followed by successful privileged logins (4624 Type 10 + 4672). Account creation (4720) and group membership changes (4732) should trigger alerts in production environments.
Key Takeaway: Monitoring specific Event IDs like 4624, 4625, 4672, 4720, and 4719 provides focused visibility into authentication, privilege escalation, account manipulation, and policy tampering — the core actions in most security incidents.