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

# BloodHound-Installation

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

### Ziel

**BloodHound** ist ein graphbasiertes Active-Directory-Analysetool.

Es kann visualisieren:

* Beziehungen zwischen Benutzern, Gruppen und Maschinen;
* die Pfade der Privilegien;
* Sitzungen;
* lokale Administrationsrechte;
* Pfade zu hochwertigen Konten;
* Fehlkonfigurationen von Active Directory.

Es ist eines der besten Werkzeuge, um Sicherheitsbeziehungen in einer AD-Domäne schnell zu verstehen.

### Neo4j mit Docker installieren

BloodHound verwendet Neo4j als seine Graphdatenbank.

Docker-Befehl:

<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>

Wichtige Punkte:

| Port   | Dienstprogramm                            |
| ------ | ----------------------------------------- |
| `7474` | Neo4j-Weboberfläche                       |
| `7687` | Von BloodHound verwendete Bolt-Verbindung |

Neo4j-Zugangsdaten im Beispiel:

```bash
neo4j / jordanmacia
```

<figure><img src="/files/3cd0bf383aa3a4df4239272389e516ebb93ea54b" alt=""><figcaption></figcaption></figure>

### BloodHound starten

{% code overflow="wrap" %}

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

{% endcode %}

<figure><img src="/files/dc2681abcee492278a1a2495c112a6e99a5aafea" 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hacking-notes.jord4n.pro/de/active-directory/enumeration/bloodhound-installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.