Art.28 ICT third-party risk: general principles
Financial entities shall manage ICT third-party risk as an integral component of ICT risk, maintain a Register of Information on all contractual arrangements for the use of ICT services, report it to competent authoritie
2
artefacts
0
held by a system
1
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
- Pre-contract risk assessment records · Vendor register / contract repository
governing documentDocuments that govern the control
- A Register of Information of ICT third-party arrangements reported to the competent authority · 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 Register of Information
- No pre-contract third-party risk assessment
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 sheetArt.27 Requirements for testers for the carrying out of TLPT · Art.29 Preliminary assessment of ICT concentration risk at entity level