EvidenceSheet
PCI DSS v4.0.1 · Req 11: Test Security Regularly

11.4.7 Multi-tenant providers support customer penetration testing

Multi-tenant service providers must support their customers in external penetration testing as required by Requirement 11.4.3 (external testing) and Requirement 11.4.4 (remediation). Applicability: applies only when the assessed entity is a multi-tenant service provider. It can be met either by giving customers evidence that penetration testing meeting 11.4.3 (external testing) and 11.4.4 (remediation) was done on their subscribed infrastructure, or by giving each customer prompt access so they can run their own tests. Evidence may be redacted results but must contain enough detail to show every element of the external testing and remediation requirements was satisfied on the customer's behalf. See also Appendix A1. Objective under the customized approach: customers' technical testing needs are met by the multi-tenant provider, either through access or through evidence that equivalent testing was done. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

Source: PCI DSS v4.0.1, 11.4.7. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open PCI DSS v4.0.1 in the compliance library.

Version 4.0.1 is the active version; 4.0 has been retired. Appendix A1 applies only to multi-tenant service providers, A2 only to card-present POS POI terminals that still use SSL or early TLS, and A3 only when a payment brand or acquirer requires it. Which requirements apply to you follows your validation type.

4
artefacts
1
held by a system
1
at each review
moderate
to go live
Vulnerability scanner / patch tooling
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Customer-facing penetration testing policy or rules of engagement · Vulnerability scanner / patch tooling

periodic reviewEvidence produced at each review

  • Records of customer test requests and the access granted · Vulnerability scanner / patch tooling

governing documentDocuments that govern the control

  • Redacted penetration test reports shared with customers, with scope showing their subscribed infrastructure · Policy repository / GRC workspace
  • Contract or responsibility matrix clauses covering customer testing support · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Vulnerability scanner / patch tooling); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

11.4.6 Service provider segmentation testing every six months · 11.5.1 IDS/IPS monitoring of CDE traffic