> 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

Notas de seguridad de Active Directory para Acceso a credenciales en memoria: LSASS, que cubren enumeración, Kerberos, credenciales, abuso de ACL, movimiento lateral, flujo de explotación y pasos de validación.

### ¿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 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 almacenadas 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 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/es/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.