Quick answer
APRA CPS 234 Information Security is a binding prudential standard that requires APRA-regulated entities, including banks, insurers and superannuation trustees, to maintain information security proportionate to the threats they face. It makes the board ultimately accountable, requires controls to be systematically tested for effectiveness, and requires material incidents and control weaknesses to be notified to APRA.
On this page
How It Works
CPS 234 applies to APRA-regulated entities: authorised deposit-taking institutions such as banks, building societies and credit unions; general, life and private health insurers; registrable superannuation entity licensees; and relevant holding companies. It is principles-based, describing outcomes rather than prescribing tools. In summary, an entity must:
- Define roles and responsibilities, with the board ultimately responsible for information security.
- Maintain an information security capability commensurate with the size and extent of threats to its information assets, including those managed by third parties.
- Maintain a policy framework that guides how security is managed.
- Identify and classify information assets by criticality and sensitivity.
- Implement controls that protect those assets, in proportion to their criticality and sensitivity and to the threats they face.
- Plan for incidents, with response plans that are regularly reviewed and tested.
- Test control effectiveness through a systematic testing program.
- Involve internal audit in reviewing the design and operating effectiveness of controls.
- Notify APRA of material information security incidents, generally within 72 hours, and of material control weaknesses that cannot be remediated in a timely manner.
The Testing Obligation
CPS 234 requires systematic testing of control effectiveness at a frequency and depth matched to the rate at which vulnerabilities and threats change, the criticality and sensitivity of the asset, and the consequences of an incident. Testing should be carried out by appropriately skilled and functionally independent people, and where controls are run by a third party, the entity must assess whether that testing is adequate. Weaknesses that cannot be fixed in time must be escalated to the board or senior management.
The standard does not name penetration testing, but penetration testing and red teaming are the most direct evidence that controls stop a capable attacker.
Why It Matters
CPS 234 makes information security a prudential matter with board accountability. A board cannot rely on management assurance alone, so independent testing results, remediation tracking and retesting become the core evidence of an effective capability.
How to Build a Testing Program
- Classify information assets by criticality and sensitivity, and include those managed by third parties.
- Set testing frequency and depth per asset based on criticality and how quickly its threats change, and record the reasoning.
- Combine methods: vulnerability assessment for breadth, penetration testing for depth, and red teaming or threat-led penetration testing for the most critical services.
- Trigger fresh testing after significant change rather than waiting for a calendar date.
- Track findings to closure, retest fixes, and report results to the board or a board committee. A clear penetration test report makes that reporting easier.
- Test incident response plans regularly, including the 72 hour notification path.
For a deeper guide to scoping, evidence and common mistakes, see APRA CPS 234 penetration testing.
Regulatory and Framework Context
CPS 234 works alongside CPS 230 Operational Risk Management, which sharpens the focus on critical operations and material service providers. Many entities use the Essential Eight Maturity Model as a technical control baseline within their CPS 234 program, and a maturity level assessment can benchmark it. Financial services entities may also have obligations under the SOCI Act. Always refer to APRA's current standard and guidance for authoritative requirements.
Latest intel on this topic
- PapRAT Cyber-Espionage Campaign Leaves a 'Bitter' Taste in South AsiaDark Reading · 2 November 2026
- FinBot CTF Is Live: A Hands-On Companion to the OWASP GenAI Security ProjectOWASP GenAI Security Project · 15 April 2026
Updated hourly from the daily briefing.
Common questions
When did CPS 234 take effect?
CPS 234 commenced on 1 July 2019. APRA's companion guide, CPG 234, gives non-binding guidance on how entities can meet it, including on control testing.
Does CPS 234 require independent testers?
The standard expects testing to be carried out by appropriately skilled and functionally independent specialists. That can be an internal team separate from the people who built and run the controls, or an external provider.
How does CPS 234 relate to CPS 230?
CPS 230 Operational Risk Management, in force from 1 July 2025, covers operational risk, business continuity and the management of material service providers. It complements CPS 234 rather than replacing it, and together they shape how entities scope security testing of critical operations and suppliers.
Change log
- 13 November 2026First published.