NIST SP 800-53: the control catalogue behind federal, FedRAMP and 800-171 compliance
SP 800-53 is the most comprehensive security and privacy control catalogue in common use, and the one every US federal system, every FedRAMP cloud service and, indirectly, every defence contractor is measured against. This guide explains how the catalogue is organised, how baselines are selected and tailored, and how to run a 800-53 programme without treating all thousand-plus controls as equal.
Revision 5 made the catalogue outcome-based and removed the word “federal” from the control statements, so that any organisation can adopt it. It integrated privacy controls into the same families, added supply chain risk management as a family, and introduced organisation-defined parameters throughout, which means a control is not fully specified until the organisation sets the values.
Nobody implements the whole catalogue. The Risk Management Framework starts by categorising the system (FIPS 199: low, moderate or high impact), selecting the matching baseline from SP 800-53B, tailoring it with overlays and parameters, and then implementing, assessing, authorising and monitoring. The system security plan records every decision along that path.
The 20 control families
Access Control (AC), Awareness and Training (AT), Audit and Accountability (AU)
Who can do what, that they know how to behave, and that actions are logged and reviewed.
Assessment, Authorization and Monitoring (CA), Configuration Management (CM), Contingency Planning (CP)
Assessing controls and authorising the system, controlling baselines and change, and recovering from disruption.
Identification and Authentication (IA), Incident Response (IR), Maintenance (MA), Media Protection (MP)
Proving identity, handling incidents, maintaining systems safely and protecting media.
Physical and Environmental Protection (PE), Planning (PL), Program Management (PM), Personnel Security (PS)
Facilities, security plans and rules of behaviour, organisation-wide programme controls, and people.
PII Processing and Transparency (PT), Risk Assessment (RA), System and Services Acquisition (SA)
Privacy processing and notices, risk assessment and vulnerability scanning, and building security into acquisition and development.
System and Communications Protection (SC), System and Information Integrity (SI), Supply Chain Risk Management (SR)
Boundary and cryptographic protections, flaw remediation and malware protection, and the supply chain family new in Rev 5.
The baselines
- Low baseline. For systems where loss would have limited adverse effect; the smallest control set.
- Moderate baseline. The most common federal and FedRAMP level; FedRAMP Moderate Rev 5 contains 323 controls.
- High baseline. For systems where loss would be severe or catastrophic; adds controls and enhancements across most families.
- Privacy baseline. Selected independently of impact level wherever PII is processed.
Who it applies to
US federal agencies and the contractors that operate systems on their behalf under FISMA; cloud service providers seeking FedRAMP authorisation; DoD systems under the DoD RMF; state agencies and healthcare, utilities and financial organisations that have adopted it as their control catalogue. Organisations pursuing SP 800-171 or CMMC meet a tailored subset of its moderate baseline.
From scope to evidence, in one system
The full Rev 5 catalogue with baselines
Scope a system to Low, Moderate or High (and Privacy), apply overlays, and set organisation-defined parameters per control, so the tailored control set and the parameter values are recorded, not scattered through a document.
Assessment against 800-53A objectives
Each control is assessed against its determination statements with evidence attached, producing the material a security assessment report and the plan of action and milestones are built from.
Continuous monitoring from your cloud
Adapters for AWS, Azure, Google Cloud, Kubernetes, Entra ID, Intune, Defender and your SIEM re-validate technical controls on a schedule, which is the ongoing authorisation evidence the RMF monitor step requires.
Inheritance and shared responsibility
Controls inherited from a FedRAMP-authorised provider or a shared service are recorded as inherited with the provider’s evidence, so the system security plan shows exactly who is responsible for what.
Crosswalk to 800-171, CSF, ISO 27001 and SOC 2
Because 800-171 and the CSF are derived from or mapped to 800-53, evidence for one supports the others, and an ISO-certified organisation sees its head start immediately.
Frequently asked questions
800-53 or 800-171: which do we need?
800-171 if you are a contractor protecting CUI in your own systems under DFARS or CMMC. 800-53 if you operate a federal information system, seek FedRAMP authorisation, or have adopted it as your enterprise catalogue. 800-171 is derived from the 800-53 moderate baseline, so they are related, not alternatives.
How many controls will we actually implement?
It depends on the baseline and tailoring. FedRAMP Moderate under Rev 5 is 323 controls; a tailored Low baseline is far smaller. The catalogue itself, with enhancements, exceeds a thousand, and nobody implements all of it.
What are organisation-defined parameters?
Values the organisation must set to complete a control statement, such as a review frequency or a lockout threshold. Rev 5 uses them extensively; an assessor expects to see the chosen value and the justification.
Does ISO 27001 certification help with 800-53?
Substantially. NIST publishes a mapping between the two, and most ISO Annex A controls satisfy one or more 800-53 controls. The gap is usually in the families ISO treats lightly, such as audit and accountability, contingency planning and supply chain.
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.