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

# Installation de BloodHound

Notes de sécurité Active Directory pour l'installation de BloodHound, couvrant l'énumération, Kerberos, les identifiants, l'abus d'ACL, le mouvement latéral, le flux d'exploitation et les étapes de validation.

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

### Objectif

**BloodHound** est un outil d’analyse d’Active Directory basé sur les graphes.

Il peut visualiser :

* les relations entre les utilisateurs, les groupes et les machines ;
* les chemins de privilèges ;
* les sessions ;
* les droits d’administration locale ;
* les chemins vers les comptes à haute valeur ;
* Les mauvaises configurations d’Active Directory.

C’est l’un des meilleurs outils pour comprendre rapidement les relations de sécurité dans un domaine AD.

### Installation de Neo4j avec Docker

BloodHound utilise Neo4j comme base de données graphique.

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

Points importants :

| Port   | Utilitaire                             |
| ------ | -------------------------------------- |
| `7474` | Interface web Neo4j                    |
| `7687` | Connexion Bolt utilisée par BloodHound |

Identifiants Neo4j dans l’exemple :

```bash
neo4j / jordanmacia
```

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

### Lancer BloodHound

{% code overflow="wrap" %}

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

{% endcode %}

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