> 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/token-observation-with-process-explorer.md).
# Observing tokens with Process Explorer
Active Directory security notes for Observing tokens with Process Explorer, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
#### Launch Process Explorer
We launch Process Explorer in an administrator PowerShell session:
```powershell
./procexp64.exe
```
Then, we also open a `cmd` without administrator rights.
This allows us to compare:
* high process;
* a non-high process;
* the associated tokens;
* the privileges available.
#### Check the token of a process
In Process Explorer:
```bash
Process -> Properties -> Security
```
In this tab, you can see:
* the user associated with the process;
* groups;
* privileges;
* the level of integrity;
* the logon session.
#### Example in the lab
Examples of observed logon sessions:
```bash
Administrator : Logon session 9d72b1
user1 : Logon session 955ec3
```
This shows that each session has its own security context.
---
# 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/token-observation-with-process-explorer.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)