EvidenceSheet
APRA CPS 230 · Business continuity (paras 33 to 45)

CPS 230 para 33 Business continuity duties: critical operations register, minimise disruption, credible BCP, activate, return

The entity must (a) define and identify its critical operations and keep a register of them; (b) take reasonable steps to cut both the likelihood and the impact of disruption to them; (c) keep a credible BCP showing how it will hold critical operations within tolerance through disruptions, with DR planning covering critical information assets (separate crisis management and DR plans can sit within the BCP set); (d) invoke the BCP when a disruption calls for it; and (e) restore normal operations promptly when the disruption ends. Para 34 describes a critical operation as a process run by the entity or its service provider whose disruption beyond tolerance would materially harm policyholders, depositors, beneficiaries or other customers, or the entity's role in the financial system.

Source: APRA CPS 230, CPS 230 para 33. 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.

4
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. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

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

  • BCP activation log and post-activation reviews · SIEM / log platform

governing documentDocuments that govern the control

  • Register of critical operations with owner, description and date of last review · Policy repository / GRC workspace
  • BCP set including disaster recovery plans for critical information assets · Policy repository / GRC workspace
  • Resilience improvement actions taken to reduce disruption likelihood and impact · Document repository

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

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 sheet

CPS 230 para 32 Notify APRA within 72 hours of a material operational risk incident · CPS 230 para 35 Minimum set of critical operations unless justified