> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/possible-as-rep-roasting-attack.md).

# Possible AS-REP Roasting Attack

### Synopsis

| Field                | Value                                                                                              |
| -------------------- | -------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                            |
| Training Period      | 30 Days                                                                                            |
| Test Period          | 1 Hour                                                                                             |
| Deduplication Period | 1 Day                                                                                              |
| Required Data        | <p>Requires all of the following:<br>XDR Agent<br>XDR Agent with eXtended Threat Hunting (XTH)</p> |
| Detection Modules    | Identity Analytics                                                                                 |
| ATT\&CK Tactic       | Credential Access (TA0006)                                                                         |
| ATT\&CK Technique    | Steal or Forge Kerberos Tickets: AS-REP Roasting (T1558.004)                                       |
| Severity             | Medium                                                                                             |

### Description

A user enumerated all accounts that don't require pre-authentication in the organization and specifically requested tickets for those accounts. This is typically a sign of an AS-REP Roasting attack.

### Attacker's Goals

Crack account credentials by obtaining an easy-to-crack Kerberos ticket.

### Investigative actions

Check who used the host at the time of the alert, to rule out a benign service or tool requesting weak Kerberos encryption.

### Variations

<details>

<summary>AS-REP Roasting Attack</summary>

**Synopsis**

| Field             | Value                                                        |
| ----------------- | ------------------------------------------------------------ |
| ATT\&CK Tactic    | Credential Access (TA0006)                                   |
| ATT\&CK Technique | Steal or Forge Kerberos Tickets: AS-REP Roasting (T1558.004) |
| Severity          | High                                                         |

**Description**

A user enumerated all accounts that don't require pre-authentication in the organization and specifically requested tickets for those accounts. This is typically a sign of an AS-REP Roasting attack.

**Attacker's Goals**

Crack account credentials by obtaining an easy-to-crack Kerberos ticket.

**Investigative actions**

Check who used the host at the time of the alert, to rule out a benign service or tool requesting weak Kerberos encryption.

</details>


---

# 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://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/possible-as-rep-roasting-attack.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.
