> For the complete documentation index, see [llms.txt](https://tt0-13.gitbook.io/overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tt0-13.gitbook.io/overview/kerberos-overview.md).

# Kerberos Overview

In this section, we explain how Kerberos operates during authentication, service access, and delegation within Active Directory environments.

## Tickets

**Kerberos** relies on **tickets** to prove identity and authorize access to services without repeatedly sending user credentials over the network.

Instead of passwords, Kerberos uses cryptographically protected tickets issued by the **Key Distribution Center (KDC)**.

<figure><img src="https://2000946950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVLHdKTDYsllKhzWHEKHj%2Fuploads%2Fy6I4wb5by0dQPTvr6sc4%2Fimage.png?alt=media&amp;token=235ceb6b-24b1-41e3-a975-ff11b73d7d35" alt="" width="563"><figcaption></figcaption></figure>

There are two primary ticket types in Kerberos:

* **Ticket Granting Ticket (TGT)**
* **Service Ticket (TGS)**

Understanding how these tickets are created, encrypted, and validated is critical, as most Kerberos abuse techniques directly target weaknesses in ticket handling.

The **krbtgt** account is a special, built-in Active Directory account used by the KDC to **encrypt and sign Ticket Granting Tickets (TGTs)**. When a user or service authenticates, the KDC issues a TGT encrypted with the **krbtgt account’s secret key**, allowing the KDC to later validate the ticket without rechecking the user’s credentials. Compromise of the krbtgt account enables attackers to forge valid TGTs (Golden Tickets), making it one of the most critical accounts in the domain.

This is a simple visualization of Active Directory Forests and Domains.

<figure><img src="https://2000946950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVLHdKTDYsllKhzWHEKHj%2Fuploads%2F7Au1O3KeE49A9mHjjQVF%2Fimage.png?alt=media&amp;token=029c9511-47ef-4c21-98ec-ab36864cdd82" alt="" width="518"><figcaption></figcaption></figure>

### Ticket Granting Ticket (TGT)

The **TGT** is issued after a user successfully authenticates to the domain.\
It proves that the user is authenticated and allows them to request access to services without re-entering credentials.

#### Key properties:

* Issued by the **Authentication Service (AS-REQ & AS-REP)**
* Encrypted with the **krbtgt account’s secret**
* Contains:
  * User identity
  * Group memberships
  * Validity period
  * Session key

#### Authentication flow:

1. User sends an **AS-REQ** to the KDC
2. KDC verifies the user
3. KDC returns an **AS-REP** containing the TGT

Once issued, the TGT is cached locally and reused to request service tickets.

### Service Ticket (TGS)

A **Service Ticket** (TGS) allows a user to access a specific service, such as:

* MSSQL
* IIS
* CIFS (SMB)
* LDAP

#### Key properties:

* Issued by the **Ticket Granting Service (TGS)**
* Encrypted with the **service account’s secret**
* Tied to a specific **Service Principal Name (SPN)**

#### Service access flow:

1. Client presents its TGT to the TGS
2. Requests access to a specific SPN
3. Receives a **TGS ticket**
4. Presents the ticket to the service

This design allows services to verify tickets without contacting the KDC again.

### Ticket Lifetime & Renewals

Tickets are **time-limited** to reduce replay risk.

Typical defaults:

* TGT validity: **10 hours**
* Renewable for: **7 days**

Misconfigurations or long-lived service accounts often make tickets valuable targets for attackers.
