STUXNET
Three years after it was discovered, Stuxnet, the first publicly disclosedcyberweapon, continues to baffle military strategists, computer security experts, political decision-makers, and the general public. A comfortable narrative has formed around the weapon: how it attacked the Iranian nuclear facility at Natanz, how it was designed to be undiscoverable, how it escaped from Natanz against its creators’ wishes. Major elements of that story are either incorrect or incomplete.
That’s
because Stuxnet is not really one weapon, but two. The vast majority of the
attention has been paid to Stuxnet’s smaller and simpler attack routine — the
one that changes the speeds of the rotors in a centrifuge, which is used to
enrich uranium. But the second and “forgotten” routine is about an order of
magnitude more complex and stealthy. It qualifies as a nightmare for those who
understand industrial control system security. And strangely, this more
sophisticated attack came first. The simpler, more familiar routine followed
only years later — and was discovered in comparatively short order.
With
Iran’s nuclear program back at the center of world debate, it’s helpful to
understand with more clarity the attempts to digitally sabotage that program.
Stuxnet’s actual impact on the Iranian nuclear program is unclear, if only for
the fact that no information is available on how many controllers were actually
infected. Nevertheless, forensic analysis can tell us what the attackers intended to
achieve, and how. I’ve spent the last three years
conducting that analysis — not just of the computer code, but of the physical characteristics
of the plant environment that was attacked and of the process that this nuclear
plant operates. What I’ve found is that the full picture, which includes the
first and lesser-known Stuxnet variant, invites a re-evaluation of the attack.
It turns out that it was far more dangerous than the cyberweapon that is now
lodged in the public’s imagination.
This new
Stuxnet variant was almost entirely different from the old one. For one
thing, it was much simpler and much less stealthy than its predecessor. It also
attacked a completely different component of the Natanz facility: the
centrifuge drive system that controls rotor speeds.
This new
Stuxnet spread differently too. The malware’s earlier version had to be
physically installed on a victim machine, most likely a portable engineering
system, or it had to be passed on a USB drive carrying an infected
configuration file for Siemens controllers. In other words, it needed to be
disseminated deliberately by an agent of the attackers.
The new
version self-replicated, spreading within trusted networks and via USB drive to
all sorts of computers, not just to those that had the Siemens configuration
software for controllers installed. This suggests that the attackers had lost
the capability to transport the malware to its destination by directly
infecting the systems of authorized personnel, or that the centrifuge drive
system was installed and configured by other parties to which direct access was
not possible.
What’s
more, Stuxnet suddenly became equipped with an array of previously undiscovered
weaknesses in Microsoft Windows software — so-called “zero day” flaws that can
fetch hundreds of thousands of dollars on the open market. The new Stuxnet also
came equipped with stolen digital certificates, which allowed the malicious
software to pose as legitimate driver software and thus not be rejected by
newer versions of the Windows operating system.
All this
indicates that a new organization began shaping Stuxnet — one with a stash of
valuable zero days and stolen certificates. In contrast, the development of the
overpressure attack can be viewed as the work of an in-group of top-notch
industrial control system security experts and coders who lived in an exotic
ecosystem quite remote from standard IT security. The overspeed attacks point
to the circle widening and acquiring a new center of gravity. If Stuxnet is
American-built — and, according to published reports, it most certainly is —
then there is only one logical location for this center of gravity: Fort Meade,
Maryland, the home of the National Security Agency.
But the
use of the multiple zero days came with a price. The new Stuxnet variant was
much easier to identify as malicious software than its predecessor was, because
it suddenly displayed very strange and very sophisticated behavior. In
comparison, the initial version looked pretty much like a legitimate software
project for Siemens industrial controllers used at Natanz; the only strange
thing was that a copyright notice and license terms were missing. The newer
version, equipped with a wealth of exploits that hackers can only dream about,
signaled to even the least vigilant anti-virus researcher that this was
something big, warranting a closer look.
Just like
its predecessor, the new attack operated periodically, about once per month,
but the trigger condition was much simpler. While in the overpressure attack
various process parameters were monitored to check for conditions that might
occur only once in a blue moon, the new attack was much more straightforward.
In other
words, blowing the cover of this online sabotage campaign came with benefits.
Uncovering Stuxnet was the end of the operation, but not necessarily the end of
its utility. Unlike traditional Pentagon hardware, one cannot display USB
drives at a military parade. The Stuxnet revelation showed the world what
cyberweapons could do in the hands of a superpower. It also saved America from
embarrassment. If another country — maybe even an adversary — had been first in
demonstrating proficiency in the digital domain, it would have been nothing
short of another Sputnik moment in U.S. history. So there were plenty of good
reasons not to sacrifice mission success for fear of detection.
We’re not
sure whether Stuxnet was disclosed intentionally. As with so many human
endeavors, it may simply have been an unintended side effect that turned out to
be critical. One thing we do know: It changed global military strategy in the
21st century.
Comments
Post a Comment