NSA Largely Back to Normal After PHP Patching Knocked Out Its Internal Network
The US National Security Agency has mostly returned to business as usual after patches to a widely used programming language caused an internal communications network to crash for much of the week, according to reporting by The Record.
A recorded message for the agency's workforce on Friday morning said the NSA was operating under "normal conditions, with exceptions". Some facilities remain under "Code Orange" for non-essential employees, which means delayed openings and, for some staff, a requirement to check in with supervisors.
The disruption hit NSANet, the system employees use to communicate classified information internally, for three days. It was attributed to maintenance affecting PHP, a ubiquitous programming language. Director of National Intelligence Jay Clayton said in a television interview that the patching which followed caused some systems not to come back up as expected. Workplace interruptions also occurred at NSA Georgia, though two sources said intelligence operations there, focused on the Middle East, were not negatively affected. The same sources said the outages did not limit the agency's ability to support President Donald Trump's trip to Asia.
Administration officials have insisted the problems are not the result of a cyberattack and are not connected to other recent IT problems affecting Microsoft products, airline travel and online banking services. The NSA did not immediately respond to a request for comment.
Why it matters
This shows that the patching process itself can take down critical systems, even in a well-resourced organisation, so the risk sits in how updates are deployed as well as in the flaws they fix. Any business that depends on PHP-based systems for internal communications or operations is exposed to the same pattern, where systems fail to restart after patching. It forces a decision about staged rollouts and tested recovery plans rather than a choice between patching and not patching.
What to do
- Stage PHP-related patches on a test or low-risk system before wider deployment.
- Confirm that systems restart cleanly after patching and keep a rollback plan ready.
- Identify which internal systems depend on PHP so you know what a failed patch could affect.