
NIST Special Publication 800-53: Controls, Families and Compliance Explained
NIST Special Publication 800-53 is the security control catalogue that US federal agencies use to protect their information systems. Its full title is Security and Privacy Controls for Federal Information Systems and Organizations, and it is published by the National Institute of Standards and Technology (NIST). If you work with federal systems, or sell products and services to the US government, you will meet SP 800-53 sooner or later.
In this guide, we explain what NIST Special Publication 800-53 is, who must use it, how its control families and baselines work, and how organisations put it into practice. You will also learn how it relates to other frameworks, such as the NIST Cybersecurity Framework and FedRAMP, and how to start a compliance project without getting lost in the catalogue.
What Is NIST Special Publication 800-53?
NIST Special Publication 800-53, usually called NIST 800-53, is a catalogue of security and privacy controls. A control is a safeguard or measure that reduces risk, such as requiring multi-factor authentication, encrypting data at rest, keeping audit logs, or training staff to recognise phishing.
The current version, Revision 5, was published in September 2020. It contains more than 1,000 controls and control enhancements, organised into 20 control families. Each control has an identifier, a description, discussion, and references to related controls. The catalogue does not tell an organisation exactly which controls to use. Instead, it gives a menu, and the organisation selects a baseline that matches the impact level of its system.
SP 800-53 is a publication, not a law. Its force comes from the laws and rules that point to it. The Federal Information Security Modernization Act (FISMA) requires federal agencies to protect their information systems, and NIST’s standards and guidelines, including SP 800-53, provide the way to do that. Federal agencies must comply with FISMA, and their contractors must meet SP 800-53 requirements in their contracts.
Who Must Use NIST 800-53?
SP 800-53 applies directly to federal agencies and their contractors. If you run a system for the US government, or you provide a cloud service to a federal agency, SP 800-53 is part of your compliance work. Cloud service providers that want FedRAMP authorisation, for example, must show that they meet the SP 800-53 controls in the FedRAMP baseline.
It is also used voluntarily by many other organisations. State and local governments, universities, hospitals, and companies in regulated industries use SP 800-53 as a comprehensive checklist for security controls, even when they are not legally required to do so. It is one of the most detailed control catalogues available, and it is free to download from NIST.
Private companies often use it alongside other rules. A company that handles personal data, for example, may need to meet both SP 800-53 and privacy rules. Our guide to the Children’s Online Privacy Protection Act explains one such privacy rule, for organisations that collect data from children, and shows how security controls and privacy duties fit together.
The catalogue is large, but its structure is simple. Controls are grouped into families, each family covers one area of security or privacy, and each system selects a baseline based on its impact level.
The 20 Control Families of NIST 800-53
| Family | Code | What it covers |
|---|---|---|
| Access Control | AC | Who can access systems and data |
| Awareness and Training | AT | Security training for staff |
| Audit and Accountability | AU | Logging and audit trails |
| Assessment, Authorisation and Monitoring | CA | Testing and authorising systems |
| Configuration Management | CM | Secure configuration and change control |
| Contingency Planning | CP | Backup and recovery |
| Identification and Authentication | IA | User identity and passwords, MFA |
| Incident Response | IR | Detecting and handling incidents |
| Maintenance | MA | Maintaining systems safely |
| Media Protection | MP | Protecting storage media |
| Physical Protection | PE | Physical security of facilities |
| Planning | PL | Security planning |
| Program Management | PM | Organisation-wide security programme |
| Personnel Security | PS | Staff screening and offboarding |
| Risk Assessment | RA | Identifying and assessing risk |
| System and Services Acquisition | SA | Buying secure systems |
| System and Communications Protection | SC | Network and data protection |
| System and Information Integrity | SI | Malware, patching, integrity |
| Supply Chain Risk Management | SR | Managing supplier risk |
| Privacy | PT / AR / AP etc. | Privacy controls (new in Rev 5) |
Each control has a short identifier, such as AC-2 for account management, or IA-2 for identification and authentication. Control enhancements add extra detail, such as AC-2(1), for a stronger version of the same control. When an auditor asks for evidence, they will usually ask by control number, so learning the family codes helps you find controls quickly.
Baselines: Low, Moderate and High
A baseline is a set of controls selected for a system, based on how bad it would be if the system were compromised. SP 800-53 defines three baselines: low, moderate, and high. A low-impact system, such as a public website with no sensitive data, uses the low baseline. A moderate-impact system, such as a system that holds personal data, uses the moderate baseline, which adds more controls. A high-impact system, such as a system that controls critical infrastructure, uses the high baseline, which is the most demanding.
The organisation first categorises its system using the guidance in FIPS 199, which looks at the impact on confidentiality, integrity, and availability. It then selects the matching baseline, tails it by adding or removing controls to match its risk, and documents its choices in a system security plan. Tailoring is allowed, but it must be justified. Removing a control because it is inconvenient is not a valid justification.
Grouping controls into families also helps teams share the work. A company that handles criminal justice information, for example, will find that the audit and access controls in SP 800-53 look familiar. Our guide to What Is CJIS explains the security policy for criminal justice systems, and shows how a similar family-based approach works in that setting.
Revision 5 brought the biggest changes to SP 800-53 in years. It added privacy controls, so the catalogue now covers both security and privacy. It added a supply chain risk management family, reflecting the rise of third-party risk. It made the controls outcome-based, so that organisations can meet a control in different ways, as long as the outcome is achieved. And it removed the separation between federal and non-federal controls, so the catalogue is now usable by any organisation.
What Changed in Revision 5?
Before Revision 5, privacy controls lived in a separate appendix of SP 800-53, and many organisations ignored them. Revision 5 integrated privacy controls into the main families, and added new families such as PT (PII Processing and Transparency) and AR (Accountability). The message is clear: privacy is not an add-on, it is part of security.
Revision 5 also moved the control baselines out of SP 800-53 and into a separate publication, SP 800-53B. That means the catalogue stays stable, while the baselines can be updated more often. If you are working from an older copy, check that you have the current baselines from SP 800-53B, not the baselines that were in Revision 4.
How to Implement NIST 800-53: The Risk Management Framework
NIST 800-53 is usually implemented through the Risk Management Framework (RMF), described in NIST SP 800-37. The RMF has seven steps, and it is a cycle, not a one-off project.
1. Prepare
Set up the organisation to manage risk. Identify roles, set risk tolerance, and make sure senior leaders support the work. Without leadership support, a compliance project will stall.
2. Categorise
Categorise the system using FIPS 199, and decide its impact level: low, moderate, or high. This step drives the baseline you will use, so get it right.
3. Select
Select the baseline for the impact level, tailor it, and document the controls in a system security plan. Explain why each control is included, and how it will be implemented.
4. Implement
Implement the controls, and document what you did. Use the system security plan as a living document, not a form to fill in once a year.
5. Assess
Assess the controls to see if they are implemented correctly and working. Independent assessors test the controls, interview staff, and review documents. Fix weaknesses found.
6. Authorise
A senior official, the authorising official, decides whether the risk is acceptable and signs the authorisation to operate. This is a risk decision, not a claim that the system is perfect.
7. Monitor
Monitor the system continuously. Watch for new vulnerabilities, changes to the system, and changes in the threat landscape. Repeat the cycle, and update the assessment when the system changes.
NIST 800-53 vs Other Frameworks
SP 800-53 is a control catalogue. Other NIST publications are frameworks that use it. The NIST Cybersecurity Framework (CSF) is a high-level framework for managing cybersecurity risk, with functions such as Identify, Protect, Detect, Respond, and Recover. It does not contain detailed controls. Organisations use CSF to organise their work, and SP 800-53 to find the detailed controls to put in place.
FedRAMP is a programme that uses SP 800-53 as its baseline for cloud services. A cloud provider that wants to serve federal agencies must meet the FedRAMP baseline, which is a tailored version of the moderate or high SP 800-53 baseline, and must be assessed by an independent assessor.
Controls also overlap with financial and privacy rules. A financial institution, for example, must protect consumer data under the Gramm-Leach-Bliley Act, and the technical controls it uses for GLBA, such as access control, encryption, and audit logging, are the same controls it will use for SP 800-53. Building one control set that serves several rules is more efficient than building a separate set for each rule.
Common mistakes can make a NIST 800-53 project much harder than it needs to be. The first is treating the catalogue as a checklist to tick off, rather than a risk-based set of controls. A control that is implemented but does not actually reduce risk is a waste of time. The second is copying another organisation’s baseline without tailoring it to your own system. The third is writing a system security plan that does not match reality, for example by saying a control is in place when it is not. Auditors will test the controls, and a plan that does not match the system will be found out quickly. The fourth is forgetting about the people side: controls need owners, and owners need training and time to do the work.
Frequently Asked Questions
Is NIST 800-53 mandatory?
SP 800-53 is mandatory for US federal agencies under FISMA, and for contractors that work on federal systems. It is voluntary for other organisations, but many use it as a best-practice catalogue, and some contracts or regulations require it indirectly, for example through FedRAMP.
How many controls are in NIST 800-53 Rev 5?
Revision 5 contains more than 1,000 controls and control enhancements, organised into 20 control families. No organisation implements all of them. Each system selects a baseline, such as low, moderate, or high, and then tailors it to its own risk.
What is the difference between NIST 800-53 and the NIST Cybersecurity Framework?
SP 800-53 is a detailed catalogue of controls. The NIST Cybersecurity Framework is a high-level framework for managing risk, with functions such as Identify, Protect, Detect, Respond, and Recover. Organisations use the Framework to organise their work, and SP 800-53 to find the detailed controls they need.
What is a NIST 800-53 baseline?
A baseline is a set of controls selected for a system based on its impact level. There are three baselines: low, moderate, and high. A low-impact system uses fewer controls, and a high-impact system uses more. Baselines are published in NIST SP 800-53B, and organisations can tailor them to their own risk.
How long does NIST 800-53 compliance take?
It depends on the size and complexity of the system, and on how mature the organisation’s security programme already is. A small system with good controls in place may take a few months. A large system, or a cloud service seeking FedRAMP authorisation, can take a year or more. Ongoing monitoring means the work never really ends.
Conclusion
NIST Special Publication 800-53 is a large and detailed catalogue, but its idea is simple. Identify your system, categorise its impact, select the controls that match that impact, implement them, test them, and monitor them. Done well, SP 800-53 gives an organisation a comprehensive and defensible set of security and privacy controls, and a common language to talk about risk with auditors, customers, and partners.
Start small if you are new to the catalogue. Pick one system, categorise it, and work through its baseline with the people who run it. Use the control families to share the work, and use the Risk Management Framework to keep the project moving. Over time, the controls will become part of how your organisation works, not just a compliance exercise, and that is when SP 800-53 delivers its real value.



[…] a deeper explanation of the framework both programs are built on, see our guide to NIST Special Publication 800-53, which defines the security controls at the heart of GovRAMP […]