PoliceOne Data Breach Exposes 710K Law‑Enforcement Accounts
What Happened — In February 2017 PoliceOne disclosed that a breach dating back to July 2014 had exposed 709,926 user records. The leaked file contained email addresses, IP addresses, usernames and salted MD5 password hashes, which later appeared for sale on a data‑broker site.
Why It Matters for Trust & Control Assurance
- Credential‑storage weaknesses (MD5) highlight the need for continuous verification that password‑hashing meets modern security standards.
- The incident underscores the importance of ongoing access‑control monitoring and evidence collection to demonstrate due‑diligence during audits.
- Detecting and responding to credential‑theft events requires a defensible audit trail that can be supplied to regulators or oversight bodies.
Who Is Affected – Law‑enforcement agencies, public‑safety personnel, and any third‑party services that integrated with PoliceOne’s authentication platform.
Recommended Actions –
- Replace MD5 hashes with a strong algorithm (e.g., bcrypt, Argon2) and enforce MFA for all accounts.
- Conduct a credential‑inventory audit, map findings to your control‑assurance framework, and capture evidence of remediation.
- Deploy continuous monitoring for anomalous login activity and integrate alerts into your incident‑response workflow.
Source: HIBP breach record
Technical Notes – The breach likely stemmed from compromised credentials or inadequate password‑storage practices; no specific CVE is associated. Exposed data types: email, IP, username, salted MD5 password hash. Source: HIBP