> 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/active-directory/enumeration/bloodhound-analysis.md).
# Analysis in BloodHound
Active Directory security notes for Analysis in BloodHound, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
### Search for a user
In BloodHound, you can search for a user, for example:
* user1
BloodHound then displays:
* its groups;
* its relationships;
* their rights;
* linked machines;
* known sessions;
* possible attack paths.
### View direct members of a group
You can select a domain group and display its **Direct Members**.
This allows you to know which users or groups are direct members of a given group.
### Use the Analysis tab
The **Analysis** tab contains very useful predefined queries.
Examples:
* find all Domain Admins;
* find paths to Domain Admins;
* find users with local administrator rights;
* find active sessions;
* find paths to high-value targets.
### Example with a group `Executives`
In your lab:
1. a `Executives` group is created;
2. this group is associated with the `Administrators` group or a privileged group;
3. user `user4` is added to the `Executives` group.
In BloodHound, we can then see that:
user4 → Executives → Administrators
This shows a privilege path.
### Mark a user as High Value
In BloodHound, you can mark a user or group as **High Value Target**.
Then, we can use:
`Shortest Paths to High Value Targets`
BloodHound then displays the shortest paths to reach this target.
### Menu Help
BloodHound often provides explanations in its help menu or in relationship details.
You can find there:
* explanations about the relationship type;
* command examples;
* GitHub references;
* technical references;
* sometimes links to NIST, blogs or videos.
---
# 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/active-directory/enumeration/bloodhound-analysis.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)