> 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/as-rep-roasting.md).

# AS-REP Roasting

Active Directory security notes for AS-REP Roasting, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.

### Principle

**AS-REP Roasting** is a technique targeting Active Directory accounts configured with the option:

```bash
Do not require Kerberos preauthentication
```

The response contains data encrypted with a key derived from the user's password.

This data can then be attacked offline with a tool like John the Ripper or Hashcat.

### Simplified diagram

{% code overflow="wrap" %}

```bash
Attacker
   │
   ├── AS-REQ to the KDC
   │
   └── AS-REP encrypted with a key derived from the user's password
                    │
                    └── Offline cracking
```

{% endcode %}

### Why it's dangerous

This attack is dangerous because:

* it does not necessarily require valid credentials;
* it can be carried out remotely against the KDC;
* cracking is performed offline;
* it strongly depends on the strength of the user's password.


---

# 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/as-rep-roasting.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.