Engineer working on a laptop connected to a device test rig, surrounded by wiring harnesses and test hardware

Firmware vulnerabilities & fixes

NIST SP 800-53: the 20 security and privacy control families, explained

Last updated:

NIST SP 800-53, "Security and Privacy Controls for Information Systems and Organizations," is the US National Institute of Standards and Technology's catalogue of security and privacy controls, organized into 20 control families — from Access Control to Supply Chain Risk Management — each identified by a two-letter code. The current version, Revision 5 (published September 2020), is kept current with dated releases on top of the same revision, most recently Release 5.2.0 on 27 August 2025, which added new controls including SA-15(13), SA-24 and SI-02(07). Written to satisfy the Federal Information Security Modernization Act (FISMA), it has become a de facto reference catalogue well beyond US federal use, underpinning the FedRAMP cloud-authorization program.

Key takeaways

  • It helps to be precise about what kind of document SP 800-53 actually is.
  • Source: NIST OSCAL baseline profiles, version 5.2.0, counted 11 November 2026.
  • The SA family is written to be passed down a contract.
  • SA-15(13) Logging Syntax (new): the developer uses a defined syntax to log defined events.

Is it a catalogue or a checklist?

It helps to be precise about what kind of document SP 800-53 actually is. It is a catalogue: a comprehensive list of possible controls, each with a defined purpose, grouped into families — not a prescription of which specific controls any one system must implement. That selection decision, and the baselines that drive it, live in a separate companion publication, SP 800-53B, covered below. A team that opens SP 800-53 expecting a single checklist to work through top to bottom is working against the document's own design.

What are the 20 control families?

Every control in the catalogue is filed under one of 20 families, each identified by a two-letter code used throughout NIST documentation and tooling:

Code Family
AC Access Control
AT Awareness and Training
AU Audit and Accountability
CA Assessment, Authorization, and Monitoring
CM Configuration Management
CP Contingency Planning
IA Identification and Authentication
IR Incident Response
MA Maintenance
MP Media Protection
PE Physical and Environmental Protection
PL Planning
PM Program Management
PS Personnel Security
PT PII Processing and Transparency
RA Risk Assessment
SA System and Services Acquisition
SC System and Communications Protection
SI System and Information Integrity
SR Supply Chain Risk Management

Within each family, individual controls carry an identifier such as AC-2 (Account Management) or SR-11 (Component Authenticity), and many controls have numbered control enhancements — optional, more stringent additions to the base control, written as AC-2(1), AC-2(2) and so on. NIST describes the controls overall as "flexible and customizable," meant to be "implemented as part of an organization-wide process to manage risk." The exact control and enhancement count changes between releases as NIST adds, retires or revises entries, so NIST's current release, not a fixed total, governs the count at any given time. As a reference point, NIST's machine-readable OSCAL catalogue for Release 5.2.0 holds 324 base controls and 872 enhancements; 182 of those 1,196 entries are marked withdrawn, which leaves 1,014 in force (our count of the JSON file on 11 November 2026). Withdrawn entries keep their number, which is why SA-12 and SA-19 still appear in tools: their content moved into the SR family.

Two families are worth calling out specifically for a device or firmware maker: PT (PII Processing and Transparency), added in Revision 5 to fold in privacy controls that earlier revisions handled as a separate appendix, and SR (Supply Chain Risk Management), which the Rev. 5 text lists among its most significant changes as "a new supply chain risk management control family." SR covers controls like supplier assessment, component authenticity and counterfeit prevention — the same territory our SP 800-161 C-SCRM guide covers in more depth for the supply-chain-specific publication built on top of this family.

How do SP 800-53B baselines decide which controls apply?

SP 800-53 itself does not say which controls a given system must implement — that is the job of its companion publication, SP 800-53B, "Control Baselines for Information Systems and Organizations." SP 800-53B's own abstract states it "provides security and privacy control baselines for the Federal Government," consisting of "three security control baselines (one for each system impact level—low-impact, moderate-impact, and high-impact), as well as a privacy baseline that is applied to systems irrespective of impact level."

Baseline Applies to Controls + enhancements selected (5.2.0 profile)
Low-impact Systems where loss of confidentiality, integrity or availability would have a limited adverse effect 149
Moderate-impact Systems where that loss would have a serious adverse effect 287
High-impact Systems where that loss would have a severe or catastrophic adverse effect 370
Privacy baseline Applied regardless of impact level, wherever personally identifiable information is processed 96

Source: NIST OSCAL baseline profiles, version 5.2.0, counted 11 November 2026.

A system's impact level is typically determined through a separate categorization step (commonly under FIPS 199), and once the matching baseline is selected, an organization tailors it — adding, removing, or adjusting controls, or applying a NIST- or organization-defined overlay, such as the operational-technology overlay SP 800-82 Rev. 3 adds on top of the SP 800-53 baselines for OT environments (see our SP 800-82 guide). Tailoring is expected, not a deviation to be avoided — a baseline is a documented starting point, not a one-size-fits-all mandate. The baselines are also where the gaps show: many supplier-facing enhancements, such as SA-10(1) firmware integrity verification or SA-11(2) threat modeling, sit in no baseline at all, so a buyer adds them through tailoring or contract language when it wants them.

Which controls reach a device or firmware supplier?

The SA family is written to be passed down a contract. Its statements begin "Require the developer of the system, system component, or system service to…", and SA-4 (Acquisition Process) is the control through which a buyer puts security requirements into a purchase. A device maker selling into a moderate-impact federal system therefore meets SP 800-53 through its customer's questionnaire, not through its own authorization. The rows below are the ones that most often land on a firmware supplier; statements are paraphrased from NIST's Release 5.2.0 catalogue, and the baseline letters come from the same release's SP 800-53B profiles.

Control What it asks for Baselines Evidence a device maker keeps
SA-4(9) Functions, Ports, Protocols, and Services in Use The developer identifies the functions, ports, protocols and services intended for use M, H Port and service list per firmware version
SA-10(1) Software and Firmware Integrity Verification The developer enables integrity verification of software and firmware components none Signing process, published hashes
SA-11 Developer Testing and Evaluation A test plan, evidence of results, "a verifiable flaw remediation process", and correction of found flaws M, H, P Test reports, fix records
SA-15(7) Automated Vulnerability Analysis Automated analysis, a view on exploitation potential, mitigations, and delivery of results to the buyer none Scan output plus the engineer's assessment
SA-22 Unsupported System Components Replace components once support ends, or provide alternative support L, M, H Published support periods, end-of-life notices
SI-2 Flaw Remediation Identify, report and correct flaws; test updates before installation L, M, H Release notes, update test records
SI-7 Software, Firmware, and Information Integrity Integrity verification tools that detect unauthorized changes M, H Secure boot and update-verification design
SI-7(15) Code Authentication Cryptographic authentication of software or firmware before installation H Signed update packages, key management records
SR-4 Provenance Document, monitor and maintain the provenance of components and data none SBOM per release, supplier records
SR-6 Supplier Assessments and Reviews Assess supply chain risks of suppliers and what they provide M, H Completed supplier questionnaires
SR-8 Notification Agreements Agreements to notify supply chain compromises or share assessment results L, M, H Contract clause, security contact, advisory process
SR-11 Component Authenticity Anti-counterfeit policy and procedures, and reporting of counterfeits L, M, H Authorized-distributor sourcing policy

Two controls outside SA, SI and SR complete the picture. CM-8 (System Component Inventory, all three baselines) asks the buyer to keep an accurate component inventory, and RA-5 (Vulnerability Monitoring and Scanning) asks it to scan "when new vulnerabilities potentially affecting the system are identified and reported." Both work better when the supplier hands over a component list. NIST's SP 800-53A assessment objects for SR-4 name a "bill of materials for critical systems or system components" as one artifact an assessor may examine, which is where a firmware SBOM fits; our SP 800-53A guide covers how those assessment procedures work.

What did Release 5.2.0 change for software and firmware updates?

Release 5.2.0 was a response to Executive Order 14306: NIST's summary of changes says it "focuses on improving the security and reliability of software updates and patches." The changes that matter to a supplier:

  • SA-15(13) Logging Syntax (new): the developer uses a defined syntax to log defined events.
  • SA-24 Design for Cyber Resiliency (new): cyber resiliency goals, objectives, techniques and design principles are defined and implemented.
  • SI-02(07) Root Cause Analysis (new): conduct root cause analysis, act on it and monitor the result. NIST says it closes a gap found by comparing the catalogue with the Secure Software Development Framework.
  • SI-07(12) (revised): integrity verification now covers all organization-defined software, not only user software.
  • SA-04 and SI-02 discussion (updated): SA-04 now mentions "notification and timing requirements for support, maintenance and updates"; SI-02 now mentions staggered deployment and checking that updates "come from authorized sources prior to downloading."

None of the three new entries sits in any SP 800-53B baseline, and NIST states SP 800-53B itself had no changes beyond its version number. A buyer that wants SA-24 or SI-02(07) from you will ask for it explicitly.

Worked example: how does a gateway maker answer an SP 800-53 supplier questionnaire?

Hypothetical case, for illustration only. A maker of an industrial Ethernet gateway is shortlisted for a facilities network that its federal customer categorizes as moderate impact. The customer's supplier questionnaire quotes SA-4(9), SA-11, SA-22, SI-2, SR-4 and SR-8.

  1. Sort the rows by ownerSA and SR rows are about the supplier's process; SI-2 and CM-8 are about the customer's operation but need the supplier's update and inventory data.
  2. SA-4(9):export the listening ports and services from the shipped firmware image and state which are on by default.
  3. SA-11:attach the last release's test summary and describe how a reported flaw becomes a tracked fix, which is the "verifiable flaw remediation process."
  4. SA-22:state the support end date for the model and what happens after it.
  5. SR-4:supply the SBOM for the version being bought, with component names and versions.
  6. SR-8:name the security contact and the advisory channel through which the maker will tell the customer about a supply chain compromise.
  7. SI-2:describe how updates are signed, tested and announced, so the customer can meet its own installation deadline.
  8. Mark the rest "customer-side"with one sentence each, rather than leaving them blank.

The answer pack is short because most of it is records the maker should already keep for each firmware release.

What are the common pitfalls?

  • Answering for the agency. A supplier cannot "implement AC-2" on the customer's system; it can describe what its product supports. Say which side owns each row.
  • Quoting a withdrawn control. NIST's catalogue marks SA-12 as incorporated into the SR family and SA-19 as moved to SR-11. Questionnaires that still cite them should be answered against the SR entries.
  • Treating enhancements as optional when the contract names them. No baseline selects SA-10(1) or SR-4, but a contract clause can.
  • One SBOM for the product line. SR-4 provenance is per component and per version; an SBOM from two releases ago does not describe what is shipping.
  • Confusing scan output with exploitation analysis. SA-15(7) asks for both the tool output and a determination of exploitation potential. The second is engineering judgement.

Where does SP 800-53 sit in NIST's risk framework?

SP 800-53 does not operate alone. It is the control catalogue consumed by NIST's Risk Management Framework (RMF), described in SP 800-37 (see our SP 800-37 guide), at the "Select," "Implement," "Assess" and "Monitor" steps. The risk assessment work that informs which controls matter most for a given system draws on the process SP 800-30 defines (see our SP 800-30 guide), and NIST's own Rev. 5 documentation includes mappings from the SP 800-53 catalogue to the NIST Cybersecurity Framework, the NIST Privacy Framework, and ISO/IEC 27001:2022 — letting an organization that already maintains one of those frameworks cross-reference its existing controls against SP 800-53's more granular catalogue rather than starting a gap assessment from zero. NIST's publication page warns that these mappings "are not always one-to-one." Incident handling under the IR family is covered in our SP 800-61 Rev. 3 guide.

What is a workable starting point?

  1. Pick a baseline before you pick controlsTrying to select individually from 20 families and hundreds of controls without first choosing low/moderate/high (or an equivalent risk-based starting point) from SP 800-53B is the most common way SP 800-53 adoption stalls.
  2. Use the two-letter family codes as your evidence index, the same way our IEC 62443-3-3 guide recommends organizing evidence under that standard's seven foundational requirements — most organizations already have documentation that maps cleanly onto AC, AU, CM, IR and SI even before a formal SP 800-53 exercise begins.
  3. Treat SR (Supply Chain Risk Management) and PT (PII Processing and Transparency) as the families most likely to be missingif your existing security program predates Revision 5 — both were added or substantially reworked in that revision.
  4. Check the release before citing a control ID or countNIST issues dated releases on top of Revision 5 (most recently 5.2.0 in August 2025) that add or revise individual controls; a control ID quoted from an older summary may not match the current catalogue.
  5. Keep one evidence folder per firmware releasewith the SBOM, port list, test summary and signing record, so SA, SI and SR answers come from the same files.

SoftWSP produces part of that per-release evidence. It extracts an SBOM from the firmware image as CycloneDX 1.6 JSON and matches the components against NVD, CISA KEV, FIRST EPSS and CISA's CSAF ICS advisories; an AI-drafted report cites the record behind each finding for an engineer to review. That supports SR-4 and RA-5 answers. It does not decide exploitation potential under SA-15(7) or write VEX statements: those calls stay with your engineers (see KEV and EPSS prioritization). Watchlist alerts on a CVE ID, vendor or product flag new advisories between scans. See device firmware security.

This guide summarises public NIST publications; it does not constitute legal or compliance advice.

Put this guide to work

Frequently asked questions

What is NIST SP 800-53?

Special Publication 800-53, "Security and Privacy Controls for Information Systems and Organizations," is NIST's catalogue of security and privacy controls. Its own abstract states it "provides a catalog of security and privacy controls for information systems and organizations to protect organizational operations and assets, individuals, other organizations, and the Nation from a diverse set of threats and risks, including hostile attacks, human errors, natural disasters, structural failures, foreign intelligence entities, and privacy risks." The current version is Revision 5, published in September 2020; NIST continues to issue dated releases on top of it, most recently Release 5.2.0 on 27 August 2025, which added new controls including SA-15(13), SA-24 and SI-02(07) alongside revisions to existing ones.

What are the 20 control families?

Each control in the catalogue is filed under one of 20 families, identified by a two-letter code: Access Control (AC), Awareness and Training (AT), Audit and Accountability (AU), Assessment, Authorization and Monitoring (CA), Configuration Management (CM), Contingency Planning (CP), Identification and Authentication (IA), Incident Response (IR), Maintenance (MA), Media Protection (MP), Physical and Environmental Protection (PE), Planning (PL), Program Management (PM), Personnel Security (PS), PII Processing and Transparency (PT), Risk Assessment (RA), System and Services Acquisition (SA), System and Communications Protection (SC), System and Information Integrity (SI), and Supply Chain Risk Management (SR).

What are control baselines, and where are they defined?

SP 800-53 itself is a catalogue of individual controls, not a prescription of which ones a given system must implement; that selection is handled in a separate companion publication, SP 800-53B, "Control Baselines for Information Systems and Organizations." SP 800-53B's own abstract states it "provides security and privacy control baselines for the Federal Government," consisting of "three security control baselines (one for each system impact level—low-impact, moderate-impact, and high-impact), as well as a privacy baseline that is applied to systems irrespective of impact level." An organization selects the baseline matching its system's impact level (typically categorized under FIPS 199) and then tailors it, adding, removing or adjusting controls to fit its actual risk and context, using the overlay mechanism SP 800-53B also describes.

Is NIST SP 800-53 only for US federal agencies?

It was written to satisfy requirements under the Federal Information Security Modernization Act (FISMA) and related federal policy, and its abstract explicitly frames the catalogue as protecting "the Nation" alongside organizations and individuals. In practice its use is much broader: NIST's own Rev. 5 documentation includes mappings to the NIST Cybersecurity Framework and NIST Privacy Framework, and to ISO/IEC 27001:2022, and the catalogue underpins the US government's FedRAMP cloud-authorization program. Private-sector organizations outside FISMA's legal scope commonly adopt SP 800-53 controls voluntarily as a detailed, free alternative or supplement to a paywalled standard like ISO/IEC 27001.

How does SP 800-53 relate to the Risk Management Framework and SP 800-30?

SP 800-53 supplies the control catalogue that gets selected, implemented, assessed and monitored inside NIST's Risk Management Framework (RMF), described in SP 800-37. Choosing which controls apply, and how, draws on the risk assessment activity SP 800-30 defines (see our [SP 800-30 guide](/guides/nist-sp-800-30-risk-assessment/)) and on the baseline/tailoring mechanism in SP 800-53B. For operational technology specifically, SP 800-82 Rev. 3 adds its own OT-specific tailoring guidance and an OT overlay on top of the SP 800-53 baselines — see our [SP 800-82 guide](/guides/nist-sp-800-82-ot-security/).

Sources

  1. NIST CSRC: SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations — final publication page
  2. NIST CSRC: SP 800-53B, Control Baselines for Information Systems and Organizations — final publication page
  3. NIST CSRC: SP 800-53 Controls — interactive control catalogue
  4. NIST: NIST.SP.800-53r5 — full text PDF
  5. NIST CSRC: SP 800-37 Rev. 2, Risk Management Framework for Information Systems and Organizations — final publication page
  6. NIST: Summary of Changes, SP 800-53 Release 5.2.0 (27 August 2025)
  7. NIST OSCAL content (GitHub): SP 800-53 Rev. 5 catalogue and SP 800-53B baseline profiles, version 5.2.0
Was this guide helpful?

In this cluster

NIST SP 800-53: the 20 security and privacy control families, explained