DFIR · Beginner
Introduction to Windows Security Event Analysis
Learn to correlate authentication and process events when investigating Windows security incidents.
Updated 2026-10-17
On this page
Important event IDs
- 4624: Successful logon
- 4625: Failed logon
- 4688: Process creation (requires the appropriate auditing policy)
- 4769: Kerberos service ticket request
Whether an event is recorded depends on the system’s audit policy. Avoid drawing conclusions from a single event without corroborating evidence.
Linux authentication investigation
SSH, PAM and sudo logs with an offline timeline
Verify Windows Event Forwarding Delivery
Distinguish source, subscription, collector and SIEM gaps
Investigate Windows Security Group Changes
Compare membership, logon and resource evidence without joining unrelated hosts
Distinguish Share Checks from NTFS File Evidence
Use eight synthetic cases to distinguish the share check from the access right used.
Investigate Windows App Control Events
Distinguish audit decisions, enforced blocks and related signature records.
Investigate missing Windows events
Windows Security log gaps · Distinguish clearing, retention, policy changes and delivery gaps.
Related articles
Backup Restore Verification · From Saved Copy to Recoverable Service
Use a real offline SQLite restore exercise to distinguish a matching hash, a usable database, an acceptable recovery point, and a service ready to resume.
Velociraptor Endpoint Collection: From a Network Alert to Host Evidence
Scope a request to one endpoint and interpret collection coverage, zero results, missing files and SIEM delivery using nine fictional cases.