12.8.2 Written agreements with TPSPs
Written agreements with TPSPs are maintained, including acknowledgement by the TPSP that they are responsible for the security of cardholder data they possess, store, process, or transmit on behalf of the customer.
5
artefacts
0
held by a system
2
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
- Procurement review checklist · Document repository
- Legal sign-off records · Document repository
governing documentDocuments that govern the control
- Master agreements with PCI clauses · Vendor register / contract repository
- DPA or addenda referencing PCI DSS · Document repository
- Sample agreements per TPSP · Vendor register / contract 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
- No PCI clause
- Acknowledgement language weak
- Old contracts unrenewed
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 sheet12.8.1 Third-party service provider inventory · 12.8.3 TPSP due diligence