The one-paragraph verdict

This is investigative journalism that actually respects the engineering. Zetter walks from the first odd Belarusian detection down to the centrifuge PLC payload, and the reporting is dense with primary sources — Symantec, Kaspersky, Langner — rather than hand-waving. The praise reviewers repeat is fair: it reads like a thriller and stays accurate, which is rare. The recurring criticism is also fair: it sags in the middle, repeats itself, and the export-control and cyberweapon-policy chapters drag where the forensic chapters fly. Read past the slow stretch; the spine is excellent.

Who should read it

Anyone who builds, defends, or threat-models systems that touch the physical world — ICS/SCADA, OT, anything with a PLC — should read it for the air-gap-is-not-a-control lesson alone. Security engineers wanting a concrete nation-state case study will get more here than from a dozen vendor whitepapers. People hunting a hands-on reverse-engineering tutorial should look elsewhere; this is narrative, not a lab manual.

Where it earned its place

The book’s core lesson — that trust boundaries you assume are impassable get crossed anyway — is exactly what I argue in Container security in .NET: the supply chain and the runtime boundary are the soft targets, not the obvious perimeter. Stuxnet rode signed drivers and removable media past an air gap; the modern analogue is a poisoned base image riding your CI past every network control.

Skip it if…

You only want the technical post-mortem — the Symantec dossier and Langner’s analysis are shorter and free. And if policy-history chapters bore you, expect to skim a third of it.