> 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/tgs-rep-roasting-or-kerberoasting.md).
# TGS-REP Roasting / Kerberoasting
Active Directory security notes for TGS-REP Roasting / Kerberoasting, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
### Principle
**Kerberoasting** involves querying Kerberos service tickets for accounts with an **SPN**, then attempting to break the encrypted portion of the ticket offline.
An **SPN**, or **Service Principal Name**, associates a service with an Active Directory account.
SPN examples:
{% code overflow="wrap" %}
```bash
HTTP/webserver.whoami.local
MSSQLSvc/sql01.whoami.local
CIFS/ws01.whoami.local
MailSrv/MS01.corp.local
```
{% endcode %}
### Objective
The goal of Kerberoasting is to target service accounts.
If the service account password is weak, the recovered ticket may be cracked offline.
### Check a computer's SPNs
With PowerView:
{% code overflow="wrap" %}
```bash
Get-NetComputer -Identity WS01
```
{% endcode %}
We can see default SPNs like:
{% code overflow="wrap" %}
```powershell
RestrictedKrbHost/WS01
HOST/WS01
RestrictedKrbHost/WS01.whoami.local
HOST/WS01.whoami.local
```
{% endcode %}
---
# 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/tgs-rep-roasting-or-kerberoasting.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.
