Summary
- Australia's operational-resilience regime runs both of its notification clocks from judgements the regulated entity makes: the tolerance level that defines tolerable failure, and the materiality call that decides which incidents count.
- APRA publishes the arithmetic — 43 notifications in 2025-26, and 80 of the top 100 reported service providers based outside Australia — while the documents read carry nothing a stranger could use to test one case.
The most consequential number in Australian operational resilience is written by the party that gets disrupted. Under paragraph 37 of Prudential Standard CPS 230 Operational Risk Management, every APRA-regulated entity must set, for each critical operation it names, three tolerance levels: the maximum period of disruption it would tolerate, the maximum extent of data loss it would accept, and the minimum service levels it would maintain on alternative arrangements while the disruption runs (the made instrument).
Those three numbers are not a disclosure. They are the trigger of a reporting duty. Paragraph 41 requires the entity to notify APRA as soon as possible, and not later than 24 hours after, a disruption to a critical operation outside tolerance. Read the sentence again: the clock does not start when a payment system falls over. It starts when the entity's own number is crossed. The Australian Prudential Regulation Authority built a regime in which the threshold that governs its own knowledge sits inside the register of the firm it supervises.
The second clock is anchored the same way. Paragraph 32 requires notification within 72 hours of becoming aware of an operational risk incident that the entity determines is likely to have a material financial impact, or a material impact on its ability to maintain critical operations (CPS 230). The entity determines. APRA's own practice guide still attributes that 72-hour clock to paragraph 33 in its notification table (CPG 230), while the July 2026 text puts the critical-operations register there instead — a small reminder that instruments drift and their cross-references stay put (the clean PDF).
The regulator is not a spectator. Paragraph 38 lets APRA require an entity to review and change its tolerance levels, and lets APRA set tolerance levels for an entity, or a class of entities, where it identifies heightened risk or material weakness. Paragraph 51 lets APRA order that a service provider, a type of provider or an arrangement be classified as material. Both are real powers, and both are discretionary; in the twelve documents read for this briefing, neither appears as a published determination.
Then there are the registers. Paragraph 33 makes the entity define, identify and maintain a register of its critical operations. Paragraph 48 requires a register of material service providers — those it relies on to run a critical operation, or that expose it to material operational risk — and paragraph 50 requires that register to be submitted to APRA annually. APRA built the plumbing: an October 2024 announcement instructed ADIs, superannuation trustees and insurers to submit a completed register back to APRA by 1 October 2025 (the register-template announcement), and the 2026 template was reissued to accommodate providers covered by the new contractual exemption, with an updated APRA Connect return to follow (APRA's consultation hub).
APRA's guidance is candid about how much joins up. CPG 230 describes the critical-operations register as typically carrying the operation's name, its description, its tolerance levels and the material service provider arrangements that support it — the operation, the number and the provider in one file. The same guide says that where an entity declines to classify a prescribed provider as material, it need not hand APRA the documented reasoning unless APRA asks for it; and the guide states plainly that practice guides do not create enforceable requirements. The duty lives in the standard. The shape of the file lives in the guidance.
What APRA publishes is arithmetic. Its 2025-26 Annual Report, released on 14 October 2026 (APRA's annual report archive), records that APRA received 43 notifications of operational risk incidents or disruptions during the year, that the majority were assessed as low risk, and that in October 2025 every regulated entity submitted a complete list of the material service providers it relies on for critical operations for the first time (the Annual Report). The government's Transparency Portal reproduces the same passage (the mirror) — a copy of one document, not a second count.
The System Risk Outlook, published on 12 November 2026, reaches further into the register without naming anyone in it: of the top 100 providers reported by APRA-regulated institutions, 80 are headquartered or have their principal operations outside Australia (the Outlook). That is 80 of 100 — four in five — and it is the one place in the material read where the fraction is printed rather than implied. The same document says some providers support institutions that collectively hold more than half of APRA-regulated financial assets, and that among significant financial institutions the typical bank identified 52 material service providers, the typical insurer 28 and the typical superannuation fund 23. It also says APRA expects a more complete system-wide view as the collection is formalised. Each of those is a separate measurement on its own stage, and none of them is a case.
Count what that adds up to. Forty-three is an annual total for one financial year. The passage read carries no quarterly split, no institution, no critical operation, no date, no notification reference, and no statement of whether any of the 43 followed a 24-hour tolerance breach or a 72-hour incident notification. A stranger can audit the arithmetic. A stranger cannot test a single case.
That matters more than it might, because the regime already has a public window. APS 330 requires certain locally incorporated significant ADIs to publish prudential information on capital, liquidity and risk exposures (APS 330). On the text inspected, that standard does not reach the CPS 230 registers of critical operations, the per-operation tolerance levels, or the material service provider arrangements. The disclosure instrument exists; the resilience artefacts are not behind it.
Where the checkable point actually sits is worth stating precisely. Across paragraphs 32 to 61 of the July 2026 text as retrieved, together with CPG 230 and APRA's two register pages, read on 18 November 2026, no requirement was found for the entity — or for APRA — to publish either register. That is an argument from silence inside the provisions read, not an express confidentiality rule: no clause imposing or excluding publication was located, and the Attachment and several footnotes were not visible in the retrieved text.
The paragraph numbers come from the made instrument and from indexed excerpts of APRA's clean PDF, which resisted direct text extraction; where APRA's own pages still cite the older numbering, this briefing says so rather than tidying it.
Nothing in the archive answers this subject either. Two literal searches run on 18 November 2026 — the regulator's own name, and the phrase "operational resilience" — returned no rows at all. The nearest thing this desk has published is a pair of clock readings, one on the European Union's DORA reporting chain and one on Singapore's one-hour notification rule, and both of those instruments start their clocks from something the firm does. CPS 230 adds the step before the clock: the threshold that decides whether a clock starts at all is a number the entity writes into its own register.
The fix is small, and it does not require publishing a bank's supplier list. One line per notification would do it: the reporting period, the entity category, the class of critical operation, whether the disruption fell inside or outside the entity's tolerance, and an outcome category. No provider name, no contract, no customer. With that line the 43 becomes testable; without it the tally is a count with the checking end cut off. APRA already collects everything needed to print it. The published record stops one field short of being a record.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






