Cybernion
← Insights

Critical Infrastructure

CIRMP Explained: Risk Management Program, Board Attestation and the Annual Report

3 July 2026 · Updated 3 July 2026

A Critical Infrastructure Risk Management Program (CIRMP) is the written program a responsible entity must run under Part 2A of the SOCI Act. It identifies the material risks of hazards to a critical infrastructure asset across four categories, sets out how each is managed, and is backed by a board approved annual report to the regulator within 90 days of the financial year end.

The CIRMP obligation is where the SOCI Act stops being a register question and becomes an operating one, running across what the program must contain, the four hazards, the board attestation and the annual report timing.

What is the CIRMP obligation under the SOCI Act?

The Critical Infrastructure Risk Management Program (CIRMP) obligation requires specified responsible entities to adopt, maintain and comply with a written risk management program for their critical infrastructure asset. It is set out in Part 2A of the Security of Critical Infrastructure Act 2018 (SOCI Act), with the detail set by the Security of Critical Infrastructure (Critical infrastructure risk management program) Rules (LIN 23/006) 2023, made on 31 January 2023 and registered on 16 February 2023. A CIRMP is a program that identifies the material risks of hazards that could have a relevant impact on the asset, then, as far as is reasonably practicable, minimises those risks and mitigates their impact. It applies only to named asset classes, not to every entity under the SOCI Act. Where an asset class is in scope, that can be confirmed in working out if SOCI and CIRMP apply to your asset. The program does not replace existing risk practices. The regulator expects it to be folded into what an entity already runs.

What are the four hazard categories in a CIRMP?

The CIRMP Rules define four hazard vectors, and a compliant program has to address all of them. Cyber and information security hazards, personnel hazards, supply chain hazards, and physical security and natural hazards. For each, the entity must identify where there is a material risk the hazard could have a relevant impact on the asset, minimise or eliminate that risk as far as is reasonably practicable, and mitigate the impact if the hazard occurs.

Hazard category What it covers
Cyber and information security Improper access to or misuse of information and computer systems, and unauthorised control that impairs the asset’s function
Personnel Critical workers acting through malice or negligence to compromise the asset, including off boarding risk
Supply chain Exploitation or disruption of the supply chain, misuse of privileged supplier access, and over reliance on major suppliers
Physical security and natural Unauthorised physical access to critical components, plus fire, flood, storm, earthquake, space weather and pandemic

The cyber hazard is the one with a hard technical bar attached, because the Rules require compliance with a named cyber security framework. We cover those in the frameworks that satisfy the CIRMP cyber rule.

What must a CIRMP contain under the CIRMP Rules?

A CIRMP must set out how the entity identifies and manages material risk across the four hazards, plus a set of general requirements the Rules spell out. It has to describe the operational context of the asset, identify the material risks, and show the process for minimising risk and mitigating impact. It must describe interdependencies between the asset and other critical infrastructure assets, up and down the chain and across sectors. It names the positions responsible for developing, implementing, reviewing and updating the program, with their contact details. It records a risk management methodology and the circumstances that trigger a review. The Rules define material risk to include a stoppage of the asset’s function, manipulation of a critical component, interference with operational technology, storage of sensitive operational information offshore, and remote access to control systems. There is no prescribed format. The regulator wants substance, not a template.

Does the CIRMP annual report need board approval?

Yes. The CIRMP annual report must be approved by the responsible entity’s board, council or other governing body before it is submitted. This is the point where accountability lands with the top of the organisation, not the security team. Section 30AG of the SOCI Act requires the report to be in the approved form and to contain a declaration that the CIRMP was up to date at the end of the Australian financial year, details of any incidents that had a significant or relevant impact on the asset during the year, any variations made to the program, a statement of whether the program was effective in mitigating the relevant impacts of hazards, and an attestation that the report was approved by the board or governing body. The board attestation is not a formality. It puts directors on record that they have oversight of how the asset’s security risks are being managed.

When is the CIRMP annual report due and who receives it?

The CIRMP annual report is due within 90 days of the end of the Australian financial year. For the year ending 30 June, that puts the deadline at 28 September. The report goes to the relevant Commonwealth regulator, which is the Cyber and Infrastructure Security Centre (CISC) for all assets except payment systems, where the Reserve Bank of Australia receives it. The SOCI Act does not allow exemptions or extensions, and the regulator follows up entities that report late. The CIRMP itself is not submitted with the report. The report attests to the program’s state, and the regulator may review the underlying CIRMP through a compliance audit. Entities can attach an independent third party audit report, though there is no requirement to. Missing the window is a compliance event in its own right, so the annual cycle has to be planned, not improvised in September.

How is a CIRMP maintained once it is in place?

Maintaining a CIRMP means complying with it, reviewing it and keeping it current, not filing it and moving on. Section 30AD of the SOCI Act requires the entity to actually comply with the program, including any mitigations and steps it committed to, such as background checks before onboarding critical workers. The Rules require a process to review the CIRMP, and at a minimum it must be reviewed once every 12 months to confirm it is still current. Triggers for an earlier review include changes in the operating environment, emerging threats, a hazard that materialises, a new critical infrastructure asset, or a change to an existing one. Under the 2024 amendments the regulator can direct an entity to remedy a CIRMP found to be seriously deficient, defined as one that poses a material risk to Australia’s national security, defence or socioeconomic stability. That power is a last resort, used after engagement, but it exists. Organisations that also handle Australian Government data may need to address ISM obligations through an IRAP assessment alongside the CIRMP.

Frequently asked questions

What is a CIRMP under the SOCI Act? A Critical Infrastructure Risk Management Program (CIRMP) is a written program a responsible entity must adopt and maintain under Part 2A of the SOCI Act. It identifies the material risks of hazards that could have a relevant impact on a critical infrastructure asset and sets out how the entity minimises those risks and mitigates their impact across four hazard categories.

What are the four CIRMP hazard categories? The CIRMP Rules define four hazard vectors. Cyber and information security hazards, personnel hazards, supply chain hazards, and physical security and natural hazards. A responsible entity must identify each hazard where there is a material risk it could have a relevant impact on the asset, then minimise the risk and mitigate the impact as far as is reasonably practicable.

Does the CIRMP annual report need board approval? Yes. The CIRMP annual report must be approved by the board, council or other governing body of the responsible entity. The report includes an attestation that its contents were approved by the governing body, along with a declaration that the program was up to date at the end of the financial year.

When is the CIRMP annual report due? The CIRMP annual report is due within 90 days of the end of the Australian financial year. For the financial year ending 30 June, that means the report must reach the relevant Commonwealth regulator by 28 September. The regulator is the CISC for most assets and the Reserve Bank of Australia for payment systems.

Do responsible entities submit the CIRMP with the annual report? No. The CIRMP itself is not submitted with the annual report. The report attests to the state of the program. The regulator may still review the CIRMP as part of a compliance audit, and can direct the entity to remedy it if it is found seriously deficient, so the underlying program has to hold up to scrutiny.


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 (Critical infrastructure risk management program) Rules (LIN 23/006) 2023, Federal Register of Legislation, 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: 3 July, 2026

Talk to us about your engagement

A scoped proposal within one business day.