CPS 230 para 17 Integrate operational risk management; align BCP with recovery and exit planning
Operational risk management has to be built into the entity's wider risk management framework and processes rather than run separately, and its continuity planning has to sit consistently with its recovery and exit planning under CPS 190, never contradicting or weakening it.
Source: APRA CPS 230, CPS 230 para 17. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open APRA CPS 230 in the compliance library.
Applies to APRA-regulated entities.
These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.
system holds itEvidence a system already holds
none for this control
periodic reviewEvidence produced at each review
- Minutes of the forum that approves both plans showing joint review · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Mapping showing operational risk processes embedded in enterprise risk processes (shared taxonomy, reporting lines, committees) · Document repository
- Reconciliation between the BCP and the CPS 190 recovery and exit plan, with conflicts resolved · Policy repository / GRC workspace
First move
Common gaps auditors find
- BCP and recovery plan owned by different teams with conflicting assumptions about critical operations
- Operational risk reported in a separate silo from enterprise risk
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 16 Review operational risk management within the CPS 220 / SPS 220 framework reviews · CPS 230 para 19 Board ultimate accountability for operational risk oversight