EvidenceSheet

A1.1.1 Logical separation between provider and customer environments

A multi-tenant service provider must implement logical separation so that: (1) the provider itself cannot reach into any customer environment unless authorized, and (2) customers cannot reach into the provider's own environment unless authorized. Guidance: tenant environments should be isolated from one another and from the provider's infrastructure; customer-facing areas such as billing or configuration portals should be kept apart from the provider's private environment; and provider access to customer environments is handled under Requirement 8.2.3. Objective under the customized approach: the provider's environment is closed to customers, and customer environments are closed to the provider without authorization. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

Source: PCI DSS v4.0.1, A1.1.1. 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.

5
artefacts
1
held by a system
2
at each review
hard
to go live
Policy repository / GRC workspace
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

  • Hypervisor, VPC or tenant isolation configuration exports · Cloud console / configuration management

periodic reviewEvidence produced at each review

  • Authorization workflow and approval records for provider staff access into tenant environments · Cloud console / configuration management
  • Interview notes with platform engineering · Document repository

governing documentDocuments that govern the control

  • Multi-tenant architecture and separation design document · Policy repository / GRC workspace
  • Network diagrams showing isolation of management, portal and tenant zones · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review 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

12.10.7 Response procedures for PAN found in unexpected locations · A1.1.2 Customers limited to their own cardholder data and CDE