Logo

CPS 230 for Software Vendors: What APRA-Regulated Clients Ask

  1. Nabeel Al Nassir

  2. November 13, 2026

  3. 8 Min read

pixbit solutions

CPS 230 is APRA's prudential standard on operational risk management. It applies directly to APRA-regulated banks, insurers and superannuation trustees, but software vendors feel it too, because regulated entities must manage the service providers their critical operations rely on. Vendors should expect contract terms on incident notice, subcontractors, continuity testing and exit, and questions about monitoring, recovery and audit logs. Software designed for resilience makes those answers straightforward.

What CPS 230 Is

Prudential Standard CPS 230 Operational Risk Management sets out how APRA-regulated entities must manage operational risk, maintain their critical operations through disruption, and manage the risks that come from relying on service providers. It took effect on 1 July 2025 and replaced several older standards on service provider arrangements and business continuity with a single framework.

The standard applies to authorised deposit-taking institutions such as banks, general insurers, life insurers, private health insurers and registrable superannuation entity licensees. For arrangements with service providers that already existed when the standard began, the service provider requirements applied from the earlier of the next contract renewal or 1 July 2026, so by now they apply to all arrangements.

CPS 230 is built around three ideas. First, entities must identify and manage operational risk across the business, with clear accountability at board and senior management level. Second, entities must identify their critical operations, set tolerance levels for disruption and be able to keep those operations within tolerance. Third, entities must manage the risks of relying on service providers, particularly those that are material to critical operations.

Why a Software Vendor Is Pulled In

A critical operation is a process whose disruption would have a material impact on the entity's customers or its role in the financial system. Payments, deposit-taking, claims processing, customer enquiries and investment management are typical examples. Many of those operations run on software, and much of that software is supplied, hosted or supported by vendors.

CPS 230 requires entities to maintain a service provider management policy and to identify material service providers, meaning providers they rely on to undertake a critical operation or that expose them to material operational risk. Arrangements with material service providers need a formal agreement covering specific matters, and the entity must monitor the provider's performance and risk throughout the relationship.

The entity must also notify APRA as soon as possible, and not more than 20 business days, after entering into or materially changing an agreement with a service provider it relies on for a critical operation. Material offshoring arrangements must be notified before they are entered into. For a vendor, being classified as a material service provider changes the relationship: procurement becomes due diligence, and the contract becomes a regulatory document.

What APRA-Regulated Clients Will Ask a Vendor For

Vendors supporting regulated entities should prepare for a consistent set of requests.

Contract terms come first. Expect clauses on service levels, the vendor's obligation to notify incidents quickly, audit and access rights for the entity and for APRA, confidentiality and data security, business continuity commitments, and termination and exit arrangements that allow an orderly transition to another provider.

Subcontractors come next. Entities must understand material fourth parties, the providers that their providers rely on. Vendors should be ready to list the hosting providers, support partners and other subcontractors involved in delivering the service, and to explain how they manage them.

Incident notification is critical. APRA requires an entity to notify it as soon as possible, and not later than 72 hours, after becoming aware of an operational risk incident likely to have a material financial impact or a material impact on its ability to maintain critical operations. It must notify APRA within 24 hours if a critical operation is disrupted outside tolerance. Entities cannot meet those timeframes if their vendors take days to tell them about an incident, so contracts increasingly specify notice within hours.

Continuity and testing follow. Entities must maintain credible business continuity plans and test them. Vendors should expect to take part in scenario tests, to share their own continuity and disaster recovery plans, and to show evidence that recovery has been tested rather than only documented.

Security questionnaires usually arrive alongside these requests. They cover access control, encryption, vulnerability management, penetration testing and staff vetting, and they are easier to answer consistently when the vendor keeps one maintained set of answers and evidence.

Exit planning closes the list. Entities must be able to exit a service provider arrangement without undue disruption. Vendors should be able to explain how data would be returned, in what format and how quickly.

Building Resilience Into the Software

Much of what regulated clients ask for depends on how the software is built and run, not just on contract wording.

Monitoring is the foundation. The vendor should know that a problem is happening before the client does, which means monitoring availability, response times, error rates and key business transactions, with alerts that reach people who can act.

Recovery objectives need to be explicit. For each service supporting a critical operation, the vendor should state how quickly service can be restored and how much data could be lost in a worst case, and those figures should match the client's tolerance levels. Backups, replication and failover should be designed to meet them and tested regularly.

Dependency maps help both sides. A clear picture of which components, cloud services and third parties the service depends on makes it easier to assess risk, plan continuity and answer questions about fourth parties.

Audit logs support investigation and assurance. The software should record administrative actions, configuration changes, access to sensitive data and system events, retained for an agreed period and exportable to the client.

Change management matters too. Many incidents begin with a change. Controlled releases, the ability to roll back quickly and records of what changed and when all reduce the likelihood and impact of disruption.

Hosting decisions belong in the same conversation. Where the vendor hosts the service, the client will want to know the cloud provider, the regions used, how environments are separated and whether data stays in Australia. Hosting critical services in Australian regions, with backups and logs held in-region, often simplifies both the client's risk assessment and its APRA notifications about offshoring.

Incident Handling and Notification Support

When something goes wrong, the vendor's first job is to tell the client quickly and accurately, so the client can decide whether APRA notification is required. That calls for a defined incident process: detection, triage, an initial notice to the client within the contracted time, regular updates, and a post-incident report explaining the cause, the impact and the fix.

Software can make this faster. Status pages, automated alerts to named client contacts and incident timelines generated from monitoring data reduce the time between detection and notice, and give the client the facts it needs.

CPS 230 and CPS 234 Together

CPS 230 sits alongside CPS 234 Information Security, which requires regulated entities to maintain information security capability proportionate to the threats they face, including where information assets are managed by third parties. CPS 234 requires notification to APRA within 72 hours of becoming aware of a material information security incident. Vendors will usually be assessed against both standards at once, so security controls, testing and incident handling should be presented as one coherent picture rather than two separate answers.

CPS 230 requirementVendor evidenceSoftware capability
Material service provider agreementContract covering required mattersService levels that can be measured
Incident notificationContracted notice times, incident processMonitoring and automated alerts
Critical operations within toleranceRecovery objectives matched to toleranceBackups, replication, tested failover
Fourth-party riskList of subcontractors and how they are managedDependency map
Business continuity testingTest results and remediationScenario testing support
Exit arrangementsData return and transition planFull data export in usable formats
Assurance and auditAudit rights, reportsExportable audit logs

Summary

CPS 230 places operational resilience at the centre of how APRA-regulated entities choose and manage software vendors. A vendor that supports a critical operation should expect to be treated as a material service provider, with contract terms on notice, subcontractors, testing and exit, and questions about monitoring and recovery. Designing software with monitoring, explicit recovery objectives, dependency maps, audit logs and controlled change makes those answers easy to give. For related deadlines, see Australia's 2026 compliance deadlines.

ItemDetail
StandardAPRA Prudential Standard CPS 230 Operational Risk Management
Took effect1 July 2025
Pre-existing service provider contractsEarlier of next renewal or 1 July 2026
Incident notice to APRAWithin 72 hours for material operational risk incidents
Disruption outside toleranceWithin 24 hours
New or changed material arrangementsWithin 20 business days

Frequently Asked Questions

What is CPS 230?

CPS 230 is APRA's Prudential Standard on Operational Risk Management. It requires APRA-regulated entities to manage operational risk, keep critical operations within tolerance through disruption, and manage risks from service providers.

Does CPS 230 apply to software vendors?

Not directly. It applies to APRA-regulated entities, but those entities must manage their service providers, so vendors supporting critical operations are drawn in through contracts, due diligence and ongoing monitoring.

What is a material service provider?

A material service provider is one that an APRA-regulated entity relies on to undertake a critical operation, or that exposes it to material operational risk. Arrangements with these providers need formal agreements and ongoing oversight.

When did CPS 230 start?

CPS 230 took effect on 1 July 2025. For service provider arrangements already in place at that time, the requirements applied from the earlier of the next renewal or 1 July 2026.

How quickly must incidents be reported to APRA?

An entity must notify APRA as soon as possible, and not later than 72 hours, after becoming aware of an operational risk incident likely to have a material impact, and within 24 hours if a critical operation is disrupted outside tolerance.

How does CPS 230 relate to CPS 234?

CPS 234 covers information security, including information assets managed by third parties, while CPS 230 covers operational risk and resilience more broadly. Vendors are usually assessed against both at the same time.

Build Software Your APRA Clients Can Rely On

Pixbit builds and supports software with the monitoring, recovery, audit logging and data export that regulated clients expect under CPS 230. Adding monitoring, logging and export to an existing product sits at the lower end of the investment range, and a platform designed for critical operations at the higher end. Explore our custom software development service or book a discovery session, and Pixbit scopes in a single discovery session.

Nabeel Al Nassir
Author
Nabeel Al Nassir

Digital Marketer

Share on

https://pixbitsolutions.com/au/blogs/cps-230-software-vendor-requirements
Have an idea that needs to go mobile? Launch it with us!

Have an idea that needs to go mobile? Launch it with us!

Let's Talk
Contact Us

You May Also Like

Explore insightful articles and tips from our experts on the latest trends in web development and marketing.

Have an idea ?

Let's make it happen

Tell us your business aspirations, and let's craft a custom solution that drives business growth, ensuring satisfaction and exceeding your goals with precision.

Let's Talk