Meet APRA CPS 234 with controls and evidence that stay current
CPS 234 is the Australian Prudential Regulation Authority's prudential standard on information security, in force since 1 July 2019. It makes the Board ultimately responsible for information security and requires a security capability, policy framework, asset classification, controls, incident response and testing proportionate to the threats faced. Material incidents must be notified to APRA within 72 hours.
Is CPS 234 right for your organisation?
Every APRA-regulated entity must comply, including authorised deposit-taking institutions, general, life and private health insurers, and RSE licensees in the superannuation sector. Service providers that host or manage information assets for these entities are pulled in through contracts, because CPS 234 requires the regulated entity to assess and test the controls of related parties and third parties.
It is a legal or regulatory requirement for organisations in scope.
- Issued by
- Australian Prudential Regulation Authority (APRA)
- In force since
- 1 July 2019
- Applies to
- ADIs, insurers, private health insurers and superannuation RSE licensees
- Incident notification
- Within 72 hours of becoming aware of a material information security incident
- Control weakness notification
- Within 10 business days for a material weakness that cannot be remediated in a timely manner
- Supporting guidance
- Prudential Practice Guide CPG 234 Information Security
- Assessment route
- Internal audit, independent control testing and APRA supervision; no certification
- Type
- Regulation (mandatory)
- Region
- Australia, Asia-Pacific
- In OneClickComply
- Supported today
OneClickComply makes it simple
OneClickComply maps CPS 234 paragraphs to a single set of controls, collects evidence automatically from your cloud, identity and device tools, and alerts you when a control drifts. You can generate an information security policy framework from your real environment, track third-party assurance in vendor risk management, and use our in-house audit team to prepare for internal audit and APRA reviews.
Requirements covered
36 numbered paragraphs, with the operative requirements in paragraphs 13 to 36 grouped under roles and responsibilities, capability, policy framework, asset classification, controls, incident management, testing, internal audit and APRA notification.
Manual CPS 234 vs. OneClickComply
- Mapping 24 operative paragraphs to controls by hand in spreadsheets
- Chasing screenshots from every system before internal audit reviews
- Assessing third-party controls with questionnaires that go stale
- Discovering control weaknesses late, with the 10-business-day clock already running
- Rewriting policies and Board reports each year to reflect changes
- One control set mapped to CPS 234 and your other frameworks
- Evidence collected automatically and logged against each control
- Vendor risk records that keep third-party assurance current
- Continuous monitoring that flags drift as soon as it happens
- Policies generated from your environment and easy to keep up to date
Everything you need for CPS 234
CPS 234 paragraphs mapped to controls you already run for ISO 27001 and SOC 2
Automated evidence from cloud, identity and device tools across 13,000+ integrations
AutoComplete information security policy framework built from your real environment
Continuous monitoring with alerts when CPS 234 controls drift
Vendor risk management to assess third-party security capability and assurance
Ask an Auditor and penetration testing to support independent control testing
Three steps to CPS 234 compliance
Connect & scan
Connect your cloud, identity and SaaS tools. OneClickComply checks them against CPS 234 and shows you exactly where you stand.
Fix & generate
OneClickFix remediates technical gaps in one click, and AutoComplete generates CPS 234-aligned policies from your real environment.
Monitor & evidence
Continuous monitoring keeps you compliant, and our in-house audit team is on hand when you need expert guidance.
APRA CPS 234 Information Security requirements
The 24 operative paragraphs of CPS 234 (13 to 36), with sub-paragraphs merged into their parent; paragraphs 1 to 12 cover authority, application, commencement and definitions.
| Reference | Requirement |
|---|---|
| 13 | Board ultimately responsible for information security |
| 14 | Defined information security roles and responsibilities |
| 15 | Information security capability commensurate with threats |
| 16 | Assessment of related and third-party security capability |
| 17 | Maintaining capability as threats and the business change |
| 18 | Information security policy framework |
| 19 | Policy direction on information security responsibilities |
| 20 | Classification of information assets by criticality and sensitivity |
| 21 | Implementation of information security controls |
| 22 | Evaluation of third-party control design |
| 23 | Mechanisms to detect and respond to incidents |
| 24 | Information security response plans |
| 25 | Incident management stages, escalation and reporting |
| 26 | Annual review and testing of response plans |
| 27 | Systematic testing of control effectiveness |
| 28 | Reliance on third-party testing programmes |
| 29 | Escalation of unremediated testing deficiencies |
| 30 | Testing by skilled, functionally independent specialists |
| 31 | Review of testing programme sufficiency |
| 32 | Internal audit review of control design and effectiveness |
Always check the official CPS 234 text for the exact wording.
CPS 234 FAQs
What is APRA CPS 234?
CPS 234 is a legally binding prudential standard issued by the Australian Prudential Regulation Authority that sets minimum information security requirements for regulated financial institutions. It took effect on 1 July 2019. It requires Board accountability, a security capability and policy framework matched to threats, classification and protection of information assets, incident response plans, systematic control testing, internal audit review and notification of material incidents to APRA.
Who must comply with CPS 234?
All APRA-regulated entities must comply with CPS 234. That includes authorised deposit-taking institutions such as banks, building societies and credit unions, general insurers, life insurers, private health insurers, RSE licensees in superannuation and authorised non-operating holding companies. Their technology and service providers are affected indirectly, because regulated entities must assess and test the security controls of third parties that manage their information assets.
What are the CPS 234 notification deadlines?
An 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 could have materially affected, the entity or its customers, or that has been notified to another regulator. A material control weakness that the entity expects it cannot remediate in a timely manner must be notified within 10 business days.
What happens if you do not comply with CPS 234?
Non-compliance is a breach of a prudential standard and APRA can respond with supervisory action. Depending on the governing legislation, this can include formal directions, additional capital requirements, conditions on a licence, enforceable undertakings or other enforcement action. APRA has also commissioned independent CPS 234 assessments across the industry and expects entities to remediate gaps they find. The exact consequences depend on the entity and the breach.
How does CPS 234 apply to third parties and suppliers?
CPS 234 extends to information assets managed by related parties and third parties. The regulated entity must assess the supplier's information security capability, evaluate the design of its controls, assess whether its testing is adequate, and have internal audit assess the assurance it provides where an incident could have a material impact. In practice, suppliers to banks, insurers and super funds face these requirements through contracts.
How does CPS 234 relate to ISO 27001 and SOC 2?
CPS 234 is a regulatory obligation, while ISO 27001 and SOC 2 are voluntary certification and attestation frameworks. They overlap heavily on governance, asset management, access control, incident response and testing, so an ISO 27001 management system provides a strong base. CPS 234 adds specific requirements, such as Board accountability, notification to APRA within set deadlines and internal audit review of third-party assurance.
What is the difference between CPS 234 and CPG 234?
CPS 234 is the binding prudential standard that sets what regulated entities must do, while CPG 234 is APRA's prudential practice guide that explains how APRA expects those requirements to be met. CPG 234 is not mandatory, but it describes good practice for areas such as control testing, cryptography, access management and incident response, and APRA uses it when supervising information security.
Does OneClickComply support CPS 234?
Yes. OneClickComply supports CPS 234 today, mapping its paragraphs to a single set of controls shared with frameworks such as ISO 27001. The platform collects evidence automatically, monitors controls continuously, generates policies and manages vendor risk. Our in-house audit team can help you prepare for internal audit and APRA reviews. OneClickComply does not certify compliance, as CPS 234 has no certification scheme.
Related standards
All standards- APRA CPS 230 Operational Risk ManagementRegulation · Asia-Pacific
- SEBI Cybersecurity and Cyber Resilience Framework (CSCRF)Regulation · Asia-Pacific
- MAS Notice on Cyber HygieneRegulation · Asia-Pacific
- India SPDI Rules 2011Regulation · Asia-Pacific
- New Zealand Information Security Manual (NZISM) v3.6Standard · Asia-Pacific
- ISMAP (Japan)Certification · Asia-Pacific
- Australian Information Security Manual (ISM)Framework · Asia-Pacific
- MAS Technology Risk Management GuidelinesGuidance · Asia-Pacific
Get CPS 234 ready, not stressed
Automate controls, gather evidence continuously and stay audit-ready, all on one platform.