Incident Score: Analysis & Impact (FLO1781202621)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Flock Safety's Breach and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts Flock Safety Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the Flock Safety breach identified under incident ID FLO1781202621.
The analysis begins with a detailed overview of Flock Safety's information like the linkedin page: https://www.linkedin.com/company/flock-safety, the number of followers: 86099, the industry type: Public Safety and the number of employees: 1454 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 760 and after the incident was 688 with a difference of -72 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on Flock Safety and their customers.
Flock Safety recently reported "Flock ALPR Data Leak Exposes Law Enforcement Search Queries in Search Engines", a noteworthy cybersecurity incident.
Privacy advocates and 404 Media uncovered a data exposure involving Flock Safety, a company specializing in automatic license plate readers (ALPRs), revealing sensitive law enforcement search details in public search engine results.
The disruption is felt across the environment, affecting Search engine indexing systems (DuckDuckGo, Bing), and exposing License plate numbers, vehicle details (make, model, color), search reasons (e.g., 'GTA' for grand theft auto, 'Investigation'), case numbers, date ranges, identifiers like 'window stickers' or 'top rack', with nearly Approximately 70 queries records at risk.
In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Working with search engines to remove cached content, and began remediation that includes Investigating the issue further, and stakeholders are being briefed through Public statement confirming the issue and steps taken.
The case underscores how Ongoing, teams are taking away lessons such as Need for stricter controls on how search engines index sensitive data; importance of transparency in surveillance technology usage, and recommending next steps like Implement measures to prevent sensitive data from being indexed by search engines; enhance data protection protocols for law enforcement queries; engage with communities on surveillance policies, with advisories going out to stakeholders covering Communities and law enforcement agencies advised to review data exposure risks and surveillance policies.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with lower confidence (40%), supported by evidence indicating surveillance data was inadvertently indexed by platforms like DuckDuckGo and Bing. Under the Collection tactic, the analysis identified Data from Information Repositories (T1213) with moderate to high confidence (80%), supported by evidence indicating license plate numbers, vehicle details, search reasons, case numbers exposed. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with lower confidence (30%), supported by evidence indicating data exposure involving Flock Safety...revealing sensitive law enforcement search details and Transfer Data to Cloud Account (T1537) with moderate confidence (50%), supported by evidence indicating inadvertently indexed by platforms like DuckDuckGo and Bing. Under the Impact tactic, the analysis identified Data Destruction (T1485) with lower confidence (20%), supported by evidence indicating working with search engines to remove cached content and Stored Data Manipulation (T1565.001) with moderate confidence (60%), supported by evidence indicating exposed data consisted of search query fragments rather than full records. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Flock Safety Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/flock-safety/incident/FLO1781202621
- Flock Safety CyberSecurity Rating page: https://www.rankiteo.com/company/flock-safety
- Flock Safety Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/flo1781202621-flock-safety-breach-may-2025/
- Flock Safety CyberSecurity Score History: https://www.rankiteo.com/company/flock-safety/history
- Flock Safety CyberSecurity Incident Source: https://www.404media.co/flock-leaked-cops-license-plate-searches-via-duckduckgo-bing/
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf