Cybernion
← Insights

Critical Infrastructure

Are You a Responsible Entity Under SOCI? Working Out if CIRMP Applies

3 July 2026 · Updated 5 Sept 2026

An organisation is a responsible entity under the SOCI Act if it owns or operates a critical infrastructure asset in one of the 11 covered sectors and meets the definition for that asset class in section 12L. Being in a covered sector is not enough. The asset has to meet the definition, and the CIRMP obligation only applies to specific asset classes.

Working out whether the SOCI Act reaches an asset is a three step question, and each step can rule an organisation out: the sector, the asset class, and whether the organisation is the responsible entity.

How do we know if we are a responsible entity under the SOCI Act?

An organisation is a responsible entity under the Security of Critical Infrastructure Act 2018 (SOCI Act) if it owns or operates a critical infrastructure asset in one of the 11 covered sectors and meets the definition for that asset class in section 12L of the Act. Three things all have to be true. The sector is one of the 11 the Act covers, the asset meets the specific definition of a critical infrastructure asset for its class, and the organisation is the entity the Act names as responsible for that asset. Miss any one and the obligations do not apply. The order matters, because each test is narrower than the last. The sector list is broad, the asset class definitions add thresholds, and the responsible entity definition then points at one specific party. For the full framework these tests fall under, see what the SOCI Act is.

Which sectors and asset classes does the SOCI Act cover?

The SOCI Act covers 11 sectors, and within them the Act defines specific asset classes. Being in a listed sector is the entry test, not the answer, because obligations attach to asset classes and not to whole sectors. The 11 sectors are 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. The table below shows the sectors and the kinds of asset class defined within each. Whether a particular asset falls inside a class depends on the definition in the Act, which usually carries thresholds such as capacity, scale or customer numbers.

Sector Asset classes defined within it
Communications Broadcasting, domain name systems, telecommunications
Financial services and markets Banking, insurance, superannuation, financial market infrastructure
Data storage or processing Data storage or processing
Energy Electricity, energy market operator, gas, liquid fuels
Food and grocery Food and grocery
Healthcare and medical Critical and designated hospitals
Transport Aviation, freight infrastructure, freight services, public transport, ports
Water and sewerage Water

Defence industry, higher education and research, and space technology are covered sectors too, each with defined assets. If an industry is not on the list of 11, the SOCI Act does not apply.

Does the CIRMP obligation apply to our asset class?

The Critical Infrastructure Risk Management Program (CIRMP) obligation applies only to specific asset classes, so an asset can be caught by the SOCI Act without being subject to the CIRMP. The CISC publishes which classes the obligation is switched on for. The table below is drawn from that guidance and shows where the CIRMP obligation applies.

Asset class CIRMP obligation
Broadcasting, domain name systems Yes
Telecommunications Separate program under the TSRMP Rules
Data storage or processing Yes
Electricity, energy market operator, gas, liquid fuels Yes
Financial market infrastructure (payment systems only) Yes
Banking, insurance, superannuation No
Food and grocery Yes
Designated hospitals Yes
Defence industry, education, space technology No
Aviation, ports, public transport No
Freight infrastructure, freight services Yes
Water Yes

So an insurer, a bank, an airport operator or a university can be a responsible entity under the SOCI Act for other obligations, yet fall outside the CIRMP. Confirm the specific class before building a program. The CIRMP obligation guide covers what the program requires once it applies, and CIRMP approved frameworks lists the cyber security frameworks the Rules accept.

Who is the responsible entity when ownership or operations are split?

The responsible entity is the party named for each asset class in section 12L of the SOCI Act, chosen to identify who has operational control, which is not always the owner. In the engagements we have worked, this is where responsible entity status is most often misread. A critical asset may be owned by one company, operated by another under contract, and branded by a third. The Act cuts through that by defining, class by class, which of them carries the obligation. For a critical data storage or processing asset the definition points at the entity providing the service under contract, for a critical electricity asset it points at the operator of the network or system, and each class has its own test. Where operations are outsourced or the corporate structure is layered, work through the definition for the specific class rather than assuming the brand name or the legal owner is the responsible entity. Getting this wrong means either building a program that was not owed, or missing one that was.

What do we do once we confirm SOCI applies to our asset?

Once an organisation confirms it is a responsible entity, the next step is to identify which obligations attach to the asset class and act on each. The three positive security obligations are to provide operational and ownership information to the Register of Critical Infrastructure Assets, report cyber security incidents affecting essential services to the Australian Cyber Security Centre within 12 hours for a critical incident or 72 hours for other significant incidents, and, if the class is switched on for it, adopt and maintain a CIRMP. There is also a standing obligation to notify data service providers. Where an asset is subject to the CIRMP, that pulls in the four hazard categories, the cyber framework requirement and the board approved annual report due within 90 days of the financial year end. A small number of assets are declared Systems of National Significance and attract further Enhanced Cyber Security Obligations, but only when the Secretary formally requires them. Map the obligations to the asset class first, then build to those, not to the Act as a whole. Where an asset class involves handling sensitive government data, an IRAP assessment may apply alongside the CIRMP obligations.

Frequently asked questions

How do we know if we are a responsible entity under the SOCI Act? An organisation is a responsible entity if it owns or operates a critical infrastructure asset in one of the 11 SOCI sectors, and it meets the definition in section 12L of the Act for that asset class. The definition varies by class to point at the entity with operational control. Being in a covered sector is not enough. The asset has to meet the definition of a critical infrastructure asset.

Does the SOCI Act apply to every business in a critical infrastructure sector? No. The SOCI Act applies to responsible entities for defined critical infrastructure assets, not to every business in a covered sector. Asset class definitions usually include thresholds, such as capacity or number of customers, so smaller operators may fall outside the definition. If an asset does not meet the definition in the Act, the obligations do not apply.

Does CIRMP apply to our asset if SOCI does? Not necessarily. The CIRMP obligation is switched on for specific asset classes, not for every asset under the SOCI Act. Classes such as defence industry, banking, insurance, superannuation, aviation, ports and public transport are covered by SOCI but are not subject to the CIRMP obligation. Check whether the specific asset class is one the CIRMP Rules turn on.

Who is the responsible entity when a critical asset is outsourced? The responsible entity is defined per asset class in section 12L to identify the entity with operational control, which is not always the owner. Where operations are outsourced, work through the definition for the class rather than assuming the brand or the owner carries the obligation. Complex ownership and outsourcing are exactly where responsible entity status is most often misread.

What do we do once we confirm SOCI applies to our asset? Confirm which obligations attach to the asset class. Register operational and ownership information if required, meet the cyber incident reporting duty, and if the class is subject to the CIRMP obligation, adopt and maintain a Critical Infrastructure Risk Management Program with a board approved annual report to the regulator within 90 days of the financial year end.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. Guidance for the Critical Infrastructure Risk Management Program, Cyber and Infrastructure Security Centre, March 2025
  2. Security of Critical Infrastructure Act 2018 (SOCI), Cyber and Infrastructure Security Centre, accessed 3 July 2026
  3. Security of Critical Infrastructure Act 2018 (compilation), Federal Register of Legislation, accessed 3 July 2026
  4. SOCI Act regulatory obligations, Cyber and Infrastructure Security Centre, accessed 3 July 2026

Last updated: 5 September, 2026

Talk to us about your engagement

A scoped proposal within one business day.