What evidence do auditors commonly ask for on CPS 230 para 41 Notify APRA within 24 hours of a disruption outside tolerance?

APRA disruption notification procedure stating the 24-hour clock and the four required content items; Notification template covering nature, actions taken, likely impact and return timeframe; Copies of notifications lodged and timestamps of tolerance breach versus lodgement.

What is the most common gap auditors find on CPS 230 para 41?

Notification waits until the disruption is resolved

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

`CPS 230 para 41` Notify APRA within 24 hours of a disruption outside tolerance

Clock: as soon as possible and no later than 24 hours after a critical operation is disrupted beyond its tolerance. The notification to APRA must describe the nature of the disruption, what action has been taken, the likely effect on business operations and the expected timeframe for getting back to normal operations.

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

artefacts

held by a system

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

none for this control

governing documentDocuments that govern the control

APRA disruption notification procedure stating the 24-hour clock and the four required content items · Policy repository / GRC workspace
Notification template covering nature, actions taken, likely impact and return timeframe · Policy repository / GRC workspace
Copies of notifications lodged and timestamps of tolerance breach versus lodgement · Policy repository / GRC workspace

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

Notification waits until the disruption is resolved
Notification lacks the expected return-to-normal 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 sheet

CPS 230 para 40 Maintain BCP execution capability; monitor tolerances; report breaches to the Board · CPS 230 para 42 Systematic BCP testing program with an annual exercise