Stuxnet Struck Five Targets In Iran
Batblue writes "Researchers at Symantec said that the notorious Stuxnet worm targeted five separate organizations, and attacks against those objectives — all with a presence in Iran — started in June 2009, more than a year before independent experts raised the alarm."
That makes me feel sooo much better about the value of antivirus software.
Does slashdot's new interface support posting from a Babbage engine running OpenBSD?
It looks like Iran fraudulently elected President could be the next regime to fall in the Middle East.
Be honest - do you think this could possibly happen with an anti-islamic goverment in the United States. Do you think that watching the US Military kill massive amounts of civilians makes arabs more or less inclined to oppose their government?
Opposed demagogues at home and abroad. Ridicule Fox "News" and expose the current batch of Republican politicians for the retarded hypocrites they are.
If by "targetted" you mean "was released from/at" then yes. The point of the worm is to spread, probably to an air gapped system, so ironically the only systems one can be certain were not the final target were the one from which it was released.
> That makes me feel sooo much better about the value of antivirus software. Does slashdot's new interface support posting from a Babbage engine running OpenBSD?
1992 is calling, it wants its Windows virus back ...
"Researchers at Symantec said that the notorious Stuxnet worm targeted five separate organizations, and attacks against those objectives — all with a presence in Iran — started in June 2009, more than a year before independent experts raised the alarm."
What experts, none of these peopel have been able to produce an Operating System that is immune to "computer viruses" ..
"Cyberwar" is just a propaganda term, and doesn't really exist.
Right?
Best Slashdot Co
...is they'll never admit to the damage that was done, so you don't have to feel too bad about it. I'm sure there are still some who will happily tell you that Saddam is still in power.
Did Iran suddenly become an Arab country or something?
Tic-Tac-Toe, Global Thermonuclear War, and relationships all have the same winning move.
ATTN: Systems Integrators.
Guys, we can’t ignore this one. Stuxnet has taught the whole world what can be done. So it is now orders of magnitude more likely that an attacker could develop a modified version of it or design something similar to it in nature with the potential of doing much more damage than Stuxnet actually caused.
Here’s a worst-case scenario:
We’re now in a situation (unlikely, but potential) where an American systems integrator could connect his laptop to a plant in India, pick up something like this, and then bring it back to our in-house systems, where it would then spread to every system they ship. The control systems then start failing, accidents occur, etc.
I don’t think Systems Integrators are at risk to this particular threat (the original Stuxnet) for the following reasons:
The antivirus vendors are all over this one. Its probably in every signature scanner, and its behavioral tricks are probably being watched by all of the behavior-based malware products.
Microsoft issued a fix for the Windows exploit Stuxnet uses in early August (or sooner). So if you’ve done Windows Update since then you’re protected regardless of antivirus status.
The quick policy change I think we need to make is this:
1. Control systems products and Internet surfing must be 100% separated. So if you run Step7 or RSLogix on your native boot laptop, then you need to surf inside a VM. OR, If you surf on your main machine, all your controls programs must run inside VMs.
2. Develop a good firewall procedure for when we connect laptops to foreign plant networks (especially International). We need to block the laptop from accepting inbound IP traffic from any addresses other than the ones in our own panel. This won’t be a big deal to implement and maintain as we travel to different networks.
3. Keep all hosts and VM’s current on Critical updates from Microsoft.
4. Keep current updates on whichever antivirus or antimalware program you’re using. I actually think we’re safer overall if we keep a mix of security products in use (different ones on different machines) rather than picking one single vendor’s solution, because we’re more likely to learn we’ve been infected, even if its just 1 of the products we’re using that detected it. Then we can use appropriate measures to remove it from any systems that didn’t detect it.
Is this good enough for now? Too extreme? Other ideas?
There's no place like 127.0.0.1
Right now I think we're seeing some spill-over from the Glenn Beck thread.
Doing this kind of shit (and plain terrorist assassinations of physicists) only re-enforces Ahmadinejaad's power in Iran. It is not too difficult for state media there to display US, CIA and Israel as evil entities. So, this stupid "solution" to Iranian A-bomb problem actually made problem almost impossible to solve now.
839*929
The first rule of cyber-warfare is:
You do not talk about cyber-warfare.
The second rule of cyber-warfare is:
You do NOT talk about cyber-warfare!
(also, that was GP's point.)
It didn't actually target SCADA systems (though Siemens does make them) - it targetted their STEP 7 PLC systems. This is worse, it's a lower level control system. Google for Bruce Schneier's writing about Stuxnet for more good info.
The subject line wasn't long enough to substitute "Middle Eastern".
They tried to charge me 30 bucks for toilet paper, if that don't scream stuxnet worm I don't know what does!
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)