138% more reported CVEs per day in 2026 than last year.New: always-on Fixboxes. Vulnerable dependencies, fixed and verified.

Security testing

Penetration testing requirements by framework

Only a few frameworks name penetration testing outright. Most ask for regular testing of your security measures and leave the method to you, and auditors and customers then expect a pentest anyway. Several of the same frameworks also ask for an inventory of the software components in what you ship, which a pentest does not produce.

Updated

Requirements at a glance

Framework Pentest required? How often Component inventory
PCI DSS 4.0.1 Yes, internal and external (requirement 11.4) At least every 12 months and after significant changes Yes: requirement 6.3.2
SOC 2 Not mandatory; named as an example of an evaluation Usually yearly, as auditors and customers expect Not named
ISO/IEC 27001:2022 Not named; security testing and vulnerability management are controls Set by your risk assessment Asset inventory; components through vulnerability management
GDPR Not named; regular testing of security measures (Article 32) "Regularly" Not named
DORA Yes, threat-led penetration testing for the financial entities the authorities select At least every three years ICT asset registers
NIS2 Not named; assess the effectiveness of security measures Set nationally and by risk Supply chain security is a required measure
Cyber Resilience Act Not named; "effective and regular tests and reviews" of product security "Regular", through the support period Yes: an SBOM covering at least top-level dependencies

PCI DSS penetration testing

PCI DSS 4.0.1 is the most specific. Requirement 11.4 asks for internal and external penetration tests at least once every 12 months and after any significant infrastructure or application upgrade or change, following a defined methodology, by a qualified tester who is organizationally independent. Segmentation controls are tested too.

Requirement 6.3.2 is the one teams overlook: it asks for an inventory of bespoke and custom software and the third-party software components incorporated into it, kept to support vulnerability and patch management. In practice that is an SBOM for every application in scope, and it has to stay current between pentests.

SOC 2 penetration testing

The SOC 2 Trust Services Criteria do not make a pentest mandatory. Penetration testing appears in the points of focus for monitoring activities as one example of a separate evaluation. In practice, most auditors and nearly every enterprise customer reviewing your SOC 2 report expect a yearly pentest, so SaaS companies treat it as required.

ISO 27001 penetration testing

ISO/IEC 27001:2022 does not name penetration testing either. Two Annex A controls lead there: 8.8, management of technical vulnerabilities, and 8.29, security testing in development and acceptance. Your risk assessment sets the method and frequency, and a yearly pentest is the usual evidence that the controls work.

GDPR penetration testing

Article 32 of the GDPR asks for a process for regularly testing, assessing and evaluating the effectiveness of technical and organizational measures for the security of processing. A pentest of the systems that hold personal data is the most common way to show it. Keep the scope and the handling of any personal data found during the test in the rules of engagement.

DORA and NIS2

DORA, the EU's Digital Operational Resilience Act for the financial sector, requires threat-led penetration testing at least every three years for the financial entities the authorities identify, on top of a general testing program. NIS2 asks essential and important entities for policies to assess the effectiveness of their security measures and to secure their supply chain, and leaves the method to national rules.

The Cyber Resilience Act

For manufacturers of products with digital elements sold in the EU, Annex I of the Cyber Resilience Act asks them to "apply effective and regular tests and reviews of the security of the product". A pentest is one way to do it; code review and fuzzing are others. The same annex asks them to identify and document the components in the product, including through an SBOM. See IoT penetration testing for connected devices.

What SaaS customers ask for

Security questionnaires from enterprise buyers usually ask three things: when your last pentest was, who ran it, and whether critical findings are fixed. Have an attestation letter ready, see penetration test reports. More and more questionnaires also ask for an SBOM or how you track vulnerable dependencies, and a yearly pentest does not answer that.

Does an AI pentest count?

None of these frameworks says how the test is done, but PCI DSS asks for a qualified, independent tester and a defined method, and auditors look for the same elsewhere. Today an AI pentest is best used between the human-led tests that compliance asks for. Ask your auditor before replacing one.

The evidence a pentest doesn't produce

CRACI does not run penetration tests and does not make you compliant with any framework. It produces the other half of the evidence: it records every package each of your GitHub Actions builds pulls in, exports the SBOM as CycloneDX or SPDX, and keeps checking each release as new vulnerabilities are published. That is the component inventory PCI DSS 6.3.2 and the CRA ask for, kept current for every release instead of once a year.

Penetration testing requirements: frequently asked questions

Does SOC 2 require penetration testing?

Not strictly. The Trust Services Criteria name it only as an example of an evaluation, but most auditors and enterprise customers expect a yearly pentest.

How often does PCI DSS require a penetration test?

At least once every 12 months and after any significant infrastructure or application change, for both internal and external testing (requirement 11.4).

Does ISO 27001 require a penetration test?

Not by name. Controls 8.8 and 8.29 call for vulnerability management and security testing, and a pentest is the usual evidence that they work.

Does GDPR require penetration testing?

Not by name. Article 32 asks for regular testing of the effectiveness of security measures, and a pentest is a common way to show it.

Does the Cyber Resilience Act require penetration testing?

It requires effective and regular tests and reviews of a product's security, and leaves the method to the manufacturer. A pentest is one way; it also requires an SBOM.

Which frameworks ask for an SBOM?

PCI DSS 6.3.2 asks for an inventory of custom software and its third-party components, and the Cyber Resilience Act asks for an SBOM. Customers increasingly ask for one too.

Keep the component inventory current

Record an SBOM of every release in your GitHub Actions builds and track new vulnerabilities in each one.

Book a demo