@War: One Citation Does Not Verify the Whole Story

“Google hacked this server” is a short line in the “Corporate Counterattack” chapter of Shane Harris’s @War. It sounds as definite as the date of the company’s public announcement about an attack. But the route to verification is different: the note points to the journalist’s conversation with a former intelligence official in February 2013. Readers can open Google’s post; they cannot similarly open Harris’s private conversation.

That does not automatically make the testimony false. It makes visible a distinction between a published document, a source’s account and the journalist’s own conclusion. A book about the military–Internet complex—the links between intelligence, armed forces and technology businesses—rewards reading that keeps these categories apart.

What the Public Post Confirms

On 12 January 2010, Google reported a targeted attack on its infrastructure originating from China, theft of intellectual property and cooperation with the relevant US authorities. That is available in David Drummond’s historical post on the official company blog.[4]

The document establishes what the company publicly said. It does not thereby become independent proof of every operational detail or everything the book goes on to recount. A statement about cooperation with government does not, by itself, disclose the terms of secret information-sharing. Nor is an attack’s geographical origin identical to establishing who directed it.

Harris does not rely on that post alone. His notes lead to other reporting and his own interviews. This is why they should be read alongside the chapter: they reveal not just that a citation exists, but which part of the account it supports.

Protect the Source, Explain the Basis of Knowledge

In “A Note on Sources,” Harris explains why some interviewees remain unnamed. An identity—and sometimes even an institution’s name—could put a person’s career or liberty at risk. He also promises to explain why a source deserves trust without supplying identifying details.

This is a necessary distinction: protecting someone’s identity does not relieve an author of explaining their competence. Readers, meanwhile, should not pretend they have the same access to testimony as the journalist. Part of the checking must be delegated to Harris. Attentive reading notices where that happens.

Later in the Google chapter comes a further level: the author’s inference. From the cooperation agreement and a reference to special solutions, Harris infers the possible development of intrusion-detection technology. He explicitly says these allow him confidently to infer it. Infer should not silently become establish through a published record. Even a reasoned reconstruction is not a disclosed technical specification.

Where a Story Must Not Become Permission

The Ukrainian edition makes a considerably bolder legal statement while describing access to another server: the line of illegality would supposedly be crossed only by deleting or destroying data. This cannot be borrowed as a present-day rule for lawful counterattack.

The official text of 18 USC §1030(a)(2) includes certain cases of obtaining information through access without authorisation or in excess of authorised access. Damage to data is not the only basis for liability described by the statute. The version consulted incorporates laws in effect through 9 October 2026.[6]

This is not a finding that Google committed a crime in the episode. Such a finding would require verified circumstances, permissions and authority; the statute also provides for certain lawfully authorised law-enforcement and intelligence activities. It is enough, however, to reject the convenient formula that no destruction means legality. An account of a famous company does not license the reader to repeat its actions.

Why Read the Ending?

In “At Dawn,” Harris moves from investigation to prediction and political argument. He asks who will gain information and power in exchange for a promise of security: government, providers or private network defenders. The issue is no longer simply how one attack happened, but who gets to make the rules.

The transition matters. A historical scene, an interview, an inference about a hidden technology and a prediction about the next decade require different kinds of checking. A dramatic narrative does not make them equally well established.

This route offers practice in reading cybersecurity accounts: separate a public statement from attribution of an attacker, testimony from an accessible document, and technical capability from legal permission. It is neither an assessment of present-day intelligence operations nor advice to undertake private counterattacks.

Before Reading

Book and author: @War — Shane Harris. The source used here is the Ukrainian translation, titled ВІЙН@: битви в кіберпросторі, not an English edition.

Edition: the Ukrainian edition jointly published by Nika-Centre and Anetta Antonenko Publishers, 2019, translated by Olena Zamoiska. Details confirmed against the publisher’s record.[2]

Main idea: a citation matters, but we must also know exactly which part of a claim it allows us to check.

Relevance: a way to trace an evidence chain, not present-day confirmation of every prediction, technical account or legal formula in the book.

Read / pass: read for the history of intelligence–business relations and practice in critically reading investigations. Do not use it in place of current technical instructions, legal advice or verified information about ongoing operations.

Verdict: read selectively, with the notes. Route: “A Note on Sources” → chapter 11, “Corporate Counterattack,” with its source notes → chapter 14, “At Dawn.” Begin with the author’s working rules, examine a concrete application, then watch the shift from description to prediction.

Sources and Scope

“A Note on Sources,” chapters 11 and 14 and the notes to chapter 11 were read in full in the Ukrainian edition. S. P. Popovych’s separate foreword was also read, not attributed to Harris. The Google post is treated as a historical statement dated 12 January 2010, not proof of a secret operation. The legal text was checked on 19 October 2026 against the official version current through 9 October. This article neither establishes every operational fact nor assesses every forecast, and it does not turn the book’s then-current descriptions into accounts of the present. Short English quotations are translated here from the Ukrainian text.

Sources

[2] https://anetta-publishers.com/books/112 — Шейн Гарріс — ВІЙН@: сторінка видавця [4] https://googleblog.blogspot.com/2010/01/new-approach-to-china.html — Google — A new approach to China, 12 January 2010 [6] https://uscode.house.gov/us/usc/119-121/t18/s1030 — OLRC — 18 USC 1030, current code route