Before starting with APRA, Over the past decade, cloud computing has had a significant impact on the financial sector, globally. It has helped the banking sector to be cost-effective, reliable, and productive. Cloud infrastructures have reduced the capital expense of buying and setting up hardware and software at data centers. This has allowed organizations of all sizes and levels to utilize elastic and virtually limitless data and network storage. However, together with these benefits, cloud computing also presents profound risks. Security in the cloud servers is a significant risk.
Financial institutions must maintain the confidentiality and security of the customer’s financial information and internal company data. Recognizing these risks and thus the momentum at which cloud computing is impacting the financial sector, the Australian Prudential Regulation Authority has called on regulated entities to implement comprehensive cloud-adoption strategies.
These strategies focus on risk assessment, regular assurance processes, and efficient governance.
Who is APRA?
It is an independent statutory authority that oversees institutions across banking, insurance, and superannuation and promotes financial system stability in Australia. It is the prudential regulator of the Australian financial services industry. In July 2015, They published an information paper titled’ Outsourcing involving shared computing services. The article focuses on the fundamental principles and prudential considerations that should be considered for utilizing cloud computing services.
In February 2018, Australia’s Notifiable Data Breach Scheme legislation became a law that introduced new reporting guidelines and penalties for organizations governed by the Australian Privacy Act. In response to this, they updated its July 2015 paper. APRA stated that this was in response to its observation of the growing usage of cloud computing services by APRA-regulated organizations and the associated rise in risk and vulnerabilities. The update also specified the key requirements that APRA-regulated entities must implement and maintain for outsourcing with regards to cloud computing services. Furthermore, the update ups the bar regarding APRA’s view of cloud practitioners.
As of 2026 — The Notifiable Data Breaches scheme is run by the OAIC under the Privacy Act. It is separate from APRA’s prudential requirements, and the post’s causal link between the two is not established. Entities regulated by APRA may need to satisfy both. See the OAIC’s guidance.
Read more about What is APRA compliance here. You can also track your posture against the standard continuously with our APRA compliance framework.
As of 2026 — This post summarises APRA’s 2015/2018 information paper on cloud outsourcing. The binding standards have moved on since then.
- CPS 234 Information Security has applied since 1 July 2019. It requires regulated entities to maintain information security capability that matches the size and extent of threats, to control third-party-managed assets, and to notify APRA of material information security incidents. See CPS 234 and the supporting guide CPG 234.
- CPS 230 Operational Risk Management commenced on 1 July 2025. It replaces the earlier outsourcing standard and requires entities to identify critical operations, set tolerance levels, keep a register of material service providers, and manage third-party risk. Existing contracts had a transition period that ended with renewal or 1 July 2026, and APRA has since issued targeted amendments. Read APRA’s announcement, CPS 230 and CPG 230.
Our APRA framework and APRA CPG 234 framework track these controls against your cloud configuration.
What is new in the APRA Guidelines?
- Risk Assessment and its Engagement
**Chapter 1 talks about understanding and managing risks.**The APRA guidelines have classified these risks into three broad categories – low, heightened, and extreme.
-
Low inherent risks are those disruptions in arrangements wherein the confidentiality, integrity, or availability of systems and data are compromised. These risks present a low or negligible impact on business operations and the ability of the regulated entity to satisfy its obligations. For such arrangements, APRA stated that it would not expect a regulated entity to consult with them before entering the arrangement. Examples of such arrangements include non-productive environments or websites that deliver publicly available information. They also include applications or data stores that are classified by an APRA-regulated entity to have low criticality and sensitivity.
-
Heightened risk arrangements are those that involve critical or sensitive IT assets. In this case, disruptions can have a profound impact on the business operations of an APRA-regulated entity to meet its obligations. For these arrangements, It states that it would expect to be consulted after the entity has completed its internal governance process.
-
Extreme inherent risk arrangements are ones that, if disrupted, can cause an extreme impact on the APRA-regulated entity, both financially and reputationally. It might threaten the ongoing ability of the entity to meet its obligations. For such arrangements, It encourages earlier engagement, as these arrangements will be subjected to a higher level of scrutiny.
- Risk Management Considerations.
Chapter 2 outlines the issues that APRA-regulated entities should consider when utilizing cloud computing services.
-
The chapter talks about the strategy for risk management when an APRA-regulated entity is considering the use of cloud computing services. It states that the entity should take comprehensive steps towards the planning of the target IT environment. APRA also recommends considering an organizational change.
-
The outsourcing governance of the APRA-regulated entity must highlight its decision-making and oversight responsibilities and address the roles of the board members and senior management. These members should be kept informed of the project status and emerging risks or issues to the assets. These members are referred to as the ‘appropriate governance authority.’
-
The selection of a solution involving cloud computing must include independent assessments besides the attestations of the provider and references.
-
The outsourcing standards make it imperative for regulated entities to include an APRA-access clause in their outsourcing agreements. This should include, getting access to documentation and information as well as reserving the right for APRA to conduct on-site visits to the service provider.
-
There should be detailed controls in place to protect information assets. This should also include assets managed by a third party. Financial-regulator programs elsewhere solve this in similar ways, such as this unified cloud security setup for an RBI-regulated data-sharing platform on AWS ECS Fargate and this account of JIT and DAM for a lean RBI-regulated fintech.
-
There should be robust mechanisms in place to respond to security incidents. These mechanisms should be comprehensive and cover all relevant stages of an incident response lifecycle, including detection to post-incident review as well as notifying the key stakeholders and law enforcement.
-
Regulated entities must notify APRA in case of a security incident of any magnitude in not more than 72 hours. It is also mandatory for the APRA-regulated entity to notify within ten business days if they become aware and identify the information security control weakness.
As of 2026 — The 72-hour clock in CPS 234 applies to material information security incidents, not to incidents “of any magnitude”. Entities must also notify APRA within 10 business days of becoming aware of a material information security control weakness that they cannot remediate in a timely manner. Check the exact wording in CPS 234 before building a runbook.
In short, the regulated entities must demonstrate the following:
-
They should have the ability to continue operations and meet obligations, even in case of any disruption.
-
They must ensure the security of critical and sensitive data.
-
They must comply with the legislative and prudential requirements.
-
Absence of jurisdictional, contractual, or technical considerations that may inhibit its ability to fulfill its duties as a prudential regulator, including impediments to timely access to documentation and data/information.
References
[1] https://www.apra.gov.au/cloud-control-apra-evolves-its-stance-on-shared-computing-services
As of 2026 — Both APRA references above have moved. The current pages are CPS 230, CPS 234 and APRA’s cyber security hub.
Why Cloudanix?
Cloudanix knows, Your Cloud infrastructure is Multi-Clouds, Multiple Accounts, Multi-Regions used by multiple team members. It requires continuous attention for multi-cloud security, Compliance, drift, Real-time activities, and Data Leakages. Cloudanix gives you security monitoring + remediation workflows to stay secure.
As of 2026: What has changed
- CPS 234 (information security) is in force and covers cloud-hosted information assets. Material incidents must be reported within 72 hours.
- CPS 230 (operational risk) commenced on 1 July 2025 and puts third-party and cloud provider risk into a single, board-accountable framework.
- Evidence matters: map your cloud controls to CPS 234 and keep continuous evidence. See cloud security for financial services: compliance, JIT access and misconfiguration playbook and what is APRA compliance.
- Third-party risk: see what is third-party risk management for the register and assurance expectations that CPS 230 introduces.
- Related regimes: Essential Eight and the Australian government’s cloud guidance are common companions. See our Essential Eight framework.
People Also Read
- Cloud Security for Financial Services: Compliance, JIT Access and Misconfiguration Playbook
- What is Third-Party Risk Management?
- What is APRA Compliance?
- A Definitive List Of Various Compliance Standards And What They Mean
- A Quick Introduction To HIPAA Compliance For A Busy Cloud User
- A quick introduction to PCI Compliance and Key Aspects To Know
- Understanding AWS Cloud Compliance
- As A Cloud User, Should I Be Worried About Cloud Compliance?
- What is the difference between NIST, CIS/SANS 20, ISO 27001 Compliance Standards?
- Top 15 Cloud Misconfigurations in 2026 - How to Fix Them?
- Why do we need continuous audits for public cloud?