APRA CPS 230: operational risk, critical operations and your service providers
CPS 230 replaced the old outsourcing and business continuity standards with one prudential standard that asks a harder question: can you keep your critical operations running inside the tolerances you set, whoever actually delivers them? This guide covers each obligation, the deadlines and how to build the registers and evidence APRA now expects.
Where CPS 234 asks whether your information assets are secure, CPS 230 asks whether the business keeps working. It requires an entity to know which of its operations are critical, to set a tolerance for how long each can be disrupted and how much data can be lost, to test that it can stay within those tolerances, and to manage the service providers it depends on as if they were its own operations.
The standard is explicit that the board is accountable for the framework and that responsibility cannot be outsourced. APRA’s companion guide, CPG 230, sets out what good practice looks like, and the regulator has said it will be reviewing critical operations lists and tolerance levels closely in its first supervisory cycle.
The obligations
Operational risk management framework
A framework for identifying, assessing and managing operational risk, with a risk profile, appetite and controls, embedded in the entity’s risk management framework under CPS 220. It must be subject to a comprehensive review by operationally independent, competent people at least every three years.
Operational risk profile and controls
Risk assessment that covers people, process, technology and third-party failures, with controls tested for effectiveness and material weaknesses escalated to the board.
Critical operations
Identify the operations that, if disrupted, would have a material adverse impact on depositors, policyholders, beneficiaries or the financial system. APRA specifies a minimum list: payments, deposit-taking and withdrawals, settlements, claims processing, investment management, fund administration, custody and systems of record.
Tolerance levels
For each critical operation, the board approves the maximum period of disruption, the maximum data loss, and the minimum service levels that would be maintained during a disruption.
Business continuity plan
A plan that enables critical operations to be maintained within tolerance, tested at least annually through scenario-based exercises, with findings actioned. The plan must cover the entity’s material service providers.
Material service providers
A register of providers on which the entity relies for a critical operation or that expose it to material operational risk. Arrangements must include termination rights, audit and access rights, sub-contracting obligations and business continuity commitments, with risk assessment before entering and ongoing monitoring.
Notifications
72 hours for a disruption outside tolerance; 20 business days after entering into or materially changing a material service provider agreement; the register submitted to APRA annually and when requested.
Who it applies to
Every APRA-regulated entity, from the largest bank to a small private health insurer or superannuation trustee. Service providers to the sector are affected in turn: cloud providers, core system vendors, administrators, custodians and claims processors are now being asked to accept CPS 230 contract terms and to supply continuity and resilience evidence.
From scope to evidence, in one system
Critical operations and tolerances as first-class records
Each critical operation is recorded with its board-approved tolerance levels, the processes, systems, people and providers it depends on, and the continuity plan that covers it, so the mapping APRA asks for is a report rather than a spreadsheet.
Material service provider register
The third-party module tiers providers, flags those supporting critical operations as material, holds the agreement clauses CPS 230 requires, tracks the 20-business-day notification, and exports the annual register in the form APRA requests.
Business continuity testing with evidence
Scenario exercises are scheduled, recorded with participants and outcomes, and findings tracked to closure, giving the annual testing evidence the standard requires.
Incident clocks and board reporting
Disruptions are tracked against tolerance with the 72-hour timer visible, and operational risk, control testing and provider status flow to board dashboards.
One programme with CPS 234 and ISO 27001
CPS 230 and CPS 234 share the asset, provider and incident records, and the crosswalk reuses ISO 27001 and ISO 22301 evidence, so the two prudential standards run as one programme.
Frequently asked questions
How is CPS 230 different from CPS 234?
CPS 234 is about protecting information assets. CPS 230 is about keeping critical operations running and managing the providers that deliver them. They overlap on third parties and incidents and share most of the same registers, which is why they are best run together.
What counts as a material service provider?
One the entity relies on to deliver a critical operation, or that exposes it to material operational risk. APRA lists the minimum categories, including core technology, data storage and processing, payments, settlements, claims and fund administration, but the entity must assess its own arrangements.
Do we still need our old outsourcing and BCM policies?
They need to be rewritten against CPS 230, not kept. The new standard sets different tests: tolerance levels, scenario testing, provider register and notifications that CPS 231 and 232 did not require.
When did existing contracts have to comply?
From the earlier of the next contract renewal after 1 July 2025 or 1 July 2026. New or materially changed arrangements had to comply from 1 July 2025.
Related frameworks
Reviewed November 2026. This guide is general information about the published framework and is not legal advice; always check the current official text from the publisher before relying on it.