A1.1.4 Penetration testing of tenant separation every six months
The provider must confirm with a penetration test, at least once every six months, that the logical separation controls isolating customer environments are effective. Applicability: this separation testing is additional to the penetration tests required by Requirement 11.4.6. Guidance: a good practice is to build temporary mock-up customer environments and try to reach one from another and from the Internet. Objective under the customized approach: the isolation between each customer environment and every other environment is periodically shown to work. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.
Source: PCI DSS v4.0.1, A1.1.4. 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.
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
- Remediation tickets and retest evidence for separation findings · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
- Last two semi-annual tenant-separation penetration test reports · Vulnerability scanner / patch tooling
- Mock tenant environment build records used in testing · Vulnerability scanner / patch tooling
governing documentDocuments that govern the control
- Test scope and methodology showing cross-tenant and Internet-to-tenant scenarios · Policy repository / GRC workspace
First move
Common gaps auditors find
- Only the 11.4.6 segmentation test is run, with no specific tenant-to-tenant testing
- Interval between tests exceeds six months
- Test covers the network layer but ignores shared application or database tenancy
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 sheetA1.1.3 Customers restricted to their allocated resources · A1.2.1 Per-customer audit logging consistent with Requirement 10