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

# Acceso a credenciales en memoria: LSASS

### ¿Qué es LSASS?

**LSASS**o **Servicio del subsistema de la Autoridad de Seguridad Local**, es un proceso crítico de Windows.

Su proceso es:

```bash
lsass.exe
```

LSASS gestiona, en particular:

* la autenticación local;
* las sesiones de usuario;
* los tokens;
* algunas credenciales;
* los secretos necesarios para los mecanismos de autenticación.

### Por qué LSASS es sensible

Si un atacante obtiene privilegios de administrador en una máquina, puede intentar acceder a la memoria de LSASS.

En un laboratorio, esto te permite entender qué tipos de información pueden estar presentes en la memoria.

Según la configuración, podemos encontrar:

* hashes NTLM;
* tickets de Kerberos;
* información de sesión;
* credenciales en caché;
* rastros de conexiones anteriores.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hacking-notes.jord4n.pro/es/active-directory/credentials/lsass-memory-credential-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.