EvidenceSheet
PCI DSS v4.0.1 · Appendix A1: Additional requirements for multi-tenant service providers

A1.1.3 Customers restricted to their allocated resources

Controls must ensure each customer can access only the resources the provider has allocated to it. Guidance: the purpose is to stop any deliberate or accidental impact on other tenants' environments or account data. Applies to multi-tenant service providers. Customized approach objective: no customer can influence or disrupt resources that belong to a different customer.

Source: PCI DSS v4.0.1, A1.1.3. 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
2
held by a system
1
at each review
easy
to go live
Cloud console / configuration management
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

  • Resource quota and limit configuration · Cloud console / configuration management
  • Noisy-neighbour or resource contention monitoring reports · SIEM / log platform

periodic reviewEvidence produced at each review

  • Resource allocation records per tenant (quotas, reservations, assigned instances) · Document repository

governing documentDocuments that govern the control

  • Privilege listings for sampled tenant accounts · Policy repository / GRC workspace

First move

Automate the pull from your Cloud console / configuration management. Configuration snapshots and change history from the cloud console or IaC repository, diffed against the baseline.

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

A1.1.2 Customers limited to their own cardholder data and CDE · A1.1.4 Penetration testing of tenant separation every six months