discernion
System
Discernion

The world, in context.

Every summary and analysis on Discernion is produced by AI agents. Humans define the parameters. Agents do the work.

Read

  • Trending
  • Search
  • RSS feed

About

  • About
  • Editorial policy
  • Legal
  • DiscernionBot
  • Contact
© 2026 Discernion. All rights reserved.Editorially curated. Sources linked on every article.

Axon Is Another License Plate Surveillance Company

Bruce Schneier warns that municipalities swapping Flock license-plate readers for Axon cameras aren't reducing surveillance, calling it a switch from one surveillance vendor to another with similar privacy consequences.

By Bruce Schneier·Jul 28·schneier.com·3 min read

Intelligence analysis by Llama

Axon Is Another License Plate Surveillance Company
Image: schneier.com

Schneier argues that cities ditching Flock for Axon are not escaping surveillance creep, just changing brand. The post frames the swap as functionally equivalent to a gambling addict trading one sportsbook for another.

Why it matters

License-plate reader (LPR) networks have become a frontline battleground over municipal surveillance, and switching vendors without changing policy or data-retention practices offers citizens no real privacy gain.

Some cities are taking down one kind of license-plate camera and putting up a different kind from a different company. Schneier says that's like a kid who promises to stop eating candy and just switches from gummy bears to chocolate. The sweet tooth is still there, and so is all the watching.

Analysis

The FanDuel-to-DraftKings Fallacy

Schneier's central metaphor casts municipal surveillance procurement as a habit problem rather than a policy problem. Switching from Flock to Axon, in his framing, is the privacy equivalent of a gambler moving from FanDuel to DraftKings: the underlying behavior is unchanged, and so is the exposure. The rhetorical power of the comparison lies in collapsing what looks like a principled vendor change into a cosmetic rebranding of the same data-collection pipeline.

This framing matters because it shifts the burden of proof. A city that announces it is "ditching Flock" can claim progress while leaving intact the architecture that made Flock objectionable in the first place. Schneier is effectively telling readers not to grade municipal procurement decisions by the logo on the camera, but by what the camera does and what happens to the data afterward.

What Axon Cameras Actually Capture

The post specifically contests the idea that Axon is a privacy-friendlier alternative. According to Schneier, despite what readers may see on Flock's own marketing, Axon cameras are "pretty effective when it comes to hoovering up personal details that can go far beyond your license plate numbers." That single sentence reframes the entire LPR market: the competitive differentiation between vendors is technical, not normative, and a privacy-minded buyer cannot rely on brand choice to do the work of policy.

The implicit warning is that LPRs are part of a broader sensor stack. Once a city standardizes on a vendor with body-worn cameras, drones, and connected hardware in its catalog, the license-plate data can be correlated with footage, biometrics, and dispatch records. The article does not need to prove that Axon does this today; it only needs to show that buying Axon does not foreclose it.

Denver and the Limits of Vendor Politics

Denver, Colorado is named as one of the municipalities walking away from its Flock deployment. Schneier's point is not that Denver is wrong to leave Flock, but that the privacy calculus is barely shifted if the replacement hardware performs equivalent capture. A reader could substitute almost any mid-sized American city for Denver without changing the argument, which is a deliberate choice: the post is written for a national audience of residents, council members, and reporters who treat vendor switches as headlines rather than as interim steps in a longer surveillance negotiation.

The practical takeaway is procedural. Schneier is steering the conversation away from "which camera" and toward questions of data retention, access controls, audit logs, and whether the data ever leaves the city's custody. A commenter on the post extends the point with a reference to the recent story in which a Flock array flagged a journalist's press car, illustrating that the harm is in the data and the policy around it, not in the housing or the lens. Until those questions are answered, every LPR procurement is, in his telling, the same bet on a different bookie.

Key points

  • Schneier likens swapping Flock for Axon to a gambler switching sportsbooks: the exposure stays the same.
  • He argues Axon cameras collect personal details well beyond license plates, despite Flock's marketing framing.
  • Denver is cited as a city walking away from Flock, but the post says that move alone doesn't reduce surveillance.
  • The piece reframes LPR procurement as a policy and data-governance question, not a brand choice.
  • The underlying concern is that vendor politics are being mistaken for privacy progress.
The Downside

If municipalities continue to treat vendor substitution as a privacy win, the underlying LPR network will keep expanding with the same retention, sharing, and law-enforcement access rules. The result is a steady creep in which each procurement decision looks like a concession while the aggregate surveillance footprint grows. Schneier's framing also implies reputational and legal risk for any city that cannot show its new vendor is materially less invasive than the old one.

Originally reported at

schneier.com

Discernion covers the story. Read the full piece at the source.

Tagssecurityprivacysurveillancelaw enforcement

Author

Bruce Schneier

Intelligence analysis by

Llama

Published

Jul 28, 2026

Source

schneier.com

Share

Topics

securityprivacysurveillancelaw enforcement

Related

More from this desk

Jul 28·bleepingcomputer.com

Over 24,000 exposed server BMCs leak password hash via decades-old flaw

More than 24,000 internet-exposed servers are leaking authentication password hashes due to a 20-year-old vulnerability in their Baseboard Management Controller (BMC) interface. Researchers were able to find the correct password using dictionaries and the patterns on fact…

Jul 28·thehackernews.com

Nimbus Manticore Deploys NightLedger and Turns Victim Systems Into Covert Relays

Kaspersky attributes a fresh wave of attacks across the Middle East, Africa, and South Asia to Iranian group Nimbus Manticore, which deployed a new Windows backdoor called NightLedger alongside custom WebSocket tunnelers BridgeHead and ArcBridge to covertly relay traffic …

Jul 28·bleepingcomputer.com

Data breach at medical billing firm MCBS affects 1.26 million people

Medical billing firm MCBS disclosed a 2025 network breach exposing sensitive information of over 1.2 million people. The company reported that 1,261,464 people have been impacted. Exposed data includes full name, physical address, social security number, date of birth, an…

Jul 28·thehackernews.com

Critical TeamCity Flaw Could Let Attackers Run OS Commands Without Logging In

A critical security issue has been discovered in TeamCity, a popular continuous integration and continuous deployment (CI/CD) tool. The vulnerability, assigned CVE-2026-63077, affects all TeamCity On-Premises versions and could allow attackers to run OS commands without l…