> 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/lsass-memory-credential-access.md).

# Access to in-memory credentials: LSASS

Active Directory security notes for Access to in-memory credentials: LSASS, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.

### What is LSASS?

**LSASS**, or **Local Security Authority Subsystem Service**, is a critical Windows process.

Its process is:

```bash
lsass.exe
```

LSASS manages in particular:

* local authentication;
* user sessions;
* tokens;
* some credentials;
* the secrets necessary for authentication mechanisms.

### Why LSASS is sensitive

If an attacker gains administrator privileges on a machine, he can attempt to access LSASS memory.

In a lab, this allows you to understand what types of information can be present in memory.

Depending on the configuration, we can find:

* NTLM hashes;
* Kerberos tickets;
* session information;
* cached credentials;
* traces of previous connections.


---

# 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/lsass-memory-credential-access.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.