From the Public Safety edition of October 26, 2026
Chicago police audit officers’ use of other agencies’ plate-reader systems, cut access and propose documented-purpose and monthly-audit rules
Chicago Police Department · Policing / automated license plate readers · Chicago, Illinois, United States
- Publisher
- Chicago Sun-Times
- Original publication
- Chicago Sun-Times, Oct. 26, 2026
- Source retrieved
- 2026-10-27
- Event date
- 2026-10-26
What happened
The Chicago Police Department is auditing whether officers abused access to other law enforcement agencies’ license plate reader systems. It has immediately limited access to outside systems to members whose position and job duties require it, and each of its five bureaus must designate someone to oversee ALPR use, including outside systems. Proposed changes in a draft directive open for public comment through Nov. 12 include non-transferable logins, a documented legitimate law enforcement purpose for every query, monthly search audits, central processing of access requests by the Office of Public Safety Administration, and penalties from loss of access to referral for prosecution. The department did not say what triggered the audit. The article notes felony charges against officers in several Illinois and Wisconsin agencies for Flock misuse and a Will County Board vote on an ALPR ban set for Nov. 12.
Why it matters
A large department that does not own Flock still relies on other agencies’ networks, so its controls must cover borrowed access, not just its own cameras.
Evidence and measured results
Opened the Sun-Times article and read it in full.
Limitations and uncertainty
The department did not explain what prompted the audit or when it will finish; no count of suspected misuse is given. Proposed rules may change after comment. Earlier coverage of CPD’s outside Flock searches (Oct. 7) is archived separately.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-27; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Large departments need to show that officers’ searches of other agencies’ plate-reader data were authorized and purposeful.
- Stakeholders
- Police superintendent and bureau chiefs
- Office of Public Safety Administration
- Inspector general and oversight board
- Partner agencies that own the cameras
- Discovery questions
- How many staff have access to outside ALPR systems today?
- Can each outside system require a purpose and export user-level logs?
- Who reviews audit exceptions?
- Value hypothesis
- Documented-purpose and audit controls could reduce misuse risk and liability.
- Potential engagement
- Access recertification and audit design for outside ALPR queries in one bureau.
- Unsupported claims
- Any estimate of misuse volume
- That the draft directive will be adopted unchanged
- That purpose fields prove legitimacy
Pre-sales engineering
Role takeaway
- Fit
- Departments relying on other agencies’ networked ALPR systems without owning cameras.
- Architecture and integration
- Controls span multiple external platforms; audits require log exports from each.
- Prerequisites
- Inventory of outside system accounts
- Log export access
- Case-number linkage
- Constraints
- Draft directive under comment to Nov. 12
- External systems controlled by other agencies
- No published audit findings
- Security
- Non-transferable credentials, MFA and query purpose logging.
- Proof of value
- Proposed: reconcile one month of queries to case numbers
- Proposed: confirm no account is used from multiple users
Delivery
Role takeaway
- Work
- Recertify access, appoint overseers, set monthly audit routine, train officers.
- Dependencies
- Final directive
- Partner agency cooperation
- Audit staffing
- Ownership
- Office of Public Safety Administration with bureau ALPR designees
- Skills and adoption
- Officers trained on purpose documentation and penalties.
- Governance checkpoints
- Directive adoption after comment
- First monthly audit
- Annual access recertification
- Acceptance criteria
- Proposed: zero shared credentials
- Proposed: purpose recorded on 100% of queries
- Risks
- External systems lack audit features
- Investigator workarounds
- Audit backlog
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?
Access to outside ALPR networks is per-user; the directive would make credentials non-transferable and require a purpose field on every query.
Governance
Who approves, reviews and stays accountable for outcomes?
Bureau-level ALPR overseers, monthly audits, central access approval and a graduated penalty scale; draft directive under public comment until Nov. 12.
Security and privacy
What data, permissions and controls need testing?
Shared logins and undocumented queries are the specific weaknesses targeted; misuse cases elsewhere led to felony charges.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Access is cut back to roles that need it, which may slow investigators who previously ran their own queries.
Procurement
What should contracts, pricing and exit terms secure?
Limited relevance; the controls concern access to other agencies’ systems rather than a purchase.
Operating model
Which teams own the service once it runs?
Moves access approval to the Office of Public Safety Administration and adds an overseer in each bureau.
Publication history
- 2026-10-26Public Safety · Issue 487 resources
Stable resource ID: chicago-pd-audits-officer-access-outside-alpr-systems-draft-directive-20261026