12.8.5 Responsibility matrix with TPSPs
Information is maintained about which PCI DSS requirements are managed by each TPSP, which are managed by the entity, and any that are shared between the TPSP and the entity.
5
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
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Annual or change-driven update records · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Responsibility matrix per TPSP mapping each requirement · Policy repository / GRC workspace
- Shared controls documentation · Policy repository / GRC workspace
- Approval by both parties · Policy repository / GRC workspace
- Reconciliation with AOC · Policy repository / GRC workspace
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 matrix
- Shared controls ambiguous
- Updates not synced
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.4 TPSP compliance monitored · 12.9.1 TPSP written acknowledgement of responsibility (SP)