SOCI Act · Australia

SOCI Act logging, ready for the 12-hour clock.

What the Security of Critical Infrastructure Act asks of your security telemetry: incident reports within 12 or 72 hours, a risk management program with a cyber framework, and more for Systems of National Significance. And how a SIEM you run on your own infrastructure supports each one.

Buy nano
Talk to sales
Mandatory cyber incident reporting · Part 2B

12 hours or 72 hours, from the moment you know.

The clock starts when you become aware of the incident. If you can't see across the asset's systems, you can't tell which clock you're on.

  1. 0 h

    Aware of a cyber security incident

    Decide quickly whether the impact on the asset is significant or relevant.

  2. 12 h

    Critical incident report

    Significant impact on the availability of the asset: report to ASD's ACSC within 12 hours of becoming aware (s 30BC).

  3. 72 h

    Other incident report

    Relevant impact on availability, integrity, reliability or confidentiality: report within 72 hours (s 30BD).

  4. +84 h

    Written record after a verbal report

    A verbal critical report is followed by a written record within 84 hours; for other incidents, within 48 hours.

CISC, Notification of Cyber Security Incidents (March 2026). Reports go to ASD's ACSC.
What the rules require

SOCI obligations, and where a SIEM fits.

Each line: what the Act, its rules or the CISC say, what it means in practice, and where nano fits.

Security of Critical Infrastructure Act 2018: obligations that rely on security logs

Which obligations apply depends on the asset class. The CISC obligations factsheet has the table by class.

Ref What the rules say In plain English How nano helps
Part 2B · s 30BC Report a critical cyber security incident, one having a significant impact on the availability of the asset, to ASD's ACSC within 12 hours of becoming aware; follow a verbal report with a written record within 84 hours. cisc.gov.au · incident notification Twelve hours from awareness, not from the start of the attack. You need to see what happened quickly enough to say so.
Detection rules run as events arrive and raise alerts; related alerts group into cases holding the evidence and timeline your report draws on. nano does not report to ASD for you.
Part 2B · s 30BD Report another cyber security incident, one having a relevant impact on the availability, integrity, reliability or confidentiality of the asset, within 72 hours; written record within 48 hours of a verbal report. Escalate with a new 12-hour report if the impact becomes significant. cisc.gov.au · incident notification Lower-impact incidents still have a clock, and can turn into the 12-hour kind.
Search across every onboarded source in one place to scope impact on integrity and confidentiality, not just availability.
Part 2A · CIRMP Have and comply with a written risk management program that minimizes or eliminates material risks from all hazards, including cyber and information security hazards. cisc.gov.au · CIRMP guidance A board-level risk program, with cyber security as one of its hazards.
Centralized, searchable logs give the program's cyber controls something to evidence: what you monitor, what fired, what you did.
CIRMP Rules · s 6(f) Minimize or eliminate the material risk of impacts to the availability, integrity, reliability or confidentiality of the data storage system holding business critical data. cisc.gov.au · CIRMP guidance Know where business critical data is stored, including at third parties and in cloud services, and protect those systems.
A SIEM you run yourself is one more system in your own inventory, not a third-party store. Whether your log store holds business critical data is a question for your advisers.
CIRMP Rules · s 8(4) Comply with a listed cyber security framework, or an equivalent. Baseline options include the Essential Eight at Maturity Level One and AS ISO/IEC 27001:2015. cisc.gov.au · CIRMP guidance Pick a framework and meet it. The Essential Eight at ML1 is one baseline option.
Essential Eight ML1 has no central logging requirement, so the baseline doesn't force a SIEM. The enhanced rules below change that for some assets.
Enhanced · s 8A(3) Assets under the enhanced CIRMP Rules (commenced 10 June 2026) comply with a listed framework at a higher level, including the Essential Eight at Maturity Level Two. cisc.gov.au · CIRMP guidance If you choose the Essential Eight under the enhanced rules, you need ML2, and ML2 brings central event logging.
Collects the events Essential Eight ML2 asks to be centrally logged and keeps them protected from unauthorized modification and deletion.
Enhanced · s 6A(2)(d) Material risks to minimize or eliminate include offshore or remote access to business critical data. cisc.gov.au · enhanced CIRMP Offshore and remote access to critical data is now a named risk for enhanced-CIRMP assets.
When you run nano yourself, the SIEM vendor has no standing access to your install, offshore or otherwise. Air-gapped, there is no connection to nano at all.
s 30AG Give the relevant regulator an annual CIRMP report within 90 days after the end of the financial year, approved by the board, council or governing body if there is one. cisc.gov.au · CIRMP guidance Once a year, the board signs off on whether the program is up to date and how it handled significant incidents.
Case history and detection records give the report's incident statements a factual base.
s 12F(3) Take reasonable steps to tell a third party that stores or processes business critical data on a commercial basis that it is doing so. cisc.gov.au · SOCI obligations Outsourced data handlers must be told, because they may pick up obligations of their own.
nano does not store or process your log data, so it is not a data service provider for it.
Part 2C · ECSO For a declared System of National Significance, the responsible entity may be required to have an incident response plan, run exercises, undertake vulnerability assessments, and provide, or install software to provide, system information to ASD. cisc.gov.au · SOCI obligations The most critical assets can be asked for more, including system information for ASD.
Your telemetry stays in your custody, in your environment, so you decide what system information leaves it and how.

Cyber Security Act 2024, Part 3: ransomware and cyber extortion payments

A separate clock that runs alongside SOCI reporting.

Ref What the rules say In plain English How nano helps
s 27 Report a ransomware or cyber extortion payment to ASD within 72 hours of making it, or of becoming aware it was made on your behalf. Applies to businesses with annual turnover over A$3 million and to responsible entities for SOCI Part 2B assets. homeaffairs.gov.au · ransomware reporting Paying is reportable, even if the incident itself was already reported. No payment, no mandatory report.
The report asks when the incident occurred, its impact and which vulnerabilities were exploited. Your SIEM timeline is where those answers come from.
CIRMP cyber frameworks

Baseline ML1, enhanced ML2. Logging lives at ML2.

The CIRMP Rules let you choose a cyber security framework. If you choose the Essential Eight, the enhanced rules that commenced on 10 June 2026 lift the level from One to Two, and Maturity Level Two is where central event logging starts.

Baseline CIRMP · s 8(4)

Any listed framework, at its entry level.

  • AS ISO/IEC 27001:2015
  • Essential Eight, Maturity Level One
  • NIST Framework for Improving Critical Infrastructure Cybersecurity
  • C2M2, Maturity Indicator Level 1
  • 2020-21 AESCSF Framework Core, Security Profile 1
Enhanced CIRMP · s 8A(3)

A higher bar for listed asset classes.

  • AS ISO/IEC 27001:2023
  • Essential Eight, Maturity Level Two
  • NIST Cybersecurity Framework 2.0
  • C2M2 version 2.1, Maturity Indicator Level 2
  • 2023 AESCSF Framework Core, Security Profile 2

Source: CISC CIRMP guidance, section 3.2.2. The CISC notes the CIRMP Rules have not yet been updated for ASD's Essentials series. Read what ML2 asks of your logs on the Essential Eight logging page.

  1. 30 May 2025 In effect

    Ransomware payment reporting starts

    Cyber Security Act 2024 Part 3 reporting commenced, with an education-first phase.

    homeaffairs.gov.au · ransomware reporting ↗
  2. 1 Jan 2026 In effect

    Compliance phase

    Home Affairs moved ransomware payment reporting to a more active regulatory focus.

    homeaffairs.gov.au · ransomware reporting ↗
  3. 10 Jun 2026 In effect

    Enhanced CIRMP Rules commence

    Higher framework levels and new material risks for listed asset classes, including electricity, gas, water and liquid fuel.

    cisc.gov.au · enhanced CIRMP ↗
  4. 10 Jun 2027 Next

    Enhanced: new material risks

    Existing assets must address the new material risks, including offshore or remote access to business critical data.

    cisc.gov.au · enhanced CIRMP ↗
  5. 10 Jun 2028 Next

    Enhanced: all other measures

    Remaining enhanced measures apply, including the higher cyber framework level.

    cisc.gov.au · enhanced CIRMP ↗
Why where your logs live matters

Telemetry from critical assets, kept in your custody.

Security logs from a critical infrastructure asset describe its systems, its weaknesses and its incidents. With nano they stay on infrastructure you control, under your own risk management program.

Your environment

Your data center, your OT network, your account in an Australian cloud region, or an air-gapped site

01 · Sources
  • SCADA / historian
  • firewall
  • Entra ID
  • EDR
  • servers
  • OT network
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.
Offshore access · s 6A(2)(d)

No standing vendor access, onshore or offshore.

nano, LLC is a US company, but it holds none of your data and has no standing access to your install. Support sees only what you choose to share. Your own staff and partners are the only remote access you have to manage.

System information · Part 2C

You decide what leaves.

If you operate a System of National Significance, your telemetry is already in your custody, so any system information you provide to ASD goes from you, on your terms.

Segmented and OT sites

Air-gapped when you need it.

Air-gapped operation is included with every license: no connection to nano, content packs you import by hand and an offline license. Air-gapped deployment

Who the SOCI Act applies to

11 sectors, many asset classes.

The SOCI Act covers critical infrastructure assets in 11 sectors. Obligations differ by asset class: check the CISC table for yours.

  • Communications
  • Data storage or processing
  • Defence industry
  • Energy
  • Financial services and markets
  • Food and grocery
  • Health care and medical
  • Higher education and research
  • Space technology
  • Transport
  • Water and sewerage

Source: CISC SOCI Act obligations factsheet. Want to buy nano through a local partner and work with them in Australia? See Threatbear.

FAQ

Questions we get asked.

What is the SOCI Act?

The Security of Critical Infrastructure Act 2018 (SOCI Act) is the Australian law that sets security obligations for owners and operators of critical infrastructure assets. It was amended in 2021 and 2022, and again in 2024 by the Enhanced Response and Prevention Act. Its obligations include registering assets, mandatory cyber incident reporting, a critical infrastructure risk management program (CIRMP) and, for Systems of National Significance, enhanced cyber security obligations. The Cyber and Infrastructure Security Centre (CISC) publishes the guidance on it.

Who does the SOCI Act apply to, and which sectors are covered?

It applies to responsible entities and direct interest holders for critical infrastructure assets in 11 sectors: communications; data storage or processing; defence industry; energy; financial services and markets; food and grocery; health care and medical; higher education and research; space technology; transport; and water and sewerage. Which obligations apply depends on the asset class.

What is a Critical Infrastructure Risk Management Program (CIRMP)?

A CIRMP is a written program a responsible entity must have and comply with under Part 2A of the SOCI Act. It identifies material risks from all hazards (cyber and information security, personnel, supply chain, and physical and natural hazards) and minimizes or eliminates them as far as reasonably practicable. It must include compliance with a listed cyber security framework, such as the Essential Eight, and the entity reports on it annually, within 90 days after the end of the financial year, with board approval where there is a board.

What are the SOCI cyber incident reporting deadlines?

A critical cyber security incident, one with a significant impact on the availability of the asset, must be reported to ASD's ACSC within 12 hours of becoming aware of it. Any other cyber security incident with a relevant impact must be reported within 72 hours. A verbal report is followed by a written record within 84 hours for critical incidents and 48 hours for other incidents. These timings are from the CISC's March 2026 guidance.

What are Systems of National Significance and enhanced cyber security obligations?

The Minister for Home Affairs can declare a critical infrastructure asset a System of National Significance (SoNS) because of its interdependencies and the consequences of its disruption. The responsible entity can then be required to meet enhanced cyber security obligations under Part 2C: an incident response plan, cyber security exercises, vulnerability assessments, and providing, or installing software to provide, system information to ASD.

How does Cyber Security Act 2024 ransomware payment reporting interact with SOCI?

They are separate obligations. Under section 27 of the Cyber Security Act 2024, a reporting business entity that makes a ransomware or cyber extortion payment must report it to ASD within 72 hours. Responsible entities for assets covered by SOCI Part 2B are reporting business entities regardless of turnover; other businesses are captured if their annual turnover exceeds A$3 million. A SOCI incident report does not replace a payment report.

Which logs do you need to keep for CIRMP evidence and incident reports?

The SOCI Act does not list log sources or a retention period. The logs you need follow from your CIRMP and the framework you comply with: if that is the Essential Eight at Maturity Level Two, for example, privileged access, MFA, application control, PowerShell and command-line events must be centrally logged and protected. For incident reports, you need enough telemetry, from the assets in scope and the systems that hold business critical data, to tell within hours whether an incident is significant.

Can a SOCI entity keep its security logs inside its own environment or onshore?

Yes. Nothing in the SOCI Act requires security logs to go to a vendor. nano is software you install in your own data center, OT network, Australian cloud account or air-gapped site, so logs are collected, stored and analyzed there and never reach nano. Air-gapped operation is included with every license.

Is nano a SOCI compliance solution?

No. No product makes an entity SOCI-compliant, and nano holds no certification. It helps you collect, protect, analyze and retain the security telemetry your CIRMP and incident reports depend on.

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