Clustered 3 filings across 3 jurisdictions · filing window Dec 9, 2022 → Dec 20, 2022. View entity profile → Other incidents for this victim →
incident inc_b0b7cf7d90bf496f · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA MT WA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 22, 2022
When the intrusion reportedly occurred, per the linked filings
Nov 17, 2022
Reported by WASHINGTON AG filing
Sequoia Benefits and Insurance Services LLC reported a data breach to the Montana Attorney General. The breach was reported on 2022-12-09. The breach occurred from 9/22/2022 to 10/6/2022. 1,053 Montana residents were affected.
Affected (this filing): 1,053
Sequoia Benefits and Insurance Services LLC, a business sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2022-11-17 and filed notice on 2022-12-12. 20,949 Washington residents were affected. 25 days elapsed between awareness and notification. 56 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 20,949
Sequoia Benefits and Insurance Services, LLC, d/b/a Sequoia Consulting Group reported to HHS on 2022-12-20 a Hacking/IT Incident affecting 4265 individuals. Breached information located on Network Server. The incident involved compromised PHI including names, dates of birth, addresses, financial and claims information, diagnoses, lab results, and medications. The covered entity implemented additional administrative and technical safeguards.
Affected (this filing): 4,265
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.