Did Stuxnet Take Out 1,000 Centrifuges At Natanz?
AffidavitDonda writes "In late 2009 or early 2010, Iran decommissioned and replaced about 1,000 IR-1 centrifuges in the Fuel Enrichment Plant (FEP) at Natanz, implying that these centrifuges broke. Iran's IR-1 centrifuges often break, yet this level of breakage exceeded expectations and occurred during an extended period of relatively poor centrifuge performance. Although Iran has not admitted that Stuxnet attacked the Natanz centrifuge plant, it has acknowledged that its nuclear sites were subject to cyber attacks."
If this is for real, this targeting sounds like a big step in the cyber attack side of the world. I wonder how cyber defense will counter it.
Home of The Suki Series
It's interesting how US was jabbing so much about cyber warfare and how they need to defend themself, and still they're the first one to attack.
From TFA, the rumored culprit is not the USA, it is "IDF’s Military Intelligence Unit 8200".
Home of The Suki Series
Somewhere, some guy working for the CIA/NSA/TLA just shat himself laughing.
Sent from my CR-48
Just spent a minute at wikipedia...
Apparently the virus is Windows specific and targets industrial control systems manufactured by Siemens.
They have distributed a removal tool, which is dependent on current patching from Microsoft
Of course, this soooo many questions, like;
Who else uses the same Siemens controllers, should they be worried as well?
Who holds the keys to this thing?
What is preventing anybody else from hijacking the root kitted systems?
What are the chances of any Microsoft patches being poisoned by the author?
And finally... Why the heck are our friends at Siemens selling systems to the Iranians?
Wherever You Go, There You Are
What antivirus software would have protected the victims of this virus? Kaspersky? AVG? Windows Security Essentials? ClamAV?
While on the one hand, it is important to prevent infections from becoming a massive swarm with the ability to hammer away at particular locations in a DDOS, in this particular case it seems like specific machines were infected with the goal of harming them directly. Since these machines are running on specialized hardware, it doesn't really make sense to consider StuxNet a "swarm" virus. The swarming aspect only seems to have helped it spread in an organic way towards the targeted systems.
On the very end lay the centrifuges, but between those and the Internet lay Windows PCs. Would having Norton (or any other AV) running on startup have blocked this virus?
If none, then what hope do we really have of protecting ourselves from deliberate attacks on our network infrastructure?
Quite frightening, actually. (Unless Windows Security Essentials would have caught it.)
It also uses (i believe) 4 windows specific 0 day hacks. Usually a 'common' virus writer uses only one, because you can use the other 3 to make 3 more viruses. It really shows these people REALLY wanted this to work. and for it to infect as many systems as it could before caught and stopped. Siemens can sell to whomever they want. Iran can use those controllers for making plush teddy bears just as easily as for nuclear refinement. And the command/control servers for the virus were taken offline a while ago, so no-one holds the keys to deactivating virus anymore.
Violence is the last refuge of the incompetent. -- Isaac Asimov
Apparently the virus is Windows specific and targets industrial control systems manufactured by Siemens.
Why the hell Siemens is running Windows for such kind of application, to begin with?
And finally... Why the heck are our friends at Siemens selling systems to the Iranians?
Friends?
Neither companies nor government have friends, they have interests.
No, AV software would not have protected those systems from infection because the virus didn't attack the OS or any 'normal' program that an AV vendor would be used to protecting, it attacked a very specific installation of an industrial control package. Better computer hygine like not taking media from lower security systems to higher security ones would have prevented the infection of the vulnerable machines but even the NSA has admitted that they do not have 100% control over such procedures.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
Iran has stepped up efforts at helping Hamas, Hezbollah, the Taliban and is now releasing all of its Al Qaeda terrorists back into the wilds of the Middle East, the question we should be asking, was this attack worth it if terrorism increased because of it? From what I have seen, no, we are now dealing with Iran supplying larger and larger munitions to the Taliban, 'Charlie Wilson's War' is going to have a sequel and this time the protagonist is going to be Iranian.
An Education is the Font of All Liberty
The IR-1 is an older model centrifuge. It's basically a copy of an old URENCO design. Iran has an IR-2 and an IR-3 model, which use carbon fibre rotors, and new installations use those. Iran has at least three enrichment plants, incidentally, and they're all different. Various reports indicate replacement of the older models by newer ones, so some of this might be a routine phase-out.
I think Iran -- or any other country -- would be pleased to have these kind of rumors about the damage done circulating. Disinformation or uncertainty as to the present condition of their activities can only benefit them, especially if it causes the enemy to underestimate their power. This assumes that Stux wasn't feeding back information about its activity or that another good source doesn't exist.
My take on this story was that the Siemens controllers were the problem. The centrifuges quit working right because the controllers went nuts, and then the controllers were careful to hide their defect.
So if Iran examined the controllers and centrifuges and figured (wrongly) that the centrifuges were the problem and replaced them, wouldn't the controllers just wreck the new ones as well? And if so, wouldn't that cause Iran to spend a lot of time replacing centrifuges again and again? It seems like that could account for some of the buying.
And of course, once the actual problem is figured out, then you need to replace the controllers and probably the centrifuges that got broken the second or third time around, and of course figure out how to keep the whole thing from happening again. Sure, you can replace the rogue controllers but how did they go bad to start with? If you don't know, this could cause a lot of extreme paranoia.
How Iran actually reacted is not clear to me, but I know what would happen if this occurred in a US factory.
If a machine broke, you'd replace the machine. If it broke again, you'd replace it again and start getting mad. If it broke again, then maybe you'd look at the controller. If it tests OK -and why would it lie to you- then you replace the centrifuge again. Etc. It might take a relatively long time to figure out that the controller is actually the problem AND that it was deliberately being subtle about it to avoid detection. The assumption with machines is that they don't lie to you. If they are good or bad, generally they will be straightforward to sort out via testing or diags.
So to start with, you have to accept the concept that yes, they can lie, before the source of the problem can begin to be understood much less dealt with.
Sig for hire.
Because normal people consider removable media to contain data but MS and by extension Windows considers it something that must be executed without gaining consent from or even informing the user.
Windows must be kept locked up in a padded cell and straitjacket. If it sees a bottle marked poison, it will drink it. If it sees a pencil it'll jam it up it's nose. Give it a pillow and it'll suffocate itself.
1. There are a lot of perfectly legitimate uses for industrial controllers. 2. Corporations have no friends, only avarice. They may act friend-like if you are currently the highest bidder but the moment they have your money they'll turn to the next highest bidder.
Why the hell Siemens is running Windows for such kind of application, to begin with?
My question exactly. Twenty years ago the standard system for such applications was the VAX/VMS and I still have to see any successful virus for the VAX/VMS. There have existed many proof-of-concept viruses and worms written for VMS, sure, but never one that caused any widespread damage.
There's a good analysis of the reasons for this here. In simple words, VMS is not quite as user-friendly as Windows and that makes all the difference.
That's the reason why I wish the "year of Linux on the desktop" will never come. We don't need an Eternal September on the Linux desktop.
You're not a high profile target.
Could your apartment door keep out an exceptional burglar who specialized in breaking into high profile objects? Could your home safe stop someone who is an expert in opening bank safes? Would someone trained in defeating multi layer security systems trip your alarm system at home?
I think none of those answers could be answered positively.
But these people do not break into your home. They got better, more profitable, targets to rob.
Likewise, nobody would "waste" 4 0day vulnerabilities just to infect YOU, and ONLY YOU (a blanket attack on multiple, nonspecific, targets is usually trivial to discover through early warning means and also quite easy to protect against).
As odd as it may sound, there's safety in numbers. The garden variety trojan is not targeted. They don't care too much who they infect, their goal is not a specific target, their goal is to infect as many machines as possible, for various reasons, but no matter what the reason, it's better (for them) to infect many instead of a specific target. Phishing, botnets, they all need many, but not specific, machines.
This is not the case here. The target was very specific and I am actually quite sure that infecting anything else with this trojan would actually have been seen as a flaw in the whole operation.
I'd guess that the malware was installed specifically where it should strike, not in the usual "release and wait" way but targeted and planted. In other words, I'd guess it would have taken a physical person to be physically present to get this rolling.
This is nothing that would affect you, or any Joe Randomsurfer for that matter.
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Eset has a particularly interesting paper on Stuxnet which may interest you.
A thistle is a fat salad for an ass's mouth...
And finally... Why the heck are our friends at Siemens selling systems to the Iranians?
Because otherwise the Russians would.
And then, good luck getting right the cyrillic encoding for the default password.
ABB still support a huge number of plants running on "Conductor VMS" systems. They are so stable that the customers are reluctant to change ;)
The problem with this is that there are few spare parts, few people with the needed skills and even fewer people who know how to -properly- set up the system.
The new HMI system is called 800xA and runs on top of Windows 2003 Server. Why?
I suspect money... And the ability to actually run it in a few years time when the old DEC hardware finally goes out of production :p
What people fail to get is that the control system functions do not run on the windows servers. The control loops and logic runs on dedicated controllers out in the field. What runs on the windows machines is the HMI or interface for operators. Getting access to the windows system doesnt mean you get access to the control functionality...
And for christ sake people, properly secure your removable media damnit..... You run the systems isolated for a reason! >.