Skip to content
NewA calmer, faster ZeroHour

Fixing Flock: The controls needed now that misuse patterns are clear

CSO Online ()12 min read3 · 3 reads
AI summary · grok-4.7Summaries by Vani AI

An opinion piece urges stronger access, retention, and audit controls for Flock's plate-reader network.

A CSO Online opinion column says Flock Safety must tighten controls on its automated license-plate reader network after documented misuse of searchable location data. Flock says it serves more than 6,000 communities, 5,000 law-enforcement agencies, and over 1,000 businesses; the Washington Post is cited for more than 120,000 cameras across 49 states and about 20 billion monthly plate observations. On August 13, 2026, Flock announced a seven-day default for ordinary plate records, required case codes and multifactor authentication, limits on outside searches, and audit lockouts for abnormal queries. The author argues longer retention should require public approval, case-bound access, immutable logs, and independent audit.

Key facts
  • Flock cites 5,000 law-enforcement customers and over 120,000 cameras.
  • The network processes about 20 billion plate observations monthly.
  • August 2026 changes add seven-day retention, case codes, and MFA.
  • The author wants graduated retention, tighter access, and audits.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

12 min read at csoonline.com

Flock Safety has stirred widespread debate of late. Flock builds interconnected networks of automated license-plate readers and other public safety cameras. Those systems can help police solve serious crimes, but they also log sensitive personal location data and make it searchable across agencies and jurisdictions.

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.