Compliance / PCI DSS

    PCI DSS penetration testing, scoped to the CDE.

    Internal, external, and segmentation-validation testing that satisfies PCI DSS v4.0 Requirement 11.4 — bounded tightly to your cardholder data environment, and delivered in the format your QSA already knows how to review.
    Segmentation testRequirements 11.4.5 & 11.4.6Out of scopeFlat · untested estateCDE · in scopeRaised, walled, testedReachable path1 of 4 probes clearedSegmentation confirmed by test12 mo · 6 mo SP · after any change

    The honest requirement

    PCI DSS 11.4 explicitly requires penetration testing.

    Unlike SOC 2 and HIPAA, PCI DSS is unambiguous. Requirement 11.4 of PCI DSS v4.0 mandates both internal and external penetration testing at least annually and after any significant change to the cardholder data environment. This is not a "recommended practice" — a QSA cannot sign an ROC or SAQ without it.

    For merchants and service providers relying on network segmentation to reduce PCI scope, Requirement 11.4.5 requires segmentation-validation testing at least every 12 months, and Requirement 11.4.6 raises that to every six months for service providers. Both also trigger after any change to segmentation controls or methods. Testing methodology must follow an industry-accepted approach (NIST SP 800-115, OWASP, PTES).

    What auditors accept

    Evidence, in the format your assessor already uses.

    • Report following NIST SP 800-115 / PTES methodology

    • Internal and external testing components clearly separated

    • Application-layer testing per Requirement 11.4.2

    • Segmentation-validation results per Requirements 11.4.5 & 11.4.6

    • Multi-tenant support for customer-run external testing per Requirement 11.4.7

    • Remediation of exploitable and high-risk findings, retested

    • Report your QSA can attach directly to the ROC or SAQ

    Engagement mapping

    The D1–D9 engagement, mapped to PCI DSS evidence.

    PCI DSS evidence timeline

    Testing window

    1. D1

      Recon & scoping, CDE boundary confirmation, segmentation map review.

    2. D2–3

      External and internal surface mapping.

    3. D4–6

      Exploit reasoning against CDE-adjacent surfaces and app layer.

    4. D7–8

      Segmentation-validation testing from out-of-scope networks.

    5. D9

      Reporting, remediation plan, retest of exploitable findings.

    D1
    Scope memo listing in-scope CDE assets and segmentation controls under test.Recon & scoping, CDE boundary confirmation, segmentation map review.
    D2–3
    Asset inventory supporting Requirement 11.4.1 methodology documentation.External and internal surface mapping.
    D4–6
    Findings register aligned to Requirements 11.4.2 (app) and 11.4.3 (external).Exploit reasoning against CDE-adjacent surfaces and app layer.
    D7–8
    Proof that out-of-scope networks cannot reach the CDE, per Requirements 11.4.5 & 11.4.6.Segmentation-validation testing from out-of-scope networks.
    D9
    Signed report your QSA attaches to the ROC or SAQ.Reporting, remediation plan, retest of exploitable findings.

    PCI DSS FAQ

    Frequently asked.

    PCI DSS v4.0 Requirement 11.4 mandates internal and external penetration testing at least annually and after any significant change to the cardholder data environment. Application-layer testing (11.4.2) and external (11.4.3) and internal (11.4.4) network-layer testing are all in scope, using an industry-accepted methodology like NIST SP 800-115, OWASP, or PTES. Exploitable findings must be corrected and retested.

    Requirement 11.4.5 requires all entities using segmentation to validate those controls at least every 12 months. Requirement 11.4.6 raises that to every six months for service providers. Both also trigger after any change to segmentation controls or methods. The test must confirm that out-of-scope systems cannot reach the CDE, attempted from every out-of-scope network segment.

    It depends on which SAQ. SAQ A merchants (fully outsourced e-commerce) typically do not require a pen test. SAQ A-EP, SAQ D-Merchant, and SAQ D-Service Provider merchants do — Requirement 11.4 applies. If you're unsure which SAQ applies to you, we'll confirm during scoping before quoting.

    Requirement 11.4.7 requires multi-tenant service providers to support their customers' external penetration testing under 11.4.3 and 11.4.4. In practice that means a documented process for authorizing customer tests against their own tenant. We scope both sides of that.

    Evidence by framework

    Same engagement. Different paperwork.

    Covers internal, external, and segmentation testing with the dated retest 11.4.4 asks for.

    Mapped to 11.4.1 – 11.4.6

    Next step

    Scope a PCI DSS pen test.

    Thirty-minute scoping call. Fixed-scope quote within one business day. Report and evidence bundle ready for your auditor.

    Request a pen test scope call →