EvidenceSheet
APRA CPS 234 · Incident management (paras 23 to 26)

CPS 234 para 25 Response plan content: stages and escalation

The response plans set out the mechanisms for (a) handling every relevant stage of an incident, from detection through to post-incident review, and (b) escalating and reporting incidents to the Board, to other governing bodies, and to the people responsible for incident management and oversight, as appropriate.

Source: APRA CPS 234, CPS 234 para 25. 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 234 in the compliance library.

Applies to APRA-regulated entities.

5
artefacts
0
held by a system
2
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

  • Post-incident review reports with actions tracked to closure · Document repository
  • Records of incidents escalated to executives and the Board · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • Response plan sections covering detection, triage, containment, eradication, recovery and post-incident review · Policy repository / GRC workspace
  • Escalation matrix with severity thresholds and Board notification criteria · Policy repository / GRC workspace
  • Communication templates for internal escalation · 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

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 234 para 24 Maintain information security response plans · CPS 234 para 26 Annual review and testing of response plans