Compliance

NIST 800-53,explained

6 min read · Updated June 2026

NIST SP 800-53 is the US federal catalogue of security and privacy controls. It is not a certification but a control set: federal systems select a baseline based on impact level, then implement and assess those controls under the Risk Management Framework. It also underpins the FedRAMP baselines for cloud services.

What NIST 800-53 is

NIST SP 800-53, now at Revision 5, is a catalogue of hundreds of security and privacy controls maintained by the US National Institute of Standards and Technology. It is used across US federal information systems and by many organisations that want a comprehensive control reference.

It is a control catalogue, not a pass-or-fail certification. The point is to select and implement the right controls for a system, then assess and authorise that system to operate.

Control families

The controls are grouped into families, each covering a domain of security or privacy, such as:

  • Access control and identification and authentication.
  • Audit and accountability, and system and information integrity.
  • Configuration management and risk assessment.
  • Contingency planning and incident response.
  • System and communications protection.

Baselines and the RMF

A companion publication, 800-53B, defines baselines of controls for low, moderate, and high impact systems. A system is categorised by impact, the matching baseline is selected and tailored, and the system is then assessed and authorised under the NIST Risk Management Framework (RMF).

How it relates to other frameworks

FedRAMP baselines for cloud services are drawn directly from 800-53. The controls also overlap heavily with ISO 27001 and SOC 2, so much of the work is shared. NIST 800-171, used for protecting Controlled Unclassified Information outside federal systems, is a focused derivative.

How to approach it

  1. 1Categorise the system by impact level to choose a baseline.
  2. 2Tailor the baseline to the system and document the selection.
  3. 3Implement the controls and gather evidence.
  4. 4Assess the controls and track weaknesses on a plan of action and milestones.
  5. 5Reuse overlapping ISO 27001 and SOC 2 work rather than starting again.

Frequently asked questions

Is NIST 800-53 a certification?

No. It is a control catalogue. Federal systems are assessed and authorised under the Risk Management Framework, and cloud services use the controls through FedRAMP. There is no standalone 800-53 certificate.

What is the difference between 800-53 and 800-171?

NIST 800-53 is the full federal control catalogue with hundreds of controls and baselines. NIST 800-171 is a focused subset for protecting Controlled Unclassified Information in non-federal systems, with 14 families. 800-171 derives from 800-53.

How does 800-53 relate to FedRAMP?

FedRAMP baselines are built from NIST 800-53 with FedRAMP-specific parameters and continuous-monitoring requirements, so 800-53 control work carries directly into a FedRAMP effort.

Do this in a fraction of the time

Diligio centralises your approved answers, drafts each response grounded in your sources, and independently verifies it before you review. RFPs, DDQs, and security questionnaires, answered from one knowledge base.

Related guides

Due diligence

What is a DDQ (due-diligence questionnaire)?

Due diligence

DDQ vs RFP: what is the difference?

RFPs

RFP vs RFI vs RFQ: what is the difference?

RFPs

The RFP response process: a step-by-step guide

RFPs

How to build an RFP content library

RFPs

The bid/no-bid decision: when to respond to an RFP

Security questionnaires

How to respond to security questionnaires faster

Security questionnaires

SIG vs CAIQ vs VSAQ: the security questionnaires explained

Security questionnaires

Vendor security assessment checklist

Compliance

SOC 2 vs ISO 27001: what is the difference?

Compliance

ISO 27001 readiness checklist: how to prepare for certification

Compliance

SOC 2 for startups: a practical guide

Compliance

GDPR compliance for SaaS: a practical guide

Compliance

HIPAA compliance for software vendors

Compliance

PCI DSS compliance, explained

Compliance

The NIST Cybersecurity Framework, explained

Compliance

ISO 42001, the AI management standard, explained

Compliance

ISO 27017 and ISO 27018: cloud security and privacy, explained

Compliance

ISO 22301 and business continuity, explained

Compliance

DORA, explained

Compliance

Cyber Essentials, explained

Compliance

The CCPA and CPRA, explained

Compliance

NIST 800-171 and CMMC, explained

Compliance

FedRAMP, explained

Compliance

HITRUST CSF, explained

Financial regulation

BSA/AML, explained

Financial regulation

The FATF 40 Recommendations, explained

Financial regulation

MiFID II and MAR, explained

Financial regulation

Consumer credit and fair lending, explained

Due diligence

Third-party risk management (TPRM): a practical guide

Putting NIST 800-53 into practice? See Diligio Compliance for NIST 800-53.