At A Glance
CMPD announced that one of its officers was arrested and charged after allegedly accessing a law enforcement computer system without authorization. Although CMPD does not own or operate Flock cameras, its officers have access to participating agencies’ systems through an interagency agreement.
At first glance, the incident appears to involve one employee.
From an Internal Affairs perspective, it raises much larger questions:
Who reviews audit logs?
How often are searches examined?
Who verifies the justification entered by employees?
How quickly are unusual search patterns identified?
What controls prevent personal curiosity from becoming criminal misconduct?
Those questions now belong on every IA commander’s and policy developer’s desk.
A National Trend
The CMPD case is part of a larger trend.
During the past several weeks:
Five former Albany Police Department officers were arrested after an internal audit reportedly identified multiple unauthorized Flock searches performed for non-law-enforcement purposes.
A former DeKalb County Sheriff’s deputy was arrested following an internal investigation into improper Flock use.
Three Fayetteville officers were terminated after audit software reportedly revealed searches involving their own license plates and those of friends or family.
A Pasadena police sergeant resigned during an internal investigation involving alleged misuse of the system.
A Baytown officer is under both administrative and criminal investigation involving alleged misuse of Flock access.
Florida agencies are not insulated from this risk.
In July 2026, a Sumter County Sheriff’s Office detective was arrested and terminated after an internal audit allegedly found she used multiple law-enforcement databases, including Flock, to obtain information involving her husband’s former wife. The sheriff temporarily suspended the agency’s Flock program while the office audited database access, user permissions, and internal controls.
Earlier in 2026, a Monroe County deputy was arrested and fired after investigators alleged he used law-enforcement databases and license-plate-reader information to locate and follow a woman he met while working an off-duty security assignment.
These cases reinforce a central lesson for Internal Affairs commanders: misuse rarely begins with a major criminal scheme. It often begins with a personal curiosity, a relationship conflict, or an employee believing no one reviews the audit trail.
Florida agencies also face a separate certification risk. FDLE identifies the willful use of a trusted electronic database for an illegitimate or personal purpose as misconduct subject to Criminal Justice Standards and Training Commission review. A sustained database-misuse case therefore might trigger agency discipline, criminal exposure, and state certification proceedings. FDLE Officer Discipline Database
What Every IA Unit Should Audit
1. Search Justifications
Review whether every search contains a valid case number, incident number, warrant, BOLO, intelligence bulletin, or documented investigative purpose.
Generic entries such as:
Investigation
Information
Officer Safety
Follow-up
should receive additional scrutiny. Poor documentation often conceals improper access.
2. Personal Connections
Look for searches involving:
Former spouses
Current dating partners
Family members
Neighbors
Political figures
Celebrities
Fellow employees
Supervisors
Personal vehicles
These represent some of the highest-risk misuse categories.
3. Repeated Searches
Repeated queries involving the same vehicle without investigative activity deserve review.
Patterns frequently reveal stalking, harassment, curiosity, or personal interest.
4. Off-Duty Activity
Review searches conducted:
Late at night
During leave
While assigned to administrative duties
Outside normal work schedules
Time-of-day analysis often identifies misuse overlooked during routine reviews.
5. Geographic Outliers
Why is an officer assigned to one patrol district searching vehicles hundreds of miles away?
Cross-jurisdictional searches deserve supervisory review unless supported by documented investigations.
6. False Case Numbers
Several recent investigations allege employees entered inaccurate or misleading reasons for searches to conceal improper activity. IA investigators should verify every justification against actual case records.
7. Supervisory Approval
Determine:
Who reviewed audit reports?
How often?
Were exceptions investigated?
Were corrective actions documented?
A missing review process often becomes a supervisory failure. These seven steps are an important module in Internal Affairs Training.
Policy Gaps To Review
Agency policy should clearly address:
Authorized uses of intelligence databases
Prohibited personal searches
Documentation requirements
Supervisor audit responsibilities
Retention of audit logs
Random compliance inspections
Criminal reporting requirements
Progressive discipline
Annual user certification
Revocation of access following violations
If the policy does not require audits, the agency is relying almost entirely on employee honesty. That is no longer sufficient.
Monday Morning Action
Ask your Professional Standards Unit these ten questions:
Who owns the audit process?
When was the last audit completed?
Are random audits documented?
Who reviews supervisors?
Are searches matched to actual investigations?
How quickly are anomalies flagged?
Are employees receiving annual training?
Does policy define unauthorized access?
Have access permissions been reviewed within the last year?
Would your audit process withstand public disclosure during litigation?
Leadership Takeaway
Flock cameras are not the issue. Access is.
Every intelligence platform provides extraordinary investigative value when used appropriately.
Every platform also creates opportunity for abuse.
Internal Affairs units must evolve from complaint investigators into technology auditors.
The agencies leading the profession will not be those with the most cameras.
They will be those with the strongest governance.
Because in every database search, every license plate query, and every intelligence request, one fact remains true:
The audit trail never lies.
