APRA CPS 234 · Australia

APRA CPS 234 security monitoring, from detection to a 72-hour notice.

What CPS 234 asks of banks, insurers and super trustees: an information security capability that detects and responds in a timely manner, notification to APRA within 72 hours, and scrutiny of every third party that holds your information. And how a SIEM you run yourself fits.

Buy nano
Talk to sales
Notification to APRA · paras 35 and 36

72 hours to tell APRA. Detection has to come first.

CPS 234's clock starts when you become aware. Paragraph 23's requirement to detect incidents in a timely manner is what makes awareness possible.

  1. 0 h

    Aware of an information security incident

    Assess whether it materially affected, or could have affected, the entity or its customers.

  2. 72 h

    Material incident

    Notify APRA as soon as possible, and no later than 72 hours after becoming aware of a material information security incident (para 35).

  3. 10 bd

    Material control weakness

    Notify APRA within 10 business days of becoming aware of a material weakness you expect not to remediate in time (para 36).

APRA, Prudential Standard CPS 234 Information Security, paragraphs 35 and 36.
What CPS 234 requires

The paragraphs that depend on monitoring.

Each line: what CPS 234 says, what it means in practice, and where nano fits.

CPS 234 Information Security: requirements that depend on security monitoring

Paragraph numbers from CPS 234 as published by APRA (in force from 1 July 2019).

Ref What CPS 234 says In plain English How nano helps
Para 15 · 17 Maintain an information security capability commensurate with the size and extent of threats to information assets, and actively maintain it as vulnerabilities and threats change. apra.gov.au · CPS 234 Your security capability, including monitoring, has to keep up with the threats you face.
Detection content updates and your own rules run on everything you onboard, in one platform you control.
Para 21 Have information security controls, including over assets managed by related parties and third parties, implemented in a timely manner and commensurate with threats, criticality and sensitivity. apra.gov.au · CPS 234 Controls, including detective ones, sized to the risk.
Collect from the systems that hold your most critical and sensitive information first, then widen coverage. Pricing is per GB/day, not per endpoint.
Para 23 "Have robust mechanisms in place to detect and respond to information security incidents in a timely manner." apra.gov.au · CPS 234 Detection and response is a requirement, not a nice-to-have.
Detection rules run as events arrive and raise alerts; related alerts group into cases for investigation and response.
Para 24 · 25 Maintain information security response plans covering all stages of an incident, from detection to post-incident review, and escalation and reporting to the Board and others. apra.gov.au · CPS 234 A response plan that starts at detection and ends with lessons learned.
Cases keep alerts, evidence, notes and the timeline from detection to close, ready for escalation and post-incident review.
Para 26 · 27 Annually review and test response plans; test the effectiveness of controls through a systematic testing program. apra.gov.au · CPS 234 Test both the plan and the controls, regularly.
Searchable history shows whether a test or exercise was detected, and when.
Para 35 Notify APRA as soon as possible, and no later than 72 hours after becoming aware, of an information security incident that materially affected, or had the potential to materially affect, the entity or its customers, or that was notified to another regulator. apra.gov.au · CPS 234 Seventy-two hours from awareness to APRA.
The case record gives you what happened, what was affected and when. nano does not notify APRA for you.
Para 36 Notify APRA within 10 business days of becoming aware of a material information security control weakness the entity expects it will not remediate in a timely manner. apra.gov.au · CPS 234 Known gaps you can't close quickly are also reportable.
Coverage gaps in collection or detection are visible in one place, which helps you spot a weakness early.

Information assets managed by third parties

CPS 234 applies to information assets whether you manage them or a related party or third party does.

Ref What CPS 234 says In plain English How nano helps
Para 16 · 22 Assess the information security capability of a related party or third party managing your information assets, and evaluate the design of its controls that protect them. apra.gov.au · CPS 234 If someone else holds your information, you have to assess how they protect it.
nano does not manage your logs: they stay on infrastructure you run. Your cloud or hosting provider, if you use one, remains in scope.
Para 20 Classify information assets, including those managed by related parties and third parties, by criticality and sensitivity. apra.gov.au · CPS 234 Security logs are information assets too, and often sensitive ones.
Source visibility rules and role-based access restrict who can see sensitive log sources.
CPS 230 and CPS 234

CPS 230 builds on CPS 234. It doesn't replace it.

CPS 230 Operational Risk Management commenced on 1 July 2025, and an amended version took effect on 1 July 2026. Three points matter for your security monitoring.

CPS 230 · para 24

CPS 234 still applies.

In managing technology risk, an entity must "meet the requirements for information security in Prudential Standard CPS 234".

CPS 230 · para 32

No double notification.

CPS 230 has its own 72-hour notice for material operational risk incidents, but an information security incident notified under CPS 234 doesn't need a second notice under CPS 230.

CPS 230 · para 60(b)

Offshoring needs notice first.

Entities notify APRA before entering a material offshoring arrangement, including where data relevant to the service will be located offshore. A SIEM you run onshore in your own environment doesn't create one.

Source: APRA, CPS 230 Operational Risk Management (amended standard, in effect from 1 July 2026). Whether any particular arrangement is material is your assessment to make.

Why where your logs live matters

No new third party holding your logs.

Security logs describe customers, accounts, privileged users and incidents. Under CPS 234, whoever holds them is part of your information security perimeter. With nano, that is only you.

Your environment

Your data center or your account in an Australian cloud region

01 · Sources
  • core banking
  • Entra ID
  • payments
  • firewall
  • EDR
  • cloud audit
02 · nano
  • Collect and parse
  • Detections and alerts
  • Search and cases
03 · Your storage
  • Disks you own
  • Optional object storage tier
  • Retention you set
Optional · AI pivt AI calls your model endpoint directly: any OpenAI-compatible API (including self-hosted models) or the Anthropic Messages API. Off by default; model calls never go through nano.
nano, the vendor

Never receives your logs.

Connected
  • Daily license check-in: deployment ID, install ID, version
  • Hourly content and enrichment-feed updates (no data sent; can be turned off)
  • One number per day: total GB ingested
  • Downloads: log-source catalog, detection rules and SOAR content, enrichment feeds, releases
Air-gapped
  • No connection to nano at all
  • Offline license file, renewed by hand
fig 01 · nano runs inside your environment. Log data is never sent to nano.
Third parties · paras 16, 22

One less assessment.

nano doesn't hold or manage your logs, so there's no SIEM vendor whose controls you must evaluate for them. Your infrastructure provider remains in scope.

Response · paras 24, 25

From detection to review.

Cases carry alerts, evidence, notes and timeline through every stage of an incident. Case management

Evidence

Keep what investigations need.

CPS 234 sets no retention period. Set yours to fit investigations and your other obligations, on storage you own. Storage and retention

FAQ

Questions we get asked.

What is APRA CPS 234?

CPS 234 Information Security is a prudential standard from the Australian Prudential Regulation Authority (APRA), in force since 1 July 2019. It requires APRA-regulated entities to maintain an information security capability commensurate with the threats they face, implement and systematically test controls to protect their information assets, have robust mechanisms to detect and respond to incidents in a timely manner, and notify APRA of material information security incidents.

Who must comply with CPS 234?

All APRA-regulated entities: authorized deposit-taking institutions (including foreign ADIs and authorized banking NOHCs), general insurers, life companies and friendly societies, private health insurers, and RSE licensees in respect of their business operations. For foreign ADIs, Category C insurers and eligible foreign life insurance companies, it applies to the Australian branch operations.

Does CPS 230 replace CPS 234?

No. CPS 230 Operational Risk Management, which commenced on 1 July 2025, is a separate standard, and CPS 234 remains in force. CPS 230 itself requires entities to meet the information security requirements in CPS 234, and says an information security incident notified under CPS 234 does not need to be notified again under CPS 230. An amended CPS 230 took effect on 1 July 2026.

What does CPS 234 require for detecting and responding to information security incidents?

Paragraph 23 requires robust mechanisms to detect and respond to information security incidents in a timely manner. Paragraphs 24 to 26 require response plans for incidents that could plausibly occur, covering every stage from detection to post-incident review plus escalation to the Board, reviewed and tested annually. APRA's guidance in CPG 234 lists logs and security information and event management (SIEM) among the controls for timely detection of unauthorized access and use.

What are the CPS 234 notification deadlines?

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 (paragraph 35). Notify APRA within 10 business days of becoming aware of a material information security control weakness the entity expects it cannot remediate in a timely manner (paragraph 36).

How does CPS 234 treat information assets managed by third parties, such as a SaaS SIEM?

CPS 234 applies to information assets managed by related parties and third parties. The entity must assess the third party's information security capability, evaluate the design of its controls, classify the assets it manages, and consider its control testing. A SaaS SIEM that stores your security logs is such a third party. With nano, the logs stay on infrastructure you run, so nano is not managing them; your cloud or hosting provider, if you use one, remains in scope.

What is the difference between CPS 234 and CPG 234?

CPS 234 is the prudential standard: its requirements are enforceable. CPG 234 is APRA's prudential practice guide on information security: it explains APRA's view of sound practice for meeting CPS 234 but does not itself create enforceable requirements.

Does CPS 234 set a log retention period?

No. CPS 234 does not specify how long to keep security logs. Retention follows from your own policy, your incident response and investigation needs, and any other rules that apply to you. CPG 234 notes that logging should facilitate investigation and preserve forensic evidence.

Is nano CPS 234 compliant?

No product is CPS 234 compliant: the standard applies to the regulated entity, and nano holds no certification. It helps you build the detection, response and evidence capability CPS 234 asks for, inside your own environment.

Primary sources

Read the rules yourself.

Start with nano.

From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.

Buy nano
Talk to sales