NIST SP 800-172
SI

NIST SP 800-172 3.14.7e: Verify Correctness of Security Functions

Verify the correctness of security critical or essential software, firmware, and hardware components through review, analysis, testing, or evaluation.

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 17 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

Azure Security Benchmark · 4 controls

  • ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
  • ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline
  • ASBv3-PV-7 Conduct regular red team operations
  • PV-2 Audit and enforce secure configurations

NIST SP 800-161 Rev 1 · 4 controls

NIST SP 800-218 · 4 controls

NIST SP 800-53 Rev 5 · 4 controls

PCI DSS 4.0 · 4 controls

  • 10.7.2 10.7.2 Detect and alert on critical security control failures
  • 11.4.2 11.4.2 Internal penetration testing annually and after change
  • 6.2.3 6.2.3 Code review before release
  • 6.2.3.1 6.2.3.1 Manual code review independence and approval

C5 (Germany) · 3 controls

CIS Controls v8 · 3 controls

  • CIS-16.12 Implement Code-Level Security Checks
  • CIS-16.13 Conduct Application Penetration Testing
  • CIS-18.4 Validate Security Measures

FedRAMP High · 3 controls

  • CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))
  • SI-6 Security and Privacy Function Verification (SI-6)

FedRAMP Moderate · 3 controls

  • CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
  • SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))
  • SI-6 Security and Privacy Function Verification (SI-6)

NIST Cybersecurity Framework 2.0 · 3 controls

  • NIST-CSF-ID.IM-02 Improvements are identified from security tests and exercises, including those done in coordination with suppliers and relevant third parties
  • NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded
  • NIST-CSF-ID.RA-08 Processes for receiving, analyzing, and responding to vulnerability disclosures are established

CMMC 2.0 · 2 controls

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

HIPAA Security Rule · 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

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-66 Rev 2 · 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 SI

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

NIST SP 800-172 3.14.7e is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-172 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 24 of 35 NIST SP 800-172 controls already carry evidence.

If you hold NIST SP 800-53 Rev 568.6% covered · 11 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.165.7% covered · 12 gapsIf you hold NIST SP 800-161 Rev 162.9% covered · 13 gapsIf you hold FedRAMP Moderate60% covered · 14 gapsIf you hold NIST Cybersecurity Framework 2.048.6% covered · 18 gapsIf you hold C5 (Germany)45.7% covered · 19 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. 5 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 44 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll NIST SP 800-172 controls