> For the complete documentation index, see [llms.txt](https://docs.fusion.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fusion.vectra.ai/detection-models/library/brute-force/kerberos_user_enumeration.md).

# kerberos\_user\_enumeration

Explanation This event is triggered by Netography's Fusion Portal when it detects a large number of failed pre-authentication attempts using the Kerberos service originating from a single internal hos

**Explanation**

This event is triggered by Netography's Fusion Portal when it detects a large number of failed pre-authentication attempts using the Kerberos service originating from a single internal host. This activity suggests an attacker attempting to validate a list of user accounts. This type of attack is typically used by an attacker that has communication with a Kerberos server, but does not control a user account on the network. Another use of this technique is called AS-REP roasting, which is a similar attack to Kerberoasting. This attack involves finding users that do not require Kerberos pre-authentication, and the attacker is able to retrieve a crackable hash for these users.

**What to Look For**

When investigating kerberos\_user\_enumeration events, look for OS logs that indicate requests for pre-authentication tickets, especially if more than one user is requested, or the tickets are requested from an uncommon host; these may indicate an AS-REP roasting attack. Look for evidence of attack tools targeting Kerberos or general signs of compromise. Since part of this attack relies on crackable passwords, make sure to rotate passwords for accounts whose hashes may have been leaked, and use strong, hard to crack passwords, and only enable pre-authentication bypass for users when absolutely necessary.

**Related MITRE ATT\&CK Categories**

[Discovery: System Owner/User Discovery, Technique T1033 - Enterprise](https://attack.mitre.org/techniques/T1033)

[Credential Access: Brute Force, Technique T1110 - Enterprise](https://attack.mitre.org/techniques/T1110)


---

# 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://docs.fusion.vectra.ai/detection-models/library/brute-force/kerberos_user_enumeration.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.
