CPS 230 para 34 Critical Operations Register, Continuity Plan and Activation
The entity must define, identify and maintain a register of its critical operations, take reasonable steps to minimise the likelihood and impact of disruption to them, maintain a credible business continuity plan setting
3
artefacts
0
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
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
- Activation records and post disruption return to normal evidence · Document repository
governing documentDocuments that govern the control
- Register of critical operations · Policy repository / GRC workspace
- Approved business continuity plan including disaster recovery planning for critical information assets · 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
- BCP exists but omits disaster recovery for critical information assets
- No evidence the plan has ever been activated or rehearsed for activation
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 33 APRA Notification of Operational Risk Incidents within 72 Hours · CPS 230 para 36 Mandatory Minimum Classification of Critical Operations