National Security Technology

NSA Georgia Staff Used Backups to Reach Middle East Colleagues During Network Outage

CNN reported that Georgia personnel lost their usual classified channel to deployed colleagues but kept sharing information through backups. Full restoration was not established in Wednesday’s reports.

Aerial view of National Security Agency headquarters buildings and parking lots at Fort Meade, Maryland.
File photo: File photo of the National Security Agency headquarters at Fort Meade, Maryland. The reported communications disruption affected NSA personnel at a facility in Georgia.National Security AgencyPhoto sourceLicense

NSA personnel at a Georgia facility that supports Middle East intelligence work could not use the classified NSANet network to communicate with colleagues deployed in the region, CNN reported November 18. They shared information through backup channels instead. The newly reported effect identifies what changed for those personnel: their usual communications route was unavailable, but information continued to move.

The NSA said November 17 that scheduled routine maintenance had temporarily degraded some internal systems. It said mission-critical capabilities remained operational and cited multiple layers of redundancy. CNN separately reported that the agency’s most sensitive intelligence-gathering systems continued to function. The accounts distinguish a disruption to communications with deployed personnel from a halt to intelligence collection.

Working network, incomplete return to normal

CNN reported Wednesday that many employees had not resumed normal work. A senior administration official told CNN that restoration was taking longer than expected. A source told The Record on November 18 that the network was working, though employee returns remained staggered. That account did not establish that ordinary access had returned for everyone.

CNN cited officials who said the trouble appeared connected to updates addressing PHP vulnerabilities rather than an attack. The NSA’s public statement attributed the degradation to scheduled maintenance without detailing the technical failure. Wednesday’s reporting established continued information-sharing through backups, but not a time for full restoration of normal access.

Read the source material

Sources & references

How we work with sources ↗

Search the publication

Search the articles published on this site.