From the Public Safety edition of September 23, 2026
Senate Crime subcommittee hearing puts bipartisan scrutiny on Flock ALPR networks
Nextgov/FCW · Independent federal technology journalism · United States (Congressional hearing; nationwide ALPR networks)
- Publisher
- Nextgov/FCW
- Original publication
- September 23, 2026
- Source retrieved
- 2026-09-24
- Event date
- 2026-09-23
What happened
On Sept. 23, 2026, members of the Senate Judiciary Subcommittee on Crime and Counterterrorism held a hearing criticizing automated license plate readers (ALPRs) for enabling warrantless searches, targeting risks, and weak cybersecurity. Sen. Josh Hawley (R-Mo.) said practically every state now has ALPRs—hundreds of thousands of cameras recording billions of images monthly—and questioned where images go, who uses them, and constitutional fit. The CEOs of Flock, Axon, Motorola, and Verkada were invited but declined to appear. Hawley criticized vendors for relying on agency self-policing and for claiming systems do not use facial recognition even though they do, and challenged Flock’s never-hacked claim; cybersecurity engineer Benn Jordan called unauthorized-data access a hack in the general sense. Sens. Katie Britt (R-Ala.) and Raphael Warnock (D-Ga.) sent DOJ a letter urging guidance for state/local agencies to prevent ALPR misuse. Democratic senators raised ICE/immigration and reproductive-care tracking concerns; ACLU’s Chad Marlow argued bans, noting ICE could use formal 287(g) agreements or a single officer’s informal help. Jordan urged independent security testing of ALPR vendors and a comprehensive federal privacy law. A Wall Street Journal report cited in the piece says Flock wrote Hawley outlining new guardrails including a dropdown justification menu and required case numbers for searches.
Why it matters
Direct federal oversight signal for U.S. policing ALPR/AI surveillance procurement—not fire/EMS. Relevant to every state/local agency buying or renewing networked ALPR and to vendors claiming FR-free or unhacked status.
Evidence and measured results
Independent federal-tech journalism of a same-day Senate subcommittee hearing with named senators, witnesses, and vendor non-appearance. Vendor product-change details attributed to a WSJ report rather than primary Flock letter text opened here.
Limitations and uncertainty
Journalism of a hearing, not a completed statutory change. Flock/Axon/Motorola/Verkada CEOs did not testify, so vendor rebuttals are absent. Case-number/dropdown changes are via secondary WSJ citation. No measured crime-outcome evaluation in this article.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-24; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies using Flock-style nationwide ALPR face bipartisan Senate scrutiny over warrantless searches, cybersecurity, FR claims, and misuse without a finished federal statute.
- Stakeholders
- Police chiefs / sheriffs
- City/county attorneys
- Mayors and councils
- State DOJ / AG offices
- ALPR vendor executives
- Discovery questions
- Can every ALPR search be tied to a case or incident number today?
- Have you commissioned independent security testing of your ALPR vendor?
- How do you document whether FR features are on or off?
- What is your written policy on immigration or interstate reproductive queries?
- Value hypothesis
- Bounded value is reducing congressional and civil-liberties exposure through auditable controls—not proving crime-reduction from this hearing report.
- Potential engagement
- 3–5 week ALPR governance readiness: case-gate enforcement, FR disclosure inventory, and Senate-hearing briefing for executives.
- Unsupported claims
- That federal law will ban ALPRs imminently
- Guaranteed DOJ guidance content or timeline
- Crime-clearance benefits from the hearing itself
Pre-sales engineering
Role takeaway
- Fit
- Multi-agency cloud ALPR networks under federal cybersecurity and purpose-limitation scrutiny.
- Architecture and integration
- ALPR SaaS + RMS/CAD case IDs + justification taxonomy + immutable audit export + optional independent pen-test evidence pack.
- Prerequisites
- Mandatory case/incident field before query
- Accurate FR feature configuration inventory
- Vendor willingness to allow independent security testing
- Constraints
- Vendor CEOs declined to testify—limited primary vendor detail
- Nationwide sharing complicates local purpose bans
- WSJ-cited product changes may lag local contracts
- Security
- Assume contested ‘never hacked’ claims; require independent testing, access monitoring, and clear unauthorized-access definitions.
- Proof of value
- Sampled searches all have case/justification
- Independent security findings remediations tracked
- FR configuration matches public/agency statements
Delivery
Role takeaway
- Work
- Implement case-linked search policy, update training, refresh vendor questionnaires, and prepare oversight briefings after the hearing.
- Dependencies
- Vendor case-number / dropdown rollout
- Local counsel on ICE/287(g) and state bans
- Records capacity for audit exports
- Ownership
- Professional standards with CISO/IT co-ownership of vendor security evidence.
- Skills and adoption
- Train officers that personal or curiosity searches are misconduct risks under national scrutiny; train supervisors on audit sampling.
- Governance checkpoints
- Case-gate live in production
- Quarterly ALPR misuse audit
- Council briefing on hearing implications
- Acceptance criteria
- Policy requires case/incident on every search
- Documented FR feature status
- Named owner for independent security testing
- Risks
- Self-policing without sanctions
- Informal officer help to federal immigration queries
- Hearing theater without contract changes
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
National ALPR clouds need independently testable security, searchable justification/case-number gates, and clear separation claims about facial-recognition features that withstand congressional scrutiny.
Governance
Who approves, reviews and stays accountable for outcomes?
Bipartisan push for DOJ guidance, possible federal privacy law, and skepticism of vendor self-policing shift ALPR from local policy-only to potential federal floor plus state guidance.
Security and privacy
What data, permissions and controls need testing?
Hearing focused on warrantless mass location tracking, ICE/immigration loopholes, reproductive and gun-store surveillance risks, and contested ‘never hacked’ assertions—elevating cybersecurity and purpose limitation as first-order requirements.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Officers need mobile-usable case/justification entry; supervisors need capacity to sample audits under heightened federal attention; cybersecurity staff need vendor-test literacy.
Procurement
What should contracts, pricing and exit terms secure?
Renewals and RFPs should require case-linked search controls, independent security-test cooperation, accurate FR disclosures, and contractual responses to federal guidance—evaluate vendors on these, not only camera count.
Operating model
Which teams own the service once it runs?
ALPR operations shift toward treating misuse and cybersecurity as national political risks requiring continuous audit, not one-time policy PDFs.
Publication history
- 2026-09-23Public Safety · Issue 174 resources
Stable resource ID: nextgov-senate-flock-alpr-hearing-20260923