> 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/windows-authentication-and-authorization.md).

# Windows 中的身份验证与授权

<details>

<summary>资源</summary>

{% embed url="<https://learn.microsoft.com/en-us/windows/win32/secauthz/access-tokens>" %}

{% embed url="<https://learn.microsoft.com/en-us/windows-server/security/windows-authentication/credentials-processes-in-windows-authentication#BKMK_CrentialInputForUserLogon>" %}

</details>

> **后台执行**：本节说明 Windows 如何处理身份验证、登录会话、访问令牌以及内存中的或缓存的凭据。所描述的操作是在一个 **授权实验室** 中进行的，以便了解 Active Directory 域中一台 Windows 工作站被攻陷所带来的风险。

#### 基本原理

当用户在 Windows 上正确进行身份验证时，系统会创建一个 **登录会话**，也就是一个连接会话。

随后，身份验证包将信息传输给 **LSA**，或 **本地安全机构**.

LSA 使用这些信息创建一个 **访问令牌** 与新用户关联的

该令牌尤其包含：

* 用户的身份；
* 其所属的组；
* 其特权；
* 其完整性级别；
* 一个称为以下内容的本地唯一凭据 **LUID**;
* 该会话的安全上下文。

该 **LUID**，或 **本地唯一标识符**，可用于在本地标识一个连接会话。


---

# 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/zh/active-directory/credentials/windows-authentication-and-authorization.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.