> 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/hacking-wifi/wpa-wpa2-psk-network-attacks/wps/wps-attacks.md).
# WPS Security Assessment
Assess WPS exposure and document the required remediation.
Wi-Fi Protected Setup (WPS) simplifies client onboarding on some access points.
Its PIN method uses an eight-digit value. Weak implementations can increase network risk.
### Define the assessment scope
Document each access point, its BSSID, channel, and firmware version.
Record the assessment date and time window.
### Verify WPS configuration
Use the router administration interface or an approved scanner.
Record whether WPS is enabled and which onboarding method is available.
Review any configured lockout, retry limit, and delay settings.
These controls reduce exposure to repeated PIN attempts.
### Report the finding
Document the WPS state and the available safeguards.
Do not include usable PINs or network passwords in the report.
### Remediate WPS exposure
Disable WPS on production networks unless a documented business need requires it.
Apply current firmware and replace default administrative credentials.
Use WPA3 where possible. Enforce a long, unique Wi-Fi passphrase otherwise.
---
# 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/hacking-wifi/wpa-wpa2-psk-network-attacks/wps/wps-attacks.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.
