Cybersecurity

NIST SP 800-53B Rev. 5

NIST SP 800-53B Rev. 5 framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
NIST SP 800-53B – Control Baselines for Information Systems and Organizations
  • Classification
    Category
    Cybersecurity
    Domain
    Cybersecurity
    Framework Family
    NIST Special Publications
  • Regulatory Context
    Type
    Control Framework
    Legal Instrument
    Guideline
    Sector
    Government Sector
    Industry
    Government & Public Sector
  • Region / Publisher
    Region
    North America
    Region Detail
    United States
    Publisher
    National Institute of Standards and Technology (NIST)
  • Versioning
    Version
    Revision 5 (October 2020; Release 5.2.0 August 27, 2025, no baseline changes)
    Effective Date
    October 29, 2020
    Issue Date
    October 29, 2020 (errata December 10, 2020)
  • Adoption
    Adoption Model
    Regulatory Compliance
    Implementation Complexity
    High
  • Official Reference
License Information

License included / downloadable: Yes

NIST SP 800-53B is a U.S. government publication available free of charge from NIST, with the control baselines spreadsheet and OSCAL profiles, and its baseline tables are included with the platform.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
NIST SP 800-53B Rev. 5
Defines control baselines for federal information systems to manage cybersecurity risks.
Key takeaways
  • NIST SP 800-53B holds the low, moderate, high, and privacy control baselines drawn from the NIST SP 800-53 Rev. 5 catalog.
  • Released October 29, 2020 with errata on December 10, 2020; Release 5.2.0 of August 27, 2025 changed no baselines.
  • Implementing a minimum set of controls is mandatory for federal systems; the privacy baseline is not mandated by law or A-130.
  • NIST's OSCAL profiles list 149 items in the low baseline, 287 moderate, 370 high, and 96 privacy.
  • The FIPS 199 high water mark sets the system impact level, and the matching baseline is selected from the Chapter Three tables.

Overview

NIST SP 800-53B, Control Baselines for Information Systems and Organizations, is the NIST publication that holds the three security control baselines (low, moderate and high impact) and the privacy control baseline drawn from the NIST SP 800-53 Rev. 5 catalog, together with the rules for selecting a baseline, the assumptions behind the baselines, tailoring guidance and overlays. This page covers the whole publication; the high baseline has its own page at NIST SP 800-53B High Baseline. Section 1.1 states that implementing a minimum set of controls from SP 800-53 is mandatory for federal information systems under OMB Circular A-130 and FISMA, while the privacy baseline is not mandated by law or A-130.

NIST released SP 800-53B on October 29, 2020 through the Joint Task Force, with an errata update on December 10, 2020, after Revision 5 of SP 800-53 moved the baselines out of the catalog. On August 27, 2025 NIST issued Release 5.2.0 of SP 800-53B, which includes no changes to the baselines; the version number was updated for consistency with SP 800-53 and SP 800-53A. In NIST's OSCAL Release 5.2.0 profiles the low baseline lists 149 controls and enhancements, the moderate 287, the high 370 and the privacy baseline 96.

Organizations use it after security categorization under FIPS 199: the high water mark of the confidentiality, integrity and availability impact values sets the system impact level, the matching baseline is selected from the Chapter Three tables (Section 2.2), and the baseline is tailored through the Section 2.4 activities, with every control accounted for and each tailoring decision justified in the system security and privacy plans.

Why does it matter?

SP 800-53B is where a FIPS 199 categorization becomes a list of required controls. FIPS 200 requires agencies to include one of three appropriately tailored baselines from SP 800-53, and since Revision 5 those baselines live here rather than in the catalog. Section 2.2 removes the guesswork from selection: a low-impact system is one in which all three security objectives are low, a moderate-impact system has at least one moderate objective and none high, and a high-impact system has at least one high objective. Section 2.4 then insists that tailoring is defensible, documented and never arbitrary, so a tailored baseline can be explained to an assessor and an authorizing official.

Key benefits include:

  • A rule for every impact level

Section 2.2 applies the FIPS 199 high water mark, used in FIPS 200, to pick one of three baselines, and Tables 3-1 to 3-20 mark each control and enhancement with an x for the baselines it belongs to.

  • A privacy baseline that stands apart

The privacy control baseline applies irrespective of impact level, based on privacy program responsibilities under OMB A-130, and is tailored by a privacy risk assessment (Section 2.2).

  • Stated assumptions

Section 2.3 lists the working assumptions behind the baselines and the threats they do not address, such as insider threats, classified information and advanced persistent threats.

  • Tailoring with a record

Section 2.4 lists the tailoring activities and requires the rationale for every decision to be recorded in the system security and privacy plans.

  • Stable since release

Release 5.2.0 of August 27, 2025 changed no baseline, so a tailoring record made against the 2020 tables still holds.

How does it work?

Chapter Two gives the fundamentals. Section 2.1 introduces control baselines as a starting point; Section 2.2 explains selection: security categorization under FIPS 199, the high water mark from FIPS 200, the choice of one of three security control baselines, and the privacy control baseline that federal agencies apply to the processing of PII under their OMB A-130 responsibilities. Not every control or enhancement in SP 800-53 is assigned to a baseline, and the baseline is a starting point from which controls may be removed, added or specialized through tailoring.

Section 2.3 lists the assumptions under which the baselines were built: information in systems is relatively persistent; systems are multi-user; some information is not shareable with all authorized users; systems exist in networked environments and are general purpose; and organizations have the structure, resources and infrastructure to implement the controls. Where an assumption does not hold, tailoring removes controls; where additional conditions apply (insider threats, classified information, advanced persistent threats, information needing specialized protection, communication across security domains), additional controls from SP 800-53 are likely needed.

Section 2.4 lists the tailoring activities: identifying and designating common controls, applying scoping considerations, selecting compensating controls, assigning values to organization-defined parameters, supplementing the baseline with additional controls and enhancements, and providing specification information for implementation. Tailoring may be done at the organization level, the system level or both; controls tied to federal legislative, regulatory or policy requirements are not tailored out; and every control from the selected baseline is accounted for in the plans. Section 2.5 adds the idea of capabilities, sets of mutually reinforcing controls such as IA-2(1), IA-2(2), IA-2(8), IA-2(9) and SC-8(1) for secure remote authentication. Appendix C explains overlays for communities of interest, technologies and environments, and NIST hosts them in the Security Control Overlay Repository (SCOR).

Key Elements

  • Three security control baselines (Section 2.2, Chapter Three)

Low, moderate and high, selected by the FIPS 199 high water mark; in the OSCAL Release 5.2.0 profiles they list 149, 287 and 370 controls and enhancements.

  • Privacy control baseline (Section 2.2)

Applied irrespective of impact level to systems that process PII, under OMB A-130 privacy program responsibilities; 96 controls and enhancements in the OSCAL profile; tailored by privacy risk assessment.

  • Baseline tables (Tables 3-1 to 3-20)

One table per SP 800-53 family, from Access Control to Supply Chain Risk Management, with an x in the privacy, low, moderate and high columns for each assigned control and enhancement.

  • Control baseline assumptions (Section 2.3)

Five assumptions the baselines rely on and five conditions they do not address, which signal when additional controls are needed.

  • Tailoring guidance (Section 2.4)

Six tailoring activities, organization- or system-level tailoring, no arbitrary removals, and the rationale documented in the system security and privacy plans.

  • Capabilities (Section 2.5)

Defining capabilities before selection, since a requirement is seldom met by one control but by a set of mutually reinforcing controls.

  • Overlays (Appendix C)

Fully specified control sets for communities of interest, technologies or environments, derived from tailoring or independently, with parameter values agreed by the community.

  • Release 5.2.0 (August 27, 2025)

No changes to the baselines; version number aligned with SP 800-53 and SP 800-53A; a control baselines spreadsheet and OSCAL profiles are published alongside.

What does it cover?

SP 800-53B establishes security and privacy control baselines for federal information systems and organizations and provides tailoring guidance for them (Section 1.1). The baselines can be implemented by any organization that processes, stores or transmits information, including state, local and tribal governments and private sector organizations. For federal information systems, implementing a minimum set of controls from SP 800-53 Rev. 5 is mandatory under OMB Circular A-130 and FISMA; use of the privacy control baseline is not mandated by law or A-130 but is designed to help agencies meet FISMA, the Privacy Act of 1974, OMB policies and the designated FIPS. National security systems follow CNSSP 22 and CNSSI 1253, and the Department of Defense follows DoDI 8510.01.

What are its objectives?

Section 1.1 and Chapter Two set out what the publication is for:

Provide one security control baseline for each system impact level and a privacy baseline applied irrespective of impact level (abstract and Section 2.2).

Give organizations a defined rule, the FIPS 199 high water mark, for selecting the baseline that matches a system's categorization (Section 2.2).

State the working assumptions behind the baselines so organizations know when a baseline does not fit (Section 2.3).

Provide tailoring guidance that keeps the result defensible, documented and commensurate with risk (Section 2.4).

Encourage capability-based thinking so that sets of mutually reinforcing controls are selected together (Section 2.5).

Enable overlays so communities of interest can standardize controls for shared technologies, missions or environments (Appendix C).

Framework in Context

SP 800-53B is a publication part of the SP 800-53 family alongside SP 800-53A Rev. 5. The catalog it draws from is NIST SP 800-53 Rev. 5; the categorization that drives selection comes from FIPS 199 and FIPS 200, with the Categorize step of NIST SP 800-37 Rev. 2 and the Select step that tailors the chosen baseline into the system plans; Section 2.3 ties the articulation of assumptions to the risk framing step of SP 800-39 and the Prepare step of SP 800-37. The high baseline, the largest of the three at 370 controls and enhancements, is described on its own page. Overlays built on these baselines are hosted in the Security Control Overlay Repository.

Common Framework Mappings

NIST SP 800-53B is commonly mapped to the authorization programs and control frameworks that build on or compare with the SP 800-53 baselines.

Mapped frameworks include:

CIS Controls v8.1

COBIT 2019

FedRAMP Rev. 5

ISO 27001:2022

ISO 27002:2022

ISO 27701

NIST CSF 2.0

NIST Privacy Framework v1.0

PCI DSS 4.0.1

SOC 2

SMARTSUITE

How SmartSuite Supports NIST SP 800-53B

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Compliance Management to hold each system's selected baseline with the Tables 3-1 to 3-20 assignments, its tailoring decisions and the rationale the plans must carry, Cyber & IT Risk to link the FIPS 199 categorization and risk assessments that justify tailoring, and Privacy Management for the privacy control baseline and the privacy risk assessment that tailors it.

Categorization and Baseline Selection (Section 2.2)

Record the confidentiality, integrity and availability impact values, the high water mark result and the low, moderate or high baseline selected for each system.

Baseline Control Assignments (Tables 3-1 to 3-20)

Hold the controls and enhancements marked for the selected baseline and for the privacy baseline as records, with owners and implementation status per system.

Tailoring Record (Section 2.4)

Document common control designations, scoping decisions, compensating controls, parameter values, supplements and the rationale for every tailoring decision.

Assumption Check (Section 2.3)

Record which baseline assumptions hold for the system and which additional conditions apply, to show why controls were added or removed.

Privacy Baseline and Risk Assessment (Section 2.2)

Track the privacy control baseline for systems that process PII and the privacy risk assessment that justifies additions and removals.

Overlays and Capabilities (Section 2.5 and Appendix C)

Maintain any overlay applied to a system and the capabilities, such as secure remote authentication, that groups of controls are meant to deliver.

Related frameworks

CIS Controls v8.1

CIS Controls v8.1 is a prioritized set of 18 Controls and 153 Safeguards, in three Implementation Groups, with a new Govern function.

CMMC 2.0

CMMC is the DoD program, 32 CFR Part 170, that requires contractors handling FCI or CUI to hold a Level 1, 2 or 3 status. Phase 2 was suspended on July 13, 2026.

FedRAMP Rev. 5

FedRAMP Rev5 is the legacy FedRAMP certification type: NIST SP 800-53 Rev. 5 baselines, 3PAO assessment and agency authorization for cloud services used by U.S. agencies.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO 27002:2022

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

MITRE ATT&CK

MITRE ATT&CK is a free knowledge base of adversary tactics, techniques and sub-techniques from The MITRE Corporation, updated twice a year; the current release is v20.0.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-171 Rev.2

NIST SP 800-171 Rev. 2: 110 CUI security requirements in 14 families, withdrawn by NIST on May 14, 2024 but still the edition DFARS 252.204-7012 and CMMC Level 2 cite.

FAQ

Frequently Asked Questions For NIST SP 800-53B (Control Baselines for Information Systems and Organizations)

Section 2.2 uses the FIPS 199 security categorization and the high water mark concept from FIPS 200. A low-impact system is one in which all three security objectives (confidentiality, integrity, availability) are low; a moderate-impact system has at least one moderate objective and none high; a high-impact system has at least one high objective. The organization then selects the matching baseline from Tables 3-1 to 3-20.

NIST's OSCAL Release 5.2.0 profiles list 149 controls and enhancements in the low baseline (131 controls, 18 enhancements), 287 in the moderate (177 and 110), 370 in the high (188 and 182) and 96 in the privacy baseline (75 and 21). Section 2.2 notes that not every control or enhancement in SP 800-53 is assigned to a baseline.

Section 2.2 provides an initial privacy control baseline for federal agencies to address privacy requirements and manage privacy risks from processing PII under their OMB A-130 privacy program responsibilities; it applies irrespective of impact level. Organizations tailor it with a privacy risk assessment, removing controls tied to inapplicable legal or policy requirements and adding unassigned controls where risks call for them. Section 1.1 notes its use is not mandated by law or A-130.

Section 2.4 lists identifying and designating common controls, applying scoping considerations, selecting compensating controls, assigning values to organization-defined parameters, supplementing the baseline with additional controls and enhancements, and providing specification information for implementation. Tailoring decisions must be defensible, controls tied to legal or policy requirements are not tailored out, every baseline control is accounted for, and the rationale is recorded in the system security and privacy plans.

No. The CSRC planning note of August 27, 2025 states that the minor release of SP 800-53B (Release 5.2.0) includes no changes to the baselines; the version number was updated for consistency with SP 800-53 and SP 800-53A, which did receive new and revised controls and assessment procedures. The OSCAL profiles carry version 5.2.0 with the 2020 baseline contents.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.