> 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/credentials/sam-database-dump.md).

# 提取 SAM 数据库

针对提取 SAM 数据库的 Active Directory 安全笔记，涵盖枚举、Kerberos、凭据、ACL 滥用、横向移动、利用流程和验证步骤。

### 什么是 SAM？

该 **SAM**或 **安全帐户管理器**，是一个包含该机器本地账户的 Windows 本地数据库。

它包含与以下内容相关的信息：

* 关于本地用户；
* 关于本地组；
* 本地账户哈希值。

### 需要访问权限

访问 SAM 需要提升的权限。

在实验中，我们使用：

```bash
privilege::debug

token::elevate
```

目标是切换到更高权限的上下文，以访问本地机密。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-39416c5de3e7556f19f10fc6322b13a593eb5b7d%2F%7B4114D558-5DFC-47E4-B42F-C62F694DB477%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

### SAM 转储

在实验中：

```bash
lsadump::sam
```

此命令允许你从本地 SAM 数据库中提取信息。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0f0529a53de712d9d61cf0fde5f8adc7b71d548b%2F%7B9D4AA135-7EFE-4A48-9F49-26BD3789698E%7D.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/credentials/sam-database-dump.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.
