Clustered 4 filings across 3 jurisdictions · filing window Sep 20, 2022 → Feb 3, 2023. View entity profile → Other incidents for this victim →
incident inc_be73900829c94b6a · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
Identity (basic) · Government ID · Financial account
CA MT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Aug 20, 2022
When the intrusion reportedly occurred, per the linked filings
Aug 20, 2022
Reported by CALIFORNIA AG filing
Sierra Joint Community College District experienced a ransomware attack on August 20, 2022, resulting in the encryption of some systems. The incident potentially exposed personal information including names, addresses, passport numbers, driver's license numbers, Social Security numbers, financial account information, and medical information. The district engaged a third-party forensic firm, secured the network, and offered 12 months of identity monitoring to affected individuals.
Sierra College reported a data breach to the Montana Attorney General. The breach was reported on 2022-11-11. The breach occurred on 8/20/2022. 5 Montana residents were affected.
Affected (this filing): 5
On August 20, 2022, Sierra Joint Community College District (Sierra College) experienced a ransomware attack that encrypted some of its systems. A third-party forensic investigation determined by December 8, 2022 that an unauthorized individual accessed systems containing personal information including names and addresses. The college implemented additional security measures and offered free IDX identity monitoring services to affected individuals.
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.