NIST 800-171 3.10.1 (PE.L2-3.10.1): Physical Access

Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.

NIST SP 800-171 Rev. 2, requirement 3.10.1

CMMC Level 2 practice PE.L2-3.10.1Published 2026-11-11

What 3.10.1 means in practice

Only authorized people can physically reach the systems, the equipment and the rooms they sit in. Keep a list of who is authorized, issue badges or keys accordingly, and lock the server rooms, wiring closets and other spaces that hold systems with CUI.

SPRS points and the CMMC POA&M

CMMC Level 2 practice: PE.L2-3.10.1
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.

Sources: NIST SP 800-171 DoD Assessment Methodology, version 1.2.1 (June 24, 2020), Annex A; 32 CFR 170.21, Plan of Action and Milestones requirements.

What an assessor checks for 3.10.1

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

3.10.1[a] authorized individuals allowed physical access are identified.
3.10.1[b] physical access to organizational systems is limited to authorized individuals.
3.10.1[c] physical access to equipment is limited to authorized individuals.
3.10.1[d] physical access to operating environments is limited to authorized individuals.

NIST SP 800-171A (June 2018), assessment objectives for 3.10.1

Evidence that shows 3.10.1 is met

The list of people authorized for physical access to each controlled area.
Badge or key system records showing access limited to that list.
Photos or a walkthrough of locked server rooms and equipment areas.

How PolicyCortex gathers the evidence

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

Related pages

Calculator: SPRS score calculator: mark 3.10.1 and the other 109 requirements and see the score.
Sample package: Sample package: an SSP, a POA&M and an evidence chain the product generated from demonstration data.
Family: All 6 Physical Protection requirements (3.10).
Previous: 3.9.2: Personnel Actions
Next: 3.10.2: Facility Monitoring
All requirements: All 110 NIST SP 800-171 requirements, by family.

Related records

Guides and articles describe the work. The evidence that work produces is described in three proof pages, the architecture page, and the two pages on authorization.

proof.state: Proof of State. What the environment was, as of a date someone else picks: point-in-time records, content hashed and chained.
proof.change: Proof of Change. Who or what altered the environment, under what authority, with before and after state hashes.
proof.agency: Proof of Agency. What a machine was permitted to do before it acted, what it did, and what would have stopped it.
architecture: Architecture. How the chain is built and where the evidence is stored in each delivery mode.
authorization: Continuous ATO. How an authorizing official's decision is recorded with its package, and how the authorized system is checked against it every hour.
baseline: NIST SP 800-53. The Low, Moderate and High baselines as evidence, with the SSP, SAR and POA&M generated from one record.