> 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/access-token.md).

# Access token

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

#### Definition

An **access token** is a Windows object that describes the security context of a process or thread.

When a user logs in, Windows checks their credentials.

If the authentication is successful, the system generates an access token.

Each process launched on behalf of this user receives a copy of this token.

#### Content of a token

A token can contain:

* the user's SID;
* group SIDs;
* privileges;
* the level of integrity;
* the token type;
* the associated session logon;
* UAC elevation related information.

#### Usefulness of the token

Windows uses the token to determine whether a process or thread can access a secure object.

Examples of secure objects:

* file ;
* folder;
* registry key;
* service ;
* processus ;
* network sharing;
* Active Directory object.

When a process tries to access a resource, Windows compares:

```bash
User token
        ↓
Object permissions
        ↓
Access allowed or denied
```

{% embed url="<https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer>" %}


---

# 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/access-token.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.