Skip to content
Business Efficiency

Officials see no sign of attacks behind a week of outages, cite patching

Lawmakers link the patching to AI-found flaws and say some systems were not built for that pace

W
WebPulse Newsroom
AI-assisted · 4 min read
Share on X LinkedIn
Officials see no sign of attacks behind a week of outages, cite patching
In brief
  • US officials told a House hearing they see no evidence so far that cyberattacks caused a week of outages, and they cited patching as a cause. Some lawmakers blame AI-found flaws.
  • Sen. Mark Warner said companies are patching many flaws at once, which strains systems not built for that pace. One lawmaker disputed this and tied the outages to rising attacks.
  • Leaders should ask how their own teams test and roll back urgent patches, because a fix is also a change to a live system.

A fix is also a change

We tend to treat patching as pure safety. A flaw is found, a fix goes in, and the risk drops. Some officials and lawmakers now argue for a more awkward truth. Every patch is also a change to a live system. Changes can break things.

That argument is taking shape in Washington, according to CyberScoop. Officials and lawmakers are examining a run of major tech outages. They include an aviation ground stop and incidents at communications and banking systems. Some of them see the speed of repair, not an attacker, as a contributing factor.

What officials told Congress

The Trump administration's witnesses spoke at a House Homeland Security Committee hearing on Wednesday. CyberScoop reports they repeatedly named patching, not hacking, as a cause of the outages. Director of National Intelligence Jay Clayton, Homeland Security Secretary Markwayne Mullin and FBI Deputy Director Christopher Raia said there is no evidence so far of a malicious attack.

CyberScoop says they added that cyber adversaries were not seen exploiting the time that patching takes. The outlet also reports that administration officials say cyberattacks almost certainly are not responsible. Clayton said "the rate of patching, the rate of upgrading of systems, is increasing." He tied this to advances in compute and applications.

The witnesses did not say the patches answered AI-found vulnerabilities. Lawmakers went further.

The case that AI is the driver

Sen. Mark Warner, D-Va., argued that AI now finds flaws across huge numbers of systems at unprecedented speed. In his words, that pressures companies and agencies to patch "immediately, often all at once." He said this strains systems "that weren't built to handle that pace of change."

Rep. Jim Himes, D-Conn., allowed that faster discovery and patching could bring more frequent outages. He also called the current pace of patching vital to shoring up IT security. CyberScoop adds a Washington Sun report. According to the Washington Sun, industry and government officials in Hill briefings cited patching of AI-found flaws as the cause.

These are statements from officials and lawmakers. The source describes no technical post-mortem of any single outage. The AI link is a view held by some lawmakers, not a finding.

How patches can break things

The sources do not say what failed in these outages. What follows is general background, not a diagnosis.

Think of a city that repairs every bridge on the same weekend. Each repair is sensible. Together they jam the roads. Software can behave the same way.

Two well-known failure modes show how. First, two changes that each work alone can clash when they land together. A new library version, for example, may not suit a setting changed the same day. Second, many patches need a restart. If many connected systems restart at once, services that depend on each other can fail to come back in the right order.

Rushed change can leave little time to test for either problem.

Warner's phrase about systems not built for that pace matters here. One reading is that it implies older, tightly coupled systems. The source does not say which systems failed.

A dispute over the cause

Not everyone accepts that patching explains the outages. Rep. James Walkinshaw, D-Va., challenged Clayton's testimony that the incidents were "unrelated." He said cyberattacks are "exploding", that the outages "are not coincidences" and that they are "connected to cybersecurity." In his account, everyone is "frantically patching systems" because of those attacks.

That view differs from the witnesses' position. They said they see no evidence that malicious attacks had anything to do with the outages. Walkinshaw was the only voice in the source arguing the outages track rising attacks. The sources do not settle who is right.

Walkinshaw's point about the agency's capacity was that, as attacks rise, CISA, the US cyber defence agency, has lost staff and funding on a large scale. Secretary Mullin answered that CISA can still do its job because of "new technology." He did not say which. He had no update on hiring. Members of both parties urged him to add staff.

What to ask your team

The lesson here is that speed and stability pull against each other. Urgent patching sits in the middle. A few questions can test your own position.

First, how many fixes can we apply in one week? What happens to our key systems when we do? Second, which systems have no test copy? Third, can every urgent patch be rolled back fast, and has anyone tried? Fourth, who sets the order when ten fixes arrive at once?

None of this argues for patching more slowly. Himes said the pace is vital. It argues for treating the patch process as a system. It needs testing, staffing and a plan for failure. Faster discovery does not help if the fix cannot land safely.

Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: CyberScoop.