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

# تثبيت BloodHound

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

### الهدف

**BloodHound** هي أداة لتحليل Active Directory قائمة على الرسوم البيانية.

يمكنها تصور:

* العلاقات بين المستخدمين والمجموعات والأجهزة؛
* مسارات الامتياز؛
* الجلسات؛
* حقوق الإدارة المحلية؛
* المسارات إلى الحسابات عالية القيمة؛
* تكوينات Active Directory السيئة.

إنها واحدة من أفضل الأدوات لفهم علاقات الأمان بسرعة داخل نطاق AD.

### تثبيت Neo4j باستخدام Docker

يستخدم 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                       |
| `7687` | اتصال Bolt المستخدم بواسطة BloodHound |

بيانات اعتماد Neo4j في المثال:

```bash
neo4j / jordanmacia
```

<figure><img src="/files/dad36fac97c97b545ae6f15d0946ee241c6ca6b0" alt=""><figcaption></figcaption></figure>

### تشغيل BloodHound

{% code overflow="wrap" %}

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

{% endcode %}

<figure><img src="/files/5039dd0130dcb100d87c4927b2b4de4059ac10e0" 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/ar/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.