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

NIST SP 800-218 SP800-218-PW.8.2: Execute Security Testing

Design, scope, execute, and document the testing of executable code (dynamic analysis), and record and triage the discovered issues.

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

What else in your programme already covers this

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

PCI DSS 4.0 · 5 controls

  • 11.3.1 11.3.1 Quarterly internal vulnerability scans
  • 11.4.1 11.4.1 Penetration testing methodology defined and implemented
  • 11.4.4 11.4.4 Correct exploitable findings from penetration tests
  • 6.4.1 6.4.1 Public web application review or automated protection
  • 6.5.1 6.5.1 Change control procedure for production

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

BSIMM · 3 controls

  • PT1.1 Use external penetration testers
  • ST1.3 Drive tests with security requirements and features
  • ST1.4 Integrate opportunistic security testing into the pipeline

FedRAMP High · 3 controls

  • CA-8 Penetration Testing
  • CM-3(2) Testing, Validation, and Documentation of Changes
  • SA-11 Developer Testing and Evaluation

FedRAMP Moderate · 3 controls

  • CA-8 Penetration Testing
  • CM-3(2) Testing, Validation, and Documentation of Changes
  • SA-11 Developer Testing and Evaluation

NIST SP 800-53 Rev 5 · 3 controls

OpenSSF Best Practices Badge Criteria · 3 controls

Azure Security Benchmark · 2 controls

  • ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline
  • ASBv3-PV-7 Conduct regular red team operations

C5 (Germany) · 2 controls

  • C5-DEV-06 Testing changes
  • C5-OPS-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests

CIS Controls v8 · 2 controls

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

ISO 27002:2022 · 2 controls

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

NIST Cybersecurity Framework 2.0 · 2 controls

NIST SP 800-161 Rev 1 · 2 controls

AWS Well-Architected Security Pillar · 1 control

CMMC 2.0 · 1 control

ISO 27001:2022 · 1 control

  • 8.29 Security testing in development and acceptance

NIST SP 800-171 Rev 3 · 1 control

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 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.8.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.

If you hold NIST SP 800-53 Rev 571.4% covered · 12 gapsIf you hold C5 (Germany)61.9% covered · 16 gapsIf you hold NIST SP 800-161 Rev 161.9% covered · 16 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.152.4% covered · 20 gapsIf you hold ISO 27002:202252.4% covered · 20 gapsIf you hold Azure Security Benchmark50% covered · 21 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. 0 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 41 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll NIST SP 800-218 controls