NIST SP 800-218
Prepare the Organization

NIST SP 800-218 SP800-218-PO.4.1: Criteria for Software Security

Define criteria for assessing the security characteristics of software before release. Tie criteria to risk and to customer commitments so that release decisions are explicit.

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

What else in your programme already covers this

This control maps to 36 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.

ISO 27001:2022 · 4 controls

  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.29 Security testing in development and acceptance
  • 8.32 Change management

C5 (Germany) · 3 controls

  • C5-DEV-03 Policies for changes to information systems
  • C5-DEV-05 Risk assessment, categorisation and prioritisation of changes
  • C5-DEV-09 Approvals for provision in the production environment

ISO 27002:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.29 Security testing in development and acceptance
  • 8.32 Change management

NIST SP 800-53 Rev 5 · 3 controls

PCI DSS 4.0 · 3 controls

  • 6.2.1 6.2.1 Secure development of bespoke and custom software
  • 6.2.3 6.2.3 Code review before release
  • 6.5.2 6.5.2 Confirm PCI DSS controls after significant change
  • ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
  • DS-6 Enforce security of workload throughout DevOps lifecycle

CIS Controls v8 · 2 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.6 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities

FedRAMP High · 2 controls

  • SA-3 System Development Life Cycle
  • SA-4(1) Acquisition Process | Functional Properties of Controls (SA-4(1))

FedRAMP Moderate · 2 controls

  • SA-3 System Development Life Cycle
  • SA-4(1) Acquisition Process | Functional Properties of Controls (SA-4(1))

NIST SP 800-161 Rev 1 · 2 controls

  • SEC11-BP02 Automate testing throughout the development and release lifecycle

BSIMM · 1 control

  • SM1.4 Implement security checkpoints and associated governance gates
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
  • OSPS-QA-03.01 OSPS-QA-03.01 Address Pass/Fail Checks Before Accepting Changes

SOC 2 · 1 control

  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

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 Prepare the Organization

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

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

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 36 it maps to, and the evidence behind each claim, over MCP and REST.