Blog · Review Essay · May 2026

Surveillance Valley and the Military Internet

Yasha Levine's Surveillance Valley is a hostile history of the internet's innocence story. Its core claim is that networked computing did not become a surveillance system by accident after a pure open web was corrupted. It grew inside military research, counterinsurgency ambition, federal procurement, privatized data businesses, and the recurring dream of seeing social life clearly enough to predict and control it. The book is not always careful enough with its strongest claims, but it is useful precisely where the official mythology is weakest: it asks what kind of politics were already present in the infrastructure.

The Book

Surveillance Valley: The Secret Military History of the Internet was published by PublicAffairs on February 6, 2018. Hachette's PublicAffairs record lists the book as political nonfiction in privacy and surveillance, and Kirkus records the hardback at 384 pages with ISBN 978-1-61039-802-2.

Levine is an investigative journalist whose book argues against the standard garage-and-campus myth of the internet. In that familiar story, the network begins as academic openness, becomes entrepreneurial liberation, and is later damaged by surveillance capitalism, state monitoring, and platform monopoly. Surveillance Valley reverses the timeline. It treats surveillance, military research, and social prediction as founding conditions rather than late betrayals.

That makes the book a useful companion to The Age of Surveillance Capitalism, The Net Delusion, Consent of the Networked, Protocol, and The Closed World. Its question is blunt: what if the network was never politically neutral infrastructure waiting for users to decide its meaning?

The Origin Story Problem

The internet's public mythology often begins with decentralization. ARPANET, packet switching, TCP/IP, academic collaboration, open standards, and hacker culture are made to stand for a politics of freedom. That story is not false, but it is selective. The Internet Society's historical account emphasizes DARPA funding, packet-switching work, the 1968 request for Interface Message Processors, and ARPANET's role as research infrastructure. The National Science Foundation similarly describes DARPA-funded researchers expanding ARPANET and developing TCP/IP before NSFNET and commercial networks helped carry the internet outward.

Levine asks readers to hold the same facts at a different angle. DARPA was not a neutral benefactor floating outside American military power. Cold War command systems, Vietnam-era counterinsurgency, domestic unrest, behavioral science, and defense-funded computing all shaped what networked information seemed useful for. Computers promised coordination, communication, logistics, database analysis, and prediction. Those are practical capacities. They are also capacities of administration and control.

The strongest version of Levine's argument is not that every engineer secretly designed a police machine. It is that infrastructure inherits institutional purposes. A network built through defense funding, research contracts, classified needs, and strategic fantasies will carry traces of those worlds even when later users build open communities on top of it.

Surveillance as Infrastructure

The book becomes most useful when it treats surveillance as an infrastructure problem rather than a scandal problem. A scandal suggests an exception: a bad program, a secret database, a corrupt agency, a breach of policy. Infrastructure suggests something more durable: logging, identification, routing, authentication, advertising markets, cloud contracts, platform analytics, predictive policing, intelligence partnerships, and default data retention.

That distinction matters because the modern internet does not need one central watcher to produce surveillance. It produces observation through ordinary operation. Search needs query logs. Social media needs graphs and behavioral signals. Advertising needs profiles. Security needs telemetry. Fraud detection needs fingerprints. Cloud providers need administrative visibility. Mobile operating systems need location, identity, app, and notification channels. The same data can support convenience, personalization, safety, market power, and state access.

Levine's phrase "military-digital complex" is polemical, but the underlying pattern is concrete: public agencies, defense contractors, universities, startups, platforms, and intelligence services repeatedly exchange money, personnel, tools, datasets, and legitimacy. The boundary between public surveillance and private surveillance is therefore less clean than ordinary privacy debates suggest. A platform can be a consumer service, an advertising broker, an infrastructure provider, and a government contractor at the same time.

The Privacy Trap

One of the book's most controversial moves is its treatment of the privacy and encryption world. Levine argues that tools associated with resistance can themselves be entangled with state funding, intelligence priorities, or a narrow theory of privacy that leaves platform business models intact. Kirkus found parts of this argument provocative but not entirely persuasive, especially where Levine links privacy technologies too broadly to intelligence interests. The Guardian review also questioned whether he collapses corporate, military, and national agendas into one oversized explanation.

Still, the underlying warning is valuable. Privacy cannot be reduced to an app choice. A person may use encrypted messaging and still live inside advertising identifiers, data brokers, workplace monitoring, cloud metadata, payment trails, location systems, school platforms, border databases, and predictive scores. Encryption can protect content while leaving relationship patterns, device identity, timing, social graph, and institutional dependence exposed.

That is not an argument against privacy tools. It is an argument against privacy theater. Tools matter, but they cannot carry the whole political burden when the business model, procurement system, legal regime, and infrastructure layer continue to reward extraction.

The AI-Age Reading

Read in 2026, Surveillance Valley has become more relevant because AI turns old surveillance capacity into model input, agent memory, synthetic judgment, and automated action.

The pre-AI internet could watch, sort, recommend, and sell. The AI-era internet can infer, summarize, classify, generate, persuade, triage, and delegate. Logs become training data. Profiles become personalization substrates. Search histories become intent models. Workplace telemetry becomes productivity judgment. Customer-service transcripts become behavioral prediction. Public-sector records become decision support. Military and intelligence interest returns through autonomous systems, cyber operations, targeting support, disinformation analysis, and command platforms.

This makes Levine's infrastructure reading sharper than a privacy panic. The central issue is not only whether someone is spying. It is whether a society's nervous system is being built so that observation naturally flows into prediction and prediction naturally flows into intervention. Once that chain exists, every institution is tempted to ask for more legibility: more data, more sensors, more scoring, more preemption, more automated control.

AI also changes the cultural side of the story. The early internet myth promised liberation through connection. The AI platform myth often promises liberation through delegation: let the system read, remember, decide, negotiate, optimize, and act. But delegation without power analysis can make users more dependent on the very infrastructures that classify them.

Where the Book Needs Friction

Surveillance Valley is strongest as a corrective myth-breaker and weakest when it risks becoming a counter-myth of its own. Los Angeles Review of Books praised the need for better histories of computing while warning that Levine does not always back the largest conclusions with enough evidence. That criticism should be taken seriously. A history that replaces heroic garage folklore with totalized military folklore can still flatten the messy pluralism of technical development.

ARPANET was defense-funded, but it was also shaped by university researchers, open protocol work, competing technical cultures, public science, commercial pressures, users, standards bodies, and later civic uses that were not reducible to counterinsurgency. The web became a surveillance machine, but it also became a library, organizing tool, publishing medium, disability access layer, diaspora connector, mutual-aid channel, and technical commons. A good political history has to keep both truths in frame.

The book also sometimes treats institutional entanglement as moral identity. Funding, contracting, influence, and alignment matter, but they are not all the same thing. A privacy tool can receive government-linked support and still provide real protection in some contexts. A platform can serve state interests and still contain internal conflicts among engineers, users, regulators, advertisers, and civil-society critics. The point is to map power precisely, not to make every connection prove the same conclusion.

The Site Reading

The practical lesson is to audit origin stories.

When a technology arrives wrapped in liberation language, ask what institutions paid for it, what problems they needed solved, what data it must collect to function, what kinds of users become most legible, who can compel access, who can refuse, and what happens when the tool is connected to predictive models and automated action.

For AI governance, this means privacy policy is not enough. Procurement records, data-retention rules, model-training boundaries, audit logs, user-export rights, public-interest alternatives, labor protections, appeal channels, and vendor exit plans all belong in the same conversation. A system that observes people at scale and then recommends or acts upon them is already a political institution, even when it presents itself as a consumer convenience.

Surveillance Valley should be read with skepticism, but not dismissed. Its value is not that every claim lands cleanly. Its value is that it breaks the habit of treating the network as innocent until misused. Some tools are born with institutional memory. The work is to make that memory visible before it becomes the environment everyone has to breathe.

Sources

Book links are paid affiliate links. As an Amazon Associate I earn from qualifying purchases.


Return to Blog · Return to Books