> 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/es/active-directory/kerberos/kerberos-key-components.md).
# Componentes clave de Kerberos
Notas de seguridad de Active Directory para Componentes clave de Kerberos, que cubren enumeración, Kerberos, credenciales, abuso de ACL, movimiento lateral, flujo de explotación y pasos de validación.
#### KDC
El **KDC**, o **Centro de distribución de claves**, se instala en el controlador de dominio.
Es responsable de emitir tickets Kerberos.
Contiene dos componentes principales:
* **AS** : Servicio de autenticación ;
* **TGS** : Servicio de concesión de tickets.
#### AS — Servicio de autenticación
El **AS** es la parte del KDC responsable de la autenticación inicial del usuario.
Ocurre cuando el usuario se conecta al dominio.
#### TGS — Servicio de concesión de tickets
El **TGS** es la parte del KDC responsable de proporcionar tickets para acceder a servicios específicos.
Ejemplos de servicios:
* recurso compartido SMB;
* servicio HTTP;
* MSSQL;
* LDAP;
* CIFS;
* servicio de aplicación interna.
#### cuenta krbtgt
En Active Directory, se crea de forma predeterminada una cuenta especial:
```
krbtgt
```
Esta cuenta es utilizada por el KDC para firmar y cifrar ciertos tickets Kerberos.
Es extremadamente sensible porque está relacionada con el funcionamiento de la autenticación Kerberos en el dominio.
---
# 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/es/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.
