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

# AS-REP Roasting

Notas de seguridad de Active Directory para AS-REP Roasting, que cubren enumeración, Kerberos, credenciales, abuso de ACL, movimiento lateral, flujo de explotación y pasos de validación.

### Principio

**AS-REP Roasting** es una técnica que apunta a cuentas de Active Directory configuradas con la opción:

```bash
No requiere preautenticación de Kerberos
```

La respuesta contiene datos cifrados con una clave derivada de la contraseña del usuario.

Estos datos pueden entonces atacarse fuera de línea con una herramienta como John the Ripper o Hashcat.

### Diagrama simplificado

{% code overflow="wrap" %}

```bash
Atacante
   │
   ├── AS-REQ al KDC
   │
   └── AS-REP cifrado con una clave derivada de la contraseña del usuario
                    │
                    └── Cracking fuera de línea
```

{% endcode %}

### Por qué es peligroso

Este ataque es peligroso porque:

* no necesariamente requiere credenciales válidas;
* puede llevarse a cabo de forma remota contra el KDC;
* el cracking se realiza fuera de línea;
* depende en gran medida de la fortaleza de la contraseña del usuario.


---

# 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/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.