NIST SP 800-172
CA

NIST SP 800-172 3.12.1e: Penetration Testing by Independent Agents

Conduct penetration testing at least annually, leveraging automated scanning tools and ad hoc tests using subject matter experts.

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

What else in your programme already covers this

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

CIS Controls v8 · 5 controls

  • CIS-16.13 Conduct Application Penetration Testing
  • CIS-18.1 Establish and Maintain a Penetration Testing Program
  • CIS-18.2 Perform Periodic External Penetration Tests
  • CIS-18.5 Perform Periodic Internal Penetration Tests
  • CIS-7.6 Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets

FedRAMP High · 5 controls

  • CA-2(1) Independent Assessors
  • CA-8 Penetration Testing
  • CA-8(1) Penetration Testing | Independent Penetration Testing Agent or Team (CA-8(1))
  • CA-8(2) Penetration Testing | Red Team Exercises (CA-8(2))
  • RA-5 Vulnerability Monitoring and Scanning

FedRAMP Moderate · 5 controls

  • CA-2(1) Independent Assessors
  • CA-8 Penetration Testing
  • CA-8(1) Penetration Testing | Independent Penetration Testing Agent or Team (CA-8(1))
  • CA-8(2) Penetration Testing | Red Team Exercises (CA-8(2))
  • RA-5 Vulnerability Monitoring and Scanning

NIST SP 800-53 Rev 5 · 4 controls

PCI DSS 4.0 · 4 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.2 11.4.2 Internal penetration testing annually and after change
  • 11.4.3 11.4.3 External penetration testing annually and after change

ISO 27001:2022 · 3 controls

  • 5.35 Independent review of information security
  • 8.29 Security testing in development and acceptance
  • 8.8 Management of technical vulnerabilities

ISO 27002:2022 · 3 controls

  • 5.35 Independent review of information security
  • 8.29 Security testing in development and acceptance
  • 8.8 Management of technical vulnerabilities
  • NIST-CSF-GV.OV-03 Organizational cybersecurity risk management performance is evaluated and reviewed for adjustments needed
  • NIST-CSF-ID.IM-01 Improvements are identified from evaluations
  • NIST-CSF-ID.RA-01 Vulnerabilities in assets are identified, validated, and recorded

NIST SP 800-161 Rev 1 · 3 controls

  • ASBv3-PV-7 Conduct regular red team operations
  • PV-5 Perform vulnerability assessments

C5 (Germany) · 2 controls

  • C5-OPS-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests
  • C5-OPS-22 Testing and Documentation of known Vulnerabilities
  • ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

  • 03.11.02 Vulnerability Monitoring and Scanning

NIST SP 800-218 · 1 control

SOC 2 · 1 control

  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)

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.

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

NIST SP 800-172 3.12.1e 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.

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.

Query this from an agent

The graph holds this control, the 49 it maps to, and the evidence behind each claim, over MCP and REST.