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

# Kerberosによるユーザー列挙

Kerberosによるユーザー列挙のためのActive Directoryセキュリティノート。列挙、Kerberos、資格情報、ACL悪用、ラテラルムーブメント、攻撃のワークフロー、検証手順を扱う。

### 目的

Kerberos は、ドメイン内にユーザーが存在するかどうかを確認するために使用できます。

この手法が有用なのは、KDC がユーザーの存在有無によって異なる応答を返す場合があるためです。

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

### ユーザー一覧の作成

次のファイルを作成します:

{% code overflow="wrap" %}

```bash
user1
user2
test1
Administrator
管理者
jordan
carlos
```

{% endcode %}

### Kerbruteによる列挙

次を使用します `kerbrute` 有効なユーザーを確認するには:

{% code overflow="wrap" %}

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

{% endcode %}

ラボでの結果:

```
user1
user2
管理者
```

これは、これらのアカウントがドメイン内に存在することを意味します。

<figure><img src="https://2001299964-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/ja/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.