Stuxnet as precision weapon

Cyber rifle-shot at Iran’s nuclear program emerges in greater detail, but who pulled the trigger?

01/18/2011


Now that there’s been some time to investigate the Stuxnet story in greater detail, the message that this bit of malware was a weapon is emerging more clearly. There are still gaps in the narrative, but official statements recently say that it set Iran back by at least two years, mostly by running centrifuges out of control until they crashed. Moreover, Iran will have to replace much of its control equipment, or it can never be sure that all traces of the worm have been eradicated.

I got an email yesterday from someone who used to work for Siemens, that pointed me to a story in the NY Times on the same topic. It goes into much greater detail and says, for all practical purposes, that the U.S. and Israel created the worm to use on Iran. If you read well into the lengthy story, it takes us back to Siemens’ user group meeting in Chicago in July 2008, and brings up the fact that Siemens and Idaho National Labs did a session on cyber security and the vulnerabilities of control systems.

If you’re a big fan of conspiracy theories, the article would not stop you from thinking that just maybe Stuxnet’s designers got their idea from that session, and found the specific vulnerabilities they needed as a result of INL’s testing. Conclude what you will, but that idea seems pretty far-fetched. Siemens’ presentation was no different than you could hear at any number of user groups, and INL/CSSP has done testing on all sorts of industrial systems. Responsible people and organizations that discuss cyber security issues are universally dedicated to avoid publicizing specific vulnerabilities, and they do not glorify hackers. You could also find similar information in dozens of articles here at Control Engineering. (See below, or search on “cyber security.” You’ll have plenty to read.)

Maybe I’m missing something, but it seems to me that one practical moral of this story is that as sophisticated as Stuxnet is, some very simple technical and procedural precautions, that should be part of even the most basic cyber security program, would have protected you from all but the most determined and deliberate infiltration of your plant by someone bent on inserting this malware in your networks. And, if you feared that potential, Siemens did offer tools to make your systems more resistant to attack.

If you don’t have such precautions in place, it’s time to work on that before Stuxnet 2 (or 3 or 4 or 5…) makes its first appearance. How and when that might happen is anybody’s guess, except for the people who are creating it. Or maybe we should say creating them. I doubt there is only one in the works.

Also read Securing Legacy Control Systems.

Check out the Garrettcom Cyber Security eGuide for a collection of related articles.



No comments
The Engineers' Choice Awards highlight some of the best new control, instrumentation and automation products as chosen by...
Each year, a panel of Control Engineering editors and industry expert judges select the System Integrator of the Year Award winners.
The Engineering Leaders Under 40 program identifies and gives recognition to young engineers who...
Learn how to increase device reliability in harsh environments and decrease unplanned system downtime.
This eGuide contains a series of articles and videos that considers theoretical and practical; immediate needs and a look into the future.
Learn how to create value with re-use; gain productivity with lean automation and connectivity, and optimize panel design and construction.
Go deep: Automation tackles offshore oil challenges; Ethernet advice; Wireless robotics; Product exclusives; Digital edition exclusives
Lost in the gray scale? How to get effective HMIs; Best practices: Integrate old and new wireless systems; Smart software, networks; Service provider certifications
Fixing PID: Part 2: Tweaking controller strategy; Machine safety networks; Salary survey and career advice; Smart I/O architecture; Product exclusives
The Ask Control Engineering blog covers all aspects of automation, including motors, drives, sensors, motion control, machine control, and embedded systems.
Look at the basics of industrial wireless technologies, wireless concepts, wireless standards, and wireless best practices with Daniel E. Capano of Diversified Technical Services Inc.
Join this ongoing discussion of machine guarding topics, including solutions assessments, regulatory compliance, gap analysis...
This is a blog from the trenches – written by engineers who are implementing and upgrading control systems every day across every industry.
IMS Research, recently acquired by IHS Inc., is a leading independent supplier of market research and consultancy to the global electronics industry.

Find and connect with the most suitable service provider for your unique application. Start searching the Global System Integrator Database Now!

Case Study Database

Case Study Database

Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.

These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.

Click here to visit the Case Study Database and upload your case study.