What CPS 234 is, and who it applies to
Prudential Standard CPS 234 Information Security is a legally binding standard made by the Australian Prudential Regulation Authority, in force since 1 July 2019. It aims to make regulated entities resilient to information security incidents, including cyber attacks.
It applies to every APRA-regulated entity:
- authorised deposit-taking institutions (banks, building societies and credit unions), including foreign ADIs and authorised banking holding companies;
- general insurers, including Category C insurers, authorised insurance holding companies and parents of Level 2 insurance groups;
- life companies, including friendly societies and eligible foreign life insurance companies;
- private health insurers; and
- RSE licensees (superannuation trustees) in respect of their business operations.
If you aren’t one of these, CPS 234 doesn’t bind you. It reaches you anyway if you manage information assets for one of them. The standard defines information assets broadly (information and information technology, including software, hardware and data) and repeatedly extends the entity’s obligations to assets managed by related parties and third parties. A SaaS platform, managed service provider, claims processor, data centre or developer with production access all qualify, whether or not the arrangement counts as outsourcing.
What CPS 234 requires
The standard is short. Its requirements sit in paragraphs 13 to 36, grouped under these headings:
- Roles and responsibilities. The Board is ultimately responsible for the entity’s information security. The entity must clearly define security roles for the Board, senior management, governing bodies and individuals.
- Information security capability. The entity must maintain a capability (resources, skills and controls) commensurate with the size and extent of threats, keep it current as threats and the business change, and assess the capability of any related or third party that manages its information assets.
- Policy framework. A framework of policies, standards, guidelines and procedures that gives direction to everyone with a security obligation, including contractors, third parties and customers.
- Information asset identification and classification. All information assets, including those held by third parties, classified by criticality and sensitivity, reflecting the impact an incident could have on the entity or on depositors, policyholders, beneficiaries or other customers.
- Implementation of controls. Controls implemented in a timely manner and commensurate with vulnerabilities and threats, criticality and sensitivity, the asset’s life-cycle stage and the potential consequences of an incident. Where a third party manages the assets, the entity must evaluate the design of that party’s controls.
- Incident management. Robust detection and response, response plans for plausible incidents covering detection through to post-incident review and escalation to the Board, and an annual review and test of those plans.
- Testing control effectiveness. A systematic testing program whose nature and frequency reflect how fast threats change, asset criticality and sensitivity, incident consequences, exposure to untrusted environments and the rate of change. Testing must be done by appropriately skilled and functionally independent specialists, deficiencies that can’t be fixed in time go to the Board or senior management, and the program is reviewed at least annually.
- Internal audit. Internal audit must review the design and operating effectiveness of security controls, including those maintained by third parties, and assess a third party’s assurance where an incident could materially affect the entity and internal audit intends to rely on that assurance.
- APRA notification. Notify APRA as soon as possible and no later than 72 hours after becoming aware of an information security incident that materially affected, or could have materially affected, the entity or its customers, or that has been notified to another regulator. Notify APRA within 10 business days of becoming aware of a material control weakness the entity expects it can’t remediate in a timely manner.
APRA’s practice guide, CPG 234 Information Security, explains how APRA expects these requirements to be met. It isn’t binding, but it holds most of the detail on third parties, testing and control expectations, and entities’ supplier assessments draw heavily on it.
How ISO 27001 maps to CPS 234
ISO/IEC 27001:2022 sets how you run information security in clauses 4 to 10, and Annex A lists 93 controls you select through risk assessment. Both standards are risk-based, so the fit is strong. The table is a guide, not a compliance opinion.
| CPS 234 requirement | ISO 27001 clause or Annex A control | Coverage |
|---|---|---|
| Board ultimately responsible (para 13) | 5.1 Leadership and commitment; 9.3 Management review | Partial. ISO 27001 places duties on top management, not the Board |
| Defined roles and responsibilities (14) | 5.3 Organizational roles, responsibilities and authorities; A.5.2, A.5.4 | Strong |
| Capability commensurate with threats, kept current (15, 17) | 4.1, 6.1, 6.3, 7.1 Resources, 7.2 Competence; A.5.7 Threat intelligence | Strong |
| Assess third parties’ security capability (16) | A.5.19 to A.5.22 supplier controls; A.5.23 cloud services | Partial. ISO 27001 requires supplier risk management, not this depth of assessment |
| Policy framework, direction to all parties (18, 19) | 5.2 Policy; A.5.1 Policies for information security; A.5.10 Acceptable use | Strong |
| Classify assets by criticality and sensitivity (20) | A.5.9 Inventory of information and other associated assets; A.5.12 Classification; A.5.13 Labelling | Strong, if your scheme rates availability impact as well as confidentiality |
| Controls commensurate with threats and life-cycle (21) | 6.1.2 Risk assessment; 6.1.3 Risk treatment and the Statement of Applicability; A.8.25 Secure development life cycle; A.7.14, A.8.10 disposal and deletion | Strong |
| Evaluate design of third-party controls (22) | A.5.20 Supplier agreements; A.5.22 Monitoring and review of supplier services | Partial |
| Incident detection, response plans, escalation (23 to 25) | A.5.24 to A.5.28 incident management; A.6.8 Event reporting; A.8.15 Logging; A.8.16 Monitoring | Strong |
| Annual review and test of response plans (26) | A.5.24, A.5.30 ICT readiness for business continuity | Partial. ISO 27001 sets no annual test |
| Systematic, independent control testing (27 to 31) | 9.1 Monitoring, measurement, analysis and evaluation; A.5.35 Independent review; A.5.36 Compliance with policies; A.8.8 Technical vulnerabilities; A.8.29 Security testing | Partial. No prescribed testing program or tester independence |
| Internal audit of control design and operating effectiveness (32 to 34) | 9.2 Internal audit | Partial. ISO internal audit tests ISMS conformity, not third parties’ assurance |
| Notify APRA within 72 hours or 10 business days (35, 36) | A.5.5 Contact with authorities; A.5.31 Legal, statutory, regulatory and contractual requirements | Gap. You must add the APRA criteria and timeframes |
For what each control involves, see our guides to the Annex A controls and clauses 4 to 10.
Where ISO 27001 doesn’t cover CPS 234
APRA notification
ISO 27001 expects you to identify your regulatory obligations and keep contact with authorities. It says nothing about APRA, 72 hours or 10 business days. An entity using ISO 27001 must build the CPS 234 materiality tests and timeframes into its incident procedure and its control-weakness process. The 10-business-day obligation is easy to miss because a weakness found in testing or audit triggers it, not an incident.
Board accountability
ISO 27001 assigns leadership duties to “top management”, which in a small organisation is often the managing director. CPS 234 names the Board as ultimately responsible and expects incidents and unremediated deficiencies to reach it. A management review attended only by executives doesn’t show Board oversight.
Assessing third parties
ISO 27001’s supplier controls require you to manage security risk in supplier relationships, put requirements in agreements and monitor supplier services. CPS 234 is more specific: assess each third party’s capability in proportion to the consequences of an incident, evaluate the design of its controls, check that its testing is adequate where you rely on it, and have internal audit assess its assurance in material cases. CPG 234 adds that you should consider the scope, depth and independence of any certification or attestation you rely on, and look at the third party’s own suppliers too.
Independence of testing
CPS 234 requires control testing by appropriately skilled and functionally independent specialists. CPG 234 explains that this means testers without operational responsibility for the controls being tested. ISO 27001 requires internal auditors to be objective and impartial and calls for independent review of your approach to security, but it doesn’t require a systematic testing program or penetration testing at all. Our article on whether ISO 27001 requires penetration testing covers that difference.
The scope of internal audit
ISO 27001 internal audit checks that your ISMS conforms to the standard and your own requirements and is effectively implemented and maintained. CPS 234 expects internal audit to review the design and operating effectiveness of security controls, including those run by third parties: a broader, more technical programme.
CPS 230 and material service providers
CPS 230 Operational Risk Management commenced on 1 July 2025, replacing APRA’s older outsourcing and business continuity standards. It requires entities to manage operational risk, maintain critical operations within tolerance levels through severe disruption, and manage the risks of using service providers. It requires them to meet CPS 234 for information security.
For suppliers, the relevant part is the register of material service providers: those the entity relies on for a critical operation or that expose it to material operational risk. Providers of core technology services are classified as material by default unless the entity can justify otherwise. Agreements with material service providers must cover matters such as audit access, data ownership, notification of the provider’s own material subcontractors and APRA’s right to access documentation and visit the provider on site. Pre-existing contracts had until the earlier of renewal or 1 July 2026 to comply, and an amended version of CPS 230 took effect on 1 July 2026. If you are material, expect longer contracts and closer monitoring on top of the CPS 234 assessment.
What a supplier to a bank, insurer or super fund should do
If you sell to an APRA-regulated entity, plan for independent assurance plus the entity’s own assessment.
- Independent assurance. An ISO 27001 certificate from an accredited certification body is the most widely accepted evidence in Australia. Make sure its scope covers the service, systems and locations the entity uses. A SOC 2 Type 2 report is a recognised alternative and gives an opinion on operating effectiveness over a period. Some entities also accept Australian controls assurance reports under ASAE 3150. See ISO 27001 vs SOC 2 to choose.
- The entity’s own CPS 234 assessment. A certificate rarely replaces the questionnaire. Expect questions on how you protect their data, who can access it, where it is stored, how and by whom controls are tested, your own suppliers, and how fast you will report an incident. Your notification commitment needs to give the entity enough time to meet its own 72-hour deadline to APRA. Our guide to security questionnaires explains how to answer efficiently.
- Evidence beyond the certificate. Have your Statement of Applicability, a recent independent penetration test summary, incident response plan and test results, and your internal audit outcome ready to share under NDA. These answer CPS 234’s testing and independence questions directly.
- Contract terms. Read the security, audit, notification and subcontracting clauses before signing. They often commit you beyond your certificate scope.
Mapping your ISMS to a specific entity’s CPS 234 assessment and closing the gaps in time for a contract is the part we most often take on for clients. Effort depends mainly on your scope and how much of your ISMS already exists; our guide to what drives ISO 27001 effort and cost explains the factors.
If you are a smaller APRA-regulated entity
An ISO 27001 ISMS is a sound base for a credit union, mutual bank, small insurer or super trustee, provided you add the gaps above: APRA notification in the incident procedure, Board reporting, a documented testing program with independent testers, and third-party assessments proportionate to each supplier’s access. Certification is optional for you; APRA cares whether the controls work.
If you supply APRA-regulated entities, our guides to ISO 27001 for fintechs and suppliers to banks and ISO 27001 for managed service providers cover what those buyers ask for under CPS 234 and CPS 230.
Next step
If you are building your ISMS yourself, ISO 27001 requires internal audits to be objective and impartial, so staff can do them only if they aren’t auditing their own work, which is why many small teams bring in an independent internal auditor. To talk through a specific customer’s CPS 234 requirements, book a free 30-minute consultation, or see how our ISO 27001 service works.
