Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Kerberos Authentication?

Kerberos authenticates users to services using time-limited tickets issued by a trusted third party, so passwords never travel to the service being accessed.

Illustration for the cybersecurity term Kerberos Authentication
Home / Blog / Cybersecurity Terms / What Is Kerberos Authentication?
17 November 2026

What Is Kerberos Authentication?

What Is Kerberos Authentication?

Kerberos was designed at MIT in the 1980s to solve a problem that still exists: how do you prove who you are to a hundred different services without giving each of them your password? The answer was a trusted third party that issues time-limited tickets, and that design—version 5, specified in RFC 4120—is what authenticates almost every logon in a Windows domain today.

The Three-Headed Arrangement

The Key Distribution Centre is the trusted party, and in Active Directory every domain controller runs one. It has two halves. The Authentication Service issues a ticket-granting ticket when you first log on. The Ticket-Granting Service issues service tickets for individual resources, using the TGT as proof that the Authentication Service already vouched for you.

Everything rests on shared secrets that only the KDC and one other party know. Your account’s key is derived from your password. Each service’s key is derived from the password of the account the service runs as. A special account called KRBTGT holds the key that encrypts every ticket-granting ticket in the domain, which is why its compromise is catastrophic.

What Happens When You Log On

  1. AS-REQ. The client sends a request identifying the user, with pre-authentication data: a timestamp encrypted using the key derived from the password. This proves knowledge of the password without sending it.
  2. AS-REP. The KDC decrypts the timestamp, checks it is recent, and returns a ticket-granting ticket encrypted with the KRBTGT key, plus a session key encrypted with the user’s key.
  3. TGS-REQ. To reach a file server, the client presents the TGT and names the service by its service principal name.
  4. TGS-REP. The KDC returns a service ticket encrypted with the service account’s key.
  5. AP-REQ. The client presents the service ticket to the file server, which decrypts it with its own key and learns who the user is—without ever contacting the KDC.

That last point is the elegance and the weakness. The service trusts the ticket because it decrypts correctly. It does not call anyone to check.

Why the Clock Matters

Kerberos uses timestamps to prevent replay, and the default tolerance in Active Directory is five minutes. A machine whose clock drifts beyond that stops authenticating entirely, with errors that look nothing like a time problem. This is why domain members synchronise time from the domain controller hierarchy, and why a failed time source is an outage rather than an inconvenience. It is also the first thing to check when a newly built server cannot join or authenticate.

The Attacks It Attracts

Hardening a Domain’s Kerberos

Remove the weak encryption first. RC4 and DES ticket encryption make offline cracking far cheaper than AES, so audit which accounts still negotiate RC4 and move them to AES-only once you have confirmed nothing legacy depends on it. Give service accounts long random passwords, or better, replace them with Group Managed Service Accounts where the operating system rotates a 240-character password automatically—this removes Kerberoasting as a practical concern for those accounts.

Then address delegation. Audit every computer and account trusted for delegation, eliminate unconstrained delegation entirely, and mark sensitive accounts as not delegatable or add them to the Protected Users group. Enable Kerberos armouring to protect the pre-authentication exchange, and review ticket lifetimes so that stolen tickets expire usefully quickly.

For detection, the highest-value signals are service ticket requests with RC4 encryption from unusual accounts, a single account requesting tickets for many services in quick succession, and tickets presenting lifetimes that do not match domain policy—a strong indicator of forgery. These sit naturally in Active Directory security monitoring rather than in a separate programme.

At Privia Security, we test domain authentication paths end to end through our infrastructure security testing services.

FAQ – Frequently Asked Questions

Why Does Kerberos Break When Clocks Drift?

Timestamps are how Kerberos prevents replay of captured messages, so the KDC rejects requests whose timestamp falls outside a tolerance window. Active Directory defaults to five minutes. A machine whose clock drifts further simply stops authenticating, usually with errors that give no hint about time, which is why checking time synchronisation is the first diagnostic step for odd authentication failures.

What Is the KRBTGT Account?

It is the special domain account whose key encrypts every ticket-granting ticket issued by the KDC. Anyone holding its password hash can forge a ticket for any user in the domain, including accounts that do not exist, which is a golden ticket attack. Recovery after compromise requires resetting the KRBTGT password twice, allowing replication to complete between the two resets.

Is Kerberos More Secure Than NTLM?

Yes, substantially. Kerberos provides mutual authentication, uses time-limited tickets rather than a reusable challenge-response, and never sends the password to the service. NTLM is vulnerable to relay and pass-the-hash techniques that Kerberos avoids. The practical issue is that many environments still permit NTLM as a fallback, which lets an attacker force the weaker protocol.

How Do I Stop Kerberoasting?

Remove the conditions it depends on. Replace service accounts that have service principal names with Group Managed Service Accounts, where Windows generates and rotates a very long random password automatically. Where that is not possible, set passwords of at least 25 random characters. Disable RC4 ticket encryption so that cracking is far more expensive, and alert on bulk service ticket requests.

Related Terms

You May Be Interested In These

What Is a Pod Security Context?

Cybersecurity Terms

17 November 2026

What Is a Pod Security Context?

Read More
What Are Reputation Feeds?

Cybersecurity Terms

17 November 2026

What Are Reputation Feeds?

Read More
What Is Smart Grid Security?

Cybersecurity Terms

17 November 2026

What Is Smart Grid Security?

Read More