COMMENTARY: The widespread outages dominating headlines in recent days have exposed just how fragile the infrastructure underpinning our most critical services has become. We are increasingly dependent on aging systems that lack the resilience to withstand even routine technical failures, raising serious questions about how prepared we are for deliberate disruption by adversaries.
If the most well-resourced organizations in the world lack the redundancies to withstand relatively minor technical failures, what happens when an adversary intentionally tries to disrupt their systems? Furthermore, what does this mean for smaller organizations that have just a fraction of those resources at their disposal?
[SC Media Perspectives columns are written by a trusted community of SC Media cybersecurity subject matter experts. Read more Perspectives here.]
First came the Microsoft outage that disrupted services across more than 70 countries. Then, the FAA ordered a nationwide ground stop after a technical problem with its legacy equipment being replaced. Next, JPMorgan Chase experienced outages because of a software bug in its on-premises hardware systems while other major U.S. banks also reported issues. And earlier this week, the National Security Agency’s (NSA's) classified internal communications network, NSANet, went down during routine scheduled maintenance.
It’s easy to put on a tinfoil hat and speculate about why all these outages may have happened, but that’s neither here nor there. What’s now clear: it doesn’t take a cyberattack to bring operations to a grinding halt – and that should make organizations take a very close look at their resilience strategy.
Rapidly aging infrastructure underpins many critical aspects of our everyday lives, yet it's increasingly incompatible with the very updates needed to keep it secure and operational. Many of these updates contain critical security fixes, yet outdated systems and concerns about downtime are leaving organizations caught between the risk of disrupting operations and the growing risk of leaving known vulnerabilities unpatched.
As organizations race to develop and deploy patches to stay ahead of AI-enabled threat actors, we’re likely to see more frequent outages. Organizations will increasingly have to balance the urgency of critical software and hardware updates with maintaining the reliability of systems we’ve long taken for granted.
That being said, despite all these recent interruptions, now's not the time to dial back patches and critical hardware updates. We need to think of innovative ways to make updates and patching easier, faster, and less disruptive so organizations aren't discouraged from deploying vital updates out of fear of downtime. For example, companies such as Apple are now reportedly exploring ways to push updates at scale without the friction that restarts require. This would have a significant impact on the resilience of organizations with really large install bases like Apple or Microsoft if updates like this became the norm.
Organizations need to use every tool at their disposal to close vulnerabilities as they emerge, but speed cannot come at the expense of reliability. That means rigorously testing updates and validating that recovery plans, including rollback procedures, failover strategies, and backups, actually work before they're needed. If our systems went down today, could we get them back up? Every organization, regardless of size, should confidently answer “yes.” As the last few days have shown us, even the largest, most well-resourced organizations aren't there yet.
It’s important to mention that organizations of all sizes should focus on resilience. Much of our critical infrastructure runs through smaller organizations and municipalities. Not only do these businesses often rely heavily on the resilience of larger orgs upstream, they also are challenged with fewer resources to ensure continuity and with much more of a target on their backs from adversaries. Our critical infrastructure is only as resilient as its weakest link, regardless of size. When one part of that interconnected backbone has a vulnerability, the entire system faces risk. So every organization has to use this as a moment to look in the mirror and ask if they could keep their business functioning if an important vendor was no longer operational?
Now more than ever, instead of finger-pointing, the public and private sectors need to come together to confront the challenges staring us in the face. That means governments at every level working alongside industry to strengthen critical infrastructure, information sharing on threats, and exchanging best practices to prevent disruptions before they happen. History gives me reason to be optimistic that we can rise to the occasion.
In 1999, American organizations spent roughly $100 billion preparing for Y2K, mobilizing at scale against an uncertain technology risk. The playbook wasn't glamorous: we needed to inventory systems, work with vendors, test backups, and rehearse contingency plans. The Senate's own postmortem found that the turning point was making Y2K a leadership priority, not just an IT problem. That's exactly what we need today. Leaders must understand what systems they depend on, what updates could break, and how to recover when things go south.
None of this will be easy. It will take time, investment, and people armed with every tool out there to get the job done. We'll likely see more outages as governments and businesses of all sizes learn from the mistakes of the past few weeks and work through these challenges. But I'm optimistic we can emerge on the other side of this bumpy road stronger, more resilient, and more connected than before.
Bryson Byrd, Cybersecurity Advisor, Huntress
SC Media Perspectives columns are written by a trusted community of SC Media cybersecurity subject matter experts. Each contribution has a goal of bringing a unique voice to important cybersecurity topics. Content strives to be of the highest quality, objective and non-commercial.