← Learn
Playbook9 min read

Penetration Testing Requirements in Australia: SOCI Act, Essential Eight, APRA and the Privacy Act

Published by Zero Hunt, an autonomous AI red team on an on-premise appliance running private AI: automated penetration testing for networks and infrastructure, black-box or gray-box, with a human approving every step that matters.

Short definition

No Australian law sets a single annual pentest rule. APRA CPS 234 requires a systematic testing program whose frequency follows threats and criticality, run by skilled and functionally independent specialists; APRA's guidance expects key controls tested at least annually. Critical infrastructure owners must follow a cyber framework such as the Essential Eight under the SOCI Act rules.

Why this matters now

Australian expectations tightened in 2025 and 2026: CPS 230 applies from 1 July 2025, enhanced SOCI risk management rules started on 10 June 2026 with Essential Eight Maturity Level Two for energy, water, freight and other subclasses, and in February 2026 the Federal Court fined a financial services licensee AUD 2.5 million over cyber failings that included missing penetration tests. At the same time, several of these rules treat offshore processing of sensitive data as a risk, which matters when choosing a testing tool.

Key points

  • ▸APRA CPS 234 (para 27) requires a systematic testing program with frequency commensurate with threats, criticality, consequences, exposure to untrusted environments and change; para 30 requires appropriately skilled and functionally independent testers.
  • ▸APRA's CPG 234 is not enforceable but expects a sufficient set of controls tested at least annually and internet-facing controls tested throughout the year, with penetration and red team tests among the techniques.
  • ▸CPS 230 (in force 1 July 2025) requires control testing in line with materiality, an annual business continuity exercise, and notice to APRA before a material offshoring arrangement.
  • ▸SOCI Act responsible entities must keep a risk management program that follows a cyber framework (Essential Eight Maturity Level One or equivalent); enhanced rules from 10 June 2026 raise this to Maturity Level Two for listed subclasses.
  • ▸None of these instruments names a fixed pentest frequency in binding text; the annual cadence comes from APRA guidance and from what regulators and courts treat as adequate.

Banks, insurers and super funds: APRA CPS 234 and CPG 234

Prudential Standard CPS 234 Information Security has applied to all APRA-regulated entities (ADIs, general, life and private health insurers, RSE licensees) since 1 July 2019. It never uses the words penetration test. In short:

  • Para 27. Test control effectiveness through a systematic testing program, with nature and frequency commensurate with how fast threats change, the criticality of the asset, the consequences of an incident, exposure to untrusted environments, and change.
  • Para 30. Testing by appropriately skilled and functionally independent specialists; no paragraph requires an external firm.
  • Para 31. Review the program at least annually or on material change. Para 36: notify APRA within 10 business days of a material control weakness that will not be remediated in time.

CPG 234 (June 2019) is guidance, not an enforceable requirement. It expects a sufficient set of controls tested at least annually and controls exposed to untrusted environments tested throughout the year, and lists penetration and red team tests among the techniques.

The paragraph-by-paragraph analysis, scope and evidence list are in APRA CPS 234 security testing requirements.

Operational risk: APRA CPS 230 and material service providers

Prudential Standard CPS 230 Operational Risk Management commenced on 1 July 2025 (para 6). For contracts that already existed, it applies from the earlier of the next renewal or 1 July 2026 (para 7).

  • Para 30. Regularly monitor, review and test controls for design and operating effectiveness, at a frequency commensurate with the materiality of the risk; report results to senior management and rectify gaps in a timely manner.
  • Para 43. A systematic testing program for the business continuity plan, covering all critical operations and including an annual business continuity exercise in severe but plausible scenarios.
  • Paras 49-51. Keep a register of material service providers and submit it to APRA every year. Providers of core technology services are material unless the entity can justify otherwise.
  • Para 59(b). Notify APRA before entering into any material offshoring arrangement, including where data or personnel relevant to the service will be located offshore.

CPS 230 does not mention penetration testing. It matters for two reasons: control testing now sits in the operational risk standard as well, and a testing service that becomes a material arrangement brings register and offshoring duties with it.

Testing duties at a glance

Rule

APRA-regulated entities
CPS 234 paras 27-31
APRA-regulated entities
CPG 234 (guidance)
APRA-regulated entities
CPS 230 paras 30 and 43
Critical infrastructure assets
SOCI Act s 30AC, CIRMP Rules s 8
Enhanced CIRMP subclasses
CIRMP Rules ss 8A-8C
Systems of national significance
SOCI Act ss 30CM, 30CU

What must be tested

APRA-regulated entities
Information security controls, through a systematic testing program
APRA-regulated entities
A sufficient set of controls; controls facing untrusted environments
APRA-regulated entities
Control design and operating effectiveness; business continuity plan
Critical infrastructure assets
Compliance with a cyber framework (e.g. Essential Eight ML1)
Enhanced CIRMP subclasses
Framework at a higher level (e.g. Essential Eight ML2), phishing-resistant MFA, segregation
Systems of national significance
Cyber security exercise; vulnerability assessment

How often

APRA-regulated entities
Commensurate with threat, criticality and change; program reviewed at least annually
APRA-regulated entities
At least annually; throughout the year for untrusted-facing controls
APRA-regulated entities
Commensurate with materiality; annual continuity exercise
Critical infrastructure assets
Board-approved annual report within 90 days of year end
Enhanced CIRMP subclasses
Comply by 10 June 2027 or 10 June 2028
Systems of national significance
On written notice from the Secretary

Who may test

APRA-regulated entities
Skilled, functionally independent specialists
APRA-regulated entities
Testers without operational responsibility for the controls
APRA-regulated entities
Not specified
Critical infrastructure assets
Not specified
Enhanced CIRMP subclasses
Not specified
Systems of national significance
The entity, or a designated officer on request

Summarized from the texts as read on 20 November 2026. Check the official text and your regulator's guidance before relying on it.

Financial services licensees: ASIC and section 912A

ASIC does not have a penetration testing rule for Australian financial services licensees. It enforces the general duties in section 912A of the Corporations Act: provide services efficiently, honestly and fairly, keep adequate resources, and keep adequate risk management systems.

In ASIC v FIIG Securities Limited [2026] FCA 92 (13 February 2026), FIIG admitted contraventions of s 912A(1)(a), (d) and (h) between March 2019 and June 2023 and was ordered to pay a penalty of AUD 2.5 million. Among the agreed facts: FIIG ran no vulnerability scans over its network and endpoints, carried out only one external penetration test (around February 2023), and did not penetration test its external perimeter, internal network and business-critical applications at least annually, or systems at the time of significant change. The judgment also cites the earlier RI Advice case.

These are agreed facts in a case settled by consent, not a rule. They still show what ASIC and the Court treated as part of adequate cyber risk management for a licensee.

Critical infrastructure: SOCI Act and the risk management program rules

Under the Security of Critical Infrastructure Act 2018, a responsible entity for a covered asset must adopt and maintain a critical infrastructure risk management program (CIRMP, s 30AC) and give a board-approved annual report within 90 days after the end of the financial year (s 30AG).

The CIRMP Rules (LIN 23/006) apply to assets such as broadcasting, domain name systems, data storage or processing, electricity, energy market operators, gas, designated hospitals, food and grocery, freight, liquid fuel, certain financial market infrastructure and water (s 4). For cyber hazards, the program must follow one framework, or an equivalent (s 8(4)-(5)):

  • AS ISO/IEC 27001
  • ASD's Essential Eight at Maturity Level One
  • the NIST Cybersecurity Framework
  • the US C2M2 at Maturity Indicator Level 1
  • the AESCSF at Security Profile 1

The enhanced CIRMP Rules commenced on 10 June 2026 for critical broadcasting, domain name system, electricity, energy market operator, freight infrastructure, freight services, gas, liquid fuel and water assets. They raise the framework bar to Essential Eight Maturity Level Two, NIST CSF 2.0, C2M2 MIL2 or AESCSF Security Profile 2 (s 8A(3)), require phishing-resistant MFA (s 8B) and segregation of critical systems (s 8C). New material risks apply from 10 June 2027 and the other measures from 10 June 2028.

Systems of national significance can be directed by written notice to run a cyber security exercise (s 30CM) or a vulnerability assessment (s 30CU), with the vulnerability assessment report due within 30 days (s 30CZ).

The rules do not name penetration testing for cyber controls. Testing is how an entity shows that the framework it claims, and the segregation it declares, actually hold.

Government and the Essential Eight

ASD's Essential Eight maturity model (last updated November 2023) defines four maturity levels, from Zero to Three, against increasing attacker tradecraft. It was designed for internet-connected IT networks, not for operational technology. It is a set of mitigations, not a testing standard, but some controls are testing-like: at Maturity Level One, for example, asset discovery runs at least fortnightly and a vulnerability scanner checks online services for missing patches at least daily.

Commonwealth entities also work under the Protective Security Policy Framework and ASD's Information Security Manual, and government systems and cloud services are commonly assessed by IRAP assessors. This guide does not cover those documents clause by clause: check the current versions with your agency security adviser.

Privacy Act and the Cyber Security Act 2024

  • Privacy Act 1988, APP 11. An APP entity must take reasonable steps to protect personal information from misuse, interference and loss, and from unauthorised access, modification or disclosure (APP 11.1). APP 11.3 now states that those steps include technical and organisational measures. Penetration tests are not named, but they are the usual evidence that the measures work.
  • Privacy Act, APP 8. Before disclosing personal information to an overseas recipient, the entity must take reasonable steps to ensure the recipient does not breach the APPs (APP 8.1).
  • Cyber Security Act 2024, Part 3. Since 30 May 2025, businesses with an annual turnover above AUD 3 million and responsible entities for SOCI Part 2B assets must report a ransomware or cyber extortion payment within 72 hours (s 27). Home Affairs moved from an education-first phase to compliance from 1 January 2026. The Act does not impose testing.

Where test data and testing tools may run

Several Australian rules treat offshore processing of sensitive information as a risk to manage:

  • CIRMP Rules s 6(d). A material risk includes the storage, transmission or processing of sensitive operational information outside Australia, including layout diagrams, schematics and configuration information.
  • Enhanced CIRMP s 6A(2)(c)-(d). Offshore or remote access to critical components and to business critical data are additional material risks.
  • CPS 230 para 59(b). APRA must be told before a material offshoring arrangement, including where data relevant to the service will be located offshore.
  • APP 8.1. Disclosure of personal information to an overseas recipient carries the entity's responsibility with it.

A penetration test produces exactly this kind of information: network maps, configurations, credentials and evidence of how to reach critical systems. A SaaS testing platform that processes it abroad, or an AI model hosted overseas that reads it, should go through the same review as any other offshore service. A tool that runs inside the entity's own network, on its own models, keeps the question simple. See the sovereign AI red team guide.

Compliance checklist

  1. List your controls and map each one to the assets it protects, their criticality and their exposure to untrusted environments (CPS 234 para 27, CPG 234).
  2. Set a documented, risk-based testing frequency: at least annual coverage of a sufficient set of controls, and continuous or frequent testing of internet-facing controls.
  3. Record who ran each test and why they are functionally independent of the controls tested.
  4. Review the testing program at least once a year and after material change; escalate deficiencies that cannot be fixed in time, and notify APRA within 10 business days where para 36 applies.
  5. For SOCI assets: confirm which framework your CIRMP follows and at what level, check whether the enhanced rules apply, and use testing to support the board-approved annual report.
  6. Check where every testing tool stores and processes findings, credentials and configurations, against CIRMP s 6(d), CPS 230 para 59 and APP 8.
  7. Re-test fixes and keep the evidence.

The requirements by regulation page compares Australia with other jurisdictions.

Where Zero Hunt fits

Zero Hunt is an autonomous AI red team on an on-premise appliance: it runs black-box and gray-box penetration tests of networks and infrastructure from inside your network, on its own private AI models with no third-party LLM, so customer data stays on your network. Intrusive steps wait for operator approval, evidence records are signed and hash-chained, and exported reports are ECDSA-signed.

Zero Hunt maps findings to 34 frameworks worldwide, including APRA CPS 234, ISO/IEC 27001 and the NIST Cybersecurity Framework (two of the frameworks listed in the CIRMP Rules). It does not map the Essential Eight, the ISM, CPS 230 or the Privacy Act, and it is not IRAP-assessed. Who runs and reviews the tests still decides whether CPS 234's independence requirement is met.

Questions

Does APRA require an annual penetration test? Not in those words. CPS 234 requires a systematic testing program with frequency based on threat, criticality and change, and an annual review of the program. CPG 234 expects a sufficient set of controls tested at least annually, and internet-facing controls tested throughout the year.

Must the tester be an external firm? No. CPS 234 para 30 requires appropriately skilled and functionally independent specialists. CPG 234 describes independence as testers without operational responsibility for the controls being validated.

Does the SOCI Act require penetration testing? The CIRMP Rules require a cyber framework, such as the Essential Eight at Maturity Level One (Level Two for enhanced subclasses), but do not name penetration testing. Systems of national significance can be directed to run a vulnerability assessment or a cyber security exercise.

Can we use a cloud or SaaS pentest platform hosted outside Australia? Check with compliance. The CIRMP Rules treat offshore processing of sensitive operational information as a material risk, CPS 230 requires notice before a material offshoring arrangement, and APP 8 applies to personal information sent overseas.

Is the Essential Eight a pentest standard? No. It is a set of eight mitigation strategies with maturity levels. Testing is a way to check that the chosen level is actually in place.

Sources

Goes deeper

Want this against your environment?

Book a 30-minute scoping call — we will map this directly to your current compliance scope and threat profile.