HackingTechnologyTelecom & MediaInformationStolen CredentialsCustomer Data InvolvedDelayed DiscoveryIdentity (basic)CredentialsHighContained

Praetorian Digital

bd_4904d3b46b46f27f · schema v1 · pii pii-v1

Severity

High

Discovered

Feb 3, 2017

Filed

Mar 21, 2017

To disclose

7 weeks

Affected

715,000

Confidence

64%

Full breach record for Praetorian Digital →

Praetorian Digital (operator of PoliceOne.com) disclosed unauthorized access to its PoliceOne Forums, which occurred in 2014 but was discovered on February 3, 2017. Approximately 715,000 accounts were affected. Compromised data included email addresses, usernames, dates of birth, and MD-5 hashed and salted passwords. The forums were taken down, and users were required to reset passwords. The company is conducting a security review.

J jump to incidentP pin to compareR raw source

California clockDiscovered Feb 3, 2017 → Notified Mar 21, 201746d ✓ CA 60-day OK7 weeks discovery → filing

Incident timeline

undetected · 1129 days

discovery → filing · 7 weeks / 46 days

Jan 1, 2014

Begins

Feb 3, 2017

Discovered

Mar 21, 2017

Filed

vs. sector median

12 wks faster

Tracked as a single-filing incident — the only disclosure on record for this event so far.Confirmed715,000 affectedView incident

Name: Praetorian
norm: praetorian
Domain: praetorian.com

Name: Praetorian Digital
norm: praetorian digital
Domain: policeone.com
Industry: TechnologyllmTelecom & Mediallm

Discovered: Feb 3, 2017
Breach occurred: Jan 1, 2014 – Dec 31, 2014
Undetected for: 1,129 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 21, 2017
Affected individuals: 715,000nationwide
Data types: Identity (basic)Credentials
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External

During the incident: Took down the forums
Set any new member login to require a password reset via email for potentially affected accounts
Sending email with a link to change your password on next login
Completing a full security review
Changes made: Confirming updates to prevent future incidents
Reviewing processes, policies, and procedures that address data security
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 7 weeks(46 days from discovery to filing)
Compliance flags: CA 60-day OK · 46d
Discovery-date grounding: letter-groundedThe discovery date is the detection date narrated in the notification letter — the defensible tier.
Clock breakdown: Statute Window Elapsed Threshold Status
California
Discovered: Feb 3, 2017
→ Notified: Mar 21, 2017
46d 60 days (analyst band, pre-2026 discoveries) CA 60-day OK

Statute	Window	Elapsed	Threshold	Status
California	Discovered: Feb 3, 2017 → Notified: Mar 21, 2017	46d	60 days (analyst band, pre-2026 discoveries)	CA 60-day OK

Status: No extraction artifact recorded for this disclosure.

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://oag.ca.gov/ecrime/databreach/reports/sb24-67050
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 21, 2017
Raw hash: 04abf135503066dea766f8f5125e43d9aa94b868b93f3dd57f536153b959ec72

Reporting entityPraetorian

Victim entityPraetorian Digital

Incidentdiscovered Feb 3, 2017

Stated responseTook down the forums

ComplianceCA 60-day OK

Extraction provenanceno artifact recorded

Source provenanceoag.ca.gov