CIS Controls v8
CIS Control 18: Penetration Testing

CIS Controls v8 CIS-18.2: Perform Periodic External Penetration Tests

Run external penetration tests periodically according to programme requirements, and at least yearly. External testing must include reconnaissance of the enterprise and its environment to uncover information that could be exploited. Penetration testing calls for specialist skills and experience and must be done by a qualified party. Either a clear box or an opaque box approach is acceptable.

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

What else in your programme already covers this

This control maps to 52 controls across 25 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 · 6 controls

  • CA-2 Control Assessments
  • CA-2(1) Independent Assessors
  • CA-7(1) Independent Assessment
  • 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))

FedRAMP Moderate · 6 controls

  • CA-2 Control Assessments
  • CA-2(1) Independent Assessors
  • CA-7(1) Independent Assessment
  • 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))

SOC 2 · 6 controls

  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-CC4.1 CC4.1 Ongoing and separate evaluations of control (COSO principle 16)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

NIST SP 800-53 Rev 5 · 4 controls

  • NIST800-CA-2 CA-2 Control Assessments
  • NIST800-CA-8 CA-8 Penetration Testing
  • NIST800-SA-11 SA-11 Developer Testing and Evaluation
  • SP800-53-CA Assessment, Authorization, and Monitoring Family

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

APRA CPS 234 · 2 controls

  • CPS234-22 Systematic Control Testing Program
  • CPS234-P30 Independence and Skill of Testing Personnel

CMMC 2.0 · 2 controls

DORA · 2 controls

  • DORA-Art.25 Testing of ICT tools and systems
  • DORA-Art.26 Advanced testing of ICT tools, systems and processes based on TLPT

ISO 27002:2022 · 2 controls

  • 8.29 Security testing in development and acceptance
  • 8.8 Management of technical vulnerabilities
  • 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-05 Threats, vulnerabilities, likelihoods, and impacts are used to understand inherent risk and inform risk response prioritization

NIST SP 800-172 · 2 controls

  • 3.11.5e Assess Effectiveness of Security Solutions
  • 3.12.1e Penetration Testing by Independent Agents

PCI DSS 4.0 · 2 controls

  • 11.4.3 11.4.3 External penetration testing annually and after change
  • 6.4.1 6.4.1 Public web application review or automated protection
  • ANSSI-HYG-38 Carry Out Regular Security Checks and Audits and Apply the Corrective Actions

C5 (Germany) · 1 control

  • C5-OPS-19 Managing Vulnerabilities, Malfunctions and Errors - Penetration Tests

HIPAA Security Rule · 1 control

ISO 22301:2019 · 1 control

  • 8.6 Evaluation of business continuity documentation and capabilities

ISO 27701:2019 · 1 control

  • 6.9.6 Technical vulnerability management

NIS2 Directive · 1 control

  • Art.21.2.f Policies and procedures to assess the effectiveness of the cybersecurity risk-management measures
  • 53A-D Penetration Testing

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 CIS Control 18: Penetration Testing

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-18.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 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. 240 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

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