> 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/weakly-encrypted-kerberos-ticket-requested.md).

# Weakly-Encrypted Kerberos Ticket Requested

### Synopsis

| Field                | Value                                                                                                       |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                     |
| Training Period      | 30 Days                                                                                                     |
| Test Period          | N/A (single event)                                                                                          |
| Deduplication Period | 30 Days                                                                                                     |
| Required Data        | <p>Requires one of the following data sources:<br>Palo Alto Networks Firewall traffic Logs OR XDR Agent</p> |
| ATT\&CK Tactic       | Credential Access (TA0006)                                                                                  |
| ATT\&CK Technique    | Steal or Forge Kerberos Tickets: Kerberoasting (T1558.003)                                                  |
| Severity             | Low                                                                                                         |

### Description

A user specifically requested weak and deprecated encryption in a Kerberos TGS request. This provides easy-to-crack hashes and is typically a sign of a Kerberoasting 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>Weakly-Encrypted Kerberos Ticket Requested on a sensitive server</summary>

**Synopsis**

| Field             | Value                                                      |
| ----------------- | ---------------------------------------------------------- |
| ATT\&CK Tactic    | Credential Access (TA0006)                                 |
| ATT\&CK Technique | Steal or Forge Kerberos Tickets: Kerberoasting (T1558.003) |
| Severity          | Medium                                                     |

**Description**

A user specifically requested weak and deprecated encryption in a Kerberos TGS request. This provides easy-to-crack hashes and is typically a sign of a Kerberoasting attack. This action occurred on a sensitive server, which may indicate a malicious activity.

**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/weakly-encrypted-kerberos-ticket-requested.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.
