Confirmed breach. Intrusion Dec 1, 2016–Nov 1, 2018, discovered Nov 1, 2018 — the first regulatory filing landed 41 days later. 716 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 clocksCalifornia✓ CA 60-day OK · 1dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Affected (total reported)
716
Data types
1
Credentials
Jurisdictions
1
CA
Linked filings
1
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Dec 1, 2016 → Nov 1, 2018
When the intrusion reportedly occurred, per the linked filings
ASI Computer Systems reported unauthorized access to customer support website credentials (usernames and passwords) affecting 716 California residents. The breach occurred prior to December 2016 but was discovered on November 1, 2018. ASI deactivated passwords, forced resets, and notified affected individuals via email on November 2, 2018.
Affected (this filing): 716
CA 60-day OK · 1d
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.