NIST SP 800-218
Protect the Software

NIST SP 800-218 SP800-218-PS.3.2: Software Bill of Materials

Produce a software bill of materials for each release in a machine readable format. Make it available to customers and use it internally to triage component vulnerabilities.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 39 controls across 18 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

NIST SP 800-53 Rev 5 · 4 controls

FedRAMP High · 3 controls

  • CM-10 Software Usage Restrictions
  • CM-8 System Component Inventory
  • SA-22 Unsupported System Components (SA-22)

FedRAMP Moderate · 3 controls

  • CM-10 Software Usage Restrictions
  • CM-8 System Component Inventory
  • SA-22 Unsupported System Components (SA-22)
  • NIST-CSF-GV.SC-09 Supply chain security practices are integrated into cybersecurity and enterprise risk management programs, and their performance is monitored throughout the technology product and service life cycle
  • NIST-CSF-GV.SC-10 Cybersecurity supply chain risk management plans include provisions for activities that occur after the conclusion of a partnership or service agreement
  • NIST-CSF-ID.AM-02 Inventories of software, services, and systems managed by the organization are maintained

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-171 Rev 3 · 3 controls

NIST SP 800-172 · 3 controls

  • 3.11.6e Supply Chain Risk Assessment, Response, and Monitoring
  • 3.11.7e Supply Chain Risk Management Plan
  • 3.4.3e Automated Inventory of System Components
  • ASBv3-AM-1 Track asset inventory and their risks
  • DS-2 Ensure software supply chain security

C5 (Germany) · 2 controls

  • C5-AM-01 Asset Inventory
  • C5-PSS-02 Identification of Vulnerabilities of the Cloud Service

CIS Controls v8 · 2 controls

  • CIS-16.4 Establish and Manage an Inventory of Third-Party Software Components
  • CIS-2.2 Ensure Authorized Software is Currently Supported
  • Annex I Part II(1) Identify and document vulnerabilities and components, including an SBOM
  • Annex II 9 User information: where the SBOM can be accessed, if offered

PCI DSS 4.0 · 2 controls

  • 12.3.4 12.3.4 Annual review of hardware and software technologies
  • 6.3.2 6.3.2 Inventory of bespoke software and components

BSIMM · 1 control

  • SE3.6 Enhance application inventory with an operations bill of materials

ISO 27001:2022 · 1 control

  • 5.21 Managing information security in the information and communication technology (ICT) supply chain

ISO 27002:2022 · 1 control

  • 5.21 Managing information security in the ICT supply chain

OpenSSF Scorecard · 1 control

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Protect the Software

You are reading one control. How much of NIST SP 800-218 have you already done?

NIST SP 800-218 SP800-218-PS.3.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-218 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 30 of 42 NIST SP 800-218 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

Query this from an agent

The graph holds this control, the 39 it maps to, and the evidence behind each claim, over MCP and REST.