---
title: "NIST 800-171 3.1.16 (AC.L2-3.1.16): Wireless Authorization"
description: "NIST SP 800-171 3.1.16 Wireless Authorization: 5 SPRS points, not allowed on a CMMC POA&M. The text, what assessors check and the evidence."
url: https://policycortex.com/nist-800-171/access-control/3.1.16
sealed: 2026-11-11
amended: 2026-11-11
register: nist-800-171/access-control/3.1.16
records: 7
digest: sha3:299f4c0d07577c68f6688ea73804770b88ccab1f0563f573f0ab3ff98a693b37
---

# NIST 800-171 3.1.16 (AC.L2-3.1.16): Wireless Authorization

NIST 800-171 / Access Control / 3.1.16

"Authorize wireless access prior to allowing such connections." ([NIST SP 800-171 Rev. 2, requirement 3.1.16](https://doi.org/10.6028/NIST.SP.800-171r2))

CMMC Level 2 practice AC.L2-3.1.16.

## What 3.1.16 means in practice

Before any wireless network connects to the system, you know it exists and someone has approved it. Keep an inventory of authorized access points, the rules for connecting to them, and a way to find rogue access points that nobody approved.

## SPRS points and the CMMC POA&M

- **CMMC Level 2 practice**: AC.L2-3.1.16
- **SPRS points**: 5 points. When it is not met, the DoD Assessment Methodology subtracts 5 from the score of 110.
- **CMMC POA&M**: Not allowed. It is worth 5 points, and 32 CFR 170.21(a)(2)(ii) admits only requirements worth 1 point, with one exception: 3.13.11 when encryption is used but not FIPS validated.
- **Scoring note**: If the system permits no wireless access, mark Met: Annex A subtracts nothing. Keep a policy and procedure that stops it being turned on by accident: without one, a Medium assessment takes 1 point.

Sources: [NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A](https://www.acq.osd.mil/asda/dpc/cp/cyber/docs/safeguarding/NIST-SP-800-171-Assessment-Methodology-Version-1.2.1-6.24.2020.pdf); [32 CFR 170.21, Plan of Action and Milestones requirements](https://www.ecfr.gov/current/title-32/section-170.21).

## What an assessor checks for 3.1.16

NIST SP 800-171A gives 2 determination statements for 3.1.16, each found satisfied or other than satisfied. Determine if:

- 3.1.16[a] wireless access points are identified.
- 3.1.16[b] wireless access is authorized prior to allowing such connections.

[NIST SP 800-171A (June 2018), assessment objectives for 3.1.16](https://doi.org/10.6028/NIST.SP.800-171A)

## Evidence that shows 3.1.16 is met

- The wireless access policy and its usage rules.
- An inventory of authorized wireless access points and networks.
- Records of wireless scans for unauthorized access points.

## How PolicyCortex gathers the evidence

No PolicyCortex collector reads the evidence for 3.1.16. Your team provides the evidence listed above.

## Related pages

- **Calculator**: [SPRS score calculator: mark 3.1.16 and the other 109 requirements and see the score.](https://policycortex.com/sprs-score-calculator#family-AC)
- **Sample package**: [Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.](https://policycortex.com/sample-package)
- **Family**: [All 22 Access Control requirements (3.1).](https://policycortex.com/nist-800-171/access-control)
- **Previous**: [3.1.15: Privileged Remote Access](https://policycortex.com/nist-800-171/access-control/3.1.15)
- **Next**: [3.1.17: Wireless Protection](https://policycortex.com/nist-800-171/access-control/3.1.17)
- **All requirements**: [All 110 NIST SP 800-171 requirements, by family.](https://policycortex.com/nist-800-171)

Meet the requirement once. Keep the evidence current. [Request Access](https://app.policycortex.com/auth?mode=request-access) · [Book a call](https://policycortex.com/book)

## Register colophon

| Seq | Label | SHA3-256 | Prev |
|---|---|---|---|
| REC 0000 | REQUIREMENT | ba4fba3185b9 | e6091f065884 |
| REC 0001 | MEANING | 6c3e4fb033e5 | ba4fba3185b9 |
| REC 0002 | POINTS AND POA&M | 775dffd65716 | 6c3e4fb033e5 |
| REC 0003 | ASSESSMENT OBJECTIVES | 1a5efa8ed749 | 775dffd65716 |
| REC 0004 | EVIDENCE | c1210f7e1605 | 1a5efa8ed749 |
| REC 0005 | COLLECTORS | 00543bebdab1 | c1210f7e1605 |
| REC 0006 | RELATED | 299f4c0d0757 | 00543bebdab1 |

Head sha3:299f4c0d07577c68f6688ea73804770b88ccab1f0563f573f0ab3ff98a693b37. Each digest is SHA3-256 over the previous digest, the register key, the record label, and the record copy; a second party can recompute it from this document.