APRA
APRA CPS 234: The Information Security Standard Explained
3 July 2026 · Updated 3 July 2026
Prudential Standard CPS 234 Information Security is APRA’s enforceable rule that regulated banks, insurers and super funds maintain an information security capability matched to their threats, test their controls, run internal audit over them, and notify APRA within 72 hours of a material incident. It has applied since 1 July 2019.
CPS 234 is not guidance an entity can risk-accept. It is a legal instrument that the Australian Prudential Regulation Authority supervises and enforces, and the Board carries the accountability. What it actually requires follows.
What is APRA CPS 234 Information Security?
Prudential Standard CPS 234 Information Security is a rule made by the Australian Prudential Regulation Authority (APRA) that requires an APRA-regulated entity to be resilient against information security incidents, including cyber attacks, by maintaining an information security capability matched to the threats to its information assets. It commenced on 1 July 2019, with a one year extension to 1 July 2020 for information assets managed by third parties. The stated objective is to minimise the likelihood and impact of incidents affecting the confidentiality, integrity or availability of information assets, including assets held by related parties and third parties. Unlike a voluntary framework, CPS 234 is made under the Banking Act, the Insurance Act, the Life Insurance Act, the private health insurance legislation and the Superannuation Industry (Supervision) Act, which is what gives APRA the power to enforce it.
Who does APRA CPS 234 apply to?
CPS 234 applies to all APRA-regulated entities. The standard lists them: authorised deposit-taking institutions (ADIs) including foreign ADIs, general insurers including Category C insurers, life companies including friendly societies and eligible foreign life insurance companies, private health insurers, and registrable superannuation entity (RSE) licensees in respect of their business operations, plus the relevant authorised and registered non-operating holding companies. For a foreign ADI, a Category C insurer or an eligible foreign life insurance company, the obligations apply only to the Australian branch operations. Where an APRA-regulated entity is the head of a group, it must apply the requirements across the group, including entities that are not themselves APRA-regulated. An organisation that is not one of these entity types is not bound by CPS 234, though its structure is a sound model to borrow.
What are the key requirements of CPS 234?
CPS 234 sets four headline obligations, then expands them across paragraphs 13 to 36. An APRA-regulated entity must clearly define information security roles and responsibilities of the Board, senior management, governing bodies and individuals. It must maintain an information security capability matched to the size and extent of threats to its assets. It must implement controls to protect information assets and systematically test their effectiveness. And it must notify APRA of material information security incidents. Around these run further obligations: maintain an information security policy framework, classify information assets by criticality and sensitivity, keep incident response plans and test them annually, and put internal audit over the design and operating effectiveness of controls. The word running through all of it is commensurate: the effort must match the criticality of the asset and the level of threat, not a fixed checklist.
What does CPS 234 require for testing and internal audit?
CPS 234 requires a systematic testing program for control effectiveness, with the nature and frequency set by how fast vulnerabilities and threats change, the criticality and sensitivity of the asset, and the rate of change to assets. Testing must be done by appropriately skilled and functionally independent specialists, and the sufficiency of the program reviewed at least annually or on material change. Separately, internal audit activities must review the design and operating effectiveness of information security controls, including those run by related parties and third parties, provided by people skilled in that assurance. This maps closely to the control testing and audit discipline in ISO 27001 and to independent testing such as a penetration test, but CPS 234 makes it an enforceable prudential obligation rather than a commercial choice.
How does CPS 234 handle third parties and related parties?
CPS 234 pushes obligations across the supply chain. Where information assets are managed by a related party or third party, the entity must assess that party’s information security capability, evaluate the design of its controls, and, where the entity relies on the third party’s own control testing, assess whether that testing is adequate. Internal audit must assess third party control assurance where an incident could materially affect the entity or its customers and audit intends to rely on that assurance. This is broader than the old outsourcing standard: it applies to all information assets held by third parties, not only formally outsourced material business activities. Where core systems run in a cloud platform or a managed service, that provider is inside the CPS 234 scope, and the Statement of Applicability style scoping needs to reflect it.
What are the CPS 234 notification requirements to APRA?
CPS 234 sets two notification clocks. An APRA-regulated entity must notify APRA as soon as possible and no later than 72 hours after becoming aware of an information security incident that materially affected, or had the potential to materially affect, the entity or the interests of its customers, or that has been notified to another regulator in Australia or overseas. Separately, it must notify APRA as soon as possible and no later than 10 business days after becoming aware of a material information security control weakness it expects it cannot remediate in a timely manner. The clock starts when the entity becomes aware, not when it finishes investigating, so incident triage and escalation need to move fast. We cover what counts as material and how the clock runs in CPS 234 incident notification.
How does CPS 234 relate to CPS 230 and other frameworks?
CPS 234 is the information security standard; CPS 230 Operational Risk Management is the broader operational resilience standard that took effect on 1 July 2025 and folds cyber into business continuity and service provider risk. CPS 230 explicitly requires entities to meet CPS 234 when managing technology risk, so the two run together rather than competing. For the differences and overlaps, see CPS 234 vs CPS 230. An entity that already holds ISO 27001 certification has a strong foundation, but it may not fully satisfy CPS 234 on its own, which we set out in does ISO 27001 satisfy CPS 234. Choosing where to start across these standards is covered in how to choose a cyber security framework in Australia. Where an organisation needs advisory support on CPS 234 readiness or control uplift, Cybernion’s IRAP assessment and advisory services include the governance and assurance work that feeds directly into prudential compliance.
Frequently asked questions
Who does APRA CPS 234 apply to? CPS 234 applies to all APRA-regulated entities. That means authorised deposit-taking institutions including foreign ADIs, general insurers, life companies and friendly societies, private health insurers, and registrable superannuation entity (RSE) licensees, along with the relevant non-operating holding companies. For foreign ADIs and branch insurers, the obligations apply to their Australian branch operations.
What is the CPS 234 notification deadline for a security incident? An APRA-regulated entity must notify APRA as soon as possible and no later than 72 hours after becoming aware of an information security incident that materially affected, or had the potential to materially affect, the entity or its customers, or that has been notified to another regulator. A separate clock of 10 business days applies to a material information security control weakness the entity cannot remediate in a timely manner.
Does CPS 234 require penetration testing? CPS 234 does not name penetration testing, but paragraph 27 requires a systematic testing program for control effectiveness, with the nature and frequency set by how fast threats change and how critical the assets are. Paragraph 30 requires testing by appropriately skilled and functionally independent specialists. In practice most regulated entities meet this with penetration testing and control assurance work.
Is CPS 234 the same as ISO 27001? No. CPS 234 is an enforceable Australian prudential standard that APRA supervises, while ISO 27001 is a voluntary international certification driven by customers and tenders. ISO 27001 provides much of the management system and control discipline CPS 234 expects, but it may not cover the specific APRA notification clocks, board accountability wording and third party assurance obligations without extra work.
Who is accountable for CPS 234 in a regulated entity? The Board of an APRA-regulated entity is ultimately responsible for the entity’s information security under CPS 234. The standard requires the entity to clearly define the information security roles and responsibilities of the Board, senior management, governing bodies and individuals with decision-making, approval, oversight and operational duties.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- Prudential Standard CPS 234 Information Security, APRA, July 2019
- CPS 234 Information Security standard page, APRA, current July 2026
- Prudential Practice Guide CPG 234 Information Security, APRA, June 2019
- Prudential Standard CPS 230 Operational Risk Management, APRA Prudential Handbook, current July 2026
Last updated: 3 July, 2026
