> 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/cached-domain-credentials-mscache.md).

# Identifiants de domaine mis en cache : MSCache

Notes de sécurité Active Directory pour les identifiants de domaine mis en cache : MSCache, 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.

### Principe

Windows peut stocker des informations d'identification de domaine mises en cache.

Cela permet à un utilisateur de se connecter à une machine même si le contrôleur de domaine n'est pas joignable.

Ce mécanisme s'appelle :

```
MSCache
```

ou plus précisément :

```
MSCache v2
```

### Pourquoi c'est important

Si un utilisateur du domaine s'est déjà connecté à une machine, Windows peut conserver un hachage spécifique permettant une authentification hors ligne.

Dans un scénario de compromission locale, cette information peut devenir sensible.


---

# 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/cached-domain-credentials-mscache.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.