On November 13, the FAA grounded every flight in the United States “due to extraordinary circumstances and for reasons of safety.” A telecommunications outage affecting all Air Route Traffic Control Centers, the regional facilities that guide flights across the country, triggered the stop. Transportation Secretary Sean Duffy blamed aging air traffic control technology and overloaded routers. Homeland Security Secretary Markwayne Mullin pointed to FAA updates to those systems and said the ground stop did not stem from a threat to the United States.
The nation had issued a ground stop of this scale only twice before: after the September 11 attacks and in January 2023, when a pilot notification system went down. This time, more than 15,000 US flights were delayed or canceled on Friday, and thousands of travelers faced a night on airport floors or in long queues.
An update to aging systems set off the failure. Indeed, the November 13 ground stop shows how quickly critical infrastructure halts when the connected systems behind it fail.
Critical infrastructure stops when the systems behind it stops. But the right technology can recover that IT layer, identity first and clean data next, so operations come back in an order that holds—and teams can prove that order before the next incident.
The Stakes When Operations Stop
Air traffic control, electric grids, pipelines, and manufacturing lines share one trait: they run continuously because the people who depend on them cannot tolerate an outage. When a control system goes dark, operators make safety decisions in real time, with fewer tools and less margin.
Every operator in these sectors has a plan for the physical failure. Fewer have a tested plan for the connected digital infrastructure behind them. Whether the trigger is a botched update, an overloaded router, or an attacker in Active Directory, the recovery question is the same: what comes back first, and has anyone tested it?
Aging Systems, Connected Dependencies
Critical infrastructure gets attention after it fails. Systems age quietly, budgets wait for a breaking point, and the largest investments arrive once the damage is done—at far greater cost than prevention would have been. Modernization takes years of funding, engineering, and testing, and operations run on what is in place in the meantime.
Recovery readiness, however, can start today.
Operational technology (OT) stays in service for decades. The IT around it changes constantly: Active Directory, Windows servers, hypervisors, historians, engineering workstations, and more. Each of these sits on the path between a command and a machine. When any layer fails, operations stop.
Incidents in these environments get filed as IT problems, and recovery plans end at the plant fence. The dependency crosses the fence. Attackers know that path. They start in IT and end in the control room.
Survive First, Recover in Sequence
Detection and monitoring matter, but the IT backbone of OT matters just as much to recovery as the OT systems themselves. Operators need working logins to reach the control systems, running servers to host them, and clean data to resume production.
Rubrik focuses on that layer. OT vendors and engineers own the controllers and machines on the plant floor, and Rubrik recovers the identity, servers, and data those teams depend on at machine speed, so operations come back online quickly and efficiently. Rubrik solutions that address these needs include:
- Identity Resilience restores Active Directory and Entra ID and rolls back malicious changes, so operators can sign in and the problem doesn’t return with the restore.
- Data Security and Protection then brings back the Windows servers, hypervisors, historians, and engineering workstations behind your control systems from a known-clean point.
- Threat Analytics uses Anomaly Detection, Threat Hunting, and Rapid Response enabling you to recover your business by locating that clean, threat free point before you restore.
- Cyber Recovery enables you to rapidly and predictably recover to a clean state with minimal downtime and data loss.
Each step restores what the next one depends on, so operations come back in an order that holds. Operators sign in, systems return from a clean point, and the plant, pipeline, or grid gets back to the work it exists to do while modernization continues.
Recovery Proven Before the Incident
A recovery plan earns trust through testing. Rubrik customers test restores before an incident and produce the evidence auditors ask for. Recovery runs from an isolated control plane, which keeps services available even at dark sites with no internet connection.
Plants, pipelines, and grids need that certainty. Ask your team one question this week: if identity and the servers behind our operations went down tonight, in what order would we bring them back, and when did we last prove it?
The people waiting on the other side of that answer are the ones who depend on the system: the passengers on the ground, the customers on the grid, and the crews on the line. Recovery is how you keep faith and trust with them.