CIS Controls v8 18.1 — Establish and Maintain a Penetration Testing Program

What this control requires

Establish and maintain a penetration testing program suited to the enterprise's size, complexity, and maturity. Define the scope (networks, web apps, APIs, hosted services, physical controls), frequency, limitations (testing hours, excluded attack types), points of contact, remediation processes (how findings are handled), and retrospective requirements.

In plain English

Establish and maintain a penetration testing program suited to the enterprise's size, complexity, and maturity. In practice, this means you can prove you establish and maintain enterprise-level controls on a defined cadence.

Why it matters

The CIS Controls are an industry-vetted, prioritised defence: skipping a safeguard widens the attack surface that the safeguards above and below it assume is closed. Audit frameworks (FedRAMP, PCI DSS, HIPAA) all cite CIS as evidence of due care.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A CIS-aligned reviewer wants to see (a) which Implementation Group you are targeting, (b) a documented owner for the safeguard, and (c) a tooling or process artefact (config, scan output, ticket) that proves the safeguard runs on the cadence the control demands.

Within Identify, the assessor will trace your implementation back to the catalogue reference (Control 18.1) and look for objective evidence on the latest two assessment cycles.

How to implement

Code Review Testing

Pipeline. Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

Physical Security

Inheritance. For cloud-only operations, inherit physical controls from the provider's SOC 2 / ISO 27001 report and document the inheritance in the SoA.

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Operational checklist

• Establish And Maintain. Document the trigger, the owner and the cadence.
• Define. Document the trigger, the owner and the cadence.
• Scope: enterprise.

Evidence to collect

• Policy Document. A signed and version-controlled policy / standard / procedure document.

Signed policy or standard documents the safeguard. Focus: Establish and Maintain a Penetration Testing Program.

Common pitfalls

• Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• ISO/IEC 27001:2022 A.7.3 — Securing offices, rooms and facilities
• SOC 2 (2017 TSC) CC6.7 — Transmission Controls

Related controls in CIS Controls v8

• Control 7.5 — Perform Automated Vulnerability Scans of Internal Enterprise Assets
• Control 7.6 — Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets
• Control 18.2 — Perform Periodic External Penetration Tests
• Control 2.2 — Ensure Authorized Software is Currently Supported
• Control 17.3 — Establish and Maintain an Enterprise Process for Reporting Incidents
• Control 18.5 — Perform Periodic Internal Penetration Tests

References

• Center for Internet Security — CIS Controls v8
• Catalogue identifier: Control 18.1

Topics: governance riskapplication securitycode review testingphysical securitypolicy management