Standard · CUI · US federal contractors
NIST 800-171 compliance: the 110 requirements, Rev 3 and SPRS scoring
NIST 800-171 compliance means protecting Controlled Unclassified Information with the security requirements in NIST SP 800-171. US defense contractors must meet the 110 requirements of Revision 2 under DFARS 252.204-7012, even though Revision 3 (97 requirements) was published in May 2024, and post a self-assessment score in SPRS.
What you need to know about NIST 800-171
Who must comply with NIST 800-171?
Non-federal organisations that process, store or transmit CUI for the US government.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does NIST 800-171 require?
NIST 800-171 requires you to protect the confidentiality of CUI on your systems through 110 requirements in 14 families (Revision 2), document them in a System Security Plan, and track gaps in a plan of action.
Access Control
22 requirements on who and what can reach CUI.
In QULDEX: Access reviews on scheduleIdentification and Authentication
MFA for privileged and network access.
In QULDEX: MFA coverage trackedAudit and Accountability
Traceable, protected logs.
In QULDEX: Log reviews as evidenceSecurity Assessment
System Security Plan and POA&M.
In QULDEX: SSP linked to live evidenceSystem and Communications Protection
Boundary protection and FIPS-validated crypto.
In QULDEX: Network evidenceSelf-assessment score
110 minus weighted deductions, posted to SPRS.
In QULDEX: Score calculated from statusWhat are the NIST 800-171 control families?
Revision 2 has 14 families and 110 requirements; Revision 3 adds three families. Select any family to see what it covers, typical evidence and the matching NIST 800-53 and ISO 27001 references.
Showing up to 6 per group. Search, filter, or open a group to see all 17.
Revision 2 families 14
3.1Access ControlLimit system access to authorised users, processes and devices, and to permitted transactions and functions. (22 requirements)
In QULDEXAccess reviews run as recurring tasks; MFA and session settings are evidence.
- Typical evidence
- Access policy, access reviews
- Maps to
- NIST 800-53 ACISO 27001 A.5.15
3.2Awareness and TrainingMake sure staff know security risks and are trained for their duties, including insider threat. (3 requirements)
In QULDEXEach requirement in this family is pre-mapped with its NIST SP 800-171A objectives and an evidence request.
- Typical evidence
- Training records
- Maps to
- NIST 800-53 ATISO 27001 A.6.3
3.3Audit and AccountabilityCreate, protect and review logs so actions can be traced to individual users. (9 requirements)
In QULDEXEach requirement in this family is pre-mapped with its NIST SP 800-171A objectives and an evidence request.
- Typical evidence
- Log configuration, review records
- Maps to
- NIST 800-53 AUISO 27001 A.8.15
3.4Configuration ManagementSet and enforce baseline configurations and control changes, software and functions. (9 requirements)
In QULDEXEach requirement in this family is pre-mapped with its NIST SP 800-171A objectives and an evidence request.
- Typical evidence
- Baselines, change records
- Maps to
- NIST 800-53 CMISO 27001 A.8.9
3.5Identification and AuthenticationIdentify and authenticate users and devices, with MFA for privileged and network access. (11 requirements)
In QULDEXMFA coverage is tracked per system.
- Typical evidence
- MFA settings, password policy
- Maps to
- NIST 800-53 IAISO 27001 A.8.5
3.6Incident ResponseEstablish incident handling, track and report incidents, and test the capability. (3 requirements)
In QULDEXIncidents run with DFARS 72-hour reporting timers.
- Typical evidence
- IR plan, test records
- Maps to
- NIST 800-53 IRISO 27001 A.5.24
3.7MaintenancePerform and control system maintenance, including remote and off-site maintenance. (6 requirements)
In QULDEXEach requirement in this family is pre-mapped with its NIST SP 800-171A objectives and an evidence request.
- Typical evidence
- Maintenance logs
- Maps to
- NIST 800-53 MA
3.8Media ProtectionProtect, mark, control and sanitise media containing CUI. (9 requirements)
In QULDEXEach requirement in this family is pre-mapped with its NIST SP 800-171A objectives and an evidence request.
- Typical evidence
- Media policy, sanitisation records
- Maps to
- NIST 800-53 MPISO 27001 A.7.10
3.9Personnel SecurityScreen people before access to CUI and protect CUI during terminations and transfers. (2 requirements)
In QULDEXEach requirement in this family is pre-mapped with its NIST SP 800-171A objectives and an evidence request.
- Typical evidence
- Screening and offboarding records
- Maps to
- NIST 800-53 PSISO 27001 A.6.1
3.10Physical ProtectionLimit physical access, escort visitors, keep access logs and protect alternate work sites. (6 requirements)
In QULDEXEach requirement in this family is pre-mapped with its NIST SP 800-171A objectives and an evidence request.
- Typical evidence
- Visitor logs, badge records
- Maps to
- NIST 800-53 PEISO 27001 A.7.2
3.11Risk AssessmentAssess risk periodically, scan for vulnerabilities and remediate them. (3 requirements)
In QULDEXScan results become CAPA items with due dates.
- Typical evidence
- Risk assessment, scan reports
- Maps to
- NIST 800-53 RAISO 27001 A.8.8
3.12Security AssessmentAssess controls periodically, run plans of action, monitor continuously and keep a System Security Plan. (4 requirements)
In QULDEXThe SSP is linked to live evidence, not a static document.
- Typical evidence
- SSP, POA&M
- Maps to
- NIST 800-53 CAISO 27001 9.2
3.13System and Communications ProtectionMonitor and protect communications at boundaries, separate functions and use FIPS-validated cryptography for CUI. (16 requirements)
In QULDEXEach requirement in this family is pre-mapped with its NIST SP 800-171A objectives and an evidence request.
- Typical evidence
- Network diagrams, crypto evidence
- Maps to
- NIST 800-53 SCISO 27001 A.8.20
3.14System and Information IntegrityFix flaws promptly, protect against malicious code and monitor systems and alerts. (7 requirements)
In QULDEXEach requirement in this family is pre-mapped with its NIST SP 800-171A objectives and an evidence request.
- Typical evidence
- Patch records, EDR evidence
- Maps to
- NIST 800-53 SIISO 27001 A.8.7
New in Revision 3 3
03.15PlanningRev 3 newRev 3 adds planning requirements such as policies and procedures and rules of behaviour. (Rev 3 family)
In QULDEXRev 3 families are mapped so you can move when DoD adopts Rev 3.
- Maps to
- NIST 800-53 PL
03.16System and Services AcquisitionRev 3 newRev 3 adds security engineering principles, unsupported components and external system services. (Rev 3 family)
In QULDEXRev 3 families are mapped so you can move when DoD adopts Rev 3.
- Maps to
- NIST 800-53 SA
03.17Supply Chain Risk ManagementRev 3 newRev 3 adds a supply chain risk management plan, acquisition strategies and supplier requirements. (Rev 3 family)
In QULDEXSupplier records in the vendor register support this family.
- Maps to
- NIST 800-53 SR
Nothing matches that search.
Family numbers follow NIST SP 800-171 Rev 2 (3.x) and Rev 3 (03.x). Requirement counts are for Rev 2. Summaries are QULDEX paraphrases.
How do you comply with NIST 800-171?
Scope where CUI lives, implement the 110 requirements, write the SSP, then score yourself and post it to SPRS. Most organisations need 6 to 12 months; a CUI enclave can shorten that.
Find and scope CUI
Map where CUI enters, is stored and leaves, and define the system boundary.
Gap assessment against 800-171A
Assess each requirement against its assessment objectives.
Write the System Security Plan
Describe how each requirement is met and the system boundary.
Remediate and track a POA&M
Close gaps, starting with high-weight requirements such as MFA and encryption.
Score and post to SPRS
Calculate the score and post it with the SSP date.
Keep it current
ContinuouslyMonitor and update the SSPEvery 3 yearsRefresh the SPRS assessment at leastOn changeRe-score after major changes
Durations are QULDEX planning ranges.
Which documents does NIST 800-171 need?
The standard names two documents outright; assessors expect the rest.
| Document | Requirement | Where it lives in QULDEX |
|---|---|---|
| System Security Plan | 3.12.4 | Policy library |
| Plan of Action and Milestones | 3.12.2 | CAPA automation |
| CUI data-flow and network diagrams | 3.13.1 | Evidence vault |
| Access control policy and reviews | 3.1 | Policy library |
| Incident response plan and tests | 3.6.1, 3.6.3 | Evidence vault |
| Configuration baselines | 3.4.1 | Evidence vault |
| Risk assessment and scan reports | 3.11.1–3.11.2 | Risk register |
| SPRS score record | DFARS 252.204-7019 | Evidence vault |
Requirement numbers follow NIST SP 800-171 Rev 2.
How long does NIST 800-171 take and what drives the effort?
Most organisations need 6 to 12 months. The size of the CUI environment and gaps in high-weight requirements such as MFA, encryption and logging drive most of the effort.
Where the time goes
Bars show the upper end of each range on one scale (12 months = full width).
What changes the effort
- CUI footprint: an enclave keeps the boundary small
- High-weight gaps: 5-point requirements cost the most score
- Cloud services: need FedRAMP Moderate or equivalent
- Legacy systems: may need compensating measures
- Existing ISO 27001: covers part of the requirements
How ready are you for NIST 800-171?
Check these eight things first. Nothing you enter leaves this page.
How NIST 800-171 maps to CMMC, NIST 800-53 and ISO 27001
NIST 800-171 is derived from NIST 800-53 Moderate, and CMMC Level 2 assesses it directly. ISO 27001 evidence covers part of it.
Revision 2 vs Revision 3 at a glance
| NIST SP 800-171 Rev 2 | NIST SP 800-171 Rev 3 | |
|---|---|---|
| Published | 2020 (with updates) | May 2024 |
| Requirements | 110 | 97 |
| Families | 14 | 17 (adds PL, SA, SR) |
| Parameters | Fixed | Organisation-defined parameters |
| Required by DFARS 7012 | Yes, via class deviation | Not yet |
| In QULDEX | QULDEX maps both revisions, so moving to Rev 3 reuses Rev 2 evidence. | |
NIST 800-171 crosswalk
| NIST 800-171 Rev 2 | CMMC Level 2 | NIST 800-53 Rev 5 | ISO 27001:2022 | Shared evidence |
|---|---|---|---|---|
| 3.1 Access Control | AC | AC | A.5.15–A.5.18 | Access reviews |
| 3.3 Audit | AU | AU | A.8.15 | Log samples |
| 3.4 Configuration | CM | CM | A.8.9 | Baselines |
| 3.5 Identification | IA | IA | A.8.5 | MFA settings |
| 3.6 Incident Response | IR | IR | A.5.24–A.5.26 | IR plan |
| 3.11 Risk Assessment | RA | RA | 6.1.2, A.8.8 | Scan reports |
| 3.12 Security Assessment | CA | CA, PL | 9.2 | SSP, POA&M |
| 3.13 Communications | SC | SC | A.8.20–A.8.24 | Network diagrams |
Indicative mapping for planning. CMMC vs NIST 800-171 is compared in full on the blog.
How QULDEX runs NIST 800-171 from SSP to SPRS score
QULDEX is NIST 800-171 compliance and audit management software built from EGV Group's audit delivery, used by contractors, their advisors and the assessors who check them. Pick your role to see who does what.
For organisations handling CUI.
- ScopeScope CUIBoundary and asset categories
- SSPWrite the SSPSSP linked to live evidence
- FixRemediate gapsPOA&M with owners and dates
- ScorePost to SPRSScore calculated from status
- MonitorKeep evidence currentRecurring evidence requests
- Rev 3Plan the moveRev 2 to Rev 3 mapping
For RPOs, consultants and internal audit.
- ScopeRun the gap assessmentA reusable 800-171A gap template
- SSPReview the SSPComments per requirement
- FixPrioritise by weightScore impact per gap
- ScoreValidate the scoreScore history
- MonitorQuarterly reviewDashboard across clients
- Rev 3Advise on timingGap list for new families
For C3PAOs and DIBCAC-style reviews.
- ScopePlanScope in a standard format
- SSPReview documentsView-only document access
- FixCheck fixesClose-out evidence
- ScoreAssess objectivesView-only evidence with download control and an access log
- MonitorReassessHistory of assessments
- Rev 3AdviseFindings into CAPA
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →NIST 800-171 questions people ask
Which revision of NIST 800-171 applies?
For defense contracts, Revision 2. A DoD class deviation keeps DFARS 252.204-7012 tied to Rev 2 (110 requirements), although NIST published Rev 3 (97 requirements) in May 2024.
How many requirements are in NIST 800-171?
Revision 2 has 110 requirements in 14 families. Revision 3 has 97 requirements in 17 families, adding planning, system and services acquisition, and supply chain risk management.
How is the SPRS score calculated?
You start at 110 and subtract 1, 3 or 5 points for each requirement not met, according to the DoD Assessment Methodology, so the lowest possible score is −203.
How does NIST 800-171 relate to CMMC?
CMMC Level 2 assesses the same 110 NIST SP 800-171 Rev 2 requirements, either by self-assessment or by a C3PAO.
Who must comply with NIST 800-171?
Non-federal organisations that process, store or transmit CUI under a contract requiring it, most often defense contractors and subcontractors through DFARS 252.204-7012.
Go deeper on NIST 800-171
NIST & CIS topic hub
NIST CSF, 800-53 and CIS Controls articles.
blog.quldex.comAudit evidence naming convention
A file-naming scheme assessors can follow.
blog.quldex.comAudit sampling size for compliance
How many samples assessors look at.
blog.quldex.comNIST CSF 2.0: the Govern function explained
Governance outcomes that support an 800-171 programme.
References
- NIST SP 800-171 Rev 2 and Rev 3 (May 2024). csrc.nist.gov
- NIST SP 800-171A, assessment procedures. csrc.nist.gov
- DFARS 252.204-7012, 7019 and 7020. acquisition.gov
- DFARS class deviation 2026-O0025 (Rev 3). acq.osd.mil
- DoD Assessment Methodology for NIST SP 800-171. acq.osd.mil
Reviewed by
Page history
- : Page first built: family explorer for Rev 2 and Rev 3, SPRS scoring and readiness check
Know your SPRS score before your next bid
Answer a short readiness check and get a gap summary by family. No sales call needed to see the result.