Two Massive Outages, No Attackers: What Last Week Should Tell Your Business

Introduction

Last week within about 36 hours of each other, Microsoft 365 stopped working across more than seventy countries, and the FAA halted departures from every commercial airport in the United States.

When large systems fail close together, the instinct is to start looking for an attacker.

But in both of these cases, there wasn’t one. What the two incidents share is something far more ordinary (and for most businesses, far more useful to understand.)

So, let’s look at what actually caused these significant outages, why that cause matters less than most continuity plans assume, and what kind of disruption your business should be preparing for as a result.

What Actually Happened?

Microsoft’s outage began on November 12 and took roughly two days to fully resolve. Exchange Online, Teams, and Copilot were all affected, with mailboxes hit hardest. Microsoft attributed it to configuration settings applied to servers following an update, which overwhelmed the process responsible for establishing secure connections.

Servers stopped handling requests, and the fix involved rolling the change back. Microsoft stated specifically that the outage was not caused by a cyberattack.

The FAA ground stop happened the following day and lasted a few hours, halting around 3,500 departures and producing close to 8,000 cancellations. According to the FAA’s own account, its legacy equipment became unstable when data began flooding the agency’s network at roughly a thousand connection attempts every four to five seconds. The source was traced to a radio communications site in Arkansas where the FAA’s network provider had been deploying a new router as part of routine infrastructure work. The FAA’s statement was direct: based on all available evidence, no indication of a cyberattack or an outside nefarious actor.

When you read those two descriptions next to each other, the resemblance is hard to miss.

The Pattern Is Change, Not Malice

In both cases, somebody did planned, sensible, well-intentioned work. An update was applied. A router was installed as part of upgrading old copper to fiber. Neither decision was reckless, and neither organization was neglecting its infrastructure. The opposite, really: both incidents happened because someone was maintaining and modernizing complex systems.

What followed in both cases was the same mechanism. A new element interacted with existing infrastructure in a way nobody predicted, something got overwhelmed, and the failure cascaded outward far past the component that started it.

This is how complex systems actually break most of the time. Not through a dramatic breach, but through a change that was correct in isolation and unpredictable in combination. We’ve written before about the gap between what you configured and what you think you configured, and this is that same problem at national scale.

Your Customers Won't Ask Why

Here’s the part that matters for planning: Your customers won’t care what the cause behind the outage was. the result for them is the same either way.

If your business had been unable to send email for two days last week, your customers experienced exactly what they would have experienced during a ransomware incident. Orders didn’t get confirmed. Questions went unanswered. Deadlines slipped. The explanation available to you, that it was your vendor’s configuration change rather than an intruder, would not have improved a single one of those conversations.

Business impact is indifferent to cause. Most continuity planning is not. Plans tend to be organized around attack scenarios because those are what security conversations focus on, which leaves a sizable gap where the far more common failure modes live.

The Dependency You Haven't Mapped

The Microsoft outage exposed something specific that’s worth checking in your own environment.

A great many businesses run email, chat, file storage, and single sign-on through the same provider. When that provider has a bad day, those don’t fail as four separate problems. They fail as one, simultaneously, and companies discovered last week that their plan for communicating during an incident ran entirely on the platform that was down.

That’s a concentration question, not a security question in the usual sense, and it’s one almost nobody has examined. If your team can’t reach each other, can’t access files, and can’t authenticate into anything, the sequence of what you do next needs to have been decided beforehand. It cannot be worked out in the moment, because working it out requires the tools that aren’t available.

When There's Nothing for You to Fix

This category of incident has a feature that makes it genuinely different from a breach: there is no remediation available to you. Nothing in your environment is broken. No patch applies. You are waiting on somebody else, with no visibility into their progress and no influence over their timeline.

Preparing for that looks different from preparing for an attack. It means knowing which of your revenue-critical processes have a manual fallback and which simply stop. It means having a way to reach your own team that doesn’t depend on your primary platform. It means deciding in advance who tells customers what, and how quickly, when the honest answer is that you don’t know when service will return. And it means understanding which single providers, if they failed, would take several of your functions down at once.

None of that is expensive. It mostly requires somebody to sit down and work through it before they need it, which is the same reason it usually doesn’t happen.

Final Perspective

Last week was a useful reminder that the biggest threat to your operations in any given year is probably not an adversary. It’s the accumulated fragility of systems you depend on and don’t control, disturbed by somebody’s reasonable “Tuesday afternoon maintenance”.

The businesses that handled last week well weren’t the ones with better security tools. They were the ones who had already worked out what to do when a vendor goes dark, because they’d thought about it on a quiet day rather than during the outage.

At Secutor, our work on business continuity and incident readiness covers exactly this, including tabletop exercises that walk leadership through the decisions before the pressure is real. If your continuity plan assumes the cause will be an attacker, it’s worth pressure-testing against what actually happened last week.

The cause of your next outage is largely out of your hands. What your business does in response is not.

Connect with an Expert for a Free Consultation

Secutor is your team of world-class problem solvers with vast expertise and experience delivering complete solutions keeping your organization protected, audit-ready, and running smoothly. Use the form below to contact us for a free consultation.

Enjoyed this Content?

Share this story on social media!

Scroll to Top

Jason Fruge

Consulting Chief Information Security Officer (CISO)

Jason Fruge is an accomplished Consulting Chief Information Security Officer at Secutor Cybersecurity, bringing over 25 years of deep expertise in information security. His storied career includes leading and managing robust security programs for Fortune 500 companies across retail, banking, and fintech sectors. His current role involves providing strategic guidance and advisory services to clients, focusing on security governance, risk management, and compliance.

Apart from his consulting responsibilities, Jason is an active member of the global cybersecurity community. He is a Villager at Team8, a prestigious collective of senior cybersecurity executives and thought leaders. Additionally, he serves as an Advisor at NightDragon, an innovative growth and venture capital firm specializing in cybersecurity and enterprise technologies.

Jason’s tenure as a CISO is marked by a proven track record in developing and implementing comprehensive security policies and procedures. He adeptly leverages security frameworks and industry best practices to mitigate risks, safeguarding sensitive data and assets. His expertise encompasses incident response and root cause analysis, where he has notably managed cyber incidents to prevent breaches and minimize business disruption and customer impact.

A key aspect of Jason’s role has been the creation and facilitation of executive and board-level cyber risk committees, ensuring organizational alignment and awareness. His responsibilities have extended to maintaining compliance programs for standards such as PCI and SOX, as well as leading privacy and business continuity programs. Holding prestigious certifications like CISSP, QSA, and QTE, Jason is also a recognized thought leader, contributing articles on cybersecurity to InformationWeek.

Jason’s passion lies in driving innovation and fostering collaboration in the cybersecurity field. He is currently seeking an executive CISO role in a leading retail, finance, or fintech organization, where he can continue to make significant contributions to the cybersecurity landscape.

Jennifer Bayuk

Cybersecurity Risk Management Expert

Jennifer Bayuk is a highly esteemed cybersecurity risk management thought leader and subject matter expert at Secutor Cybersecurity. Her extensive experience encompasses managing and measuring large-scale cybersecurity programs, system security architecture, and a wide array of cybersecurity tools and techniques. Jennifer’s expertise is further deepened with her proficiency in cybersecurity forensics, the audit of information systems and networks, and technology control processes.

Jennifer’s skill set is comprehensive, including specialization in cybersecurity risk and performance indicators, technology risk awareness education, risk management training curriculum, and system security research. Her academic achievements are noteworthy, holding Masters degrees in Philosophy and Computer Science, and a Ph.D. in Systems Engineering. This strong academic background provides a solid foundation for her practical and strategic approach to cybersecurity challenges.

Certified in Information Systems Audit, Information Systems Security, Information Security Management, and IT Governance, Jennifer is a well-rounded professional in the field. Her credentials are further enhanced by her license as a New Jersey Private Investigator, adding a unique dimension to her cybersecurity expertise.

At Secutor, Jennifer plays a pivotal role in steering cybersecurity initiatives, aligning them with organizational risk appetites and strategic objectives. Her ability to educate and train in the realm of technology risk has been instrumental in raising awareness and enhancing the cybersecurity posture of our clients. Her dedication to research and continual learning makes her an invaluable resource in navigating the ever-evolving cybersecurity landscape.

Jennifer Bayuk’s blend of academic prowess, practical experience, and certifications make her an indispensable part of our team, as she continues to drive forward-thinking cybersecurity solutions and risk management strategies.

Steve Blanding

CISO Consultant

CISSP, CISA, CGEIT, CRISC

Steve is an IT management consultant living in Dallas, TX. Steve has over 35 years of experience in executive IT leadership, IT governance, risk and compliance (GRC), systems auditing, quality assurance, information security, and business resumption planning for large corporations in the Big-4 professional services, financial services, manufacturing, retail electronics, and defense contract industries. He has extensive experience with industry best practices for adopting and implementing new technologies, IT service management frameworks, and GRC solutions that have dramatically improved customer satisfaction while reducing cost.

Industry Experience

  • State Government: 5 years
  • Retail: 5 years
  • Defense Contract: 5 years
  • Manufacturing: 2 years
  • Health Care: 2 years
  • Local Government: 2 years
  • Public Accounting (Big 4): 7 years
  • Insurance: 3 years
  • Financial Services: 5 years

Key Career Accomplishments

  • Conducted a full-scale ISO27000 audit 4 times over the past 6 years.  Also, conducted a “light” ISO27000 review of a small Dallas-based company in 2007.
  • Developed and authored a comprehensive IT security policy manual, incident response plans, training programs, security contingency plans and configuration management plans for FedRAMP regulatory compliance.
  • Conducted multiple DR and operational backup and recovery IT risk assessments of critical business systems on mainframe, LAN, and distributed system networks located across North America.
  • Conducted data centers audits for Tyco Corporation (Brussels, 2005 and Denver, 2006), Farmers Insurance (Los Angeles, 2006), Zurich Financial Services (Chicago, Kansas City, and Grand Rapids, 2006), and Convergys Corporation (Dallas, 2010, 2011, and 2012).
  • Led a project to remediate segregation of duties and streamline user access system security and HIPAA compliance administration across 5 regions in North America, resulting in cost savings of $700,000 per year (Kaiser Permanente).
  • Implemented Sarbanes-Oxley Section 302 and 404 IT general and application controls, reducing security administration costs and improving operational performance by 50% or $500,000 annually (Tyco Corporation).
  • Led the global SAP business-IT alignment, process re-design implementation initiative for financial accounting, materials management, production planning, quality management, sales and distribution, warehouse management, and plant maintenance, which resulted in creating $2,000,000 in cost savings.
  • Engaged by Arthur Andersen in Houston to transform the local IT organization and then direct 3 organizational mergers/consolidations, which resulted in a 25% reduction in operating costs, or $3,250,000, while improving customer satisfaction by 30%, and improving employee morale, technology availability and the quality of IT infrastructure and service delivery.
  • Assigned by Arthur Andersen global leadership to lead global project teams responsible for data center and customer support call center consolidation, which resulted in annual operational cost savings of 45% or $4,000,000.
  • Implemented ITIL service management practices for problem management, incident management, help desk, project management, and operations management.
  • Conducted SOX 404 audits at Duke Energy (6 months), Red Hat (3 months), Tyco (9 months), Zeon Chemicals (4 months), and Convergys (2 months). Experience includes control design/documentation and effectiveness testing.

Publications:

Author, various articles in EDPACS and Auerbach’s IT Audit Portfolio Series, 1981 – 2001

Author, various articles in the Handbook of Information Security Management, 1993 – 1995

Editor, Auerbach’s Enterprise Operations Management, 2002

Editor, Auerbach’s IT Audit Portfolio Series, 2000 – 2002

Consulting Editor, Auerbach’s EOM Portfolio Series, 1998 -2001

Ready to Find Your Solution?

Reach out using the form below, and we’ll contact you as soon as possible to schedule your consultation.

Ready to Find Your Solution?

Use the form to schedule a consultation, and we’ll reach out within 48 hours to confirm the appointment.

Considering this delay, please only select meeting dates 48 hours or more in advance. Your information will only be used to facilitate a meeting.