Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
NIST SP 800-53 is a catalogue of around 1,000 security and privacy controls grouped into 20 families, used for US federal systems, FedRAMP, and as a reference library elsewhere.

What Is NIST SP 800-53?
NIST Special Publication 800-53 is a catalogue of security and privacy controls for information systems, maintained by the US National Institute of Standards and Technology. Revision 5, published in September 2020, contains roughly 1,000 controls and control enhancements arranged into 20 families, and it is the control set behind FISMA compliance, FedRAMP cloud authorisation, and much US federal contracting.
Outside government, teams treat it as a reference library. When a risk assessment concludes that “we need something for session management” or “our logging is thin”, SP 800-53 supplies a precise, peer-reviewed statement of what that control should do, what evidence proves it works, and how it can be strengthened.
Every control carries a two-letter family identifier and a number, so AC-2 is the second control in the Access Control family and AC-2(12) is its twelfth enhancement. Each entry gives the control statement, a discussion section explaining intent, and a list of related controls. The 20 families are:
The families map neatly onto the preventive, detective, and corrective control types most risk registers already use, which is why the catalogue travels well beyond its original audience.
SP 800-53 itself selects nothing. The baselines live in a companion document, SP 800-53B, which defines low, moderate, and high impact baselines plus a separate privacy baseline. A system is first categorised under FIPS 199 according to the worst-case impact of losing confidentiality, integrity, or availability, and that category picks the baseline. Tailoring then adds, removes, or adjusts controls with documented justification.
The wrapper around all of this is the Risk Management Framework in SP 800-37: prepare, categorise, select, implement, assess, authorise, and monitor. Assessment procedures for each control, including the objects to examine and the people to interview, are published separately in SP 800-53A.
Revision 5 was more than a refresh. The word “federal” came out of the title, signalling that the catalogue was meant for any organisation. Privacy controls were integrated into the main families rather than sitting in an appendix, and two families were added: SR for supply chain risk, reflecting the lessons of the SolarWinds era, and PT for the processing of personal information. Control statements were also rewritten as outcomes rather than instructions to a named role, which makes them easier to apply to a cloud provider, a contractor, or an internal team alike. Patch releases since then, including 5.1.1, have aligned the supply chain controls with SP 800-161 Revision 1.
No UK law requires SP 800-53. British organisations usually meet it through the back door: selling software to a US federal agency, pursuing FedRAMP for a SaaS product, or answering a customer questionnaire written by an American security team. For domestic obligations, ISO 27001 and the NCSC Cyber Assessment Framework carry far more weight with regulators and buyers here.
The two worlds are not far apart. NIST publishes mappings between SP 800-53 and ISO/IEC 27001 Annex A, and the informative references in the NIST Cybersecurity Framework point directly at 800-53 controls, so an ISMS can usually be evidenced against both with one set of artefacts. The full text is free from NIST.
Adopting all 1,000 controls voluntarily is a mistake. The practical pattern is to let your risk assessment choose the families that matter, then borrow the control text and its enhancements as a ready-made maturity ladder: AC-2 for account management, AU-6 for log review, IR-4 for incident handling. The enhancements are numbered roughly in order of rigour, so they answer the question “what would good look like next year” without inventing new wording.
Whichever catalogue you select from, the controls still have to work. If you need an independent view of whether yours do, our regulation and compliance services test controls against the evidence an auditor will ask for.
No. SP 800-53 applies to US federal information systems and to suppliers brought into that scope, for example through FISMA or FedRAMP. A UK organisation normally encounters it only when selling to American public sector buyers or answering a customer security questionnaire written against it. For UK obligations, ISO 27001, Cyber Essentials, and the NCSC Cyber Assessment Framework are the expected references.
The Cybersecurity Framework is a high-level structure of functions, categories, and outcomes used to describe and compare security programmes. SP 800-53 is the detailed control catalogue underneath it. The framework tells you that you need recovery planning; SP 800-53 tells you exactly what a contingency plan must contain and how an assessor should test it. Many organisations use both together.
Revision 5 contains over 300 base controls across 20 families, and roughly 1,000 items once control enhancements are counted. No organisation implements all of them. The baselines in SP 800-53B select a subset according to the impact level of the system, and tailoring then adjusts that subset with documented justification for each addition or removal.
Yes. NIST publishes mapping tables between SP 800-53 controls and ISO/IEC 27001 Annex A, and many GRC platforms ship the same crosswalk. The mapping is rarely one to one, because SP 800-53 is more granular, but it is close enough that a single set of policies, logs, and test results can usually evidence both frameworks with modest extra work.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.