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

# Authentication and authorization in Windows

Active Directory security notes for Authentication and authorization in Windows, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.

<details>

<summary>Ressources</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>

> **Background**: This section explains how Windows handles authentication, login sessions, access tokens, and in-memory or cached credentials. The manipulations described are carried out in an **authorized laboratory** in order to understand the risks linked to the compromise of a Windows workstation in an Active Directory domain.

#### General principle

When a user authenticates correctly on Windows, the system creates a **logon session**, that is to say a connection session.

The authentication packet then transmits information to the **LSA**, or **Local Security Authority**.

The LSA uses this information to create an **access token** associated with the new user.

This token notably contains:

* the identity of the user;
* the groups to which he belongs;
* its privileges;
* its level of integrity;
* a local unique credential called **LUID**;
* the security context of the session.

The **LUID**, or **Locally Unique Identifier**, allows you to locally identify a connection session.


---

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