03:10, Sunday, at a site we have made up for this post. The night operator phones the on-call engineer: two HMIs are showing a ransom note. At 03:55 the engineer confirms the historian server is encrypted. At 04:20 the operations manager decides this is a reportable incident. Three timestamps, and depending on which rules cover the site, each one may have just started a different regulator's clock.
Most OT incident response plans cover this moment with one sentence: "Notify regulators and other stakeholders as required." Required by whom, counted from which of those three times, and sent by which person at 04:21 are left for the worst hour of the year. This post is for whoever is writing or rewriting the incident response plan for an industrial site in the US, the EU, Canada or Australia. If someone at your company already owns notifications and keeps a dated table of them, skip to the three objections.
The tightest clock in this post sits in NERC CIP-008-6, Requirement R4, Part 4.2, which sets initial notification at:
"One hour after the determination of a Reportable Cyber Security Incident."
The hour starts at a determination made under the entity's own documented process, not at detection. Other rules count from "identification", from "becoming aware", or from a decision about materiality. Different words, different moments, so one incident can carry several deadlines that began at different times.
The notification matrix, one row at a time
The fix is a table in the plan, the notification matrix, with one row per recipient per reporting stage. A regulator that wants an early warning, a notification and a final report gets three rows, because each stage has its own deadline, template and possibly sender. Here is the whole row.
Can you say, right now, which of the three timestamps in the opening starts the clock that binds your site? If you can, column four is a ten-minute job. If you cannot, the table below is where to start.
The clocks, seeded and dated
These are the reporting clocks our course research verified against the primary sources in mid-October 2026, with the word that starts each one. Where that word was not part of the verified research, the cell says to check it rather than guess.
| Rule | Clock starts at | Stages and deadlines | Status as checked mid-October 2026 |
|---|---|---|---|
| NERC CIP-008-6 R4 (bulk electric system) | Determination | Reportable incident: 1 hour. Attempt to compromise: end of the next calendar day. Updates within 7 calendar days of new information | Enforceable. CIP-008-7.1 becomes effective 1 July 2028 |
| TSA Security Directive Pipeline-2021-01G | Identification | 72 hours to CISA; supplemental information within 24 hours of learning it | Expires 15 January 2027. Older 12-hour and 24-hour figures are out of date |
| US Coast Guard, 33 CFR 101 subpart F | Check the current requirement | Without delay, to the National Response Center | In force since 16 July 2025 |
| SEC Form 8-K Item 1.05 (listed companies) | Materiality determination | Generally within 4 business days | In force; rescission has been petitioned |
| CIRCIA | Statute: reasonable belief that a covered incident occurred | Statute: 72 hours; 24 hours after a ransom payment | Not in force. Final rule not published; at White House review since 1 October 2026. Placeholder row |
| EU NIS2 Directive, Art. 23 | Becoming aware | Early warning 24 hours; notification 72 hours; final report within one month | Recipient, portal and thresholds are national; transposition is incomplete in some states |
| EU CER Directive, Art. 15 (designated critical entities) | Check the current requirement | Initial notification 24 hours; detailed report within one month | Goes to the CER competent authority, often a different body from the NIS2 recipient |
| GDPR, Art. 33 | Check the current requirement | 72 hours to the data protection authority | Only when personal data is breached |
| Australia, SOCI Act Part 2B | Becoming aware | Critical incident (significant impact on availability): 12 hours, written within 84 hours if first reported orally. Other incident (relevant impact): 72 hours, written within 48 hours if oral | In force; reports to ASD's ACSC |
| Australia, Cyber Security Act 2024, ransomware payments | The payment, or becoming aware it was made | 72 hours | Turnover above AUD 3 million, or any SOCI Part 2B entity |
| Canada, Critical Cyber Systems Protection Act | Set by regulation | When in force: a period set by regulation, not exceeding 72 hours | Part 2 not in force. Royal Assent 15 June 2026; no designated operators. Placeholder row |
| Ontario distributors and transmitters | Confirmation | End of the next business day, to the IESO | Since 22 September 2025. Other provinces differ |
"We are a manufacturer, not a utility. None of this applies to us."
"Half that table is pipelines and power grids. We make packaging. Why would I spend a week on a matrix of rules that will never touch us?"
Check before you rule yourself out. The NIS2 Directive's Annex II, according to our verified research, covers the manufacture, production and distribution of chemicals, food production, and several manufacturing sectors, from machinery to electrical equipment. A packaging plant inside an EU group may sit closer to that line than it looks from the shop floor. And if your parent company is listed in the US, the Item 1.05 row exists whether or not your plant is critical infrastructure.
And regulators are not the only rows. The rows plans forget are the ones a contract creates: the insurer's notice condition, which may require notice before you engage an outside response firm; customers whose own lines stop when yours do; the equipment maker, when a product flaw is suspected; mutual-aid partners; your own staff; and the public, through whoever approves the holding statement. A site with no regulatory rows still has five or six of these. Each needs the same ten columns.
"I am an engineer. I cannot interpret statutes at three in the morning."
"I know what a historian is. I do not know what a 'significant impact on availability' is in law, and I am not going to find out with a ransom note on the screen."
Nobody should be interpreting statutes in the small hours, which is the point of column three. The interpretation happens once, in daylight, with counsel in the room, and is written down as a trigger the night shift recognises. "Significant impact on availability" becomes "the plant cannot deliver at contracted rates for more than an hour" or "any unplanned loss of a processing line", whatever counsel and operations agree it means for your asset. The shift lead's job at 03:55 is to match what they see to a sentence they already know, then call the role named in column seven.
A useful test: read each trigger to a shift supervisor and ask whether they would know, from that sentence alone, that the row has fired. If they ask "what does that mean here?", the sentence is still written in the regulator's language. Rewrite it in theirs.
"These rules change every few months. Whatever I write will be wrong by spring."
"CIRCIA has been coming for years. Canada passed a law that is not in force. TSA reissues its directive every year. I will finish the matrix and it will already be out of date."
Some of it will be, and the matrix is built for that. Column two carries a status date on every row, and column ten carries a flag: in force, pending, not in force. CIRCIA goes in today as a pending row, with the statute's 72 hours noted and the words "final rule not published" beside it. Canada's new Act goes in as a placeholder, ready to fill when the regulations name a period. The TSA row carries its expiry date, which is also its re-check date.
Then put the re-checks on a calendar owned by a role, not a person: on each row's expiry date, and at least once a year for the rest.
Back to 04:20
Run the opening again with the matrix in place. The 03:10 call is logged as the first awareness time. The 04:20 decision is logged as the determination, with a name. The rows that fire are already written, each with the word that started its clock; the shortest deadline among them is everyone's deadline; and column seven says who drafts, approves and sends.
Nobody needed to know the law at 04:20. They needed to know which row they were on.
Sources: NERC CIP-008-6 | NERC Standards and Compliance Bulletin, July 2026 | TSA SD Pipeline-2021-01G | 33 CFR 101 subpart F | SEC, Cybersecurity Disclosure fact sheet | CISA, CIRCIA | Directive (EU) 2022/2555 (NIS2) | Directive (EU) 2022/2557 (CER) | Regulation (EU) 2016/679 (GDPR) | Security of Critical Infrastructure Act 2018 | ASD, help during a cyber security incident | Home Affairs, ransomware payment reporting fact sheet | S.C. 2026, c. 9 | IESO, cyber security reporting requirements


