Two operators at a control-room desk with a row of monitors, a laptop and keyboards

OT/ICS security

Australia's Security of Critical Infrastructure (SOCI) Act: cyber obligations, explained

Last updated:

Australia's Security of Critical Infrastructure Act 2018 (SOCI Act) is the Commonwealth's framework for protecting critical infrastructure — originally a narrow 2018 law covering four sectors, now, after two major rounds of amendment, a broad regime spanning 11 sectors, mandatory risk management programs, cyber incident reporting with 12-hour/72-hour clocks, and Enhanced Cyber Security Obligations for the most sensitive assets. It is Australia's closest analogue to the EU's NIS2 Directive and the US's CIRCIA — a mandatory, regulator-facing incident reporting and risk-management regime for critical infrastructure operators, rather than a voluntary or product-focused scheme.

The obligations below are drawn from the Federal Register of Legislation's consolidated Act text (Compilation No. 9, 4 June 2026) and the CIRMP Rules (Compilation No. 2, 10 June 2026), read on 12 November 2026, with the Cyber and Infrastructure Security Centre's obligations page for regulator context. legislation.gov.au and cisc.gov.au remain the authoritative sources for exact section numbers and current asset-class thresholds.

Key takeaways

  • The obligations below are drawn from the Federal Register of Legislation's consolidated Act text (Compilation No.
  • The Act commenced 11 July 2018 covering only electricity, gas, water and maritime ports.
  • Source: CIRMP Rules LIN 23/006, s 8(4), Compilation No.
  • Section 4A(6) gives grace periods of 12 months for some of these duties and 24 months for others.

How did SOCI grow from four sectors to eleven?

The Act commenced 11 July 2018 covering only electricity, gas, water and maritime ports. The amendment history in the consolidated text (Endnotes 3 and 4) shows which Act added which obligation:

Amending Act In force What it added
Security Legislation Amendment (Critical Infrastructure) Act 2021 (No. 124, 2021) 3 December 2021 11 sectors, mandatory cyber incident reporting (Part 2B), government assistance powers (Part 3A), data provider notification (s 12F)
Security Legislation Amendment (Critical Infrastructure Protection) Act 2022 (No. 33, 2022) 2 April 2022 Risk management program (Part 2A), Enhanced Cyber Security Obligations (Part 2C), Systems of National Significance (Part 6A)
Security of Critical Infrastructure and Other Legislation Amendment (Enhanced Response and Prevention) Act 2024 (No. 100, 2024) 20 December 2024, telecoms parts 4 April 2025 Data storage systems treated as part of the asset (s 9(7)), telecommunications security (Part 2D), wider consequence management powers

Source: SOCI Act Compilation No. 9, Endnotes 3–4, read 12 November 2026.

The Act now covers 11 critical infrastructure sectors: communications, financial services and markets, data storage or processing, defence industry, higher education and research, energy, food and grocery, healthcare and medical, space technology, transport, and water and sewerage. CISC describes these as holding 22 types of critical infrastructure asset. The 2024 data storage rule matters to OT vendors: a system the responsible entity owns or operates that holds "business critical data" for the asset is now taken to be part of the asset, so a historian or engineering workstation can carry the same obligations as the plant itself.

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

A CIRMP is a written program, required by section 30AC (civil penalty: 200 penalty units), that for each asset must identify every hazard with a material risk of a "relevant impact", minimise or eliminate those risks so far as reasonably practicable, and mitigate their impact (s 30AH). "Relevant impact" means an impact on the asset's availability, integrity or reliability, or on the confidentiality of its information.

The Security of Critical Infrastructure (Critical Infrastructure Risk Management Program) Rules 2023 (LIN 23/006) apply this to 13 asset classes, including critical electricity, gas, water, liquid fuel, freight, data storage or processing, food and grocery assets and designated hospitals. The rules set four hazard domains — cyber and information security, personnel, supply chain, and physical security and natural hazards. For the cyber domain, section 8(4) requires the entity to comply with one named framework, or an equivalent:

Framework (baseline, s 8(4)) Condition
AS ISO/IEC 27001:2015 —
ASD Essential Eight Maturity Model Maturity level one
NIST Framework for Improving Critical Infrastructure Cybersecurity —
US DoE Cybersecurity Capability Maturity Model (C2M2) Maturity Indicator Level 1
2020-21 AESCSF Framework Core (AEMO) Security Profile 1

Source: CIRMP Rules LIN 23/006, s 8(4), Compilation No. 2.

Governance matters here, not just documentation. Section 30AG requires an annual report within 90 days after the end of the financial year, which is 28 September for a 30 June year-end, stating whether the program was up to date. For entities with a board, the report must be approved by the board, council or other governing body. Telecommunications assets sit under Part 2D instead of these rules.

What did the June 2026 enhanced CIRMP requirements add?

The Enhanced Critical Infrastructure Risk Management Program Rules 2026 (LIN 26/075) commenced on 10 June 2026 and add a second, stricter tier for nine asset classes: broadcasting, domain name systems, electricity, energy market operators, freight infrastructure, freight services, gas, liquid fuel and water (s 4A(1)). Where the tiers conflict, the enhanced requirement wins. The new sections are specific in a way the 2023 rules were not:

  • Section 8A names material risks the program must address, including failure to patch operating or security systems in a timely manner, and failure to replace or mitigate legacy components that are "redundant, unsupported, obsolete or discontinued." It also raises the framework bar: AS ISO/IEC 27001:2023, Essential Eight maturity level two, NIST CSF 2.0, C2M2 v2.1 at MIL 2, or the 2023 AESCSF at Security Profile 2.
  • Section 8B requires phishing-resistant multi-factor authentication for access to internet-connected computers and critical systems, privileged and unprivileged access to critical components, and remote access, with central logging of successful and failed MFA attempts.
  • Section 8C requires an inventory of critical systems and their connections, and network segregation in which critical systems can run independently and stay operational for at least three months while other computers are restored.
  • Section 10A requires mapping the supply chain for major suppliers and critical components, a "maximum acceptable outage" for supply disruption, and an assessment of each major supplier that covers foreign ownership, control or influence (FOCI), sanctions, and the supplier's access to and control over the asset.

Section 4A(6) gives grace periods of 12 months for some of these duties and 24 months for others. Check CISC guidance for the dates that apply to a given asset.

What are the 12-hour and 72-hour reporting rules?

Under Part 2B, a responsible entity must report cyber security incidents to the "relevant Commonwealth body", which is the Australian Signals Directorate (ASD) unless rules name another (s 30BF). The clock starts when the entity becomes aware of the incident:

Section Trigger Deadline If reported orally
30BC, critical incident Has had, or is having, a significant impact on the availability of the asset 12 hours Written record in the approved form within 84 hours
30BD, other incident Has had, is having, or is likely to have a relevant impact on the asset (includes imminent incidents) 72 hours Written record within 48 hours

Source: SOCI Act ss 30BC, 30BD, 30BEA, Compilation No. 9. Each obligation carries a civil penalty of 50 penalty units.

Section 30BEA makes "significant impact" narrow: the asset is used to provide essential goods or services and the incident has materially disrupted their availability, or a circumstance the rules specify exists. An intrusion that has not disrupted supply is usually a 72-hour report, not a 12-hour one. Mandatory reporting took effect 8 July 2022 for the asset classes the rules specified at that stage. This reporting duty is separate from the 72-hour ransomware-payment report under the Cyber Security Act 2024 (s 27), which responsible entities for Part 2B assets must also make.

What are Enhanced Cyber Security Obligations and Systems of National Significance?

The Minister can declare an asset a System of National Significance (SoNS) under Part 6A where the national consequences of its compromise would be especially severe. CISC describes SoNS as "a very, very small subset" of critical infrastructure assets. The Secretary of Home Affairs can then apply up to four Enhanced Cyber Security Obligations under Part 2C: an incident response plan (s 30CD), cyber security exercises (s 30CM), vulnerability assessments (s 30CU), and access to system information. The Secretary must weigh the likely cost to the entity and proportionality before applying them. Part 3A separately gives the government assistance and intervention powers for serious incidents, including Ministerial authorisations under section 35AB.

What will a SOCI-covered customer ask an OT or IoT supplier for?

SOCI puts no duty on the supplier of a PLC, gateway, meter or sensor; it puts duties on the operator, who passes them up the supply chain. A water utility or electricity network building its CIRMP will, in practice, ask its vendors for evidence like this:

Customer obligation Typical request to the supplier
s 8A(2)(a)–(b) timely patching, unsupported components Published support period, patch cadence, and an SBOM showing which components are end-of-life
s 8B phishing-resistant MFA on critical components and remote access Support for central authentication, no shared local accounts, remote support through the customer's MFA gateway
s 8C inventory, segregation, three months of independent operation Documented ports, protocols and data flows; product works with cloud services cut off
s 10 / 10A supplier privileged access, FOCI, maximum acceptable outage Who can reach the device remotely, ownership and jurisdiction, spares and repair times
s 12F(3) data service provider notice Confirmation of whether the vendor's cloud stores business critical data for the asset
ss 30BC/30BD incident reports A PSIRT contact and fast advisories when a vendor flaw is behind an incident

Much of this is the same evidence IEC 62443-4-2 component certification and IEC 62443-2-4 service provider requirements already ask for. A supplier that maps its answers once can reuse them across SOCI, NIS2 and Secure by Demand questionnaires. The three-month independent-operation test in section 8C is the item most likely to surprise vendors of cloud-managed devices. For devices sold to consumers, Australia's separate smart device security standard under the Cyber Security Act 2024 applies directly to the manufacturer.

How does SOCI compare with NIS2, CIRCIA and the Cyber Security Act 2024?

  • NIS2 (EU) — mandatory risk-management and incident-notification regime for "essential" and "important" entities across a similarly broad sector list, with a 24-hour early-warning / 72-hour full-notification sequence.
  • CIRCIA (US) — a 2022 statute whose reporting duties start only once CISA's final rule takes effect. CISA held further town hall meetings in 2026, and no final rule had appeared in the Federal Register by 12 November 2026.
  • Cyber Security Act 2024 (Australia) — sits beside SOCI: ransomware-payment reporting within 72 hours for businesses over the turnover threshold and for Part 2B responsible entities, plus mandatory security standards for consumer smart devices.
  • SOCI Act (Australia) — fully operational: CIRMP, 12/72-hour cyber incident reporting and Enhanced Cyber Security Obligations have all been in force since 2022, and the 2026 enhanced CIRMP tier is the newest layer.

How should a responsible entity or supplier start?

  1. Confirm whether your asset meets a prescribed asset-class definitionSector membership alone doesn't trigger obligations — check the asset-class definitions in the Act and rules, or CISC's asset class guidance.
  2. Check whether the asset is in the enhanced tierIf it is one of the nine classes in section 4A(1), plan to the 2026 framework levels (for example Essential Eight level two) rather than the 2023 baseline.
  3. Build the CIRMP as a living, board-governed program, not a one-off documentThe annual report and the hazard-by-hazard review assume ongoing maintenance.
  4. Pre-build the 12-hour reporting path before an incident happensDecide in advance who judges "material disruption" and who calls ASD, and keep the 84-hour written follow-up in the runbook.
  5. Suppliers: prepare a SOCI evidence packSupport periods, SBOMs, remote access design, data flows and a PSIRT contact answer most CIRMP questionnaires.
  6. Watch for amendmentslegislation.gov.au and cisc.gov.au publish the current consolidated Act, rules and guidance, which govern over this summary if the two ever diverge.

What can AI do when a 12-hour reporting clock is running?

A 12-hour deadline for a critical cyber incident leaves no time to write an ASD report from scratch while also triaging what happened. What SoftWSP's platform does under that kind of clock is narrower than detecting the incident itself. From a packet capture it lists the hosts and services it observed and flags management sessions (SSH, Telnet, RDP, VNC) that crossed a network boundary; from an SBOM it matches components to NVD, KEV, EPSS and vendor CSAF advisories. AI then drafts a plain-language summary an engineer can adapt into the ASD notification or the CIRMP review, citing the evidence behind each sentence. AI doesn't decide whether an incident meets the "critical" threshold or file the report itself; a person makes that call and submits it. The deterministic matching that produces the underlying evidence runs whether or not AI is available to draft the summary on top of it.

SoftWSP's PSIRT setup work can help build the incident intake, triage and reporting workflow a SOCI-covered entity, or its suppliers, need to meet 12-hour/72-hour ASD reporting deadlines: see PSIRT services.

This guide summarises the Security of Critical Infrastructure Act 2018 and the CIRMP Rules as reflected in the Federal Register of Legislation's consolidated text, with the Department of Home Affairs' independent review of the Act for background; it is not a substitute for the Act's own current text, the CIRMP Rules, or legal advice; compliance decisions rest on that current official text, not on this summary.

Put this guide to work

Frequently asked questions

What is the SOCI Act and who does it apply to?

The Security of Critical Infrastructure Act 2018 (Cth) is an Australian Commonwealth law establishing a national framework to identify, manage and reduce security risks — including cyber risks — to the country's critical infrastructure. It received royal assent on 11 April 2018 and commenced 11 July 2018, originally covering only four sectors (electricity, gas, water, maritime ports). Amendments in 2021 (the Security Legislation Amendment (Critical Infrastructure) Act) and 2022 (the Security Legislation Amendment (Critical Infrastructure Protection) Act) expanded coverage to 11 sectors: communications, financial services and markets, data storage or processing, defence industry, higher education and research, energy, food and grocery, healthcare and medical, space technology, transport, and water and sewerage. Being in one of these sectors doesn't automatically make an organisation a 'responsible entity' — only assets meeting specific asset-class definitions and thresholds set out in the Act and its rules are actually captured; the Act defines roughly 22 asset classes across the 11 sectors.

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

The CIRMP, set out in Part 2A of the Act, requires a responsible entity for an applicable critical infrastructure asset to establish, maintain and comply with a written risk management program addressing material risks across hazard domains that per secondary legal summaries include cyber and information security, personnel, supply chain and physical/natural hazards. The obligation became operational through the Security of Critical Infrastructure (Critical Infrastructure Risk Management Program) Rules 2023 (LIN 23/006), which applies CIRMP duties to responsible entities across 13 prescribed asset classes (telecommunications assets are instead subject to a separate risk management framework). An annual CIRMP report, reviewed and approved at board level, is due to the Cyber and Infrastructure Security Centre (CISC) by 28 September each year, and the asset register itself must be updated within 30 days of a material change.

What are the mandatory cyber incident reporting timeframes?

Per secondary legal and industry summaries of the Act's cyber incident reporting provisions (sections in and around 30BC/30BD), responsible entities for in-scope asset classes must notify the Australian Signals Directorate (ASD) of a cyber security incident within one of two timeframes depending on severity: 12 hours for a 'critical' cyber security incident — one that has had, or is having, a significant impact on the availability of the asset's essential goods or services — and 72 hours for other reportable cyber security incidents with a lesser but still relevant impact. Mandatory reporting under this regime took effect 8 July 2022, applying across 21 defined asset classes spanning each of the 11 sectors except space technology and defence industry, which were carved out at that stage. legislation.gov.au is the authoritative source for the exact section numbers cited above, which are drawn from secondary legal summaries rather than the primary text.

What are the Enhanced Cyber Security Obligations (ECSO), and what is a System of National Significance?

Part 2C of the Act establishes Enhanced Cyber Security Obligations that apply to assets the Minister formally declares a 'Systems of National Significance' (SoNS) under the separate declaration power in Part 6A — these are the most critical of Australia's critical infrastructure assets, where the consequences of compromise would be especially severe nationally. Per secondary summaries, ECSO duties for declared SoNS include developing and maintaining incident response plans, undertaking cyber security exercises, and providing vulnerability assessments on CISC's request, plus additional system information reporting duties. The Act also grants the Commonwealth government assistance and intervention powers — including, in defined and exceptional circumstances, directing or directly assisting an entity's response to a serious cyber incident threatening national security or essential services — that go beyond the baseline obligations applying to all in-scope entities. The regime was further amended in 2024 by the Security of Critical Infrastructure and Other Legislation Amendment (Enhanced Response and Prevention) Act, which (per secondary summaries) extended data storage protections, among other changes.

Sources

  1. Federal Register of Legislation: Security of Critical Infrastructure Act 2018 (Cth), consolidated text
  2. Wikipedia: Security of Critical Infrastructure Act 2018 (history overview)
  3. Department of Home Affairs: Independent Review of the Security of Critical Infrastructure Act 2018 (final report, PDF)
  4. Cyber and Infrastructure Security Centre (CISC) — regulator for the SOCI Act (program site)
  5. Federal Register of Legislation: Security of Critical Infrastructure (Critical infrastructure risk management program) Rules (LIN 23/006) 2023, Compilation No. 2 (10 June 2026, includes the enhanced CIRMP requirements)
  6. CISC: SOCI Act regulatory obligations
  7. CISC: Enhanced Cyber Security Obligations and Systems of National Significance
  8. Federal Register of Legislation: Cyber Security Act 2024 (ransomware payment reporting, smart device standards)
  9. US Federal Register: Town Hall Meetings To Provide Input on CIRCIA Rulemaking (26 May 2026)
Was this guide helpful?

In this cluster

Australia's Security of Critical Infrastructure (SOCI) Act: cyber obligations, explained