Duluth Pulls Flock Cameras After 6 of 9 Devices Stolen or Damaged
Physical attacks on police license plate readers in Duluth left six of nine Flock endpoints stolen or damaged and all offline, underscoring endpoint security and data exposure risks for internet-connected public safety devices.
Beat this week
Last 7 days · Security
Impact 5.4/10, unchanged. Counts are stories in our record, not a market forecast.
Open the change reportCoverage balance Balanced directional read. Positive and negative coverage are within 0 percentage points.
This story sits in Security — the counts compare this beat's last 7 days with the previous 7 in our verified record, not a market forecast.
Figures are computed live from our source-verified story record (as of ) The volume change compares this window with the prior 7 days in the same record. — see our methodology for how impact and sentiment are derived.
Cybersecurity briefing
Key takeaways
- Physical attacks on police license plate readers in Duluth left six of nine Flock endpoints stolen or damaged and all offline, underscoring endpoint security and data exposure risks for internet-connected public safety devices.
In this briefing
Mentioned
Key Intelligence
Key Facts
- 1Duluth Police Department will end its one-year contract for nine Flock Safety stationary license plate readers; the contract expires Sept. 7, 2026.
- 2Six of the nine Flock cameras had been stolen or damaged since June 2026, and all nine were offline as of Aug. 12, 2026.
- 3Chief Mike Ceynowa said the devices were 'easily susceptible to vandalism and theft' and no ongoing funding source existed after a one-year grant.
- 4The department issued its non-renewal notification Aug. 3, 2026, one day before statewide headlines about destroyed or stolen cameras.
- 5Duluth has about 60 mobile license plate readers in its patrol fleet, first funded in 2011 with two squad-car readers.
- 6Flock cameras have been controversial locally and nationwide over privacy, misuse, and error concerns, with departments reporting vandalism.
Who's Affected
All nine devices were offline by Aug. 12, 2026, weeks before the Sept. 7 contract expiration.
Analysis
For cybersecurity teams, Duluth's Flock deployment is a real-world physical security incident: 67% of street-mounted cameras were stolen or damaged between June and August 2026, forcing all nine offline. Lost devices raise hard questions about onboard data at rest, network authentication, and whether stolen hardware could become an entry point into municipal systems.
The Duluth Police Department is pulling out of its one-year pilot with Flock Safety after the fixed license plate reader cameras proved, in Chief Mike Ceynowa's words, 'easily susceptible to vandalism and theft,' with six of nine devices stolen or damaged since June and all nine offline as of Aug. 12, 2026. The department issued its non-renewal notice Aug. 3, the day before Minnesota headlines began highlighting stolen and destroyed Flock cameras across the state, and the contract officially expires Sept. 7. Duluth is not abandoning plate-reader technology altogether: it has used mobile readers since 2011, starting with two squad-car units and growing to about 60 devices across its patrol fleet. But the fixed-camera deployment, funded through a one-year grant, lacked an ongoing funding source and became a target of physical attacks.
For cybersecurity teams, Duluth's Flock deployment is a real-world physical security incident: 67% of street-mounted cameras were stolen or damaged between June and August 2026, forcing all nine offline.
The decision is operationally significant but not isolated. Flock Safety has become one of the most visible vendors in the public safety surveillance market, with stationary cameras installed in thousands of communities. Duluth's exit highlights three frictions. First, physical security: a 67% physical loss rate for deployed cameras over a few months is an extraordinary failure for infrastructure whose core purpose is surveillance and deterrence. If cameras can be stolen or vandalized at that rate, their deterrence value is questionable and their total cost of ownership rises sharply. Second, funding: the pilot was grant-funded for one year, with no identified continuation money. This mirrors a broader local government challenge in which grant-funded surveillance tools are adopted without a sustainable budget path, leaving departments with hardware they cannot maintain or renew. Third, public legitimacy: Flock systems have become controversial nationwide over privacy, misuse, and error concerns. Duluth's timing—notifying the vendor a day before statewide destruction reports—suggests the department was already on a path to unwind the technology before the latest wave of scrutiny.
The retention of roughly 60 mobile plate readers is often overlooked. The 2011 investment in two squad-car units demonstrates long-standing institutional acceptance of LPR data for specific missions such as tracking missing people, stolen vehicles, and Amber or Silver alerts. That track record may partly explain why the department is willing to exit only the stationary Flock product rather than the entire LPR category. The mobile form factor keeps equipment within police vehicles, reducing vulnerability and perhaps lowering the volume of continuous stationary collection that has driven privacy objections. The distinction between mobile and fixed collection could become important in future debates over where and how LPR data is gathered.
What to Watch
From a market and policy standpoint, Duluth's experience may reinforce calls for procurement standards that require vendors to specify durability, tamper resistance, and replacement cost. It also raises questions about whether Flock or similar companies will adapt designs to survive physical attacks or shift more responsibility to municipal clients. The retention of mobile readers suggests the demand signal for license plate recognition remains strong, but the form factor matters: mobile units inside patrol vehicles are less exposed than street-mounted cameras. For Flock, losing a small but visible contract to vandalism and funding gaps could have a disproportionate reputational effect, since the company markets itself as a force multiplier for law enforcement.
Looking forward, the termination may be used as a template by cities weighing similar contracts. Legal observers will watch whether non-renewal language cites performance or vandalism deficiencies, and whether any data custody or breach disclosures follow. Cybersecurity and physical security teams will assess the risk of stolen devices containing unencrypted data or credentials. Duluth's chief left the door open to future stationary readers, but only if a product meets operational expectations. The episode underscores that adoption of law enforcement technology is not just a purchase decision; it is a sustained risk management commitment that must account for physical attack, funding cliffs, and community trust.
Cite This Page
"Duluth Pulls Flock Cameras After 6 of 9 Devices Stolen or Damaged." Cyber Intelligence Brief, August 16, 2026. https://getcyberbrief.com/story/duluth-flock-cameras-physical-endpoint-loss
How we covered this story
Every story in our cybersecurity coverage is assembled from multiple primary sources, cross-referenced for factual consistency, and scored along three independent dimensions: sentiment, operational impact, and source-cluster confidence. Single-source rumors and unverifiable claims do not pass our editorial gate. When a story shows "Verified by N sources" with N≥2, the development is independently corroborated; when N=1, we mark it explicitly so readers can weigh the signal accordingly.
Impact scoring uses a 1-10 scale weighted toward regulatory, financial, and operational consequence rather than coverage volume. A topic that runs in every outlet but moves no real decisions ranks lower than a niche regulatory filing that reshapes how operators in the cybersecurity space have to behave. Read our full methodology for the scoring rubric, our glossary for term definitions, and our trends index for the longitudinal view across the beat.
Sources are only linked to a story once they clear our classification pipeline at a minimum 35 percent relevance threshold. According to that methodology, reviewed July 2026, this follows multi-source corroboration standards recommended by journalism research bodies such as the Reuters Institute for the Study of Journalism.
See something wrong in this story — a wrong fact, a broken source link, a misattributed entity? Report a data issue.
| Signal on this page | What it tells you |
|---|---|
| Verified by N sources | Independent corroboration count. N≥2 is our confidence floor; N=1 is marked explicitly. |
| Impact score (1-10) | Regulatory + financial + operational weight. 8+ signals an experienced-operator action item. |
| Sentiment | Five-tier classification trained on labeled cybersecurity-specific corpora. |
| Timeline | Where applicable, the related-events sequence that contextualizes today's development. |