GLOBALClaimed by HiveFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Dec 20, 2022bd_306f846842b6e704
Innovative Education Management (IEM) has been successfully developing and operating California charter schools since 1998
Clustered 2 filings across 2 jurisdictions · filing window Dec 20, 2022 → Dec 22, 2022. View entity profile → Other incidents for this victim →
incident inc_2b8411d1ccc44967 · merge_method human · 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.
PII · Identity (basic)
CA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 6, 2022 → Nov 14, 2022
When the intrusion reportedly occurred, per the linked filings
Nov 14, 2022
Reported by CALIFORNIA AG filing
Innovative Education Management (IEM) has been successfully developing and operating California charter schools since 1998
Innovative Education Management, Inc. (IEM) notified the California Attorney General of a security incident where an unauthorized party gained access to its network. The breach occurred between November 6, 2022, and November 14, 2022. IEM discovered the incident on November 14, 2022. Personal information, including names, addresses, and potentially Social Security numbers, may have been accessed. IEM engaged outside cybersecurity professionals and is offering one year of complimentary credit monitoring to affected individuals. The investigation is ongoing.
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.