NIST SP 800-218
Produce Well Secured Software

NIST SP 800-218 SP800-218-PW.8.1: Executable Testing for Security

Test executable software to detect vulnerabilities using dynamic application security testing, fuzz testing, and penetration testing on a defined cadence. Tie test scope to risk and feature changes.

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

What else in your programme already covers this

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

C5 (Germany) · 3 controls

  • C5-DEV-06 Testing changes
  • C5-OPS-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests
  • C5-PSS-02 Identification of Vulnerabilities of the Cloud Service

CIS Controls v8 · 3 controls

  • CIS-16.12 Implement Code-Level Security Checks
  • CIS-16.13 Conduct Application Penetration Testing
  • CIS-18.1 Establish and Maintain a Penetration Testing Program

FedRAMP High · 3 controls

  • CA-8 Penetration Testing
  • RA-5 Vulnerability Monitoring and Scanning
  • SA-11 Developer Testing and Evaluation

FedRAMP Moderate · 3 controls

  • CA-8 Penetration Testing
  • RA-5 Vulnerability Monitoring and Scanning
  • SA-11 Developer Testing and Evaluation

NIST SP 800-53 Rev 5 · 3 controls

  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • SEC11-BP03 Perform regular penetration testing
  • ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline
  • ASBv3-PV-7 Conduct regular red team operations

BSIMM · 2 controls

  • PT1.3 Use penetration testing tools internally
  • ST1.1 Perform edge/boundary value condition testing
  • NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-161 Rev 1 · 2 controls

NIST SP 800-171 Rev 3 · 2 controls

NIST SP 800-172 · 2 controls

  • 3.12.1e Penetration Testing by Independent Agents
  • 3.14.7e Verify Correctness of Security Functions

PCI DSS 4.0 · 2 controls

  • 11.3.1.3 11.3.1.3 Internal scans after significant change
  • 6.4.1 6.4.1 Public web application review or automated protection

SOC 2 · 2 controls

  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 8.29 Security testing in development and acceptance

ISO 27002:2022 · 1 control

  • 8.29 Security testing in development and acceptance

ISO/IEC 42001:2023 · 1 control

  • A.6.2.4 AI system verification and validation

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