CPS 230 para 32 Identification and Escalation of Incidents and Near Misses
Operational risk incidents and near misses must be identified, escalated, recorded and addressed promptly, and must feed promptly into the assessment of the operational risk profile and of control effectiveness.
3
artefacts
0
held by a system
2
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
- Escalation records with timestamps · Document repository
- Evidence incidents updated the risk profile and control assessments · Document repository
governing documentDocuments that govern the control
- Incident and near miss register · 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
- Near misses not captured
- Incidents recorded but never reflected in the risk profile
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 31 Remediation of Material Operational Risk Weaknesses · CPS 230 para 33 APRA Notification of Operational Risk Incidents within 72 Hours