What to collect
- Username and account type.
- Source network address.
- Logon type.
- Authentication package or method.
- Host and timestamp.
- Related failures or successes.
Use successful and failed Windows logon events as the foundation of authentication investigations.
Event ID 4624 records a successful logon and 4625 records a failed logon. The surrounding fields and sequence matter more than the event ID alone.
Use this page after the daily quiz: learn the concept first, then follow the investigation workflow and examples.
Which log event is associated with a failed Windows logon: 4624 or 4625?
Quiz flow: introduce this topic briefly on social media, ask the question, reveal the answer, then send learners here for the detailed investigation.
Windows Security Event 4624 records a successful logon and 4625 a failed attempt, but the event fields and logon type determine how to interpret the record. Review account, source, workstation, authentication package, status/substatus, and surrounding events.
Compare a fictional 4625 burst with a later 4624 and check identity, host, and authentication context. Service activity, stale credentials, and user error are possible explanations; a success after failures deserves follow-up but is not conclusive alone.
Continue practicing: open a fictional mission and test your reasoning against the simulated evidence.