> 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/zh/active-directory/enumeration/bloodhound-installation.md).

# BloodHound 安装

面向 BloodHound 安装的 Active Directory 安全笔记，涵盖枚举、Kerberos、凭据、ACL 滥用、横向移动、利用流程和验证步骤。

{% embed url="<https://github.com/SpecterOps/BloodHound-Legacy>" %}

### 目标

**BloodHound** 是一款基于图的 Active Directory 分析工具。

它可以可视化：

* 用户、组和机器之间的关系；
* 权限路径；
* 会话；
* 本地管理员权限；
* 到高价值账户的路径；
* 不良的 Active Directory 配置。

它是快速理解 AD 域中安全关系的最佳工具之一。

### 使用 Docker 安装 Neo4j

BloodHound 使用 Neo4j 作为其图数据库。

Docker 命令：

<pre class="language-bash" data-overflow="wrap"><code class="lang-bash"><strong>sudo docker run /
</strong>    --name neo4j-bloodhound /
    -p 7474:7474 -p 7687:7687 /
    -d /
    -v ~/neo4j/data:/data /
    -v ~/neo4j/logs:/logs /
    --env NEO4J_AUTH=neo4j/jordanmacia/
    --env NEO4J_dbms_connector_bolt_tls_level=DISABLED /
    neo4j:4.4
</code></pre>

重要提示：

| 端口     | 实用工具                   |
| ------ | ---------------------- |
| `7474` | Neo4j Web 界面           |
| `7687` | BloodHound 使用的 Bolt 连接 |

示例中的 Neo4j 凭据：

```bash
neo4j / jordanmacia
```

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

### 启动 BloodHound

{% code overflow="wrap" %}

```bash
bloodhound --no-sandbox &
```

{% endcode %}

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-73a8f1a61dd33c48dc664cb23ef836d4df12f68e%2Fimage%20(3226).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/zh/active-directory/enumeration/bloodhound-installation.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.