SAIF Corporation reported a data breach to the Oregon Attorney General. The breach was reported on 2022-12-07. The breach occurred during 10/24/2022 - 10/24/2022. The breach was discovered on 10/27/2022. Notice was sent on 12/8/2022.
Clustered 2 filings across 2 jurisdictions · filed Dec 7, 2022. View entity profile → Other incidents for this victim →
incident inc_429929b65a1d4f8a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ID OR
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 24, 2022
When the intrusion reportedly occurred, per the linked filings
Oct 27, 2022
Reported by OREGON AG, IDAHO AG filings
SAIF Corporation reported a data breach to the Oregon Attorney General. The breach was reported on 2022-12-07. The breach occurred during 10/24/2022 - 10/24/2022. The breach was discovered on 10/27/2022. Notice was sent on 12/8/2022.
SAIF Corporation notified the Idaho Attorney General of a data incident occurring on October 24, 2022, where an unauthorized third party gained access to its network. The breach affected archived policyholder and claimant data, potentially exposing SSNs, financial account numbers, and medical information. No evidence of misuse was found. SAIF offered 12 months of free credit monitoring and is reviewing internal security policies.
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.