Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Depending on one hosting provider: concentration risk and APRA CPS 230

Technical article
Cloud

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

This is general information, not legal advice.

Relying on one hosting provider is a legitimate choice, but it concentrates risk: one contract, one control system and one group of people sit behind every system you run there. APRA's Prudential Standard CPS 230 does not tell regulated entities to avoid a single provider. It tells them to identify which providers they depend on for critical work, assess concentration before and during the arrangement, agree specific contract terms, test what happens when a provider fails, and keep a workable way out.

CPS 230 binds APRA-regulated entities such as banks, insurers and superannuation trustees. It does not bind a hosting provider as such, and it does not bind a business outside APRA's reach. This guide is for regulated entities reviewing service providers, and for larger or non-regulated businesses that want to borrow its questions. It explains what the standard says and which parts translate into practical checks. It makes no statement about whether any provider meets it.

Why it matters

Our illustration of how provider problems arise: a mistaken change, a regional outage, a billing or account dispute, a security incident. When one provider holds your servers, your backups, your identity system and your DNS, one event can take out all of them at once. Our reading: that bundle, not the size of any single system, is what concentration risk looks like.

For regulated entities this is a prudential matter. CPS 230 states that an entity "must not rely on a service provider unless it can ensure that in doing so it can continue to meet its prudential obligations in full and effectively manage the associated risks". The guidance adds that where an entity uses a provider, "the entity still owns and is responsible for managing its risk".

Who CPS 230 applies to

The standard's application section lists authorised deposit-taking institutions, general insurers, life companies, private health insurers and registrable superannuation entity licensees, along with certain related holding companies. The version read for this guide states in paragraph 6 that it commences on 1 July 2026. APRA's page says targeted amendments published on 30 April 2026 add limited exemptions from some contract requirements for certain non-traditional service providers such as central banks and clearing facilities. Those exemptions are not relevant to an ordinary hosting contract (our reading).

A prudential practice guide such as CPG 230 shares APRA's views on sound practice. APRA says such guides "do not themselves create enforceable requirements". The guide says each regulated entity, "regardless of size", has operational risks, and expects significant financial institutions to have stronger practices. The standard itself says an entity's approach must be appropriate to its size, business mix and complexity.

What CPS 230 expects about material service providers

Decide which providers are material. Paragraph 48 says "Material service providers are those on which the entity relies to undertake a critical operation or that expose it to material operational risk." Paragraph 49 lists services that must be classified as material unless the entity can justify otherwise, including, for all regulated entities, "risk management, core technology services and internal audit". Our reading: a hosting provider that runs the core systems for a critical operation is likely to be caught, but the standard does not name hosting providers and each entity must decide.

Keep a register. The entity must maintain a register of material service providers and submit it to APRA each year (paragraphs 48 and 50). CPG 230 says a prudent entity would record the person responsible for each arrangement, the critical operations it supports, and, where the arrangement delivers a critical operation, "take reasonable steps to list fourth parties". A fourth party is, in the standard's footnote, a party that a service provider relies on to deliver services to the entity. Our reading: for a hosting arrangement, that could be a data-centre operator, network carrier, software supplier or a larger cloud platform underneath a reseller.

Assess concentration before you sign. Before entering or materially changing a material arrangement, the entity must assess risks "including risks associated with geographic location or concentration of the service provider(s) or parties the service provider relies on in providing the service" (paragraph 52). CPG 230 lists "concentration risk" among the factors to consider when selecting a provider, alongside country or region risk, supplier risk and reputational risk. It adds that a prudent entity would manage the risk of groups of providers "where the aggregate impact is material, but each individual provider is not". Our reading: many small dependencies on the same upstream platform can add up to one large one.

Sign a formal agreement with minimum content. Paragraph 53 requires, among other things, the services and service levels to be specified, and rights and responsibilities covering ownership of assets, ownership and control of data, dispute resolution, audit access, liability and indemnity. It also requires notification by the provider of "its use of other material service providers", responsibility of the provider for failures of its subcontractors, a force majeure provision, and termination rights including "the right to terminate both the arrangement in its entirety or parts of the arrangement". Paragraph 54 adds access for APRA to documentation, data and an on-site visit.

Monitor. Paragraph 59 requires regular assessment of performance against agreed service levels, the effectiveness of controls, and compliance of both parties with the agreement. CPG 230 suggests reviews of operational issues including information security incidents and service disruptions.

Plan to exit. Paragraph 55 requires the entity, for each material arrangement, to "ensure it can conduct an orderly exit from the arrangement if needed" and to ensure it can execute its business continuity plan (BCP). The service provider policy must cover how the entity will enter, monitor, substitute and exit agreements (paragraph 47). CPG 230 expects BCPs to consider "alternative arrangement considerations (including where the service provider is unable to provide the service for an extended period of time)".

Tolerance levels, testing and notification

CPS 230 expects an entity to set tolerance levels for each critical operation: the maximum period of disruption it would accept, the maximum extent of data loss, and the minimum service level during a disruption (paragraph 37). Our reading: these correspond to recovery time and recovery point objectives, which CPG 230's table also links to the concept.

The BCP testing programme must include an annual exercise and "disruptions to services provided by material service providers" (paragraphs 42 and 43). CPG 230 adds that an entity would seek to confirm that providers also maintain robust BCP testing and that "Joint testing of arrangements with the service provider could be considered."

Notification duties also reach provider outages. An entity must notify APRA "not later than 24 hours after" a disruption to a critical operation outside tolerance (paragraph 41), and within 72 hours of an operational risk incident likely to have a material impact (paragraph 32).

Four terms that get mixed up

Concentration thinking depends on being exact about what protects against what. In plain terms:

  • Backup is a separate copy of data that lets you restore after loss.
  • Replication copies data continuously to another location.
  • Failover switches running services to a standby.
  • Disaster recovery is the whole plan and capability to restore service within agreed times.

None of these removes concentration if the copy sits under the same provider, account and control system as the original. Our reading: a replica in another region of the same provider reduces some risks but leaves the contract, the account, the identity system and the provider's staff as common points. A backup you hold yourself, under your own control and key, reduces more of them.

What a non-regulated business can take from it

CPS 230 gives no duty to businesses outside its scope, and nothing here makes it mandatory for them. As a checklist, though, it translates well. Our recommendation:

  1. List material service providers. Name each provider you could not do without for more than a short time, and the services they support.
  2. Record the exit route for each. What would you do, with whom and how long would it take, if the provider vanished or refused service tomorrow? Where would the data come from?
  3. Map the fourth parties. Ask which other companies the provider relies on for the service.
  4. Set your own tolerance. Decide how long each critical system can be down and how much data you could lose.
  5. Check the contract terms. Look for service levels, data ownership and return, subcontractor notification, termination rights and what happens in a force majeure event.
  6. Test a provider-outage scenario. Write down what you would do if the provider's console, support line and email were all unavailable.
  7. Hold something outside the provider. Keep at least one recoverable copy of key data outside the provider's control.

If you are a supplier or service provider to a regulated entity, expect that entity to ask you for contract terms or evidence along these lines, because CPS 230 puts its obligations on the entity's arrangements with its service providers (our reading; the standard does not set duties on an unregulated supplier directly). If you are only a customer of a regulated entity, CPS 230 is the entity's obligation; it does not ask you for this evidence unless a separate contract or arrangement does.

Questions to put to your provider

  1. Which other companies do you rely on to deliver the hosting we receive, and will you tell us if that changes?
  2. What is your documented process if we want to leave, and in what format and time do we get our data back?
  3. Which of our systems, backups, identity and DNS depend on a single account, region or control system?
  4. How do you test your own continuity plans, and can we take part in a test?
  5. What happens to the hosted systems and our data in a force majeure event?
  6. What notice and cooperation can we expect during an incident that affects many customers?

A worked example (illustrative)

The following is invented. A mid-sized firm runs its servers, backups, DNS and email filtering with one provider. A review lists the services and finds that a single account console controls all four. The firm records the provider as material, notes that the provider uses a larger platform underneath, and sets a tolerance of one working day of downtime for its main application.

It asks the provider for the exit process in writing and learns that data return takes weeks. It therefore arranges a second backup copy under its own control and schedules a yearly exercise in which the provider is assumed to be unreachable for a day. The exercise shows that staff cannot reach the DNS settings without the provider's console, so it moves that dependency onto a separate service.

Risks and limits

  • CPS 230 binds APRA-regulated entities. Whether a provider or a customer is covered depends on legal advice about that entity's circumstances.
  • CPG 230 is guidance; its examples are not requirements.
  • We used the July 2026 clean versions published after the April 2026 amendments. Earlier versions, transition arrangements and APRA's supervisory approach were not reviewed.
  • "Material" is a judgement the regulated entity makes. This guide does not say which providers are material.
  • A checklist taken from CPS 230 does not make an unregulated business compliant with anything.

Next step

List your material service providers, what each supports and the exit route for each, starting with the provider that holds the most. If you are reviewing a hosted service, the For Businesses page is a starting point for that conversation; ask for the scope in writing.

Sources

All accessed 15 November 2026.

Learning notes

  • Concentration risk means many things depending on one party, even if each looks small.
  • CPS 230 applies to APRA-regulated entities, not to every business, and a practice guide is guidance, not law.
  • A material service provider is one you rely on for critical work or that exposes you to material operational risk.
  • A second copy under the same provider's control does not remove the single dependency.
  • An exit route you have never tried is a hope, not a plan.