Insights / Critical Infrastructure

When the Systems We Count On Stop Working

Recent outages and a supply-chain attack show why essential services need tested backup procedures, continuous cybersecurity monitoring, and clear response plans.

Nov 18, 2026Critical Infrastructure
Illustration of an emergency communications operator using a paper log beside monitoring screens, with essential infrastructure in the background.

On Thursday, November 12, people opened Outlook and couldn’t reach their inboxes. A global Microsoft 365 outage delayed email and disrupted other workplace tools.

On Friday, departures across the country had to wait. The FAA ordered a nationwide ground stop after a telecommunications failure disrupted aircraft communications and radar feeds. Controllers and pilots used established safety procedures to land aircraft already in the air.

On Monday, someone opening the BBC to read the news or visiting Zoom’s website could be exposed to malicious code just by loading a page. An attacker had compromised Optimizely, a service companies use to test changes to their websites. Researchers found malicious code in scripts used by 178 organizations, including the BBC, CNN, Fox News, Zoom, HSBC, and IKEA. A shared service gave the attacker a way to reach visitors across industries while the affected pages could still appear to work normally.

These were three separate incidents. The first two showed how far the consequences of a technical failure can spread. The third showed how an attacker can reach people through a service they already trust.

What would stop if your systems went down?

At a 911 center, losing a dispatch system can force staff to find another way to locate callers and coordinate responders. At a hospital, a system failure can send clinicians back to manual procedures while patients still need care. At a utility, losing remote visibility can leave operators relying on crews in the field to verify conditions.

A manual fallback may be workable for a short outage. Sustaining it through a busy shift is a different challenge. Over the years, automation has let organizations handle more work with fewer people. When those systems go down, the work returns to staff, often without the staffing levels that made the old process feasible. A dispatcher can track calls by hand. The question is how many calls the whole shift can handle that way before callers start waiting longer for help.

Imagine a dispatch center switches to paper during a busy shift. A dispatcher can still record an address and radio a crew. But the team also has to track which units are available, update incidents as details change, and pass that information to the next shift. The longer the outage lasts, the more work goes into keeping everyone’s picture current. When the system comes back, someone still has to reconcile the paper records with the digital ones while new calls keep coming in.

A continuity exercise should measure that whole shift. How long can the team keep up with incoming calls? What work starts to pile up? How much extra staffing would buy them time?

Leaders need to test backup procedures with the people who would actually be on duty and the volume of work they could face. How much of the service can they keep running safely? For how long? Knowing those limits helps leaders decide where preventing an outage, containing an attack, or restoring a system faster will make the biggest difference.

What 24/7 defense looks like

Endpoint security helps protect devices. A security information and event management system, or SIEM, brings alerts and logs together. Those tools give defenders a place to start. Someone still has to recognize when an alert matters, investigate it, and act while there’s time to limit the damage.

The work starts before an incident. Proactive threat hunting looks for signs of compromise that routine alerts may miss. Vulnerability scans find weaknesses, and experts work with system owners to fix the ones that put essential services at risk. Controlled network testing checks whether defenses work as intended. Recovery exercises give staff practice keeping services running when their usual tools are unavailable.

Around-the-clock coverage means qualified people are available to investigate and coordinate containment with operators at any hour. They need the authority to act and a plan for protecting essential services while they do it.

Say an analyst spots unusual activity on an account with access to a critical system at 2 a.m. The analyst checks whether the activity matches scheduled maintenance, finds out which systems the account reached, and contacts the on-duty operator. Together, they decide how to contain the threat while keeping the service running safely.

That response depends on decisions made well before the alert. The analyst needs access to the right logs. The operator needs to know who can authorize containment. Both need a way to reach each other if their usual communications are down.

At 2 a.m., who will see the first sign of trouble? Who can act on it? And how long can your team keep serving the public while the system comes back?

The time to answer those questions is while everything still works.

If those answers are unclear, OTM Cyber can help you work through them. Start with a conversation about your current cybersecurity approach, your response plans, and what your team needs to keep essential services running.

Sources

Get practical cyber readiness updates

Receive OTM Cyber insights, relevant event invitations, and guidance for leaders who have to keep operations moving.

Get Cyber Readiness Updates
Next Step

Continue the conversation.

Explore related services or talk with OTM Cyber about the cybersecurity pressures facing your environment.