> 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/general-kerberos-flow.md).

# General Kerberos Flow

Active Directory security notes for General Kerberos Flow, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.

### Step 1 — AS-REQ

When a user logs in, their client sends a query to the KDC:

```bash
AS-REQ
```

This query corresponds to the initial authentication query.

### Step 2 — AS-REP

If the authentication is valid, the KDC returns a response:

```bash
AS-REP
```

This response notably contains a **TGT**, or **Ticket Granting Ticket**.

The TGT can be seen as a general ticket allowing you to query service tickets.

### Step 3 - TGS-REQ

When the user wants to access a resource, for example a network share, he presents his TGT to the KDC.

The client then sends:

```bash
TGS-REQ
```

This request queries a ticket for a specific service.

### Step 4 — TGS-REP

The KDC checks the TGT and returns a service ticket:

```bash
TGS-REP
```

This ticket is specific to the requested service.

### Step 5 — Access to the resource

The client presents the service ticket to the target server.

For example, to access:

```bash
//WS01/C$
```

The client submits a service ticket to server `WS01`.

If the ticket is valid but the user does not have the necessary permissions on the share, authentication may succeed but SMB access will be denied.


---

# 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/general-kerberos-flow.md?ask=<question>&goal=<user_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.