Cybernion
← Insights

APRA

CPS 234 Incident Notification: The 72-Hour Clock

3 July 2026 · Updated 3 July 2026

CPS 234 sets two APRA notification clocks. Notify APRA within 72 hours of becoming aware of a material information security incident, one that materially affected or could have affected the entity or its customers, or that was notified to another regulator. Separately, notify within 10 business days of a material control weakness that cannot be remediated in time.

Two questions cause most of the confusion here: what “material” means, and when the clock starts. Both are defined tightly enough to plan around, and both reward a runbook built before the incident, not during it. The detail follows.

What are the CPS 234 notification requirements to APRA?

CPS 234 sets two distinct obligations to notify the Australian Prudential Regulation Authority (APRA). Under paragraph 35, an APRA-regulated entity must notify APRA as soon as possible and no later than 72 hours after becoming aware of an information security incident that materially affected, or had the potential to materially affect, financially or non-financially, the entity or the interests of depositors, policyholders, beneficiaries or other customers, or that has been notified to another regulator in Australia or overseas. Under paragraph 36, it must notify APRA as soon as possible and no later than 10 business days after becoming aware of a material information security control weakness it expects it cannot remediate in a timely manner. The two clocks are separate and can both be running from different triggers. Neither is a maximum to aim for, because the standard says “as soon as possible” first.

What counts as a material information security incident under CPS 234?

Under CPS 234, an incident is notifiable if it materially affected, or had the potential to materially affect, the entity or the interests of its customers, financially or non-financially. The “potential to materially affect” wording matters: an incident does not have to cause proven harm to be notifiable, it only has to have had the capacity to. So a contained breach that could have exposed customer data but did not can still be notifiable. There is also a second trigger independent of the entity’s own materiality judgment: where the entity has notified any other regulator about the incident, in Australia or another jurisdiction, it must notify APRA. That catches incidents reported to the OAIC, ASIC or an overseas authority even where the internal view of materiality is borderline. CPS 234 does not publish a numeric threshold, so materiality is a documented judgment, which is why the assessment should be defined before an incident, not argued during one.

When does the CPS 234 72-hour clock start?

The 72-hour clock starts when the entity becomes aware of the incident, not when it verifies the full impact. This is the single most important operational point in the standard. Awareness can arrive through a monitoring alert, a customer report, a supplier disclosure or a staff escalation, and from that moment the window is running while the team is still triaging. Where detection lands in a team that takes a day to escalate to the people who make the notification call, a third of the window is already gone. That is why CPS 234 pairs with the detection and response obligations in paragraphs 23 to 26, and why entities that meet the clock comfortably have a pre-agreed decision path from alert to APRA contact. The CPS 234 guide covers those response plan obligations in full.

CPS 234 notification clocks at a glance

Event type Clock Who to notify
Material information security incident (affected or could have affected the entity or its customers) As soon as possible, no later than 72 hours from awareness APRA
Incident already notified to another regulator (Australia or overseas) As soon as possible, no later than 72 hours from awareness APRA
Material information security control weakness the entity cannot remediate in a timely manner As soon as possible, no later than 10 business days from awareness APRA

What is a material control weakness under CPS 234, and how is it different?

A material control weakness under CPS 234 is a gap in an entity’s information security controls that is significant and that the entity expects it will not be able to fix in a timely manner. It is notified under a separate clock, 10 business days, and for a different reason: it is not an incident, it is a known deficiency that leaves the entity exposed. The distinction matters because the two obligations catch different moments. The 72-hour clock is about something that happened, while the 10-business-day clock is about something that could happen because a control is missing or broken and cannot be remediated quickly. A failed penetration test finding that cannot be closed, an unpatchable legacy system, or a third party control gap that cannot be forced fixed can all fall in this category. Testing that surfaces these is exactly the systematic testing CPS 234 requires, so the two obligations feed each other.

How does CPS 234 notification work alongside CPS 230 and the Privacy Act?

A single incident can trigger several regimes at once with different clocks, so map them together. CPS 234 notification goes to APRA for information security incidents. CPS 230 has its own operational risk notifications, including a 72-hour clock for material operational incidents and a 24-hour clock for a critical operation disrupted outside tolerance, though CPS 230 says an incident already reported under CPS 234 does not need separate reporting under CPS 230. On top of the prudential standards, an eligible data breach may require notification to the Office of the Australian Information Commissioner under the Notifiable Data Breaches scheme in the Privacy Act. The CPS 234 vs CPS 230 comparison lays out how the prudential clocks interact. The safe design is one incident runbook that lists every clock and every recipient, so an analyst is not deciding notification law mid-incident. Where an organisation needs help building the governance and response capability CPS 234 requires, Cybernion’s IRAP assessment and advisory services include the assurance work that supports prudential compliance.

Frequently asked questions

What is the CPS 234 notification timeframe? CPS 234 requires an APRA-regulated entity to notify APRA as soon as possible and no later than 72 hours after becoming aware of a material information security incident. A separate clock of no later than 10 business days applies after becoming aware of a material information security control weakness the entity expects it cannot remediate in a timely manner.

What counts as a material incident under CPS 234? Under CPS 234, a notifiable incident is one that materially affected, or had the potential to materially affect, financially or non-financially, the entity or the interests of depositors, policyholders, beneficiaries or other customers. An incident already notified to another regulator, in Australia or overseas, is also notifiable to APRA regardless of the entity’s own materiality view.

When does the CPS 234 72-hour clock start? The CPS 234 72-hour clock starts when the APRA-regulated entity becomes aware of the material information security incident, not when it confirms the full scope or finishes investigating. Because awareness triggers the clock, entities need fast internal escalation from detection to the notification decision so they do not lose most of the window to triage.

Does CPS 234 require notification for a control weakness? Yes. Separate from incidents, CPS 234 requires notification to APRA as soon as possible and no later than 10 business days after becoming aware of a material information security control weakness the entity expects it will not be able to remediate in a timely manner. This is a distinct obligation with its own clock, not part of the 72-hour incident rule.

Is a CPS 234 notification the same as a CPS 230 or Privacy Act notification? No. A CPS 234 notification goes to APRA for information security incidents. CPS 230 has its own operational risk notifications, though an incident reported under CPS 234 need not be reported again under CPS 230. Eligible data breaches may also require notification to the OAIC under the Privacy Act. A single incident can trigger several regimes with different clocks.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. Prudential Standard CPS 234 Information Security, APRA, July 2019
  2. Prudential Practice Guide CPG 234 Information Security, APRA, June 2019
  3. Prudential Standard CPS 230 Operational Risk Management, APRA Prudential Handbook, current July 2026

Last updated: 3 July, 2026

Talk to us about your engagement

A scoped proposal within one business day.