Windows Logon Types
Understand Windows logon types so authentication alerts can be interpreted in context.
Logon type provides context about how a Windows session was established. Analysts should use it with source, account, host and application context.
Use this page after the daily quiz: learn the concept first, then follow the investigation workflow and examples.
Investigation approach
- Identify the logon type.
- Determine the source address and workstation.
- Check whether remote access was expected.
- Compare with the user’s normal access pattern.
- Correlate with VPN, endpoint and application logs.
Example
A privileged account logging in remotely outside its normal administrative window deserves more scrutiny than a routine scheduled service account event. The analyst should validate the change with authorized administrators and supporting telemetry.Common mistakes
- Treating one logon type as automatically malicious.
- Ignoring service and automation accounts.
- Skipping asset and user context.
Daily quiz hook
Why is logon type useful during a suspicious authentication investigation?
Quiz flow: introduce this topic briefly on social media, ask the question, reveal the answer, then send learners here for the detailed investigation.
Analyst practice note
Windows logon types describe how a session was created, not whether it was malicious. Interpret the type alongside account, source host, authentication protocol, time, and expected service or task behavior.
Compare the same account’s ordinary and unusual sessions in the synthetic timeline. Background services and scheduled tasks can produce noninteractive logons; investigate the sequence and resulting activity before making an attribution.
Continue practicing: open a fictional mission and test your reasoning against the simulated evidence.
