Teams that confuse NIST SP 800-53 with SP 800-171 either build a federal-grade control programme they never needed, or claim CUI compliance against a catalogue their contracting officer will not assess. SP 800-53 is the full catalogue of security and privacy controls for federal information systems and organisations; SP 800-171 is a smaller set of requirements, derived from the 800-53 moderate baseline, that federal agencies impose through contracts on nonfederal organisations holding Controlled Unclassified Information (CUI). This guide explains which one applies to you, how 800-171 is derived from 800-53, how organisation-defined parameters and assessment differ, where CMMC and FedRAMP sit, and how to avoid over-scoping. It is written for compliance leads, security architects and assessors at federal agencies, cloud providers and defence or civilian contractors. Status reflects official sources checked on 14 November 2026.
Key takeaways
- Who owns the system decides. A federal system, or a system operated on behalf of an agency, uses SP 800-53 through FISMA and the Risk Management Framework; a contractor's own system that holds CUI uses SP 800-171 through contract clauses.
- 800-171 is a derived subset, not a light version. NIST starts from the SP 800-53B moderate baseline and removes controls that are federal responsibilities, not about CUI confidentiality, covered elsewhere, or not applicable.
- The revision you build to depends on the customer. NIST's current edition is SP 800-171 Rev. 3 (May 2024), but DoD contracts and CMMC Level 2 still assess the 110 requirements of Rev. 2; SP 800-53 Rev. 5 is at Release 5.2.0 (27 August 2025).
- Parameters move from the agency to you. Both documents use organisation-defined parameters (ODPs); in 800-171 Rev. 3 NIST sets none, so the agency or the contractor must assign them.
- Over-scoping is the costliest mistake. Applying the whole 800-53 catalogue to a CUI enclave, or putting the whole corporate network in CUI scope, multiplies cost without improving the assessment result.
The short answer: which applies to you
| Your situation | Applies | Why | Assessed how |
|---|---|---|---|
| Federal agency system | SP 800-53 (baseline from SP 800-53B) | FISMA and OMB Circular A-130; RMF (SP 800-37) | SP 800-53A procedures, authorisation to operate (CA-6) |
| Contractor operating a system on behalf of an agency | SP 800-53, as the contract specifies | The system is a federal information system even if a contractor runs it | Agency RMF authorisation |
| Cloud service sold to federal agencies | FedRAMP baseline built on SP 800-53 | FedRAMP authorises at LI-SaaS, Low, Moderate or High | FedRAMP assessment by a third-party assessor |
| Defence contractor holding CUI | SP 800-171 Rev. 2 (110 requirements) | DFARS 252.204-7012 and CMMC Level 2 | SPRS score, CMMC self or third-party assessment |
| Civilian agency contractor holding CUI | SP 800-171, revision as the contract states | Agency contract terms and the CUI programme (32 CFR Part 2002) | As the contract specifies, often SP 800-171A |
| Contractor holding only Federal Contract Information | FAR 52.204-21 basic safeguarding (CMMC Level 1 where it applies) | No CUI, so 800-171 is not triggered | Annual self-assessment |
| Private sector, no federal data | Neither is mandatory | Either may be adopted voluntarily as a control reference | Your own or a customer's assurance process |
Both documents may apply to one company: a defence prime can operate a federal system for one programme (800-53) and hold CUI in its own enclave for another (800-171). Keep them as separate scopes with separate evidence. For FISMA and RMF context, see the FISMA Guide and the NIST Risk Management Framework (SP 800-37) Guide.
Side-by-side comparison
| Aspect | SP 800-53 Rev. 5 | SP 800-171 Rev. 3 |
|---|---|---|
| Purpose | Catalogue of security and privacy controls for information systems and organisations | Requirements to protect the confidentiality of CUI in nonfederal systems and organisations |
| Security objectives | Confidentiality, integrity and availability, plus privacy | Confidentiality of CUI; integrity where the same mechanisms serve both |
| Size | 20 control families; Release 5.2.0 holds about 300 active base controls and over 700 enhancements | 97 requirements in 17 families |
| Selection | Choose a low, moderate or high baseline (SP 800-53B) from FIPS 199 categorisation, then tailor | Fixed set; CUI is categorised at no less than FIPS 199 moderate confidentiality |
| Privacy | Integrated (PT family and privacy baseline) | Not in scope |
| Parameters | ODPs assigned by the organisation, or by FedRAMP, an overlay or the agency | NIST sets none; the agency or contractor assigns them |
| Assessment procedures | SP 800-53A | SP 800-171A (Rev. 3 for Rev. 3; June 2018 edition for Rev. 2) |
| Outcome | Authorisation decision on residual risk | Contract compliance: a score, a status or an assessment result |
| Numbering | Family plus number, e.g. IA-2(1) | 03.FF.NN, e.g. 03.05.03 |
Release figures for 800-53 are from the live NIST SP 800-53 Guide, which counts them from NIST's OSCAL catalogue.
How 800-171 is derived from 800-53
Section 2.2 of SP 800-171 Rev. 3 explains that NIST starts from the SP 800-53B moderate baseline and tailors it. Appendix C records the decision for every moderate control with one of five symbols:
| Symbol | Meaning (SP 800-171 Rev. 3, Appendix C) | What it means for you |
|---|---|---|
| CUI | The control is directly related to protecting the confidentiality of CUI | It becomes a requirement you implement and evidence |
| NCO | Not directly related to protecting the confidentiality of CUI | Not required by 800-171, though it may be good practice (availability controls, for example) |
| FED | Primarily the responsibility of the federal government | Not your requirement; the agency carries it |
| ORC | The outcome is adequately covered by other related controls | Satisfied through the related requirement |
| N/A | The control is not applicable | No action |
This is why 800-171 is not simply a subset of 800-53. Requirements are reworded for nonfederal organisations, some combine several 800-53 controls, and control enhancements are folded in. For example, 03.05.03 Multi-Factor Authentication draws on IA-2 and its enhancements, 03.13.11 Cryptographic Protection traces to SC-13, and 03.15.02 System Security Plan traces to PL-2. NIST publishes the full trace in the 800-171 Rev. 3 CUI overlay spreadsheet and the Rev. 2 to Rev. 3 change analysis on the publication page.
- Practical use: if you already run an 800-53 moderate programme, map your controls through the overlay and you will find most 800-171 requirements covered, with gaps mainly in ODP values and contractor-specific evidence.
- Reverse direction: an 800-171 programme does not give you 800-53 moderate. Controls marked NCO or FED, such as most availability and privacy controls and agency programme management (the PM family), are absent.
- Enhanced requirements: for CUI tied to critical programmes, SP 800-172 adds enhanced requirements on top of 800-171. See the NIST SP 800-172 Rev 3 Guide.
Organisation-defined parameters: who fills the blanks
An ODP is a variable in a control or requirement, such as a lockout threshold, a log review frequency or a password length. Until it has a value, the control cannot be implemented consistently or tested.
| Question | SP 800-53 | SP 800-171 Rev. 3 |
|---|---|---|
| Who sets the value | The organisation, often constrained by FedRAMP parameter values, an overlay or agency policy | Federal agencies or a consortium of agencies may specify values; otherwise the nonfederal organisation assigns them |
| Example | AC-7: number of consecutive invalid logon attempts and time period | 03.01.08 Unsuccessful Logon Attempts: the same variables, set per contract |
| Where recorded | System security and privacy plan (PL-2) | System security plan (03.15.02) |
| Rev. 2 contrast | Not applicable | Rev. 2 requirements had fixed wording; ODPs arrived with Rev. 3 |
DoD published its own ODP values for Rev. 3 in April 2025 but has not mandated Rev. 3 for DFARS 7012 or CMMC, as covered in the NIST SP 800-171 Rev 3 Transition. A contractor serving several agencies should record the most restrictive value per ODP and note the source of each value.
Assessment: 800-53A versus 800-171A and CMMC
- SP 800-53A: assessment procedures for each 800-53 control using examine, interview and test methods, applied by an agency assessor or a FedRAMP third-party assessor. The result feeds a risk-based authorisation decision and a plan of action and milestones (CA-5); a gap does not automatically fail the system. See the NIST SP 800-53A Guide.
- SP 800-171A: assessment objectives per requirement with the same three methods. For DoD, the score goes into SPRS under DFARS 252.204-7019 and -7020. See the NIST SP 800-171A Rev 3 Assessment Guide.
- CMMC: verifies the 800-171 Rev. 2 requirements at Level 2 by self-assessment or third-party assessment. Phase 1 of the rollout has been in force since 10 November 2025. According to law firm Hunton Andrews Kurth (10 November 2026), the DoD CIO paused Phase II on 13 July 2026 and the pause remains in effect with no announced end date; Level 1 and Level 2 self-assessments still apply where CMMC is in a contract. See the NIST SP 800-171 and CMMC 2.0 Guide.
The difference that matters: 800-53 assessment informs a risk acceptance decision by an authorising official; 800-171 and CMMC assessment determine contract eligibility, with fixed scoring rules and limited room for accepted risk.
Threat model and architecture for each
SP 800-53: protecting a federal mission system
The threat model is broad: hostile attacks, human error, natural disasters, structural failures, foreign intelligence activity and privacy risks, as the publication abstract lists. The architecture is a defined authorisation boundary with a categorised impact level, inherited common controls from the agency or cloud provider, and continuous monitoring (CA-7). Failure modes are mostly governance failures: baselines copied without tailoring, ODPs left blank, inherited controls assumed rather than documented, and continuous monitoring that stops after the authorisation.
SP 800-171: protecting CUI outside federal control
The threat model is narrower and sharper: exfiltration of CUI from contractor networks, including through suppliers and managed service providers. The architecture is usually a CUI enclave: a segmented set of systems, identities and cloud tenants where CUI is processed, stored or transmitted, plus the security protection assets (identity provider, SIEM, endpoint management) that protect them. Failure modes: CUI spreading by email outside the enclave, protection assets left out of scope, and cloud services used for CUI that do not meet DFARS 7012 cloud expectations. See the CMMC Scoping Guide and the CUI Guide.
Decision criteria and worked scenario
- Federal system or contractor system: read the contract. Language about operating an information system on behalf of the government points to 800-53 and an agency authorisation; DFARS 252.204-7012 or an agency CUI clause points to 800-171.
- CUI or only FCI: if no CUI is marked or identified in the contract, the basic FAR 52.204-21 controls apply instead.
- Revision: DoD work builds to Rev. 2 numbering with a Rev. 3 crosswalk; civilian work follows the contract.
- Cloud provider for CUI: a cloud service used to hold DoD CUI needs FedRAMP Moderate or equivalence under DFARS 7012, which brings an 800-53 based baseline to the provider while the contractor still answers to 800-171. See the FedRAMP Guide and the DFARS 252.204-7012 Guide.
- Small versus large organisation: a small contractor should keep CUI in one enclave or a single compliant cloud tenant and use 800-171 alone; a large group with federal systems and CUI programmes benefits from one 800-53 based control library with an 800-171 view generated through the overlay.
Worked scenario: a 200-person engineering firm wins a DoD subcontract with DFARS 7012 and receives export-controlled drawings marked CUI. Its IT lead proposes adopting the full 800-53 moderate baseline. That would add availability, privacy and programme controls no one will assess, while missing what the prime will ask for: a Rev. 2 SSP, an SPRS score and CMMC Level 2 readiness. The better plan is an enclave for engineering workstations and a compliant cloud tenant, the identity provider and SIEM in scope as protection assets, Rev. 2 requirements documented with a Rev. 3 crosswalk and ODP values recorded, and a self-assessment scored before bidding further work. If the firm later hosts a system for an agency, that system gets its own 800-53 boundary.
Where identity fits
Both documents treat non-human identities as in scope. In 800-53, AC-2 Account Management covers service accounts and IA-5 Authenticator Management covers authenticators for devices and services; in 800-171 Rev. 3, 03.01.01 Account Management and 03.05.12 Authenticator Management carry the same duties for the CUI enclave. Service accounts used by backup, scanning and RMM tools that touch CUI are in scope, and their secrets need rotation and storage evidence. Multi-factor requirements (IA-2(1), 03.05.03) apply to privileged access, including MSP technicians. See the Cybersecurity for MSPs and MSSPs Guide.
Framework mapping for common control themes
| Theme | SP 800-53 Rev. 5 | SP 800-171 Rev. 3 | NIST CSF 2.0 |
|---|---|---|---|
| Accounts and service accounts | AC-2 | 03.01.01 | PR.AA |
| Lockout | AC-7 | 03.01.08 | PR.AA |
| MFA | IA-2(1) | 03.05.03 | PR.AA |
| Authenticators and secrets | IA-5 | 03.05.12 | PR.AA |
| Logging | AU-2 | 03.03.01 | DE.CM |
| Risk assessment | RA-3 | 03.11.01 | ID.RA |
| Cryptography | SC-13 | 03.13.11 | PR.DS |
| Security plan | PL-2 | 03.15.02 | GV.PO |
| Supply chain plan | SR-2 | 03.17.01 | GV.SC |
| Assessment and monitoring | CA-2, CA-7 | 03.12.01 | ID.IM, DE.CM |
For the ISO view, see the NIST SP 800-53 to ISO 27001 Mapping Guide. For machine-readable control data, see the OSCAL Guide.
Implementing the right one: a phased approach
- Classify obligations. List every contract and system; tag each as federal system (800-53), CUI (800-171 with revision), FCI only, or none.
- Draw boundaries. For 800-53, the authorisation boundary; for 800-171, the CUI enclave and protection assets. Test the boundary by tracing where CUI actually flows, including email and file sharing.
- Select and tailor. For 800-53, pick the SP 800-53B baseline from FIPS 199 categorisation and tailor with overlays. For 800-171, take the full requirement set; tailoring is not offered to the contractor.
- Assign ODPs. Record each value, its source (agency, DoD, FedRAMP or internal) and its owner in the security plan.
- Self-assess before the external test. Run 800-53A or 800-171A procedures internally; pilot on one boundary before extending.
- Remediate with dated plans. Track gaps in a POA&M; for CMMC, respect the scoring and closure rules in the CMMC guide.
- Monitor and re-baseline. Track new 800-53 releases and DoD decisions on Rev. 3; a crosswalk kept current turns a revision change into a documentation update. Rollback is simple: if a contract reverts to Rev. 2, the Rev. 2 numbering remains your primary index.
Measuring it
- Percentage of contracts and systems with a recorded 800-53 or 800-171 classification and revision.
- Percentage of ODPs with an assigned value and source.
- Number of systems outside the CUI enclave found holding CUI in discovery scans (target zero).
- Self-assessed SPRS score trend and open POA&M items past due date.
- Percentage of service accounts in scope with an owner and rotation evidence.
Common failure patterns
- Over-scoping with 800-53: adopting the full catalogue for a CUI contract wastes effort on controls marked NCO or FED and delays the evidence the assessor actually wants.
- Over-scoping the enclave: putting the whole corporate network in CUI scope because CUI is emailed freely; fix the data flow first.
- Under-scoping protection assets: leaving the identity provider, SIEM or MSP tooling out of scope even though they protect CUI systems.
- Building to the wrong revision: writing the SSP to Rev. 3 numbering for a DoD contract that is assessed against Rev. 2.
- Blank ODPs: a requirement with no assigned value cannot be shown as implemented.
- Treating 800-171 as satisfied by a FedRAMP cloud: the provider's authorisation covers its controls, not the contractor's configuration and use of the tenant.
Practitioner checklist
- Read each contract for DFARS 252.204-7012, FAR 52.204-21, agency CUI clauses or language about operating a federal system.
- Record the applicable document and revision per contract, with the date checked.
- Define the CUI enclave and list protection assets in scope.
- Assign and document every ODP with its source.
- Keep Rev. 2 and Rev. 3 numbering side by side for DoD work.
- Use the 800-171 Rev. 3 CUI overlay to reuse an existing 800-53 programme.
- Self-assess with the matching A-series procedures before any external assessment.
- Inventory service accounts and secrets that touch CUI or federal systems.
- Re-check CMMC rollout status and 800-53 releases each quarter.
Standards and references
- NIST: SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations
- NIST: SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations
- NIST: SP 800-171 Rev. 3 full text (PDF)
- NIST: SP 800-53B, Control Baselines for Information Systems and Organizations
- FedRAMP: Baselines
- DoD CIO: Cybersecurity Maturity Model Certification
- Hunton Andrews Kurth: CMMC Phase 2 Remains Paused
Related NHI Mgmt Group resources: NIST SP 800-53 Guide · NIST SP 800-171 and CMMC 2.0 Guide · NIST SP 800-53A Guide · CMMC Level 1 vs Level 2 vs Level 3 · NIST SP 800-53 Privacy Controls and FIPS 199/200 Categorisation Guide