NIST SP 800-218
Produce Well Secured Software

NIST SP 800-218 SP800-218-PW.7.1: Code Review

Review the human readable source code to identify vulnerabilities. Use a combination of manual code review and automated static analysis tools tuned to the language and framework.

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 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 · 3 controls

  • CM-3 Configuration Change Control
  • SA-11 Developer Testing and Evaluation
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))

FedRAMP Moderate · 3 controls

  • CM-3 Configuration Change Control
  • SA-11 Developer Testing and Evaluation
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))

ISO 27001:2022 · 3 controls

  • 8.28 Secure coding
  • 8.29 Security testing in development and acceptance
  • 8.32 Change management
  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • SEC11-BP04 Conduct code reviews

BSIMM · 2 controls

  • CR1.2 Perform opportunistic code review
  • CR1.5 Make code review mandatory for all projects

C5 (Germany) · 2 controls

ISO 27002:2022 · 2 controls

  • 8.28 Secure coding
  • 8.32 Change management
  • 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-53 Rev 5 · 2 controls

PCI DSS 4.0 · 2 controls

  • 6.2.3 6.2.3 Code review before release
  • 6.2.3.1 6.2.3.1 Manual code review independence and approval

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
  • ASBv3-DS-4 Integrate static application security testing into DevOps pipeline

CIS Controls v8 · 1 control

  • CIS-16.12 Implement Code-Level Security Checks

CMMC 2.0 · 1 control

NIST SP 800-172 · 1 control

  • 3.14.7e Verify Correctness of Security Functions
  • OSPS-VM-06.02 OSPS-VM-06.02 Publish and Enforce an Application Security Testing Policy

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