> 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/sharphound-collection.md).

# Collection with SharpHound

Active Directory security notes for Collection with SharpHound, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.

\#Collection with SharpHound

### Objective

**SharpHound** is the collector used by BloodHound.

It retrieves the Active Directory information necessary to create the graphs.

{% embed url="<https://github.com/SpecterOps/BloodHound-Legacy/blob/master/Collectors/SharpHound.exe>" %}

### Running on a Windows machine

On `WS01`, place `SharpHound.exe`, then execute:

{% code overflow="wrap" %}

```powershell
./SharpHound.exe -c All
```

{% endcode %}

The `-c All` option collects all available categories.

Examples of data collected:

users ;/ groups ;/ computers; sessions ;/ ACL ;/ local administrators; GPO ;/ domain relationships.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0f40051d486fb259638b5e6ed3f5f7d9ccc9d79b%2Fimage%20(3231).png?alt=media" alt=""><figcaption></figcaption></figure>

### SharpHound result

SharpHound usually generates:

* a `.zip` file containing the data;
* sometimes a log file.

We then transfer the `.zip` file to the Linux machine, then import it into BloodHound by drag and drop.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-8bc625e98cb4a106e9f939b2825e397288d2a59e%2Fimage%20(3232).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/active-directory/enumeration/sharphound-collection.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.