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

A1.2.2 Support for prompt forensic investigation of any customer

The provider must have processes or mechanisms that support or enable fast forensic examination of the relevant servers whenever any customer suffers a suspected or confirmed security incident. Guidance: quick, efficient responses to investigator requests shorten the time needed to find the cause, remove the attacker and secure the customer environment. Applies to multi-tenant service providers. Objective under the customized approach: every customer can obtain forensic investigation readily when a suspected or confirmed incident occurs.

Source: PCI DSS v4.0.1, A1.2.2. 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
0
held by a system
1
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

none for this control

periodic reviewEvidence produced at each review

  • Records of past forensic support requests and turnaround times · Document repository

governing documentDocuments that govern the control

  • Forensic support procedure for tenant incidents · Policy repository / GRC workspace
  • Evidence preservation and snapshot procedures for shared infrastructure · Policy repository / GRC workspace
  • Contact and escalation path for customer forensic investigators · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

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.2.1 Per-customer audit logging consistent with Requirement 10 · A1.2.3 Customer reporting and remediation of incidents and vulnerabilities