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

# Accès aux identifiants en mémoire : LSASS

Notes de sécurité Active Directory pour l'accès aux identifiants en mémoire : LSASS, couvrant l'énumération, Kerberos, les identifiants, l'abus des ACL, le mouvement latéral, le flux de travail d'exploitation et les étapes de validation.

### Qu’est-ce que LSASS ?

**LSASS**, ou **Service du sous-système de l’autorité de sécurité locale**, est un processus Windows critique.

Son processus est :

```bash
lsass.exe
```

LSASS gère notamment :

* l’authentification locale ;
* les sessions utilisateur ;
* les jetons ;
* certaines informations d’identification ;
* les secrets nécessaires aux mécanismes d’authentification.

### Pourquoi LSASS est sensible

Si un attaquant obtient des privilèges d’administrateur sur une machine, il peut tenter d’accéder à la mémoire de LSASS.

Dans un laboratoire, cela permet de comprendre quels types d’informations peuvent être présents en mémoire.

Selon la configuration, on peut trouver :

* des hachages NTLM ;
* des tickets Kerberos ;
* des informations de session ;
* des informations d’identification mises en cache ;
* des traces de connexions précédentes.


---

# 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/fr/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.