> 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-and-sam-dump-on-windows.md).
# Extracción de LSASS y SAM en Windows
Notas de seguridad de Active Directory para Extracción de LSASS y SAM en Windows, que cubren enumeración, Kerberos, credenciales, abuso de ACL, movimiento lateral, flujo de explotación y pasos de validación.
### Ejecución en el laboratorio
En el laboratorio, abrimos varias sesiones de PowerShell:
* dos sesiones con un administrador local;
* una sesión con un administrador de dominio.
Luego, lanzamos la herramienta desde una PowerShell de administrador local:
```bash
./mimikats.exe
```
### Mostrar información de la sesión
En la herramienta:
```powershell
sekurlsa::logonpasswords
```
Este comando muestra información relacionada con las sesiones de autenticación presentes en la memoria.
Dependiendo del contexto, podemos ver información como:
* usuarios conectados;
* dominio;
* tipo de autenticación;
* hashes ;
* tickets o elementos relacionados con Kerberos;
* sesiones interactivas o de red.
### Crackear un hash NTLM
Si se obtiene un hash NTLM del laboratorio, se puede probar con John:
```bash
john --format=NT admin.hash
```
Esto ayuda a ilustrar el riesgo de contraseñas débiles o reutilizadas.
---
# 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-and-sam-dump-on-windows.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)
