Confirmed breach. Intrusion Jun 23, 2014–Oct 22, 2016, discovered Oct 17, 2016 — the first regulatory filing landed 53 days later (flagged late). 407 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 clocksOregon✗ OR AG >45dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
407
Data types
—
Jurisdictions
1
OR
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jun 23, 2014 → Oct 22, 2016
When the intrusion reportedly occurred, per the linked filings
Asante reported a data breach to the Oregon Attorney General. The breach was reported on 2016-12-09. The breach occurred during 6/23/2014 - 10/22/2016. The breach was discovered on 10/17/2016. 407 individuals were affected. Notice was sent on 12/9/2016.
Affected (this filing): 407
OR AG >45d
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.