EvidenceSheet

12.9.2 TPSP supports customer requests for compliance info (SP)

Additional requirement for service providers: TPSPs support their customers' requests for information to meet Requirements 12.8.4 and 12.8.5 by providing PCI DSS compliance status and information about which requirements

5
artefacts
0
held by a system
1
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Annual update cycle · Document repository

governing documentDocuments that govern the control

  • Customer trust portal or AOC distribution process · Document repository
  • Standard responsibility matrix shared with customers · Policy repository / GRC workspace
  • SLA for compliance info requests · Vendor register / contract repository
  • Sample customer responses · Document repository

First move

This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.

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.9.1 TPSP written acknowledgement of responsibility (SP) · 12.10.1 Incident response plan