Satya Nadella, the chief executive of Microsoft ($MSFT), used his appearance at The New York Times‘ DealBook Summit on Wednesday to warn that much of the country’s critical infrastructure cannot be patched. “Remember, there is a lot of stuff in our critical infrastructure that’s unpatchable,” he said, pointing to “all the firmware and the chillers” and “the HVAC systems everywhere else.” Firmware is the code built into a device’s hardware, and a chiller is the cooling unit that prevents a data center’s servers from overheating. His next sentence made it a security problem: “So all of that, by the way, they’re on the internet.”
Nadella said AI has made sophisticated cyberattacks much easier to launch. He also described transportation systems with a lot of equipment that is “discoverable but with unpatchable firmware,” which means an attacker can find it online and nobody can fix the code inside it. Officials have denied that a recent wave of large-scale failures, including one involving Microsoft Outlook, came from attacks, so the threat he described is a risk rather than a proven cause.
That risk changes who has to act. When a device cannot be patched, defending it stops being the software maker’s job and becomes the job of the people who own and wire it, because the only options left are to cut it off, watch it, or replace it.
Why Nobody Can Ship the Fix
A modern system is often a collection of parts from different makers joined by standard connections, which lets each maker change its own part without waiting on anyone else1. The same arrangement means no single maker can change the whole. A chiller might run firmware from one company, answer to a control system from a second, and reach the internet through a network that a third set up. A flaw in that firmware waits on the one company that wrote it, and only if it still supports the device.
Even code that can be patched is under strain. “We now have a very powerful tool that finds vulnerabilities,” Nadella said, and he noted that companies used to have time to test a patch before putting it into service. That time is gone: “The patch [now] needs to go instantly from being available to being patched in production, because it’s being exploited in the wild, right? So that’s going to create instability.” If the fastest available fix brings instability, a device with no fix at all has nothing to rush.
Connecting Was the Decision That Stuck
The article states the cause plainly: the smartification of the economy, in which ordinary devices were hooked up to the internet, “is now causing tremendous headaches.” Nobody wrote bad code on purpose here. Someone chose to put a cooling unit online so it could be watched and adjusted from somewhere else, and that choice outlasted the code’s support.
Teiva Harsanyi’s guide to complex systems separates one-way doors, decisions that can’t be undone and deserve care, from two-way doors that can be reversed cheaply. Connecting a chiller looked like a two-way door, since a cable can be unplugged. The catch is that remote control was the reason to connect it, so unplugging it gives up the benefit that justified the cable. The defense Nadella’s warning points to is to make that door swing both ways again: put equipment that cannot be fixed on its own separate network, where it can be cut off without the building losing sight of it.
Who Pays to Close the Door
That work falls on owners of buildings and data centers, and Microsoft is one of them. Nadella said Microsoft had put out an incident response and would take “all of the learnings, both upstream architectural, as well as operational,” and fix the problem. On unpatchable equipment he went further: “So we’ll have to really modernize for sure.” Modernizing a chiller means replacing a machine, not downloading an update, and the owner pays for the machine.
Because the burden sits with owners, data center operators, Microsoft included, could start treating the network around each chiller as part of the chiller. Buyers of building equipment may ask how a unit can be isolated or taken offline as routinely as they ask what it costs to run, and makers with a good answer could win those contracts. Nadella’s two tasks, to “detect and then defend in real time,” would then apply to the wiring around a device as much as to the code inside it.
Firmware that nobody can fix stays defensible only while someone can afford to unplug it, and Nadella’s warning about chillers and HVAC systems is that the someone is now the owner.
Sources
“Amidst fears of AI cyberattacks, Satya Nadella says lots of critical infrastructure is ‘unpatchable’.” techcrunch.com.
Harsanyi, Teiva. Working on Complex Systems.
1 Ulrich, Karl. Design.
Leave a Reply