CPS 230 para 59 APRA Notification of Service Agreements and Offshoring
The entity must notify APRA as soon as possible and no more than 20 business days after entering into or materially changing an agreement for a service it relies on to undertake a critical operation, and must notify APRA
3
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
- Notification records with execution and submission dates · Document repository
governing documentDocuments that govern the control
- Offshoring notifications evidencing they preceded execution · Document repository
- Identification of arrangements where data or personnel move offshore · 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
- Offshoring notified after signature instead of before
- The 20 business day clock tracked from contract start rather than execution
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 sheetCPS 230 para 58 Monitoring and Senior Management Reporting on Material Arrangements · CPS 230 para 60 Internal Audit Review of Proposed Critical Operation Outsourcing