> 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/kerberos-user-enumeration.md).

# User enumeration with Kerberos

Active Directory security notes for User enumeration with Kerberos, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.

### Objective

Kerberos can be used to check if users exist in the domain.

This technique is useful because the KDC may respond differently depending on whether the user exists or not.

{% embed url="<https://github.com/ropnop/kerbrute>" %}

### Creating a list of users

We create a file:

{% code overflow="wrap" %}

```bash
user1
user2
test1
Administrator
Administrador
jordan
carlos
```

{% endcode %}

### Enumeration with Kerbrute

We use `kerbrute` to check valid users:

{% code overflow="wrap" %}

```bash
kerbrute userenum -d whoami.local --dc dc01.whoami.local usernames.txt
```

{% endcode %}

Result in the lab:

```
user1
user2
Administrador
```

This means that these accounts exist in the domain.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-8640be0f22eee744cb75427b27274f6c59ed047c%2F%7B215733D8-485D-40FF-84C3-034CCFA5C616%7D.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/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.
