NIST SP 800-53
NIST Special Publication 800-53 Security and Privacy Controls — NIST (National Institute of Standards and Technology)
Also known as: SP 800-53, NIST 800-53, 800-53, NIST SP 800-53 Rev 5, 800-53r5, Rev. 5
Official site Official change log Subscribe to NIST SP 800-53 (RSS)
At a glance
- Status
- In force
- Next deadline
- None announced
- Who must comply
- US federal information systems: FIPS 200 requires federal agencies to meet minimum security requirements using SP 800-53 controls. Other organizations may use the catalog voluntarily. source
- How it is assessed
- Federal systems are assessed with the SP 800-53A procedures; an agency authorizing official then grants an authorization to operate, followed by continuous monitoring. source
- Authority
- NIST (Joint Task Force) writes the catalog under FISMA. OMB Circular A-130 and FIPS 200 make it binding on federal agencies; programs such as FedRAMP build their baselines on it. source
- Enforced by
- NIST is not a regulatory agency. Federal agencies report under FISMA, and their security programs must also cover systems that contractors provide or manage. source
- Last change
Comprehensive catalog of security and privacy controls for US federal information systems, de-facto global reference for government and regulated industries.
Recent changes
-
Medium
GovRAMP releases guidance on phishing-resistant MFA compliance requirements
GovRAMP has released comprehensive guidance to help Service Providers understand and implement phishing-resistant MFA requirements under GovRAMP Rev. 5. The guidance clarifies which authentication methods meet …
-
Medium
CISA and NIST release guidelines to protect federal cloud identity systems from token theft, forgery…
CISA and NIST released Interagency Report (IR) 8587 providing comprehensive guidelines for federal agencies and cloud service providers to defend identity tokens and assertions used in …
Key dates
No upcoming dates- Executive Order 14306 deadline for NIST to update SP 800-53 with guidance on securely and reliably deploying patches and updates (met by Release 5.2.0)
- Release 5.2.0 of SP 800-53 and SP 800-53A published; SP 800-53B re-released unchanged
- NIST concept paper on SP 800-53 control overlays for securing AI systems (COSAiS) opened for comment
- Release 5.1.1 (first patch release, one new control and three enhancements) published
Amendments
-
SP 800-53 Rev. 5, Release 5.2.0 AmendmentCurrent text
Minor release issued in response to Executive Order 14306, focused on secure and reliable software updates and patches. source
More
- New controls and enhancements SA-15(13), SA-24 and SI-02(07); revised SI-07(12); updated discussion in SA-04, SA-05, SA-08, SA-08(14), SI-02 and SI-02(05).
- SP 800-53A got matching assessment procedures; the SP 800-53B baselines did not change but were re-released for consistency.
-
SP 800-53 Release 5.2.0 (draft controls) Draft
Proposed controls on secure and reliable patches and updates released for an expedited public comment period that ran through 5 August 2025. source
-
SP 800-53 Rev. 5, Release 5.1.1 Amendment
First "patch release", issued through NIST's online reference tool (CPRT). source
More
- Added one new control with three enhancements on identity providers and authorization servers, introduced leading zeros in control identifiers (AC-1 became AC-01) and made minor editorial clarifications.
- The new items are not in any SP 800-53B baseline, and organizations may defer them until Release 6.0.0.
-
Not confirmed by an official source yet.
-
SP 800-53 Rev. 5 Major version
Controls made outcome-based (no longer naming who satisfies them), security and privacy controls merged into one catalog, a new supply chain risk management (SR) family added, and the baselines and tailoring guidance moved out to SP 800-53B. source
More
- New controls cover cyber resiliency, secure design and governance.
- "Federal" was dropped from the title.
Show 3 older amendments
-
SP 800-53 Rev. 4 (update 3) Errata
Last update of Rev. 4 ("April 2013, updated 1/22/2015"). source
More
- Rev. 4 was withdrawn on 23 September 2021, one year after Rev. 5 was published.
-
Not confirmed by an official source yet.
-
Not confirmed by an official source yet.
Who it applies to
FIPS 200 requires federal agencies to use the security controls in SP 800-53; nongovernmental organizations may use SP 800-53 voluntarily.
- Federal agencies
- FIPS 200, a mandatory federal standard, requires federal agencies to meet minimum security requirements by using the security controls in SP 800-53. source
- Scope
- It covers all federal information and systems except classified information and national security systems. source
- Time to comply
- When NIST revises the controls or baselines, agencies get up to one year from final publication to comply. source
- Risk Management Framework
- OMB Circular A-130 requires agencies to run the Risk Management Framework that selects these controls. source
- Other organizations
- Nongovernmental organizations may use SP 800-53 voluntarily. source
How compliance is assessed
Federal systems are assessed with the SP 800-53A procedures; an agency authorizing official then grants an authorization to operate, followed by continuous monitoring.
- Certification
- NIST does not offer or endorse any program or tool for compliance with its risk management guidance. source
- Assessment
- Federal systems implement a baseline from SP 800-53B and are assessed with the SP 800-53A procedures. source source
- Authorization
- An agency authorizing official then grants an authorization to operate under the Risk Management Framework (SP 800-37), followed by continuous monitoring. source
- Cloud services
- Cloud services reach agencies through FedRAMP, whose baselines are built on SP 800-53 Rev. 5. source
Enforcement and penalties
NIST is not a regulatory agency. Federal agencies report under FISMA, and their security programs must also cover systems that contractors provide or manage.
- Not a regulator
- NIST is not a regulatory agency. source
- Federal agencies
- Federal agencies provide FISMA reports in accordance with processes established by OMB and DHS. source
- Waivers
- FIPS 200 allows no waivers to FIPS made mandatory by the Secretary of Commerce. source
- Contractors
- FISMA requires each agency's information security program to cover systems provided or managed by another agency, a contractor or another source. source
Documents
- Standard NIST SP 800-53 Rev. 5 (PDF, includes updates as of 10 December 2020)
- Standard SP 800-53 Rev. 5 publication page (Release 5.2.0 PDF and summary of changes, mappings, OSCAL)
- Standard NIST SP 800-53A Rev. 5 – Assessing Security and Privacy Controls
- Standard NIST SP 800-53B – Control Baselines for Information Systems and Organizations
- FAQ SP 800-53 Release 5.1.1 FAQ (patch releases, Release 6.0.0)
Show 1 more document
Frequently asked questions
What is the latest version of NIST SP 800-53?
Revision 5, currently at Release 5.2.0, issued 27 August 2025. Release 5.2.0 added controls on secure software updates and patching (SA-15(13), SA-24, SI-02(07)). CSRC lists no Revision 6 draft; NIST's 5.1.1 FAQ said its timeline was not yet determined. source
What is the difference between SP 800-53 Rev. 5 and Release 5.2.0?
Rev. 5 is the revision published in September 2020. Since 2023 NIST updates it through numbered releases in its online reference tool: 5.1.1 (November 2023) and 5.2.0 (August 2025). Releases add or adjust individual controls without a new revision. source
Is NIST 800-53 mandatory?
For US federal agencies, yes: FIPS 200 requires them to use SP 800-53 controls to meet minimum security requirements. For everyone else it is voluntary unless a contract or program, such as FedRAMP, requires it. source
Do I have to implement Release 5.1.1 changes now?
NIST does not mandate implementation. The new control added in 5.1.1 is not in any SP 800-53B baseline, and organizations may defer the 5.1.1 changes until Release 6.0.0. source
Verified against official sources on 18 October 2026. We monitor the official sources for this framework. Watching since 7 September 2026. Subscribe to NIST SP 800-53 (RSS)