Somewhere in most critical infrastructure businesses there is a document that gets attention once a year. The risk management program is written, it is reviewed, it goes to the board, a director approves the annual report, and it is submitted within ninety days of the end of the financial year. Then everyone goes back to work.
The Critical Infrastructure Security Centre has published an updated CIRMP Guidance, together with a shorter Snapshot. It runs to a bit over two hundred pages and it is not light reading.
Two things in it are worth the time of anyone who already has a program, because they change what that annual document has to be able to survive. Neither is a new rule. Both are the regulator being specific about how it reads the rules it already has.
A note on what follows. CISC keeps one current version of each document online and does not publish prior editions, so the comparison here is against the February 2023 guidance, which is the earliest published edition. Everything described as new is new relative to that. Some of it may have arrived in an intermediate update rather than this one.
The first change: what the annual report has to demonstrate
In February 2023 the guidance asked for a declaration. The report had to state whether the program “was or was not up to date” at the end of the financial year, and the purpose of the report was described as assuring the regulator that the program “remains up-to-date and appropriate”.
The current guidance states the test in a box of its own. The annual report must “include sufficient information to demonstrate that the CIRMP is current and effective”.
Appropriate describes a document. Effective describes an outcome.
That is a short sentence doing a lot of work. “Up to date and appropriate” are both properties of a document. You can satisfy both by having written something sensible and reviewed it recently. “Current and effective” is a different kind of claim, because effectiveness is not a property of the document at all. It is a property of what the document caused to happen in the business.
The guidance goes on to recommend that entities include an assessment of “whether the CIRMP has been effective in mitigating risks and managing impacts, taking into account lessons learned, incident outcomes, and any identified gaps or areas for improvement”. It also notes that while the report does not require the program itself to be submitted, “the relevant regulator may request access to the CIRMP for compliance, assurance, or audit purposes”.
One thing to be accurate about, because it is easy to overstate. Where a hazard had a significant relevant impact during the year, the requirement to evaluate the program’s effectiveness against that hazard was already there in 2023. That part is not new. What is new is that effectiveness is now the frame for the whole report, not only for the incidents in it.
The second change: you now have to show your working on what you didn’t do
This is the one most people will miss, and it is the more demanding of the two.
The CIRMP obligation is qualified by the phrase “so far as it is reasonably practicable”. In February 2023 the guidance treated that as latitude. It said the standard “allows entities to determine how they address material risks”, and that mitigations should be commensurate with factors such as the size of the business, its maturity and its income. Sensible, and almost impossible to fail.
The current guidance has a section on documenting those decisions that has no equivalent in the earlier edition. It sets out four parts.
Identify the hazard or risk, with the potential consequence and an assessment of likelihood, and where there are multiple assets, which ones are affected and why.
Outline the potential controls or mitigations, across a range of reasonably available options, and how each one would reduce the impact.
Assess what is reasonably practicable, recording the analysis conducted. The guidance lists what that analysis may consider: “severity of impact; likelihood; effectiveness; and the cost or burden of implementation and why particular measures were not adopted”.
Record the decision, including which controls will be implemented, the implementation timeframes, “the reasons for not adopting other measures”, and the review triggers that would cause the decision to be revisited.
An audit trail for the things you decided not to fund.
Read those four together and the shape is familiar to anyone who has worked in a regulated industry. It is not a request for more controls. It is a request for the reasoning behind the controls you chose, and, more pointedly, the reasoning behind the ones you declined.
The guidance is direct about the standard being applied: an entity “should be able to demonstrate that all reasonable steps to protect the asset were taken unless further measures would be clearly excessive in relation to the risk”.
That is a much harder document to produce after an incident than before one. The analysis of cost against severity, the options considered and rejected, the timeframes, the review triggers: all of it is straightforward to write down at the time and close to impossible to reconstruct credibly twelve months later with a regulator in the room.
The two changes are really one change
Put them side by side. The report has to demonstrate effectiveness rather than currency. The decisions underneath it have to show what was considered and what was declined.
Both are asking for the same thing from a different direction, and it is not a bigger program. It is evidence that the program is a live thing rather than a document. Effectiveness cannot be asserted in a sentence, and a decision not to act cannot be defended from memory.
Which puts a sharper point on something the guidance says about the annual reporting process itself. It describes that process as an opportunity for boards and governing bodies to “review the effectiveness of the CIRMP, identify areas for improvement, and ensure that appropriate resources are allocated to manage risks”. Resourcing appears in the regulator’s description of what the board is doing when it approves that report. Late submission attracts a civil penalty of 150 penalty units, but that is the least interesting consequence on offer.
Where this gets uncomfortable, and it isn’t the cyber chapter
The guidance covers hazards across cyber and information security, credential compromise, lateral movement, personnel, supply chain, and physical security and natural hazards.
In most of the operators we talk to, the cyber chapters are the ones that can be evidenced. There is tooling, there are owners, there is a budget line, and there is somebody who can produce a report.
Personnel and supply chain are quieter. Not because anyone is ignoring them, but because they ask a different kind of question. Who holds access, whether the role was ever genuinely assessed for it, and what has changed since. Who is actually behind a major supplier, what sits behind them in turn, and what happens to your asset when they have a bad week. The guidance also treats interdependency as a factor in whether a risk is material at all, noting that where a risk could extend through other critical infrastructure sectors and amplify in severity, “it is more likely to be a material risk”.
Those are not security problems in the ordinary sense. They are closer to intelligence work, and most security teams were not built to do them. They are also, now, two of the areas where the annual report has to demonstrate effectiveness.
Where BayRisk lands on this
So here is the position, stated plainly.
Nothing above calls for a bigger program. It calls for a program that is being run rather than maintained, and that is a different activity with a different cost.
A program that is maintained gets attention before a review. A program that is being run produces evidence as a by-product of normal weeks: controls recorded as working because somebody checked, suppliers assessed on evidence rather than on their own account of themselves, access reviewed against roles rather than against a list, and the decisions about what not to do written down at the moment they are taken, with the reasoning intact.
That last one is the cheapest thing on the list and the one most often skipped, because at the time it feels like paperwork and only later turns out to have been the evidence.
A program that is maintained gets attention before a review. A program that is being run produces evidence as a by-product of normal weeks.
What we do is run that as a continuous operation on an organisation’s behalf. The senior judgement, the evidence kept current between assessments rather than assembled before them, the supplier and personnel work that sits outside what most internal teams were resourced for, and a position that can be put in front of a board, a regulator or an insurer on any given day rather than in the fortnight before one asks.
The risk itself does not move. It belongs to the board and the executive, by law and by governance, and it cannot be handed to anyone, including us. The annual report is still signed by a director. What changes is whether the person signing it is being handed a position or a document.
If you want to work through what “current and effective” would mean against your own program, that is a short conversation: hello@bayrisk.com.au.
References
- Critical Infrastructure Security Centre, Critical Infrastructure Risk Management Program Guidance, Commonwealth of Australia, 2026. The annual report test, the documentation of decisions about what is “so far as it is reasonably practicable”, the hazard chapters, the materiality treatment of interdependencies and the board approval provisions are all drawn from this edition. cisc.gov.au
- Critical Infrastructure Security Centre, Critical Infrastructure Risk Management Program Guidance Snapshot, Commonwealth of Australia, 2026. cisc.gov.au
- Department of Home Affairs, Guidance for the Critical Infrastructure Risk Management Program, February 2023, for the “up-to-date and appropriate” formulation and the earlier treatment of “as far as is reasonably practicable”.
- Security of Critical Infrastructure Act 2018 (Cth), section 30AG, for the annual report obligation, the approved form, board approval and the civil penalty.