CPS 230 para 42 APRA Notification of Disruption Outside Tolerance within 24 Hours
The entity must notify APRA as soon as possible and no later than 24 hours after suffering a disruption to a critical operation outside tolerance, covering the nature of the disruption, the action taken, the likely impac
3
artefacts
0
held by a system
3
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 disruption and submission timestamps · Document repository
- Evidence the notification covered all four required content elements · Document repository
- Tolerance breach detection records feeding the notification · Document repository
governing documentDocuments that govern the control
none for this control
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
- Tolerance breach detected late so the 24 hour clock is missed
- Notification sent without impact or return timeframe
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 41 BCP Execution Capability and Tolerance Breach Reporting · CPS 230 para 43 Systematic BCP Testing Program