November 14, 2026

OT Incident Response Plan: What It Must Contain

OT Incident Response Plan: What It Must Contain

Setting the Foundation for OT Cybersecurity Part 9: Incident Response and Recovery for OT

On the night of November 1, refrigerated cases in supermarkets across Belgium, Sweden and Ireland started to warm up. Dozens of Delhaize stores in Belgium were affected. In Ireland, 13 SuperValu stores pulled chilled and frozen stock as a precaution. Three weeks earlier, the same pattern had hit hundreds of stores in France.

The attackers changed settings on internet-exposed refrigeration controllers. Nothing about the method was new, and the first fix is still prevention: those controllers should never have been reachable from the internet. This post is about the night that fix was missed. What decides whether that night becomes a costly week is how fast you notice, decide and restore.

One response that worked

France's blood service, the Établissement français du sang (EFS), said attackers reached cold rooms at three of its sites through its refrigeration contractor and set temperature and defrost thresholds far out of range. Monitoring and alarms caught the change quickly. Staff moved products to other facilities, collection and distribution continued, and EFS reported that no blood products were altered.

That outcome was decided before the attack: alarms that someone watched, authority to move stock without waiting for a meeting, and other sites ready to receive it. That is what an OT incident response plan is for.

On November 5, CISA, the FBI, HHS, USDA and the US Department of Transportation published a joint fact sheet on hardening industrial refrigeration and cold chain monitoring systems. Most of its actions are preventive. Two are about response: keep tested backups offsite and offline, and set limits on setpoints with alerts when they are exceeded.

Why your IT plan does not cover this

Your corporate incident response plan probably assumes the right move is to isolate, wipe and rebuild. In OT the first questions are different. Is the process still safe? Can you run it without the control system, and for how long?

NIST SP 800-82 Rev. 3 says OT responses "can range from doing nothing to performing a full system shutdown", including a move to manual operations. The right choice depends on the process, and the people who understand the process work in operations and engineering. NIST's draft Rev. 4, open for comment until November 30, extends the guidance to building automation and to food and agriculture.

Colonial Pipeline's CEO told the US Senate in 2021 that the company shut down its pipeline after ransomware hit its IT systems because even a one percent chance that OT was compromised justified it. Investigators found no evidence the attackers reached OT. You can debate that call. The point is that it was made under pressure, without a decision agreed in advance.

What the plan needs to contain

  • Decision rights. Name who can order a shutdown, a switch to manual, or a disconnect of vendor remote access, on every shift. A committee cannot answer an alarm at 3 a.m.
  • Safe states and manual modes. For each critical system, write down what safe looks like and how to get there by hand: chillers to local control, air handlers to hand mode, doors to a defined fail state. If nobody on the night shift has run the plant in hand, you do not have a manual mode yet. Consequence reduction covers how to plan for this.
  • Signs an operator will recognize. Setpoints that change without a work order, schedules nobody wrote, alarms that were disabled. Operators see these before any security tool does.
  • Vendor contacts and access. Your service provider may be the way in, as it was at EFS. Know whom to call, and how to cut their remote access without losing their support.
  • Offline copies. Keep the plan, controller configurations, programs and setpoint lists where ransomware on your network cannot reach them. NIST recommends paper or an offline system for the plan itself.
  • Reporting duties. Under NIS2, essential and important entities in the EU send an early warning within 24 hours of becoming aware of a significant incident and a notification within 72 hours. Canada's Bill C-8 received Royal Assent in June 2026; once its critical cyber systems part is in force, designated operators will report within a period that cannot exceed 72 hours. Saudi Arabia's OTCC requires OT recovery procedures, including for safety instrumented systems, to be part of incident response.

Recovery is where the time goes

Restoring a controller is slow. You need the right firmware version, the last good configuration, a licensed copy of the engineering software and someone who knows the system. CERT-FR told the French operators that a factory reset alone was not enough: each unit had to be reconfigured before it went back into service. If your last configuration backup dates from commissioning, you will be rebuilding from memory.

Test the restore, not only the backup. This quarter, restore one controller's configuration to a spare or bench unit and time it. Then run a one-hour tabletop with the night shift and your main BAS or refrigeration contractor, using the supermarket attacks as the scenario. The Canadian Centre for Cyber Security recommends regular tabletop exercises for exactly this reason. A ready-made scenario is in What If? Part 1.

Track two numbers: the time to put a critical system into manual operation, and the time to restore one controller to its last good configuration. They describe your exposure better than any count of alerts.

An attacker decides when your incident starts. Your preparation decides how long it lasts.

Next in this series: vulnerability management when you cannot patch.

Frequently asked questions

What should an OT incident response plan contain?

Decision rights on every shift, safe states and manual modes, signs operators recognize, vendor contacts and access, offline copies and reporting duties.

Why is an OT plan different from an IT plan?

In OT the first questions are whether the process is still safe and whether you can run it without the control system, not whether to isolate, wipe and rebuild.

What should I measure?

The time to put a critical system into manual operation, and the time to restore one controller to its last good configuration.

Other articles in this series

Related reading

Planning a new smart building or plant, upgrading the systems in an existing one, or buying technology for a facility? Actimeta is an OT cybersecurity and technology advisory firm that helps owners get the design, the vendors and the security right from the start.

Book a free consultation

References

  1. Al Jazeera, Suspected cyberattacks trigger supermarket fridge failures across Europe (November 2, 2026): https://aljazeera.com/news/2026/11/2/freezers-in-sweden-belgium-overheat-following-possible-cyberattacks
  2. Agriland, SuperValu withdraws chilled and frozen food in 13 stores after cyber attack (November 2026): https://www.agriland.ie/farming-news/supervalu-withdraws-chilled-and-frozen-food-in-13-stores-after-cyber-attack/
  3. Help Net Security, Cyberattack hits French blood banks (November 4, 2026): https://www.helpnetsecurity.com/?p=390313
  4. CISA, FBI, HHS, USDA and DOT, US Government Partners Urge Hardening Industrial Refrigeration and Cold Chain Monitoring Systems (November 5, 2026): https://www.ic3.gov/CSA/2026/261105.pdf
  5. CERT-FR, CERTFR-2026-ALE-012 (October 12, 2026): https://cert.cyber.gouv.fr/alerte/CERTFR-2026-ALE-012
  6. NIST SP 800-82 Rev. 3, Guide to Operational Technology Security (September 2023): https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-82r3.pdf
  7. NIST SP 800-82 Rev. 4, initial public draft (September 2026): https://csrc.nist.gov/pubs/sp/800/82/r4/ipd
  8. US Senate Committee on Homeland Security and Governmental Affairs, Threats to Critical Infrastructure: Examining the Colonial Pipeline Cyber Attack (June 8, 2021): https://www.govinfo.gov/content/pkg/CHRG-117shrg46569/html/CHRG-117shrg46569.htm
  9. Directive (EU) 2022/2555 (NIS2), Article 23: https://eur-lex.europa.eu/eli/dir/2022/2555/oj/eng
  10. Public Safety Canada, Royal Assent of Bill C-8 (June 2026): https://www.canada.ca/en/public-safety-canada/news/2026/06/government-of-canada-strengthens-cyber-security-and-critical-infrastructure-with-royal-assent-of-bill-c8.html
  11. National Cybersecurity Authority (Saudi Arabia), OTCC-1:2022: https://cdn.nca.gov.sa/ar/otcc_en.pdf
  12. Canadian Centre for Cyber Security, AL25-016 Internet-accessible industrial control systems abused by hacktivists (October 29, 2025): https://cyber.gc.ca/en/alerts-advisories/al25-016-internet-accessible-industrial-control-systems-ics-abused-hacktivists

‍

Author:
Editorial Team