> 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/zh/active-directory/enumeration/sharphound-collection.md).

# 使用 SharpHound 收集

面向使用 SharpHound 收集的 Active Directory 安全笔记，涵盖枚举、Kerberos、凭据、ACL 滥用、横向移动、利用流程和验证步骤。

\#使用 SharpHound 收集

### 目标

**SharpHound** 是 BloodHound 使用的收集器。

它会检索创建图谱所需的 Active Directory 信息。

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

### 在 Windows 机器上运行

在 `WS01`，将 `SharpHound.exe`，然后执行：

{% code overflow="wrap" %}

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

{% endcode %}

该 `-c All` 选项会收集所有可用类别。

收集的数据示例：

用户；/ 组；/ 计算机；会话；/ ACL；/ 本地管理员；GPO；/ 域关系。

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

SharpHound 通常会生成：

* 一个 `.zip` 包含数据的文件；
* 有时还会有一个日志文件。

然后我们将 `.zip` 文件传输到 Linux 机器，然后通过拖放将其导入 BloodHound。

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