Police Are Hiding Their Use of Flock Surveillance Cameras
Overview
In Wapello County, Iowa, a policy regarding the use of Flock license plate reader cameras has come to light, revealing that police are instructed to keep their usage a secret from the public. The policy explicitly directs officers not to mention the Automated License Plate Recognition (ALPR) technology to individuals during stops or in their reports unless absolutely necessary. This raises concerns about transparency and accountability in law enforcement practices. The use of such surveillance tools without public awareness parallels past incidents involving IMSI-catchers, which were similarly concealed. The implications of this secrecy affect public trust and raise questions about the balance between security and individual rights.
Key Takeaways
- Affected Systems: Flock license plate reader cameras, Wapello County police department
- Timeline: Newly disclosed
Original Article Summary
A usage policy for Flock license plate reader cameras tells police not to talk about the cameras: When cops use Flock to arrest someone in Wapello County, Iowa, they don’t want them to know. A usage policy for the automated license plate reader cameras in the county tells police, in no uncertain terms, to keep them a secret: “DO NOT MENTION ALPR USAGE TO THE OCCUPANTS OF THE VEHICLE,” the policy document reads. “DO NOT MENTION ALPR USAGE IN YOUR REPORT OR COMPLAINT UNLESS ABSOLUTELY NECESSARY.” This reminds me of IMSI-catchers (Stingray was the most popular) a couple of decades ago. Police would go to even more extremes to hide their usage...
Impact
Flock license plate reader cameras, Wapello County police department
Exploitation Status
No active exploitation has been reported at this time. However, organizations should still apply patches promptly as proof-of-concept code may exist.
Timeline
Newly disclosed
Remediation
Not specified
Additional Information
This threat intelligence is aggregated from trusted cybersecurity sources. For the most up-to-date information, technical details, and official vendor guidance, please refer to the original article linked below.