news.mlab.sh
Back to the feed
threat-intel

On Flock License Plate Tracking Cameras

Medium
Summary

A writer was mistakenly identified and tracked by Flock license plate cameras, leading to an arrest. The issue stemmed from Flock’s AI system flagging vehicles with similar alphanumeric plate structures, even when the full plate number differed. Police departments are increasingly using Flock’s cameras to track individuals based on descriptions, raising concerns about privacy and potential misuse of surveillance technology. Flock’s CEO initially defended the system, but has since apologized for past rhetoric.

A writer was mistakenly identified and tracked using Flock license plate tracking cameras, ultimately leading to an arrest. The incident began when a New Jersey license plate, 34 03 DTM, was entered into Flock’s system as simply 34 DTM. This occurred because Flock’s AI system was designed to flag vehicles with similar alphanumeric plate structures, regardless of whether the full plate number matched. Officer Ganshyn observed that this created a nationwide issue, as any police department partnered with Flock would flag any JLR-owned car with the same plate structure as a stolen vehicle. Four other cars with the same plate structure (34 DTM) were being tracked in Minnesota at the same time.

Flock Safety initially defended its system, explaining that the AI correctly identified the requested plate and didn’t flag any other potential matches. However, the CEO later apologized for previously labeling privacy advocates as "terrorists." Beyond vehicle tracking, police departments are utilizing Flock’s cameras to track individuals based on detailed descriptions, including physical characteristics and even political affiliations – searches have included terms like "heavy-set male with a black and white hat" and "person wearing orange vest and construction hat." This represents a significant expansion of how police are utilizing surveillance technology and raises serious concerns about privacy and potential abuse.

Read the full article at Schneier on Security