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."
Iranians aren't arabs, so whether something "makes arabs more or less inclined" is irrelevant to them.
"Cyberwar" is just a propaganda term, and doesn't really exist.
Right?
Best Slashdot Co
Of course, most anti-virus software is reactionary based off previous viri found in the wild. They're reversed engineered and a solution is rolled up into the next set of scheduled updates. Most of the time, anti-virus is good to have for the home user and/or small and medium business. But if your organization is explicitly targeted with custom code, most anti-virus software will do squat to help unless you provide them exploited code to reverse engineer.
Life is not for the lazy.
Did Iran suddenly become an Arab country or something?
Tic-Tac-Toe, Global Thermonuclear War, and relationships all have the same winning move.
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
You first paragraph is great. The second is insane.
Any language which gives the programmer the power to write a good program, also gives the power to write a poor one. A language which was 'immune to exploitation' would be a language which was impossible to write a decent (non-trivial) program in as well. It would be so crippled that nothing of consequence could be done without invoking incredible overhead and redirection costs.
Security is the job of the system architect first, the coder second, the user third. To create a system where all three can neglect their responsibility without consequence all three would have to be essentially neutered in favour of a god-like compiler that, even if perfectly executed, would still produce the most bloated object code imaginable. And then what happens when someone finds a flaw in the compiler itself? Instead of vulnerabilities affecting a single program, they would affect a whole class of programs, and even better, a class of programs likely exempted from normal oversight and limitations since they are presumed secure.
The only entities that would benefit from that would be the hardware manufacturers (since you would need incredible hardware to run any non-trivial program produced in this way) and the crackers.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Friends don't let friends enable ecmascript.
"Then we can use appropriate measures to remove it from any systems that didnâ(TM)t detect it. Is this good enough for now? Too extreme? Other ideas?"
You need to block and be able to reset/restore any effected system quickly as well. If you have to clean up afterwords, the deed/damage may already be done. Your idea of virtualization is a good one, but it does not go far enough, in that VMs are not security but simulation with potential for leakage in one form or another.
Also, relying on AVs as your core protection ignores the fact that you are only going to snag 30% - 50% of the total population of potential malware on average; and when talking about critical industrial control systems, this represents and unacceptable level of risk. This means that you need to research a more robust, intelligent layering approach where the weaknesses in any given security measure/solution are backed up by the other solutions and control measures you use in the whole.
So this would be virtualization with antiexecute/HIPS, System/image restore on the fly, and physical/policy restrictions on dangerous activities that could lead to infection. It is not enough to be reactive which has been proven over and over again.
Coldmoon over Dark water...
Thinking that the lack of ability to directly manipulate pointers makes better programs strikes me as very much like thinking that non-removable training-wheels would make better bicycles.
Also I cannot help but laugh when I see people calling C++ a "low level" language. You realise the original "high-level" language was Assembler?
=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Friends don't let friends enable ecmascript.
in C# you can manipulate pointers and p/invoke to unmanaged code for performance critical bits of your app... these are just not capabilities that are not needed for most problems.