> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/active-directory/kerberos/kerberos-key-components.md).
# Key Kerberos Components
Active Directory security notes for Key Kerberos Components, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
#### KDC
The **KDC**, or **Key Distribution Center**, is installed on the domain controller.
It is responsible for issuing Kerberos tickets.
It contains two main components:
* **AS** : Authentication Service ;
* **TGS** : Ticket Granting Service.
#### AS — Authentication Service
The **AS** is the part of the KDC responsible for initial user authentication.
It occurs when the user connects to the domain.
#### TGS — Ticket Granting Service
The **TGS** is the part of the KDC responsible for providing tickets to access specific services.
Service examples:
* SMB share;
* HTTP service;
* MSSQL;
* LDAP;
* CIFS;
* internal application service.
#### krbtgt account
In Active Directory, a special account is created by default:
```
krbtgt
```
This account is used by the KDC to sign and encrypt certain Kerberos tickets.
It is extremely sensitive because it is related to how Kerberos authentication works in the domain.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/active-directory/kerberos/kerberos-key-components.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
