APRA CPS 234 Copilot
A general AI answer on CPS 234 can treat it as a bank-only rule with a single 72-hour clock. It can miss that insurers, private health insurers and super trustees are covered too, that many of its duties, from asset classification to internal audit, reach information assets a third party manages for you, and that a material control weakness you cannot fix in time has its own 10-business-day notice. This assistant works from APRA's standard itself.
CPS 234 has applied since 1 July 2019, and to assets third parties manage since 1 July 2020 at the latest. Check which of your information assets sit with third parties and how your testing and internal audit cover them.
What the APRA CPS 234 Copilot Can Do
Applicability check across the main entity types APRA names: ADIs, general insurers, life companies and friendly societies, private health insurers, RSE licensees and the holding companies it lists, including the branch-only reach for foreign ADIs, Category C insurers and EFLICs
Group-wide application for a Head of a group, including group entities that APRA does not regulate itself
Information asset classification by criticality and sensitivity, covering assets that related parties and third parties manage for you
Third-party work under paragraphs 16, 22, 28 and 34: assessing a provider's security capability, evaluating the design of its controls, judging its testing, and assessing its assurance before internal audit relies on it
A systematic control testing programme run by appropriately skilled, functionally independent testers, escalation of deficiencies you cannot fix in time, and the annual review of the programme and of your incident response plans
Cross-mapping from an ISO 27001 ISMS or Essential Eight work to the CPS 234 paragraphs, with CPG 234 as APRA's practice guidance
About APRA CPS 234 Copilot
APRA CPS 234 assistant: who is covered, third-party information assets, control testing, internal audit, and the 72-hour and 10-business-day notices to APRA.
The standard (CPS 234, in force since 1 July 2019)
Roles and responsibilities: the Board is ultimately responsible for information security and the entity defines security roles for the Board, senior management, governing bodies and individuals (paragraphs 13 and 14)
Capability, policy framework and asset classification: security capability in line with the threats faced, kept current as threats and assets change, a policy framework that sets duties for staff, contractors, third parties and customers, and assets classified by criticality and sensitivity (paragraphs 15 to 20)
Controls, incident management and testing: controls in line with threats, asset criticality, life-cycle stage and consequences, timely detection and response, response plans reviewed and tested every year, and a testing programme reviewed every year, and sooner when your assets or business environment change materially (paragraphs 21 to 31)
Information assets a third party manages for you
Assess the security capability of a related party or third party that manages your information assets, in proportion to the possible consequences of an incident (paragraph 16)
Evaluate the design of that party's controls protecting your assets, and check that its testing is suitable where you rely on it (paragraphs 22 and 28)
The standard says these duties apply to all information assets that related parties and third parties manage, not only formal outsourcing arrangements
Internal audit and notification (paragraphs 32 to 36)
Internal audit reviews the design and operating effectiveness of security controls, including those run by related parties and third parties, using appropriately skilled people
Where internal audit intends to rely on a third party's assurance over assets whose compromise could materially affect the entity or its customers, it assesses that assurance itself
APRA notification within 72 hours for a material incident or one notified to another regulator, and within 10 business days for a material control weakness you cannot fix in time
Where it sits in the APRA framework
CPS 230 Operational Risk Management, in its current version that commenced on 1 July 2026, refers entities to CPS 234 for information security requirements
An incident already reported under CPS 234 does not need a separate report under CPS 230
CPG 234, dated June 2019, is APRA's practice guide on how to meet CPS 234
Related frameworks
ISO 27001
A common way to organise the CPS 234 policy framework, controls and testing evidence.
Essential Eight
ASD's mitigation strategies, which can form part of the controls an APRA-regulated entity tests.
Privacy Act 1988
The federal privacy law, with its own breach notification scheme run by the OAIC.
MAS TRM
Singapore's technology risk guidelines for financial institutions, for groups operating in both markets.
ISMS Copilot for Australia
Australian hub: Essential Eight, the Privacy Act, APRA CPS 234 and ISO 27001.
Cross-framework mappings
Working across APRA CPS 234 and another standard? ISMS Mappings is a free public directory of control maps (ISO 27001, SOC 2, NIST, GDPR, and more). A Better ISMS tool, separate from the chat assistant.
Browse free mappingsFrequently Asked Questions
What is CPS 234?
CPS 234 is a prudential standard on information security made by the Australian Prudential Regulation Authority (APRA) under the Banking Act, the Insurance Act, the Life Insurance Act, the Private Health Insurance (Prudential Supervision) Act and the SIS Act. It was determined in November 2018 and has been in force since 1 July 2019. It is binding on the entities it covers, not a voluntary framework. APRA's practice guide CPG 234 explains how APRA expects it to be met, but the standard is where the obligations sit.
Who has to comply?
Every APRA-regulated entity: authorised deposit-taking institutions (banks, building societies and credit unions) and authorised banking NOHCs, general insurers, authorised insurance NOHCs and parent entities of Level 2 insurance groups, life companies including friendly societies, eligible foreign life insurance companies and registered life NOHCs, private health insurers, and RSE licensees for their business operations. For foreign ADIs, Category C insurers and eligible foreign life insurance companies, it reaches only the Australian branch. A Head of a group must also apply it across the group, including group entities that are not APRA-regulated. APRA can adjust or exclude a specific requirement for an individual entity. Service providers are not covered directly, but the regulated entity must assess the security of the information assets they manage for it, and their own testing and assurance where it relies on them, so the work reaches its suppliers through contracts and assurance requests.
When do we have to notify APRA?
There are two clocks. An information security incident must be notified as soon as possible and no later than 72 hours after you become aware of it, when it had, or could have had, a material effect, financial or not, on the entity or on the people it serves (depositors, policyholders, fund members and other customers), or when it has been notified to another regulator in Australia or abroad (paragraph 35). A material control weakness that you expect you cannot fix in a timely manner must be notified within 10 business days of becoming aware of it (paragraph 36). APRA's notification page says that one notification is enough when an incident is notifiable under both CPS 230 and CPS 234, and that the earliest deadline then applies.
How does the Copilot help, and what does it not do?
It reads your situation against the CPS 234 paragraphs rather than a generic security checklist: which entity type and group position you are in, which information assets are critical or sensitive, what you need from each provider that manages them, how your testing and internal audit cover those assets, and whether an event meets either notification test. It can map an existing ISO 27001 programme to the standard and draft policies, response plans and board papers for your review. It does not notify APRA for you, it is not legal advice, and APRA decides whether your capability is adequate.
Ask it from your AI.
Connect ISMS Copilot to the assistant you already use and send it your CPS 234 questions: entity scope, third-party assets, control testing, internal audit, APRA notification.
ISMS Copilot