> 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/zh/active-directory/kerberos/kerberos-key-components.md).
# Kerberos 关键组件
针对 Kerberos 关键组件的 Active Directory 安全笔记，涵盖枚举、Kerberos、凭据、ACL 滥用、横向移动、利用流程和验证步骤。
#### KDC
该 **KDC**或 **密钥分发中心**，安装在域控制器上。
它负责签发 Kerberos 票据。
它包含两个主要组件：
* **AS** ：认证服务；
* **TGS** ：票据授予服务。
#### AS — 认证服务
该 **AS** 是 KDC 中负责用户初始认证的部分。
它发生在用户连接到域时。
#### TGS — 票据授予服务
该 **TGS** 是 KDC 中负责提供访问特定服务票据的部分。
服务示例：
* SMB 共享；
* HTTP 服务；
* MSSQL；
* LDAP；
* CIFS；
* 内部应用程序服务。
#### krbtgt 账户
在 Active Directory 中，默认会创建一个特殊账户：
```
krbtgt
```
该账户供 KDC 用于对某些 Kerberos 票据进行签名和加密。
它极其敏感，因为它与域中 Kerberos 身份验证的工作方式有关。
---
# 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/zh/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.
