> 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/logon-session-observation.md).
# Observing login sessions
Active Directory security notes for Observing login sessions, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
#### LogonSessions Tool
To see the connection sessions present on the machine, we use the tool:
```bash
./logonsessions.exe
```
This tool allows you to observe the different active sessions on the system.
We can see, for example:
* a standard user session;
* an administrator session;
* a network session;
* a service session.
#### Show related processes
To view processes related to logon sessions:
```bash
./logonsessions.exe -p
```
The `-p` option allows you to associate processes with login sessions.
This helps understand which processes use which security context.
#### Example observation
In the lab, when a domain administrator connects to a remote share:
```bash
cd //WS01/c$
```
We can observe a session of the type:
```bash
Logon Type : Network
Authentication Package : Kerberos
```
This indicates that network access was achieved via Kerberos.
---
# 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/logon-session-observation.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)
.png?alt=media)