Confirmed breach. Intrusion May 6, 2023, discovered May 6, 2023 — the first regulatory filing landed 55 days later. 1,244 individuals reported across the linked filings.
incident inc_cbb1f9009b7e4958 · merge_method human · confidence 100%
Litigation Timing
Notification delay
55days
Discovered → first regulatory filing
Leak precedence
42days
Gap between first leak claim and first regulatory filing
Filing span
Regulatory clocksMaine⏱ ME AG >30d · 55dFull clock table in Litigation Timeline
Leak SiteState AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcednokoyawa
42days
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.
Affected (total reported)
1,244
Data types
—
Jurisdictions
2
ME
Linked filings
2
Leak Site · State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 6, 2023
When the intrusion reportedly occurred, per the linked filings
Chattanooga State Community College is a public community college in Chattanooga, Tennessee. The college is a member of the Tennessee Board of Regents System and is accredited by the Southern Association of Colleges and Schools (SACS).Chattanooga State offers a variety of programs...
42 days
🦞Maine State AGMost recentLeaked → filing gap · 42dlinked via operator-confirmed · 100%
Chattanooga State Community College reported an external system breach discovered on May 6, 2023. The incident compromised the names and Social Security numbers of 1,244 individuals. The college began notifying affected individuals in writing on June 28, 2023, and offered 12 months of credit monitoring services from Equifax.
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.