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

A1.2.1 Per-customer audit logging consistent with Requirement 10

The provider must enable audit logging for every customer environment, in line with PCI DSS Requirement 10, such that: logging is on for common third-party applications; logging is switched on by default; each customer's logs can be reviewed only by that customer; the provider tells each customer clearly where its logs are kept; and the content and availability of log data match Requirement 10. Applies to multi-tenant service providers. Customized approach objective: all customers have logging capability without any loss of confidentiality for other customers.

Source: PCI DSS v4.0.1, A1.2.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
2
held by a system
0
at each review
moderate
to go live
Identity provider / directory
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

  • Log access control settings showing per-tenant restriction · Identity provider / directory
  • Log retention and content settings mapped to Requirement 10 · SIEM / log platform

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Default logging configuration templates for tenant environments · Policy repository / GRC workspace
  • Customer-facing documentation stating log locations · Policy repository / GRC workspace
  • List of supported third-party applications with logging enabled · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (Identity provider / directory); 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

A1.1.4 Penetration testing of tenant separation every six months · A1.2.2 Support for prompt forensic investigation of any customer