NIST SP 800-218
Produce Well Secured Software

NIST SP 800-218 SP800-218-PW.4.1: Reuse Trusted Software Components

Acquire and reuse well secured software components rather than creating new ones for common functions. Track the origin and version of each component and verify its provenance.

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

What else in your programme already covers this

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

FedRAMP High · 4 controls

  • RA-3(1) Risk Assessment | Supply Chain Risk Assessment (RA-3(1))
  • SR-11 Component Authenticity (SR-11)
  • SR-3 Supply Chain Controls and Processes (SR-3)
  • SR-5 Acquisition Strategies, Tools, and Methods (SR-5)

FedRAMP Moderate · 4 controls

  • RA-3(1) Risk Assessment | Supply Chain Risk Assessment (RA-3(1))
  • SR-11 Component Authenticity (SR-11)
  • SR-3 Supply Chain Controls and Processes (SR-3)
  • SR-5 Acquisition Strategies, Tools, and Methods (SR-5)

NIST SP 800-53 Rev 5 · 4 controls

CIS Controls v8 · 3 controls

  • CIS-16.11 Leverage Vetted Modules or Services for Application Security Components
  • CIS-16.4 Establish and Manage an Inventory of Third-Party Software Components
  • CIS-16.5 Use Up-to-Date and Trusted Third-Party Software Components

ISO 27001:2022 · 3 controls

  • 5.21 Managing information security in the information and communication technology (ICT) supply chain
  • 8.28 Secure coding
  • 8.4 Access to source code

NIST SP 800-161 Rev 1 · 3 controls

NIST SP 800-172 · 3 controls

  • 3.11.6e Supply Chain Risk Assessment, Response, and Monitoring
  • 3.14.3e Include Systems in Scope of Enhanced Requirements or Segregate into Purpose-Specific Networks
  • 3.4.1e Authoritative Source for Software and Firmware

OpenSSF Best Practices Badge Criteria · 3 controls

OpenSSF Open Source Project Security Baseline (OSPS Baseline) · 3 controls

AWS Well-Architected Security Pillar · 2 controls

  • SEC06-BP02 Provision compute from hardened images
  • SEC11-BP05 Centralize services for packages and dependencies

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

ISO 27002:2022 · 2 controls

  • 5.21 Managing information security in the ICT supply chain
  • 8.28 Secure coding

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-GV.SC-04 Suppliers are known and prioritized by criticality
  • NIST-CSF-GV.SC-06 Planning and due diligence are performed to reduce risks before entering into formal supplier or other third-party relationships

Azure Security Benchmark · 1 control

  • DS-2 Ensure software supply chain security

BSIMM · 1 control

  • SR1.5 Identify open source and manage its risk

C5 (Germany) · 1 control

  • C5-PSS-02 Identification of Vulnerabilities of the Cloud Service

ISO/IEC 42001:2023 · 1 control

  • 8.3 AI risk treatment

NIST SP 800-171 Rev 3 · 1 control

  • 03.17.03 Supply Chain Requirements and Processes

OpenSSF Scorecard · 1 control

PCI DSS 4.0 · 1 control

  • 6.3.2 6.3.2 Inventory of bespoke software and components

US Executive Order 14144 - Strengthening and Promoting Innovation in the Nation's Cybersecurity · 1 control

  • 2(e) Sec. 2(e) (now 2(c)) Manage agency use of open source software

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 Produce Well Secured Software

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

NIST SP 800-218 SP800-218-PW.4.1 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.

If you hold NIST SP 800-53 Rev 571.4% covered · 12 gapsIf you hold C5 (Germany)61.9% covered · 16 gapsIf you hold NIST SP 800-161 Rev 161.9% covered · 16 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.152.4% covered · 20 gapsIf you hold ISO 27002:202252.4% covered · 20 gapsIf you hold Azure Security Benchmark50% covered · 21 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll NIST SP 800-218 controls