Confirmed breach. Intrusion Nov 1, 2017, discovered Nov 1, 2017 — the first regulatory filing landed 56 days later. 639 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksHIPAA✓ HHS notifiedFull clock table in Litigation Timeline
HHS OCRConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
639
Data types
4
PHI · Health (basic) · Identity (basic)
Jurisdictions
1
CO
Linked filings
1
all HHS OCR
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Nov 1, 2017
When the intrusion reportedly occurred, per the linked filings
Colorado Department of Human Services reported to HHS on 2017-12-27 a Hacking/IT Incident affecting 639 individuals. Breached information located on Desktop Computer. An employee accessed an imposter site that downloaded malware, allowing the operator to access PHI of 639 individuals.
Affected (this filing): 639
HHS notified
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.