From the Public Safety edition of October 3, 2026
Casar–Brown letter: House Oversight Democrats probe FBI RFP for nationwide near-real-time ALPR network access
U.S. House Committee on Oversight and Government Reform (Democratic Ranking Members) · Policing / federal oversight of ALPR · United States — federal (FBI Directorate of Intelligence RFP; implications for state/local camera networks)
- Publisher
- Office of Rep. Greg Casar / Oversight Committee Democrats
- Original publication
- 2 October 2026
- Source retrieved
- 2026-10-04
- Event date
- 2026-10-02
What happened
In a 2 October 2026 letter, Ranking Members Greg Casar and Shontel Brown tell FBI Director Kash Patel they are investigating an FBI RFP (May 2026 SAM.gov IDIQ) seeking nationwide ALPR access with near-real-time plate, vehicle-description, time/date, and geo-location search—capabilities vendors such as Flock and Motorola likely can meet. The letter cites documented misuse (Texas abortion-related multi-state plate chase; IJ finding ≥26 romantic-interest stalking uses; Washington Post tally of ≥69 officials accused/charged/convicted of ALPR misuse) and Flock transparency failures (e.g., Loveland CBP/HSI access contradictions). It requests six categories of FBI response covering current vendor access, intended use/legal basis, storage practices, sharing with CBP/ICE, relation to existing NCIC LPR programs, and abuse-prevention safeguards.
Why it matters
Primary federal oversight signal that local/state ALPR networks may be federally re-consumed at scale—SLED agencies must know who else can query their cameras and under what legal theory.
Evidence and measured results
Opened Casar house.gov PDF via curl (HTTP 200, application/pdf) at 2026-10-04T02:50:44Z; extracted text with pdftotext; confirmed RFP framing, misuse citations, and six information requests.
Limitations and uncertainty
Oversight letter states investigation and requests—not adjudicated findings against the FBI; misuse statistics attributed to cited press/IJ sources; partisan Democratic letterhead.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-04; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Local ALPR deployments may be pulled into federal near-real-time networks without clear local consent or safeguards.
- Stakeholders
- mayors/councils
- police executives
- privacy officers
- state fusion centers
- federal partners
- Discovery questions
- Which federal agencies can query our cameras today?
- What did the vendor tell council about CBP/HSI access?
- Can we technically disable near-real-time external search?
- Value hypothesis
- Transparent sharing controls and contract clauses reduce surprise federal access and political cancellation risk.
- Potential engagement
- 2-week ALPR external-access disclosure and MOU gap assessment keyed to the letter’s six FBI asks.
- Unsupported claims
- That the FBI RFP is already enjoined
- That Oversight findings are final adjudications
- That local opt-out is always contractually available
Pre-sales engineering
Role takeaway
- Fit
- Applies to agencies on nationally searchable ALPR graphs that federal IDIQs could consume.
- Architecture and integration
- Enforce allow-lists for external tenants; tag queries with requesting agency; document geo/time/descriptor search APIs.
- Prerequisites
- vendor admin visibility into partners
- written sharing policy
- logging of external queries
- Constraints
- vendor pilot contracts with CBP/HSI
- NCIC LPR vs commercial network overlap
- near-real-time latency requirements
- Security
- Prevent unauthorized federal or commercial reuse; encrypt stored plate traces; alert on bulk geo-fence stalking patterns.
- Proof of value
- complete partner access inventory
- sample external-query audit
- vendor written attestation matching runtime config
Delivery
Role takeaway
- Work
- Build sharing register; draft council brief; renegotiate disclosure clauses; test technical disable of unwanted tenants.
- Dependencies
- vendor cooperation
- counsel interpretation of RFP scope
- council schedule
- Ownership
- City attorney/privacy officer owns disclosure; IT owns technical enforcement.
- Skills and adoption
- Brief command staff on distinguishing NCIC LPR sharing from commercial near-real-time graphs.
- Governance checkpoints
- inventory completeness sign-off
- public transparency decision
- contract amendment review
- Acceptance criteria
- six-ask-mapped local answers on file
- no undocumented federal tenants in vendor console
- retention/storage description approved by counsel
- Risks
- vendor misrepresentation
- political conflict with federal partners
- incomplete historical access logs
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?
Assume federal IDIQ demand for near-real-time multi-criteria search; local systems need clear sharing matrices and technical controls for who can query.
Governance
Who approves, reviews and stays accountable for outcomes?
City/state contracts should disclose and constrain federal secondary access; prepare answers if FBI-like buyers attach to local camera graphs.
Security and privacy
What data, permissions and controls need testing?
Nationwide near-real-time ALPR plus prior misuse patterns elevates stalking, immigration, and sensitive-travel exposure if safeguards are weak.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Council and civilian oversight need plain-language sharing maps; avoid vendor jargon that hid CBP pilots elsewhere.
Procurement
What should contracts, pricing and exit terms secure?
Require truthful federal-access disclosures, audit rights, and unilateral local disable of external tenants in ALPR contracts.
Operating model
Which teams own the service once it runs?
Treat every camera as potentially nationally queryable unless proven otherwise; assign an owner for external-access reviews.
Publication history
- 2026-10-03Public Safety · Issue 264 resources
Stable resource ID: casar-brown-fbi-alpr-rfp-letter-20261002