NIST 800-171 requirements: all 110, by family
NIST SP 800-171 Rev. 2 sets 110 security requirements, in 14 families, for nonfederal systems that handle CUI, and CMMC Level 2 assesses the same 110. Each page here quotes one requirement and the objectives an assessor checks, gives its SPRS point value and CMMC POA&M rule, and names the evidence that shows it is met.
110 requirements14 families320 assessment objectives
The 14 families
All 110 requirements
| Requirement | CMMC practice | SPRS points | CMMC POA&M |
|---|---|---|---|
| 3.1.1 Authorized Access | AC.L2-3.1.1 | 5 points | Not allowed |
| 3.1.2 Transaction Control | AC.L2-3.1.2 | 5 points | Not allowed |
| 3.1.3 CUI Flow Control | AC.L2-3.1.3 | 1 point | Allowed |
| 3.1.4 Separation of Duties | AC.L2-3.1.4 | 1 point | Allowed |
| 3.1.5 Least Privilege | AC.L2-3.1.5 | 3 points | Not allowed |
| 3.1.6 Non-Privileged Accounts | AC.L2-3.1.6 | 1 point | Allowed |
| 3.1.7 Privileged Functions | AC.L2-3.1.7 | 1 point | Allowed |
| 3.1.8 Unsuccessful Logons | AC.L2-3.1.8 | 1 point | Allowed |
| 3.1.9 System Use Notices | AC.L2-3.1.9 | 1 point | Allowed |
| 3.1.10 Session Lock | AC.L2-3.1.10 | 1 point | Allowed |
| 3.1.11 Session Termination | AC.L2-3.1.11 | 1 point | Allowed |
| 3.1.12 Remote Access Control | AC.L2-3.1.12 | 5 points | Not allowed |
| 3.1.13 Remote Access Encryption | AC.L2-3.1.13 | 5 points | Not allowed |
| 3.1.14 Remote Access Routing | AC.L2-3.1.14 | 1 point | Allowed |
| 3.1.15 Privileged Remote Access | AC.L2-3.1.15 | 1 point | Allowed |
| 3.1.16 Wireless Authorization | AC.L2-3.1.16 | 5 points | Not allowed |
| 3.1.17 Wireless Protection | AC.L2-3.1.17 | 5 points | Not allowed |
| 3.1.18 Mobile Device Connection | AC.L2-3.1.18 | 5 points | Not allowed |
| 3.1.19 Encrypt CUI on Mobile | AC.L2-3.1.19 | 3 points | Not allowed |
| 3.1.20 External Connections | AC.L2-3.1.20 | 1 point | Never |
| 3.1.21 Portable Storage Use | AC.L2-3.1.21 | 1 point | Allowed |
| 3.1.22 Public Information | AC.L2-3.1.22 | 1 point | Never |
| 3.2.1 Security Awareness | AT.L2-3.2.1 | 5 points | Not allowed |
| 3.2.2 Role-Based Training | AT.L2-3.2.2 | 5 points | Not allowed |
| 3.2.3 Insider Threat | AT.L2-3.2.3 | 1 point | Allowed |
| 3.3.1 System Audit Logs | AU.L2-3.3.1 | 5 points | Not allowed |
| 3.3.2 User Accountability | AU.L2-3.3.2 | 3 points | Not allowed |
| 3.3.3 Review Logged Events | AU.L2-3.3.3 | 1 point | Allowed |
| 3.3.4 Audit Failure Alerts | AU.L2-3.3.4 | 1 point | Allowed |
| 3.3.5 Audit Correlation | AU.L2-3.3.5 | 5 points | Not allowed |
| 3.3.6 Audit Reduction | AU.L2-3.3.6 | 1 point | Allowed |
| 3.3.7 Authoritative Time | AU.L2-3.3.7 | 1 point | Allowed |
| 3.3.8 Audit Protection | AU.L2-3.3.8 | 1 point | Allowed |
| 3.3.9 Audit Management | AU.L2-3.3.9 | 1 point | Allowed |
| 3.4.1 Baseline and Inventory | CM.L2-3.4.1 | 5 points | Not allowed |
| 3.4.2 Security Settings | CM.L2-3.4.2 | 5 points | Not allowed |
| 3.4.3 Change Control | CM.L2-3.4.3 | 1 point | Allowed |
| 3.4.4 Security Impact Analysis | CM.L2-3.4.4 | 1 point | Allowed |
| 3.4.5 Change Access Limits | CM.L2-3.4.5 | 5 points | Not allowed |
| 3.4.6 Least Functionality | CM.L2-3.4.6 | 5 points | Not allowed |
| 3.4.7 Nonessential Services | CM.L2-3.4.7 | 5 points | Not allowed |
| 3.4.8 Application Execution | CM.L2-3.4.8 | 5 points | Not allowed |
| 3.4.9 User-Installed Software | CM.L2-3.4.9 | 1 point | Allowed |
| 3.5.1 Identification | IA.L2-3.5.1 | 5 points | Not allowed |
| 3.5.2 Authentication | IA.L2-3.5.2 | 5 points | Not allowed |
| 3.5.3 Multifactor Authentication | IA.L2-3.5.3 | 3 or 5 points | Not allowed |
| 3.5.4 Replay Resistance | IA.L2-3.5.4 | 1 point | Allowed |
| 3.5.5 Identifier Reuse | IA.L2-3.5.5 | 1 point | Allowed |
| 3.5.6 Inactive Accounts | IA.L2-3.5.6 | 1 point | Allowed |
| 3.5.7 Password Complexity | IA.L2-3.5.7 | 1 point | Allowed |
| 3.5.8 Password Reuse | IA.L2-3.5.8 | 1 point | Allowed |
| 3.5.9 Temporary Passwords | IA.L2-3.5.9 | 1 point | Allowed |
| 3.5.10 Protected Passwords | IA.L2-3.5.10 | 5 points | Not allowed |
| 3.5.11 Obscured Feedback | IA.L2-3.5.11 | 1 point | Allowed |
| 3.6.1 Incident Handling | IR.L2-3.6.1 | 5 points | Not allowed |
| 3.6.2 Incident Reporting | IR.L2-3.6.2 | 5 points | Not allowed |
| 3.6.3 Incident Response Testing | IR.L2-3.6.3 | 1 point | Allowed |
| 3.7.1 System Maintenance | MA.L2-3.7.1 | 3 points | Not allowed |
| 3.7.2 Maintenance Tools | MA.L2-3.7.2 | 5 points | Not allowed |
| 3.7.3 Off-Site Maintenance | MA.L2-3.7.3 | 1 point | Allowed |
| 3.7.4 Diagnostic Media Checks | MA.L2-3.7.4 | 3 points | Not allowed |
| 3.7.5 Nonlocal Maintenance | MA.L2-3.7.5 | 5 points | Not allowed |
| 3.7.6 Maintenance Personnel | MA.L2-3.7.6 | 1 point | Allowed |
| 3.8.1 Media Protection | MP.L2-3.8.1 | 3 points | Not allowed |
| 3.8.2 Media Access | MP.L2-3.8.2 | 3 points | Not allowed |
| 3.8.3 Media Sanitization | MP.L2-3.8.3 | 5 points | Not allowed |
| 3.8.4 Media Marking | MP.L2-3.8.4 | 1 point | Allowed |
| 3.8.5 Media Transport | MP.L2-3.8.5 | 1 point | Allowed |
| 3.8.6 Encrypt Media in Transit | MP.L2-3.8.6 | 1 point | Allowed |
| 3.8.7 Removable Media | MP.L2-3.8.7 | 5 points | Not allowed |
| 3.8.8 Ownerless Storage | MP.L2-3.8.8 | 3 points | Not allowed |
| 3.8.9 Backup Confidentiality | MP.L2-3.8.9 | 1 point | Allowed |
| 3.9.1 Personnel Screening | PS.L2-3.9.1 | 3 points | Not allowed |
| 3.9.2 Personnel Actions | PS.L2-3.9.2 | 5 points | Not allowed |
| 3.10.1 Physical Access | PE.L2-3.10.1 | 5 points | Not allowed |
| 3.10.2 Facility Monitoring | PE.L2-3.10.2 | 5 points | Not allowed |
| 3.10.3 Visitor Escort | PE.L2-3.10.3 | 1 point | Never |
| 3.10.4 Physical Access Logs | PE.L2-3.10.4 | 1 point | Never |
| 3.10.5 Physical Access Devices | PE.L2-3.10.5 | 1 point | Never |
| 3.10.6 Alternate Work Sites | PE.L2-3.10.6 | 1 point | Allowed |
| 3.11.1 Risk Assessment | RA.L2-3.11.1 | 3 points | Not allowed |
| 3.11.2 Vulnerability Scanning | RA.L2-3.11.2 | 5 points | Not allowed |
| 3.11.3 Fixing Vulnerabilities | RA.L2-3.11.3 | 1 point | Allowed |
| 3.12.1 Control Assessment | CA.L2-3.12.1 | 5 points | Not allowed |
| 3.12.2 Plans of Action | CA.L2-3.12.2 | 3 points | Not allowed |
| 3.12.3 Ongoing Monitoring | CA.L2-3.12.3 | 5 points | Not allowed |
| 3.12.4 System Security Plan | CA.L2-3.12.4 | No point value | Never |
| 3.13.1 Boundary Protection | SC.L2-3.13.1 | 5 points | Not allowed |
| 3.13.2 Security Engineering | SC.L2-3.13.2 | 5 points | Not allowed |
| 3.13.3 Management Separation | SC.L2-3.13.3 | 1 point | Allowed |
| 3.13.4 Shared Resources | SC.L2-3.13.4 | 1 point | Allowed |
| 3.13.5 Public-Facing Subnets | SC.L2-3.13.5 | 5 points | Not allowed |
| 3.13.6 Deny by Default | SC.L2-3.13.6 | 5 points | Not allowed |
| 3.13.7 Split Tunneling | SC.L2-3.13.7 | 1 point | Allowed |
| 3.13.8 Encryption in Transit | SC.L2-3.13.8 | 3 points | Not allowed |
| 3.13.9 Connection Termination | SC.L2-3.13.9 | 1 point | Allowed |
| 3.13.10 Key Management | SC.L2-3.13.10 | 1 point | Allowed |
| 3.13.11 FIPS Cryptography | SC.L2-3.13.11 | 3 or 5 points | Only if not FIPS validated |
| 3.13.12 Collaborative Devices | SC.L2-3.13.12 | 1 point | Allowed |
| 3.13.13 Mobile Code | SC.L2-3.13.13 | 1 point | Allowed |
| 3.13.14 Voice over IP | SC.L2-3.13.14 | 1 point | Allowed |
| 3.13.15 Session Authenticity | SC.L2-3.13.15 | 5 points | Not allowed |
| 3.13.16 CUI at Rest | SC.L2-3.13.16 | 1 point | Allowed |
| 3.14.1 Flaw Remediation | SI.L2-3.14.1 | 5 points | Not allowed |
| 3.14.2 Malware Protection | SI.L2-3.14.2 | 5 points | Not allowed |
| 3.14.3 Security Advisories | SI.L2-3.14.3 | 5 points | Not allowed |
| 3.14.4 Malware Updates | SI.L2-3.14.4 | 5 points | Not allowed |
| 3.14.5 Malware Scanning | SI.L2-3.14.5 | 3 points | Not allowed |
| 3.14.6 Attack Monitoring | SI.L2-3.14.6 | 5 points | Not allowed |
| 3.14.7 Unauthorized Use | SI.L2-3.14.7 | 3 points | Not allowed |
How SPRS points and the CMMC POA&M work
- Score
- An SPRS score starts at 110 and loses each unmet requirement's value: 5, 3 or 1 point. The lowest possible score is -203.
- Partial credit
- Only 3.5.3 (multifactor authentication) and 3.13.11 (FIPS-validated cryptography) can lose 3 points instead of 5.
- CMMC POA&M
- Under 32 CFR 170.21 a POA&M can hold only requirements worth 1 point, plus 3.13.11 when encryption is used but not FIPS validated, never 3.1.20, 3.1.22, 3.10.3, 3.10.4, 3.10.5 or 3.12.4, and only with a score of at least 88. That leaves 47 of the 110.
- Practice numbers
- 32 CFR 170.14(c) numbers each CMMC requirement DD.L#-REQ, and CMMC Level 2's requirements are identical to NIST SP 800-171 Rev. 2, so requirement 3.1.1 is practice AC.L2-3.1.1.
Sources
- Assessment objectives
- NIST SP 800-171A (June 2018)
- Practice numbers
- 32 CFR 170.14(c), CMMC level requirements
Questions about the NIST 800-171 requirements
- Q-01
How many requirements are in NIST SP 800-171?
Rev. 2 has 110 security requirements in 14 families, from Access Control (22) to Personnel Security (2). An SPRS score counts all 110, and CMMC Level 2 assesses the same 110.
- Q-02
Is a CMMC Level 2 practice the same as a NIST 800-171 requirement?
Yes. Under 32 CFR 170.14(c), CMMC Level 2's security requirements are identical to NIST SP 800-171 Rev. 2 and are numbered DD.L2-REQ, so AC.L2-3.1.1 is requirement 3.1.1 in the Access Control domain.
- Q-03
Which NIST 800-171 requirements can go on a CMMC POA&M?
47 of the 110: those worth 1 point, plus 3.13.11 when encryption is used but not FIPS validated, minus the 6 that 32 CFR 170.21(a)(2)(iii) never allows. The score must also be at least 88, and each item must be closed within 180 days.
- Q-04
Where do the assessment objectives come from?
From NIST SP 800-171A (June 2018), which gives 320 determination statements for the 110 requirements. An assessor finds each statement satisfied or other than satisfied.
- Q-05
Are these the Rev. 3 requirements?
No. These are the 110 requirements of NIST SP 800-171 Rev. 2, the version CMMC Level 2 assesses. NIST published Rev. 3 in May 2024 with a different structure; Rev. 3 requirements are not in PolicyCortex yet.
Related pages
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.
One record for all 110 requirements, ready for the assessor.
- Published
- Last updated
- Unchanged since publication
