When you log into a Windows domain, one of two protocols proves who you are — modern Kerberos or legacy NTLM. Understanding both is essential for support and security roles alike.
Kerberos — ticket-based authentication
Kerberos Authentication
How Windows proves who you are without sending your password.
Tap or hover a part to learn more.
Prove who you are.
At logon the client sends an Authentication Service Request to the Key Distribution Center (KDC) on a Domain Controller, encrypting a timestamp with a key derived from the user's password. The KDC verifies it — the password itself never crosses the network.
Check your understanding
1. What does the KDC issue after a successful logon?
2. Why must clocks be accurate for Kerberos?
Keep learning
Kerberos never sends your password over the network. Instead the Key Distribution Center issues a Ticket-Granting Ticket (TGT), which you exchange for per-service tickets. Because tickets are time-stamped, accurate clocks (within ~5 minutes) are essential — clock skew is a classic cause of logon failure.
NTLM — the legacy fallback
NTLM Authentication
The legacy challenge-response protocol — and why it's risky.
Tap or hover a part to learn more.
Client asks to authenticate.
NTLM is Microsoft's older challenge-response protocol, used when Kerberos can't be (e.g. connecting by IP address, workgroup machines, or legacy apps). The client tells the server it wants to authenticate with NTLM.
Check your understanding
1. What attack is NTLM particularly vulnerable to?
2. When is NTLM typically used instead of Kerberos?
Keep learning
NTLM is a challenge-response protocol used when Kerberos can't be — connecting by IP address, workgroup machines or legacy apps. It has no mutual authentication and is vulnerable to pass-the-hash attacks, so prefer Kerberos and disable NTLMv1.
Why it matters
Authentication issues are among the most common help-desk tickets, and understanding Kerberos vs NTLM is a favourite Security+ interview topic. It builds directly on Active Directory.
