EvidenceSheet

12.9.1 TPSP written acknowledgments to customers

Service providers only: TPSPs must give customers written agreements containing an acknowledgment that the TPSP answers for protecting account data it holds, stores, processes or transmits for the customer, or to whatever extent it could affect the cardholder data or sensitive authentication data of that customer. Applicability: applies only when the assessed entity is a service provider. The wording depends on the service and allocated responsibilities and need not copy the requirement text. An AOC, website declaration, policy statement, responsibility matrix or any evidence sitting outside a written agreement does not qualify as the acknowledgment. Customized approach objective: each TPSP formally accepts, toward its customers, its security obligations.

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

4
artefacts
0
held by a system
1
at each review
hard
to go live
HR system / LMS
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

  • Customer engagement procedure requiring the acknowledgment · HR system / LMS

governing documentDocuments that govern the control

  • Standard customer agreement template with security acknowledgment clause · HR system / LMS
  • Sample executed customer agreements · Vendor register / contract repository
  • Register of customers and agreement status · Vendor register / contract 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

12.8.5 Responsibility allocation between entity and TPSPs · 12.9.2 TPSP support for customer information requests