Incident sheet · /infrastructure

Filed
Read
3 min · 690 words
Severity
Routine

No coordinated attack behind outage wave, DNI tells Congress

DNI Jay Clayton says the Microsoft 365, FAA and NSA outages stem from maintenance, not a coordinated attack, as DHS convenes industry talks on software safety.

Tech outages shine spotlight on infrastructure vulnerabilities
FeedTech outages shine spotlight on infrastructure vulnerabilities — AI-generated

Event log

  1. DNI Jay Clayton told Congress the outages were 'separate service outages associated with maintenance and technical changes,' not a coordinated or state-sponsored attack.
  2. Incidents included a nearly daylong Microsoft 365 outage, a nationwide FAA ground-stop from a router upgrade, and routine maintenance taking down a classified NSA network.
  3. DHS Secretary Markwayne Mullin said he is '98% confident' adversaries were not involved and is convening an industry call.
  4. The Software Safety Institute, co-founded by Lauren Zabierek and Bob Lord, builds on CISA's 'Secure by Design' initiative.
  5. Some outages were linked to rapid patching in response to AI-driven vulnerabilities, Clayton said.

Three federal systems went dark in one week — Microsoft 365 for nearly a day, the FAA's nationwide airspace on Saturday, and a classified NSA communications network — and the nation's top intelligence official has a verdict: maintenance, not adversaries.

At a House Homeland Security Committee hearing Wednesday, Director of National Intelligence Jay Clayton described the incidents as "several unrelated issues that have recently caused service disruptions."

"I understand the timing of these incidents can raise questions, and it should," Clayton said. "The American people should ask us these questions. But based on what we know today, after a great deal of diligence, these are separate service outages associated with maintenance and technical changes. They are not a coordinated or state sponsored attack."

What exactly broke?

The incident string included:

  • A nearly daylong Microsoft 365 outage caused by a hidden defect in the company's cloud gateway.
  • Saturday's nationwide FAA ground-stop, triggered by a telecommunications network failure linked to a router upgrade.
  • A classified communications network at the National Security Agency, taken down by what officials called "routine maintenance."

Homeland Security Secretary Markwayne Mullin backed Clayton's assessment. He said he is "'98% confident that this has nothing to do with our adversaries hacking or going after our systems."

Mullin also said DHS officials are convening a call with industry to discuss the outages and how to avoid repeats. "It'd be helpful, as we're moving forward, that maybe the industry that's doing the upgrade could inform their customers that it's going to take place," Mullin said. He pointed to patching pressure and aging infrastructure as part of the challenge.

"We're not pressuring the industry to do it," he added. "We just want to have a conversation, say, maybe we should start communicating, because what happens online is a tremendous amount of fear."

What does this change for critical infrastructure operators?

Some of the outages have been tied to rapid patching driven by AI-discovered vulnerabilities. Clayton framed it as the new normal. "Anytime you are going to do those things, you take systems down, you bring them back up," he said. "We are in an environment where the rate of patching, the rate of upgrading of systems is increasing."

Former officials argue the root cause matters less than the exposure. Anjana Rajan, CEO of cybersecurity firm Atalanta and a former White House cyber official, said Mullin's industry call comes at a crucial time, since the private sector owns and operates most U.S. critical infrastructure.

"As our critical infrastructure is becoming more and more software defined, our ability to understand what those systems will do under normal, abnormal, or hostile conditions is not keeping pace," Rajan told Federal News Network. "And I think you know the American people, regardless of what the root cause is, like the catastrophic impact is the same. They're stuck on the tarmac. Their credit card's not working. Their email is out."

The software safety argument

Lauren Zabierek, CEO and co-founder of the Software Safety Institute and a former CISA official, said the outages prove that "software doesn't have to be hacked to cause harm."

"We think of security and quality as properties of the product, but safety is about the outcome for the people who depend on it every day," she told Federal News Network. "Our national security, our economy, and our public health and safety all depend on software, and too much of it is built with unsafe components and practices and shipped with unsafe defaults."

Zabierek and former CISA colleague Bob Lord recently co-founded the Software Safety Institute to tackle vendors shipping products with known defects. The institute builds on CISA's "Secure by Design" initiative. Lord serves as chief strategy officer.

Lord said the online panic around the outages reflects a deeper problem: missing safety and security data. "We don't have enough information in the software sector as a whole, and we don't have the institutions in place to give us the right dots, so we tell the right story," he said. "We don't have transparency."

via federalnewsnetwork.com (Source)

Filed under

  • critical-infrastructure
  • service-resilience
  • software-safety
  • network-maintenance
  • cloud-outages
Share this article:

More from Tom Whitfield

Tom Whitfield

Show full bio

Market editor covering people, launches and day-to-day practice in enterprise information technology and the leaders who run at CIO Monitor.

185 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›