NIST SP 800-218
NIST SP 800-218: Access Control

NIST SP 800-218 SP800-218-PW.7.2: Perform Code Review and Analysis

Perform the code review and/or code analysis based on the organization's secure coding standards, and record and triage the discovered issues.

What else in your programme already covers this

This control maps to 38 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-4 Impact Analyses
  • SA-11 Developer Testing and Evaluation
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis. Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of

FedRAMP Moderate · 3 controls

  • CM-4 Impact Analyses
  • SA-11 Developer Testing and Evaluation
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis. Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of

ISO 27001:2022 · 3 controls

  • 8.28 Secure coding
  • 8.29 Security testing in development and acceptance
  • 8.8 Management of technical vulnerabilities

NIST SP 800-53 Rev 5 · 3 controls

  • ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
  • DS-6 Enforce security of workload throughout DevOps lifecycle

C5 (Germany) · 2 controls

CIS Controls v8 · 2 controls

  • CIS-16.12 Implement Code-Level Security Checks
  • CIS-16.6 Establish and Maintain a Severity Rating System and Process for Application Vulnerabilities

NIST SP 800-161 Rev 1 · 2 controls

  • CM-4 Impact Analyses
  • SA-11 Developer Testing and Evaluation
  • CM-4 Impact Analyses
  • SA-11 Developer Testing and Evaluation

PCI DSS 4.0 · 2 controls

  • 6.2.3 Custom software reviewed prior to production
  • 6.2.3.1 Code review findings corrected

BSIMM · 1 control

  • CR1.4 Use automated code review tools (SAST)

CMMC 2.0 · 1 control

ISO 27002:2022 · 1 control

  • 8.29 Security testing in development and acceptance

NIST SP 800-172 · 1 control

  • 3.14.7e Verify Correctness of Security Functions
  • CM-4 Impact Analyses

SOC 2 · 1 control

  • SOC2-CC8.1 Change management processes are in place

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 NIST SP 800-218: Access Control

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

NIST SP 800-218 SP800-218-PW.7.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 38 it maps to, and the evidence behind each claim, over MCP and REST.