


Team Shieldworkz
Most OT tabletop exercises fail the same way. The scenario is a generic ransomware infection, the room is mostly IT staff, and everyone leaves agreeing the plan "mostly works." Nobody is asked what happens when the alarm email never arrives, or who has the authority to cut a vendor's remote session at 2 a.m.
Since mid-October, real incidents have given us better material than any facilitator could invent. Attackers took over refrigeration controllers across Europe by walking in through the front door. A cloud email outage silenced a chlorine alarm and put guests at a German hotel in hospital. A hijacked remote support tool reached hundreds of customer endpoints in roughly ninety minutes. None of it needed a zero-day or malware written for PLCs.
This guide turns those events, plus two patterns from this year's industrial incident data, into five OT tabletop exercise scenarios you can run with your own team. Each one gives you the real-world trigger, a timed set of injects, the decisions the room has to make, and what a good response looks like. It is written for CISOs, OT security leads, plant and operations managers, and the safety and legal people who end up in the room when it counts.
Key takeaways
The damage came through normal functions. The three freshest incidents used setpoints, email alerts and remote sessions, not exotic exploits.
Most ransomware shutdowns are decisions, not attacks on controllers. In second-quarter industrial ransomware data, no ransomware case reached control-system manipulation. Shutdowns followed IT encryption or a precautionary stop, so your IT-to-OT shutdown criteria need testing as much as your PLC defenses.
Test the whole chain. Exercise the alarm path, the authentication path and the recovery tools, not just the controller.
Cadence and attendance matter. Run at least two exercises a year, rotate scenarios, and include operations, safety, legal, communications and key vendors.
Why do OT tabletop exercises need a rewrite right now?
Because the incidents of the last few weeks show three shifts that generic scenarios do not cover: attackers target the management plane, non-malicious IT failures can hurt people, and trusted access has become the attack path.
1. The target is the management plane, not the process
In one analyzed attack on an internet-exposed Copeland XWEB Pro refrigeration controller, threat-intelligence analysts reported that the attackers needed no vulnerability, only the factory default login. Two administrator sessions read the settings of 31 devices and made 743 changes, including setpoints of 110°C and 150°C, plus commands to mute alarms and lock local keypads. There was no malware and no ransom demand. Industrial ransomware reporting tells the same story: internet-facing edge devices and remote access gateways remain the dominant way into industrial and industrial-adjacent networks.
2. A non-malicious IT failure can hurt people
Microsoft's global outage on 12 and 13 November was, by the company's account, not a cyberattack. It still contributed to a physical-safety failure at a German hotel pool (see Scenario 2). If your exercises only start when an adversary shows up, you are skipping the failure mode that just hospitalized people.
3. Trusted access became the attack path
The ScreenConnect campaign against managed service providers worked because the tool was supposed to be there. Much of the activity ran through a legitimate remote support product's own features, which is hard to flag as malicious.
Published scenario libraries mostly stay at the category level: ransomware, trusted vendor compromise, insider threat. That is a reasonable starting menu, but categories do not tell your team what breaks at 05:40 on a Saturday. The scenarios below are written at that level of detail.

How do you design an OT tabletop exercise that produces real findings?
Use a structured, discussion-based format where nothing gets disconnected and nobody touches a live system. That is the whole point: you can rehearse decisions that would be dangerous to rehearse on the plant floor. The format below works for all five scenarios.
Element | What to do | Why it matters |
Participants | Operations and engineering staff, OT security, IT security, safety, legal, communications, and one or two critical vendors or contractors | Decisions about isolating control systems or stopping a process need the people who understand the operational consequences |
Roles | Facilitator, inject controller, scribe, and an observer who is not part of the response team | The observer catches the assumptions the team cannot see in itself |
Injects | Hand over artifacts: an alarm email, a screenshot, a vendor's voicemail transcript, a regulator's question | Narrative descriptions let people answer in the abstract; artifacts force a concrete decision |
One decision per inject | Each inject ends with a question and a clock | Stops the discussion drifting into theory |
Safety first | Treat safe process state as the primary constraint, with manual workarounds and component availability in play from the start | OT response is limited by what the process can tolerate, not by what the security tool can do |
Convergence | Include scenarios where IT and OT both feel the impact | Most real incidents cross the boundary |
Cadence | Two exercises a year, using different scenarios | Gives time to fix findings and keeps the team from rehearsing one story |
The 90-minute blueprint
Minutes 0 to 10: Set the scene and ground rules.
Minutes 10 to 70: Work through four to six injects, one decision each.
Minutes 70 to 80: Hold a hot wash while memory is fresh.
Minutes 80 to 90: Assign owners to the findings.
Longer sessions tend to turn into slide reviews.
One more rule separates useful exercises from theater: write down the assumptions the team makes out loud. "Operations will just run manually" and "the vendor will be reachable" are the sentences that become your best findings.
Scenario 1: Exposed controllers hijacked overnight
Best for: food and cold-chain operators, pharma and healthcare logistics, and anyone with remotely managed building or refrigeration systems run by a contractor.
The real-world trigger
On the night of 11 October, refrigeration controllers at hundreds of French supermarkets were switched into defrost cycles with stock still inside. Store counts differ by source, from roughly 250 to 350 in some reporting to as many as 700 in others, so treat any single figure with care.
Overnight into 2 November a second wave hit stores in Belgium, Sweden, Estonia, Ireland, the Netherlands, Finland, Portugal, Italy and Luxembourg. The Hacker News reported that no chain lost more than several dozen stores. One Swedish store reported freezers set to 50°C, and a Belgian butcher lost about €15,000 of meat after fridges climbed to 18°C.
Danfoss told Dutch media that the systems hit there were not on a secure network and still used default passwords. It also said most units hit in France were older models it no longer updates.
In early November the French Blood Establishment confirmed that an incident at a refrigeration equipment provider had altered temperature and defrost settings at three blood product storage facilities.
On 5 November, CISA, the FBI, HHS, USDA and the Department of Transportation issued a joint fact sheet listing three access paths: authentication bypass, arbitrary code injection and weak configurations. It also flagged a quieter risk, loss of visibility: a site that relies on the controller to raise its own alarm may not learn about tampering until staff open the cases in the morning.
Separately, internet-scanning research found hijacked Copeland XWEB Pro units being used as spam relays and proxy exits, most likely through CVE-2026-25085, with low-to-medium confidence. A controller nobody monitors can be abused for weeks.
No one has been officially identified. Pro-Russian groups claimed the supermarket attacks on 4 November, but investigators have not confirmed that, and Belgium's federal prosecutor has opened a criminal investigation.
The exercise
Setup. You run a regional food distributor with 140 sites, or a pharmacy network, or a hospital group's central stores. A refrigeration contractor manages the controllers remotely. It is 05:40 on a Saturday.
Injects
T+0: Two site managers call to say cabinets feel warm. The central monitoring dashboard shows no alarms.
T+15: Your contractor reports 31 units with changed setpoints and muted alarms. The event log cannot tell you what temperatures the units actually reached.
T+30: A journalist asks whether you are part of "the same campaign as France." Separately, your insurance contract has conditions about the data feed to the contractor. Someone asks whether cutting it is allowed.
T+45: An inventory check shows roughly four in ten controllers are end-of-life models. The vendor stopped issuing fixes for them.
T+60: A pharmacy customer asks for temperature records for the last 12 hours. You do not have independent ones.
T+90: The contractor asks to restore remote access through a filtered IP allowlist "just for today."
Decision points for the room
Who has the authority to cut remote access to 140 sites, and how fast can they act?
Which stock is quarantined, which is sold, and who signs that off?
What is your independent evidence of temperature history?
How do you verify defrost schedules and setpoints across every site, not just the ones that called?
Do you reconnect the contractor, and on what terms?
What good looks like
An inventory of every internet-reachable controller, including ones a contractor installed.
Remote access only through a VPN or protected network with an allowlist, plus changed default credentials and updated firmware. CERT-FR's guidance for Danfoss devices also includes setting the security level to Strict.
Separate temperature loggers with their own alarm path, so tampering with the controller does not blind you.
A plan to retire end-of-life units. CERT-FR warned that such devices left online are very likely to be compromised again, and a factory reset alone will not fix that.
Pre-agreed stock disposition rules and a contractor agreement that spells out who holds credentials and how quickly access gets cut.
Scenario 2: The cloud goes dark and the alarm never arrives
Best for: water and wastewater, chemical and process plants, utilities, building-heavy operators, and anyone whose alarms, logins or runbooks sit inside a cloud suite.
The real-world trigger
On 12 November, Microsoft's Exchange Online and parts of Microsoft 365 failed worldwide. Al Jazeera reported users in 74 countries affected, and the disruption ran into a second day. Microsoft said there was no indication of a cyberattack. Its preliminary explanation points to a latent defect exposed by a network change, and recovery dragged because restarted servers were immediately swamped by queued traffic and failed again.
The outage also degraded Defender XDR connectivity, so some security teams lost their primary console at the same moment they lost email. Some government agencies fell back to the telephone, according to Shieldworkz's analysis.
On 13 November at the Ling Bao hotel inside the Phantasialand resort in Brühl, Germany, an automatic chlorine dosing system malfunctioned and over-dosed the pool. Per WDR reporting, the monitoring system generated an email warning, but the email never reached staff because of the Microsoft disruption. Fifteen guests were injured and several went to hospital. There is no evidence that Microsoft caused the dosing fault or that the control system was compromised. The Shieldworkz case study notes that public reporting does not establish whether independent local alarms existed.
A variant worth keeping in your back pocket: during the Google Cloud outage in London on 19 and 20 October, Google's statement blamed a voltage-sensing design flaw and a PLC misconfiguration that kept the generator plant from receiving a start signal. Capacity reported the impact spread across 38 products. Sometimes the cloud's own OT is the failure.
The exercise
Setup. A regional utility or chemical plant. Alarms go to on-call staff by email. Engineers reach jump hosts through cloud single sign-on. The SOC works from a cloud XDR console. The incident bridge runs on Teams and the call tree lives in Outlook contacts. Runbooks sit in SharePoint. It is 13:00 on a Friday.
Injects
T+0: Email is down. The provider says it is investigating and gives no cause or ETA.
T+20: A dosing or pump fault develops at a remote site. The controller generates its alarm. Hand the team the "sent" log. No one receives it.
T+40: The on-call engineer cannot log in to the jump host because the identity provider is unreachable.
T+60: The SOC analyst reports the cloud console is slow and incomplete. Phishing messages posing as "mailbox recovery" instructions start landing in personal inboxes.
T+75: The plant manager asks to switch off MFA or relax conditional access "just until email is back."
T+100: Someone realizes the emergency contact list and the engineering runbooks are in the unreachable tenant.
T+130: The provider announces staged recovery. A backlog of stale alarm emails starts arriving, hours old, in no particular order.
Decision points for the room
How would you learn about an abnormal process condition if email vanished tomorrow? Who finds out first, and how?
Who may approve a security-control relaxation during an outage, and who reverses it?
What is the minimum time each site can run safely with no external digital services?
How do you sort real alarms from the stale backlog at recovery?
What good looks like
Alarm delivery is monitored, not just alarm generation. A message sent to a mail server is not a message received by a person.
Local annunciation (strobes, horns, panel indications) that does not depend on the enterprise network, plus a second notification route such as an SMS gateway or radio that does not share your identity provider.
Hardware-token break-glass accounts on the systems that matter, with strict control and review.
Offline copies of runbooks, call trees and network diagrams.
Log buffering on-site so your forensic trail survives a cloud console outage.
A standing playbook for outage-themed phishing and a rule that nobody weakens MFA to "get things moving."
Scenario 3: The trusted remote support tool turns hostile
Best for: any plant that relies on an integrator, MSP or OEM with a standing remote path, which is nearly everyone.
The real-world trigger
On 11 November, security researchers flagged a campaign in which attackers who controlled cloud-hosted ConnectWise ScreenConnect environments belonging to managed service providers used the product's own Run Command feature to push rogue ScreenConnect clients and a toolkit called SCKit onto customer endpoints. The first count was six MSPs and 286 endpoints across 47 organizations. Later reporting put it at no fewer than 288 endpoints across 48 organizations, all within about 90 minutes.
The activity was linked to versions 1.0.31 and 1.0.32 of a third-party extension called RMM+, which accepted a blank access key when none was configured. ConnectWise had not independently confirmed the initial access vector at the time of the research notes we reviewed, and it said the presence of the extension alone does not mean a customer was compromised.
The rogue clients kept access after the MSP's session ended, and removing the extension did not remove the attacker's foothold. SCKit adds Microsoft Defender exclusions, creates a scheduled task and displaces the legitimate ScreenConnect client.
On 17 November, SC Media reported confirmed in-the-wild exploitation of a separate, technician-side flaw (CVE-2026-84869, CVSS 9.9) that turns the tool's file-transfer behavior against the technician's own machine. That is the reverse pivot: the person with access to your plant becomes the way in.
In June, CISA added a SimpleHelp remote-support flaw to its Known Exploited Vulnerabilities catalog, one that let an attacker defeat MFA by registering their own method at first login.
Shieldworkz's reading of the ScreenConnect campaign: no OT impact has been reported. The exposure is the access pathway, which is exactly what a tabletop should test.
The exercise
Setup. Your systems integrator also manages your IT. They hold a standing remote path to the OT DMZ and to two engineering workstations through a commercial remote support tool. It is Tuesday, 15:00.
Injects
T+0: The integrator's security lead phones. They have seen unauthorized use of their remote tool and do not yet know which customers are affected.
T+10: Your EDR flags a second remote access client on an engineering workstation, along with new Defender exclusions and an unfamiliar scheduled task.
T+25: Your asset inventory cannot say how many OT-adjacent hosts carry the integrator's agent. Three are unmanaged and nobody can say who installed them.
T+40: The integrator says one technician laptop may be compromised. It stores credentials for your jump host.
T+55: A vendor-run patch window is scheduled for tonight through the same tool. Your contract has a penalty clause for missed windows.
T+75: Session records show commands executed on a Level 3.5 host with no matching login event.
T+100: Legal asks which notification clocks have started: regulators, insurer, customers, the integrator under contract.
Decision points for the room
Do you kill every vendor remote path now, or only this one? What does safe emergency support look like for equipment that cannot wait?
If the integrator removes the tool, how do you know the attacker's access is gone?
Who owns the decision to cancel tonight's patch window, and who tells the plant manager?
What do you do about credentials that sat on a laptop you do not control?
What good looks like
A complete inventory of remote access tools and agents, including those installed by vendors. Treat remote support tooling as tier-zero infrastructure, in the same class as identity providers and domain controllers.
Vendor sessions brokered through your own OT DMZ: approved in advance, time-boxed, recorded and protected by MFA that you enforce, not just the vendor.
A per-vendor kill switch that has been tested, plus a documented emergency-support route.
Contract clauses that require the supplier to tell you within hours, not days.
Detection for second remote access clients, security-tool exclusions being added, and sessions with no matching authentication event.
Scenario 4: IT ransomware, OT shutdown
Best for: discrete and process manufacturers, food and beverage, life sciences, and any operator whose production depends on ERP, MES, virtualization or identity systems.
The real-world trigger
This is the most common way industrial operations actually stop, and it rarely involves an attacker touching a controller. In second-quarter industrial ransomware reporting, researchers saw no case in which the operator reached Stage 2 of the ICS Cyber Kill Chain or directly manipulated a control system. Where operations stopped, it followed encryption or a precautionary shutdown of the enterprise and virtualization systems that OT depends on.
The cases this year read like a template:
Foxconn, Mount Pleasant, Wisconsin: a full network outage from 1 May, production systems taken offline, and about two weeks of paper timekeeping before public confirmation.
West Pharmaceutical Services: a precautionary global shutdown and isolation of on-premises infrastructure in May. No control system was directly compromised, yet shipping, receiving and manufacturing were disrupted across sites.
Two sugar mills in the middle of crushing season: milling and cane haulage halted in June.
Fairlife: production suspended at all four U.S. facilities in July.
Boston Scientific: unauthorized activity on 25 August cut access to the business applications needed to manufacture and ship, with disruption lasting about two weeks.
In the third quarter, industrial ransomware attacks rose 11%, manufacturing accounted for 69% of victims, Qilin was the most active group with 195 industrial victims, and operators increasingly stole data before or instead of encrypting. Internet-facing edge devices, stolen credentials and weak remote access remained the main routes in.
Then there is the pattern seen on 17 November, when Equinor disclosed an ongoing cyberattack against certain IT systems. The company said operations and production were not affected and that it had no indication of data theft, and it had not disclosed how the attackers got in. That sentence is exactly the one your communications team will want to write about you, so rehearse whether you could stand behind it.
The exercise
Setup. A manufacturer with two plants, a shared virtualization cluster, an ERP, an MES and an OT DMZ. It is 06:10 on a Monday, shift change.
Injects
T+0: Virtualization hosts are encrypted. ERP is down. A ransom note appears on a jump server.
T+20: The MES cannot pull work orders. A shift lead asks whether to keep running from printed schedules.
T+35: The network team proposes cutting the IT/OT conduit. But the historian replicates to IT, and quality records sit in the encrypted environment.
T+50: You cannot confirm which OT assets are clean because the asset inventory lived on the affected virtual machines.
T+70: The attackers post a sample of what they claim is your network topology and technical drawings.
T+90: A key customer asks for delivery status. Legal wants to tell the market that "operations are unaffected." Who can verify that?
T+120: Backups exist, but nobody has decided restore order, and PLC project files were stored on the encrypted file server.
Decision points for the room
What are the written criteria for stopping production versus keeping it running in isolation, and who can invoke them?
What evidence would let you say "OT is verified clean" rather than "we have no indication"?
Can you run manually, for how long, and with which staff?
What gets restored first, and who decides?
Which reporting clocks have started, and who owns each one?
What good looks like
Isolation criteria decided in advance. When a team cannot confirm what is safe, the easy default becomes a plant-wide stop, because no narrower response can be shown to be safe. A current, independent picture of assets and connections makes narrower responses possible.
An asset inventory and network map that live outside the blast radius.
Offline, tested copies of PLC, HMI and DCS projects, plus golden images for engineering workstations.
Manual operating procedures that operators have actually walked through.
Pre-approved holding statements that separate "IT systems impacted" from "OT verified," so nobody over-promises to customers or markets.
Scenario 5: The wiper in the substation network
Best for: electric, gas and water utilities, renewable and distributed generation operators, and any business with many remote sites and thin local staffing.
The real-world trigger
The four scenarios above are about access and dependency. This one is about destruction. The attack on Poland's power sector began on 29 December 2025 and ran into the next day. It stood out because it targeted both IT devices and physical industrial devices, and it involved wiper malware. Attribution is not uniform. CERT Polska attributed the attack to Berserk Bear, while other researchers pointed to Sandworm with medium confidence. In August, CERT Polska published a follow-up report that found the incident considerably more complex than first believed.
We use it here because it forces an uncomfortable question: what if your recovery plan assumes the devices are still alive?
The details below are illustrative. They are not a description of what happened in Poland.
The exercise
Setup. A distribution or generation operator with a dozen remote sites, a small field crew and a central control room. It is 02:00 in the depth of winter.
Injects
T+0: Several sites lose remote visibility at once. Operators see HMIs and gateways rebooting or failing to boot.
T+20: The vendor confirms that affected devices need a firmware reflash on site. You hold three spares per region.
T+40: The national CERT calls and asks you to preserve samples and logs. Your engineers want to wipe and restore.
T+60: Overnight temperatures are forecast to drop sharply. The regulator wants a status report, and crews need to be dispatched to run sites manually.
T+90: Social media starts attributing the attack to a specific state. Government contacts ask you to hold public statements.
T+120: The last known-good configuration backup is five months old, and the golden images sit on a server in the same network segment that was hit.
Decision points for the room
What do you restore first, and how do you decide?
Who runs the sites manually, for how long, and what do they need to do it safely?
How do you balance evidence preservation with the need to restore quickly?
Who talks to the regulator, the government and the media, and in what order?
What mutual-aid or sector arrangements can you invoke at 03:00?
What good looks like
Golden images and configuration backups held offline and tested by actually restoring from them.
Spare hardware in the right places, with a documented and rehearsed manual operating mode.
Out-of-band communications between the control room and field crews.
Existing relationships with the national CERT, the sector ISAC and the regulator, so the first call is not a cold call.
A forensic capture procedure that fits inside a restore plan instead of competing with it.
The five OT tabletop exercise scenarios at a glance
Start with the scenario closest to how your plant really works. Most teams get the most from Scenario 2 or Scenario 3 first, because the weak spots are usually dependencies nobody has written down.
# | Scenario | Real-world anchor | Question it tests | Add to the room |
1 | Exposed controllers hijacked | Refrigeration controller attacks across Europe | Can you cut access, prove temperature history and decide on stock? | Contractor, quality or food safety, insurer contact |
2 | Cloud outage, no alarm | Microsoft outage and the Brühl chlorine incident | Do alarms, logins and runbooks survive losing a cloud suite? | Facilities, on-call staff, identity team |
3 | Remote support tool turns hostile | ScreenConnect campaign against MSPs | Can you find and kill every vendor path without stopping the plant? | Integrator or OEM, procurement, legal |
4 | IT ransomware, OT shutdown | Quarterly industrial ransomware data and recent plant stoppages | When do you stop production, and what proves OT is clean? | Plant manager, communications, investor relations |
5 | Wiper in the substation network | Attack on Poland's power sector | Can you restore from offline copies and run sites by hand? | Field crews, national CERT contact, regulator liaison |
If you run only one exercise this year, pick the scenario where your answer to "how would we know?" is weakest.
How do you turn one OT tabletop exercise into a program?
A single tabletop gives you a list of findings. A program gives you evidence that the findings got fixed.
Score each inject, not the session. Have the observer rate four things on a simple 0 to 3 scale:
Dimension | What the observer watches for | Red flag |
Detect | How the team first learns something is wrong, and from what source | Discovery by a customer, a journalist or a physical symptom |
Decide | Who has authority, how long the decision takes, whether criteria exist | Waiting for someone who is not in the room |
Communicate | Channels used, who is told, whether they work without the primary platform | Everything routed through the system that just failed |
Recover | Restore order, manual operation, evidence handling | Plans that depend on the compromised environment |
Track a few numbers across exercises:
Time to name the incident owner.
Time to a documented isolate-or-continue decision.
Share of external dependencies (cloud, vendors, contractors) that someone can list from memory.
Share of findings closed in 30 and 90 days.
The trend matters more than any single score.
Keep the after-action report short. Five findings at most, each with an owner and a date. A twelve-page report that nobody reads is worse than one page that is actually acted on. Then feed the results into your incident response plan, asset inventory, vendor contracts and training, and re-test the weakest scenario within six months.
Rotate and layer. Run a discussion-based tabletop twice a year with a different scenario each time. Between them, pick one or two findings and test them in a hands-on drill, such as restoring a PLC project from offline backup or checking that a local alarm still sounds. Where a live test could affect safety, keep it a simulation.
Frequently asked questions about OT tabletop exercises
What is an OT tabletop exercise?
An OT tabletop exercise is a facilitated, discussion-based simulation of a cyber or operational incident in an industrial environment. The team talks through detection, decisions, communication and recovery against a scripted scenario, without touching live systems. Its value is in exposing gaps in plans, authority and dependencies before a real event does.
How is an OT tabletop different from an IT tabletop?
OT exercises treat safety and process state as the main constraint. Isolating a network segment can stop production or create a hazard, manual workarounds and spare parts matter, and operations and engineering staff have to be part of every decision. IT-focused exercises tend to skip all of that.
How often should we run OT tabletop exercises?
Two a year is a common recommendation, with different scenarios each time. Add one after any major architecture change, a new vendor access arrangement, or a notable incident in your sector.
Who should take part in an OT tabletop exercise?
Operations and engineering, OT and IT security, safety, legal and compliance, communications, plant or site leadership, and any critical vendor or contractor with access to your systems. Add an observer who is not part of the response team.
How long does an OT tabletop exercise take?
Plan on 90 minutes to half a day. Ninety minutes works for a focused scenario with four to six injects. Executive-level or multi-site exercises take longer.
Can we run an OT tabletop exercise without a vendor?
Yes, and many teams start that way using internal facilitators and the scenarios above. An outside facilitator brings fresh eyes, can challenge assumptions more freely, and often has recent incident experience to draw on.
What should we do with the findings from a tabletop exercise?
Turn the top five into tracked actions with owners and dates, update the incident response plan and asset inventory, and schedule a re-test of the weakest scenario.
Building OT incident readiness with Shieldworkz
Shieldworkz is an end-to-end industrial OT cybersecurity company, covering the products, services and solutions that critical infrastructure operators need to protect SCADA, OT and IoT environments. Tabletop exercises are most useful when they connect to the rest of your program, and that is where the findings usually point:
Know what you have and where it is exposed. An OT security risk assessment and gap analysis gives you the asset and dependency picture that Scenarios 1, 3 and 4 depend on.
Be ready before the call comes. An OT incident response retainer gives you a team that already knows your environment when an incident starts.
See what is happening in the network. The Managed SOC service and the OThello platform help close the visibility gaps that exercises tend to expose.
Related Shieldworkz analysis: the Microsoft outage and its OT implications, the Brühl chlorine incident, the ScreenConnect attack on MSPs and refrigeration controller cybersecurity.
Ready to turn these scenarios into exercises for your sites? Request a demo or speak with the Shieldworkz team.
Additional resources:
Comprehensive Guide to Network Detection and Response NDR in 2026 here
NERC CIP-015 Internal Network Security Monitoring Readiness Checklist for Electric Utilities here
OT SOC Foundational Guide here
Managed SOC Service here
OT Cyber Threat Intelligence Advisory - Middle East here
NIS2 Directive Achieving NIS2 Compliance Through IEC 62443 here
What Is Removable Media? Risks, Policies, and Industrial OT Security Solutions here
Free Removable Media Policy Template for OT and IT Teams here
Get Weekly
Resources & News
See How Our Industry-Leading OT Security Solutions Address Critical Security Challenges
You may also like

Manufacturing Ransomware Statistics 2026: Latest Data on Sectors, Groups and Attack Paths

Team Shieldworkz

SBOM for OT and ICS: What the Latest lwIP Advisories Teach Us About Component Visibility

Team Shieldworkz

FERC Approves NERC CIP-015-2: What Changes for Your INSM Program

Team Shieldworkz

What the equinor cyberattack reveals about energy infrastructure resilience

Prayukth K V

Refrigeration Controller Cybersecurity: What the CISA/FBI Advisory Says, What Has Happened Since, and a Cold-Chain OT Hardening Checklist

Team Shieldworkz

2027 OT Security Budget Guide: Where to Spend and How to Justify It

Team Shieldworkz

