NIST SP 800-171: protecting CUI in contractor systems
SP 800-171 is the set of security requirements that any non-federal organisation must meet when it handles Controlled Unclassified Information for a US agency. It is the backbone of CMMC and of the DFARS clauses in defence contracts, and it is increasingly cited by civilian agencies too. This guide covers the requirements, the two current revisions and the reporting obligations that come with them.
The requirements are deliberately written as outcomes rather than technologies: limit system access to authorised users, use MFA for network access to privileged accounts, encrypt CUI on mobile devices, and so on. Each one has assessment objectives in SP 800-171A that say precisely what an assessor checks. Treating those objectives as the real checklist is the difference between a system security plan that survives an assessment and one that does not.
Revision 3 reorganised the requirements, removed some, merged others and added three families (Planning, System and Services Acquisition, Supply Chain Risk Management). It also introduced organisation-defined parameters, so the organisation sets values such as review frequencies that Rev 2 left implicit.
What a compliant programme contains
A CUI inventory and system boundary
Where CUI enters, is stored, processed and transmitted. Everything inside that boundary is in scope; the smaller and better defined it is, the cheaper compliance becomes.
A system security plan (SSP)
Required by requirement 3.12.4. Describes the boundary, the environment and how each of the requirements is implemented. Assessors read it before they look at anything else.
A plan of action and milestones (POA&M)
Requirement 3.12.2. Every unimplemented requirement, with the fix, the owner and the date. Under CMMC, POA&Ms are limited and time-boxed.
An assessment against 800-171A objectives
Self-assessment under the DoD methodology, producing the score posted to SPRS, and the evidence per objective that backs it.
Incident reporting capability
DFARS 7012 requires cyber incidents affecting CUI to be reported to DoD within 72 hours, images preserved for 90 days and access provided to DoD on request.
Cloud and subcontractor flow-down
Cloud services holding CUI must meet FedRAMP Moderate or equivalent; the requirements flow down to subcontractors who receive CUI.
Who it applies to
Any non-federal organisation that handles CUI under a federal contract or agreement: defence contractors and their subcontractors under DFARS, and increasingly contractors to civilian agencies under the proposed FAR CUI rule. Universities and research institutions with federal research data, and non-US suppliers to US primes, are in scope when they receive CUI.
From scope to evidence, in one system
Both revisions, selectable per system
Scope a system to Rev 2 for DFARS and CMMC, or Rev 3 where a contract or agency specifies it, with the requirement families and assessment objectives of that revision.
Objective-level assessment and scoring
Each requirement is assessed against its 800-171A objectives with evidence attached; the gap view shows where points are lost under the DoD methodology and what closes them.
Evidence from Microsoft 365, Entra, Intune, Defender, AWS and Azure
Read-only adapters collect the access, authentication, logging, configuration and integrity settings that prove the technical requirements, and keep them current between assessments.
Crosswalk to 800-53, ISO 27001 and SOC 2
Requirements are mapped to their 800-53 Rev 5 sources and to ISO 27001 and SOC 2, so evidence gathered for one programme supports the others.
Policy set and SSP material
The AI Policy Builder writes the policies the requirements call for, and control status with narrative exports as the basis of the SSP and POA&M.
Frequently asked questions
Rev 2 or Rev 3: which applies to us?
DFARS 7012 and CMMC Level 2 currently point to Rev 2 under a DoD class deviation. Use Rev 2 for defence work until DoD says otherwise; use Rev 3 if a non-DoD contract or agreement specifies it. GRCorb lets you assess against either.
What exactly is CUI?
Information the federal government creates or possesses, or that an entity creates on its behalf, that a law, regulation or government-wide policy requires to be safeguarded or controlled. The National Archives maintains the CUI Registry of categories; your contract or the agency marks what is CUI.
Is a self-assessment enough?
For DFARS 7019 a self-assessment score in SPRS is required at minimum. For CMMC Level 2 on most contracts a C3PAO certification assessment is required. Either way the evidence has to exist; the difference is who examines it.
How does 800-171 relate to 800-53?
800-171 is derived from the moderate baseline of 800-53, tailored to contractor systems. Rev 3 makes the mapping explicit. Organisations that already run 800-53 for a federal system have most of the work done.
Related frameworks
Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.