NIST 800-171 3.4.5 (CM.L2-3.4.5): Change Access Limits

Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.

NIST SP 800-171 Rev. 2, requirement 3.4.5

CMMC Level 2 practice CM.L2-3.4.5Published 2026-11-11

What 3.4.5 means in practice

Only approved people can make changes, physically and logically. Define who may change what, document and approve those restrictions, and enforce them, for example with locked equipment rooms, restricted administrative roles and deployment pipelines that only certain accounts can run.

SPRS points and the CMMC POA&M

CMMC Level 2 practice: CM.L2-3.4.5
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.4.5

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

3.4.5[a] physical access restrictions associated with changes to the system are defined.
3.4.5[b] physical access restrictions associated with changes to the system are documented.
3.4.5[c] physical access restrictions associated with changes to the system are approved.
3.4.5[d] physical access restrictions associated with changes to the system are enforced.
3.4.5[e] logical access restrictions associated with changes to the system are defined.
3.4.5[f] logical access restrictions associated with changes to the system are documented.
3.4.5[g] logical access restrictions associated with changes to the system are approved.
3.4.5[h] logical access restrictions associated with changes to the system are enforced.

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

Evidence that shows 3.4.5 is met

The documented physical and logical access restrictions for making changes.
Approval records for those restrictions.
Role assignments and access lists showing who can change production systems.
Physical access controls on equipment rooms.

How PolicyCortex gathers the evidence

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

Related pages

Calculator: SPRS score calculator: mark 3.4.5 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 9 Configuration Management requirements (3.4).
Previous: 3.4.4: Security Impact Analysis
Next: 3.4.6: Least Functionality
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.