> 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/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/hidden-network-attacks.md).

# Évaluation des réseaux sans fil cachés

Valider la valeur de sécurité limitée des SSID cachés.

Masquer un SSID n’offre pas de contrôle d’accès significatif.

Les clients peuvent révéler un nom de réseau masqué lors d’une découverte ou d’une association normales.

### Objectif de l’évaluation

Valider si le réseau masqué reste identifiable grâce à l’analyse des paquets.

N’émettez pas de sondes et ne perturbez pas les clients pendant ce contrôle.

### Examiner les captures approuvées

Inspectez le trafic de gestion de l’environnement sans fil.

Recherchez des requêtes de sonde, des réponses de sonde ou des trames d’association qui divulguent le SSID.

Consignez le type de trame, l’horodatage, le BSSID et le nom du réseau observé.

### Mesure corrective recommandée

Utilisez WPA3 lorsqu’il est pris en charge. Sinon, utilisez WPA2 avec une phrase secrète forte et unique.

Considérez le masquage du SSID comme une préférence de découverte, et non comme un contrôle de sécurité.


---

# 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/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/hidden-network-attacks.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.