> For the complete documentation index, see [llms.txt](https://viperone.gitbook.io/pentest-everything/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://viperone.gitbook.io/pentest-everything/everything/everything-active-directory/credential-access/steal-or-forge-kerberos-tickets.md).

# Steal or Forge Kerberos Tickets

https\://attack.mitre.org/techniques/T1558/

**ATT\&CK ID:** [T1558](https://attack.mitre.org/techniques/T1558/)

**Description**

Adversaries may attempt to subvert Kerberos authentication by stealing or forging Kerberos tickets to enable [Pass the Ticket](https://attack.mitre.org/techniques/T1550/003). Kerberos is an authentication protocol widely used in modern Windows domain environments. In Kerberos environments, referred to as "realms", there are three basic participants: client, service, and Key Distribution Center (KDC).[\[1\]](https://adsecurity.org/?p=227)

Clients request access to a service and through the exchange of Kerberos tickets, originating from KDC, they are granted access after having successfully authenticated. The KDC is responsible for both authentication and ticket granting. Adversaries may attempt to abuse Kerberos by stealing tickets or forging tickets to enable unauthorized access.The table below shows only results that are pertinent to Windows.

## Sub Techniques

### T1558.001: Golden Ticket

{% content-ref url="/pages/-Miopfo4QXmaT8MZJW6R" %}
[Golden Ticket](/pentest-everything/everything/everything-active-directory/credential-access/steal-or-forge-kerberos-tickets/golden-ticket.md)
{% endcontent-ref %}

### T1558.002: Silver Ticket

{% content-ref url="/pages/-MlGoIp1pcelslPlaVJk" %}
[Silver Ticket](/pentest-everything/everything/everything-active-directory/credential-access/steal-or-forge-kerberos-tickets/silver-ticket.md)
{% endcontent-ref %}

### T1558.003: Kerberoasting

{% content-ref url="/pages/MlcYd1r6BqFr4tEEqmfH" %}
[Kerberoasting](/pentest-everything/everything/everything-active-directory/credential-access/steal-or-forge-kerberos-tickets/kerberoasting.md)
{% endcontent-ref %}

### T1558.004: AS-REP Roasting

{% content-ref url="/pages/-MjO64HOsR8WUCmRW-84" %}
[AS-REP Roasting](/pentest-everything/everything/everything-active-directory/credential-access/steal-or-forge-kerberos-tickets/as-rep-roasting.md)
{% endcontent-ref %}

## S4U2Self

{% content-ref url="/pages/Ev0EXMthLqSjomWenHOK" %}
[S4U2Self](/pentest-everything/everything/everything-active-directory/credential-access/steal-or-forge-kerberos-tickets/s4u2self.md)
{% endcontent-ref %}

### Ticket Acquisition

{% content-ref url="/pages/9jI179NhFiNUqhgQRlGT" %}
[Ticket Aquisition](/pentest-everything/everything/everything-active-directory/credential-access/steal-or-forge-kerberos-tickets/ticket-aquisition.md)
{% endcontent-ref %}

### Constrained Delegation

{% content-ref url="/pages/11vhTvfTAq0FFZ4lbpBQ" %}
[Constrained Delegation](/pentest-everything/everything/everything-active-directory/credential-access/steal-or-forge-kerberos-tickets/constrained-delegation.md)
{% endcontent-ref %}

### Unconstrained Delegation

{% content-ref url="/pages/-MlR0k6mahCzXH5q3iIQ" %}
[Unconstrained Delegation](/pentest-everything/everything/everything-active-directory/credential-access/steal-or-forge-kerberos-tickets/unconstrained-delegation.md)
{% endcontent-ref %}


---

# 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://viperone.gitbook.io/pentest-everything/everything/everything-active-directory/credential-access/steal-or-forge-kerberos-tickets.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.