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

# Instalación de BloodHound

Notas de seguridad de Active Directory para Instalación de BloodHound, que cubren enumeración, Kerberos, credenciales, abuso de ACL, movimiento lateral, flujo de explotación y pasos de validación.

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

### Objetivo

**BloodHound** es una herramienta de análisis de Active Directory basada en grafos.

Puede visualizar:

* relaciones entre usuarios, grupos y máquinas;
* las rutas de privilegio;
* sesiones;
* derechos de administración local;
* rutas hacia cuentas de alto valor;
* Configuraciones incorrectas de Active Directory.

Es una de las mejores herramientas para comprender rápidamente las relaciones de seguridad en un dominio AD.

### Instalación de Neo4j con Docker

BloodHound utiliza Neo4j como su base de datos de grafos.

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

Puntos importantes:

| Puerto | Utilidad                               |
| ------ | -------------------------------------- |
| `7474` | Interfaz web de Neo4j                  |
| `7687` | Conexión Bolt utilizada por BloodHound |

Credenciales de Neo4j en el ejemplo:

```bash
neo4j / jordanmacia
```

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

### Iniciar BloodHound

{% code overflow="wrap" %}

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

{% endcode %}

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