
NSA's classified network goes down: what it says about change and recovery
The National Security Agency's classified internal network, NSA Net, went down on 17 November 2026, sources told CNN, with no evidence of a cyberattack and a software patch reportedly to blame. It follows a week of US outages and raises a familiar question about how change and recovery are controlled.
Mark FermorCTO, CMO and Founder, Firevault
Published 17 November 2026 · 5 min read
The network the US National Security Agency uses for its internal classified communications went down on Tuesday 17 November 2026, according to six people familiar with the matter who spoke to CNN.
The network, NSA Net, allows agency employees to communicate classified information internally. CNN's sources said there was no evidence of a cyberattack.
What happened
As the agency worked to understand the scope of the problem, it introduced staggered arrivals for personnel, CNN reported. A person familiar with the matter told Fox News that the network was experiencing an "intermittent outage", that critical communications remained intact and that the staggered start was intended to stop tens of thousands of employees trying to log in at the same time.
The same source said the agency had not lost critical communications capabilities and had numerous backup facilities available to maintain operations.
The reported cause
A person familiar with the incident later told the Wall Street Journal that the NSA was "simply updating its software to patch the system", that the network would only be offline temporarily and that there was no evidence of a cyberattack, according to Reuters reporting published by The Jerusalem Post.
The NSA had not commented publicly at the time of writing. The cause has not been officially confirmed, and this story is developing.
Communications with the president
A current and a former US official told CNN that the outage would not affect the agency's ability to communicate urgent intelligence to President Donald Trump, who is travelling in Asia. Both described multiple redundancies and backup networks that the government could use to communicate securely with the president.
The latest in a week of outages
The NSA disruption follows a run of major technology failures in the United States:
- Microsoft: a global outage last week left people unable to use Outlook email and Teams meetings. Microsoft attributed it to a combination of a "latent defect" and overwhelmed servers, The New Republic reported.
- Federal Aviation Administration: flights nationwide were grounded for hours on Friday 14 November after a systems failure that the FAA traced to a single router in Arkansas, CNN reported.
- United Airlines and JPMorgan Chase: on Monday 16 November, a technology issue delayed United departures and a software bug slowed Chase transactions. We covered both in US technology disruptions continue.
Homeland Security Secretary Markwayne Mullin told CNBC that the outages were not tied to cyberattacks. "They're pushing new technology on top of really old computer systems, and it just seems to overwhelm the system," he said, as quoted by Reuters.
There is no indication that any of these outages was caused by a cyberattack, and no evidence that they are connected.
Why this matters beyond the NSA
If the reported cause is correct, the lesson is a familiar one. Routine change is one of the most common causes of disruption. A patch is meant to reduce risk, but when it is applied to a system an entire organisation depends on, it can take that system offline.
Two details in the reporting also stand out. The agency reportedly had backup routes for its most critical communications, and it brought people back gradually rather than letting everyone reconnect at once. Recovery is not only about restoring a system. It is about controlling how, and in what order, people and connections return to it.
Every organisation that runs systems its people cannot work without should ask:
- Which updates touch systems the whole organisation depends on, and who approves when they happen?
- Is change confined to agreed windows, and what happens to a change attempted outside them?
- If a core network goes down, what do critical communications fall back to, and when was that last tested?
- When the system returns, how are users and connections brought back in a controlled order?
- Can we prove that our recovery copies are intact before we restore from them?
Where Firevault fits
Neither Control by Firevault nor Offline Secure Storage® would have prevented a faulty software update. Both address what happens around one.
Control by Firevault applies just-in-time access to the connections around critical systems. Paths for approved change exist when that work needs them and are physically disconnected the rest of the time. Our Plans for high-risk production changes and controlled post-incident reconnection set out how organisations make change and recovery deliberate, and the Defence Blueprint and Public Sector Blueprint apply the approach to government and defence environments.
Offline Secure Storage® keeps recovery copies on dedicated hardware that is physically disconnected and offline by default, so a known-good copy remains available if an update or an incident damages connected systems.
The NSA reportedly had backups for what mattered most and a plan for bringing people back. The question for everyone else is whether they could say the same before their next update, not after it.
Mark Fermor is CTO, CMO and Founder of Firevault. Explore Control by Firevault or talk to the team.
Questions
NSA Net is the highly classified network that the US National Security Agency uses for internal communications. According to CNN, it allows agency employees to communicate classified information internally.
CNN's sources said there was no evidence of a cyberattack. A person familiar with the incident told the Wall Street Journal that the agency was updating its software to patch the system. The NSA had not commented publicly at the time of writing, and the cause has not been officially confirmed.
A current and a former US official told CNN it would not affect the agency's ability to communicate urgent intelligence to President Trump, describing multiple redundancies and backup networks the government could use.
There is no evidence that they are connected, and none has been attributed to a cyberattack. Each has a different reported cause.
No. Neither Control by Firevault nor Offline Secure Storage® would have prevented a faulty software update. Control makes the connections around critical systems available only for approved work and controls how they return after an incident, and Offline Secure Storage® keeps physically disconnected recovery copies available if connected systems are damaged.

About the author
Mark FermorCTO, CMO and Founder of Firevault. Mark writes on physical control, offline storage and the incidents that show why both matter.
Why #OSS
Keep a clean copy out of reach.
Offline Secure Storage® keeps one copy physically disconnected at the hardware level between sessions.
Control
Govern the paths attackers depend on.
Physical, out-of-band control of selected network paths, composed into Control Plans and industry Blueprints.

Ready to start?
Create your Vault online.
Business Vaults from £360 a month inc VAT, on a 36-month commitment.
