- Inventory the access points and wireless networks that exist, then compare against the ones you authorized — periodically, because the gap reopens.
- Decide and document which devices may join which wireless network, and keep guest wireless away from systems holding CUI.
3.1.16 — Wireless access authorization
3.1 Access Control · NIST SP 800-171 Rev. 2 · The heading label is this site's navigational shorthand; the official language is the statement below.
Authorize wireless access prior to allowing such connections.
NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems ↗NIST SP 800-171A — Assessing Security Requirements for CUI ↗What this requirement is after
Wireless access exists only where you have decided it should: approved access points, authorized devices, and a deliberate answer for what wireless can reach. The unauthorized access point an employee plugged in for convenience is exactly what this requirement exists to catch.
Brilliant at the Basics practices that support this requirement
The campaign’s twenty practices are a priority list, not a control catalog, and none of them works this requirement’s substance directly. It still applies to you if it is in your contract’s scope: address it through your own implementation and the related artifacts below, and treat the absence of a mapping here as honesty, not permission to skip it.
Implementation considerations and evidence
- The authorized wireless network and access point list
- Periodic rogue access point scan results
Templates and worksheets with a mapped relationship
No artifact in the library names this requirement yet. The library index groups everything by category and practice.
Where this lands in Rev. 3
Sources and review status
| Primary sources | NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A — Assessing Security Requirements for CUI |
|---|---|
| Review status | Pending NIST SME review |
| Content version | 1.0 |
| Updated |