12.8.3 TPSP due diligence
An established process is implemented for engaging TPSPs, including proper due diligence prior to engagement.
5
artefacts
0
held by a system
3
at each review
hard
to go live
Vendor register / contract 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
- Sample due diligence packs (security questionnaires, SOC 2 reviews) · Vendor register / contract repository
- Risk assessment outputs per vendor · Vendor register / contract repository
- Approval records before engagement · Vendor register / contract repository
governing documentDocuments that govern the control
- TPSP due diligence procedure · Vendor register / contract repository
- Risk tiering criteria · 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
- Due diligence informal
- No risk tiering
- Engagement without approval
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.2 Written agreements with TPSPs · 12.8.4 TPSP compliance monitored