APRA CPS 230

What the authority establishes

CPS 230 requires APRA-regulated entities to manage operational risk, maintain critical operations through disruption, and manage risks arising from service providers through policy, formal agreements, monitoring, and accountable governance.

The standard connects third-party oversight to operational resilience and material-service-provider records. Programs need to identify material arrangements, preserve contractual and monitoring evidence, understand concentration and dependency, and maintain credible continuity and exit plans.

The record is written for operational interpretation, not legal advice. Applicability depends on entity type, jurisdiction, relationship, service, data, criticality, contractual commitments, and later authority guidance.

Who should read it

The primary audiences named in this review are Australian banks, insurers, and superannuation entities, operational-risk and resilience leaders, procurement, legal, compliance, and third-party risk teams, material service providers to APRA-regulated entities. Those roles may divide responsibility differently, but the operating record should still show scope, accountable ownership, evidence, review, exceptions, and the final decision.

Third-party lifecycle implications

Service-Provider Policy

Teams should determine what this authority expects at the service-provider policy stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Materiality Classification

Teams should determine what this authority expects at the materiality classification stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Due Diligence

Teams should determine what this authority expects at the due diligence stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Contracting

Teams should determine what this authority expects at the contracting stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Register Maintenance

Teams should determine what this authority expects at the register maintenance stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Ongoing Monitoring

Teams should determine what this authority expects at the ongoing monitoring stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Business Continuity

Teams should determine what this authority expects at the business continuity stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Exit And Transition

Teams should determine what this authority expects at the exit and transition stage, which function owns the judgment, what evidence must be retained, and what later change would reopen the record.

Capabilities that may support the work

These links identify relevant operating capabilities; they do not state that any product creates compliance.

Intake And Inventory

establishing an accountable record of relationships, products, owners, and critical services. Buyers should test the workflow against their own scope and evidence requirements.

Inherent Risk Tiering

using relationship context to determine proportional diligence and review. Buyers should test the workflow against their own scope and evidence requirements.

Due Diligence And Assessments

collecting and reviewing evidence before and during a relationship. Buyers should test the workflow against their own scope and evidence requirements.

Evidence Collection

preserving source material, responses, and reviewer context. Buyers should test the workflow against their own scope and evidence requirements.

Continuous Monitoring

bringing material external and internal change into an owned response workflow. Buyers should test the workflow against their own scope and evidence requirements.

Issue Remediation

assigning findings, deadlines, exceptions, and closure evidence. Buyers should test the workflow against their own scope and evidence requirements.

Fourth-Party Visibility

identifying and explaining important downstream dependencies. Buyers should test the workflow against their own scope and evidence requirements.

Regulatory Mapping

connecting program records to obligations and examination needs. Buyers should test the workflow against their own scope and evidence requirements.

Reporting

turning program activity into operator, executive, and board-ready information. Buyers should test the workflow against their own scope and evidence requirements.

Offboarding

closing access, data, evidence, and residual obligations when a relationship ends. Buyers should test the workflow against their own scope and evidence requirements.

What software cannot decide

Software can structure records, route work, preserve evidence, surface change, and support reporting. It cannot determine legal applicability, set risk appetite, negotiate accountable contract terms, validate every external claim, accept residual risk, or make management responsible for an outcome. Those remain organizational decisions.

Related market changes