Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsTechnical analyses of Stuxnet’s code strongly support the conclusion that it was designed to target Siemens industrial-control systems associated with Iran’s Natanz uranium-enrichment plant. The evidence is specific to centrifuge operations, but it does not establish who created or sponsored the malware, and the reported physical impact remains uncertain.
Was Stuxnet created to attack Iran?
The technical evidence supports Iran as the intended target, particularly Natanz, but “created to attack Iran” should be understood as an evidence-based inference about the malware’s design—not proof of its authorship. Stuxnet acted against industrial-control equipment, rather than being aimed primarily at ordinary personal-computer use. The analyses discussed here focus on Siemens programmable logic controllers (PLCs), which control industrial processes.
The Institute for Science and International Security (ISIS) compared attack-sequence code for a Siemens S7-315 PLC connected to frequency converters with the operating characteristics of IR-1 centrifuges at Natanz. The specified rotational frequencies matched those characteristics. ISIS also described another sequence whose code appeared to contain an exact copy of the Natanz Fuel Enrichment Plant cascade. These details make Natanz a compelling target inference, but code analysis alone cannot identify the people or organization behind the malware. ISIS’s February 15, 2011 technical assessment explains both the target comparison and the limits of what could be determined.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Verbatim DVD+R DL 8.5GB 8X AZO with Branded Surface - 15Pk Spindle | $39.99 | Buy on Amazon |
Was Natanz the target of Stuxnet?
Evidence from more than one Stuxnet version points toward uranium-processing operations at Natanz, but the findings should not be collapsed into a single account of one sample.
| Analysis | Version or sample | PLC and process described | What the finding supports |
|---|---|---|---|
| ISIS, February 15, 2011 | The sample discussed in its report | S7-315 attack sequences associated with frequency converters; a separate sequence appeared to reproduce the Natanz cascade. ISIS also discussed 417 code in the sample. | The S7-315 code’s frequencies aligned with IR-1 centrifuge characteristics. ISIS said the 417 code in its sample was not activated and that key data needed to determine exactly what was affected or sabotaged was missing. ISIS report |
| Symantec, February 26, 2013 | An earlier version, Stuxnet 0.5 | Siemens 417 PLC devices associated with uranium processing at Natanz | Symantec described operational 417 attack code in this earlier version. That finding concerns a different version from the sample discussed by ISIS. Symantec’s Stuxnet 0.5 analysis |
The apparent difference over the 417 code is therefore a version-and-sample distinction: ISIS described inactive code in the sample it examined, while Symantec reported operational code in an earlier version. “Operational” describes the code’s capability; it does not, by itself, establish exactly what happened at a facility.
#1 Best Overall
- 15 high-grade non-rewritable DVD+R discs with a one hundred year archival life; OEM drive certified
- Advanced AZO recording dye optimizes read/write performance and is supported by high speed double layer writers.
- Blazing speeds up to 10X allow for 8.5GB files to record in approximately 12-15 minutes and store 4 hours of DVD quality television and video
- Ideal for archiving home movies. Compatible with most DVD-R and DVD+R drives including Pioneer, Apple, Sony, Dell, LG, HP, Lenovo and others
- Verbatim has been a leader in data storage technology since 1969, and guarantees this product with a limited lifetime warranty and technical support
What is known about Stuxnet’s authors and impact?
Authorship and responsibility
The code evidence can indicate what equipment a malware sample was designed to affect, but it cannot prove who wrote it or who ordered its use. A Congressional Research Service report dated December 9, 2010, called Iran an apparent likely target while stating that the actual target was unknown. It also described attribution as difficult and recorded that no country or group had claimed responsibility at that time. That is a description of the public record in 2010, not a statement about present-day claims. Read the CRS report hosted by the National Security Archive.
Physical effects
The available account does not establish a verified measure of damage at Natanz. The CRS report recounted Iranian officials’ claims of minor centrifuge problems and other reports of a possible interruption, but concluded that the impact on nuclear facilities was unclear. Those reports should not be treated as a settled damage figure. The ISIS analysis likewise noted that key data needed to determine precisely what was affected or sabotaged was missing.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
