Confirmed breach. Intrusion May 28, 2023, discovered May 31, 2023 — the first regulatory filing landed 324 days later (flagged late). 800,000 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksLeak gap✗ Leak >180dMaine✗ ME AG >90d · 342dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
800,000
Data types
1
Government ID
Jurisdictions
2
IN ME
Linked filings
2
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
May 28, 2023
When the intrusion reportedly occurred, per the linked filings
Breach discovered
May 31, 2023
Reported by MAINE AG filing
324 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 95%
The Board of Regents of the University System of Georgia reported a data breach to the Indiana Attorney General. The breach occurred on 2023-05-28 and was reported on 2024-04-19. 725 Indiana residents were affected. 800,000 individuals affected in total.
The University System of Georgia reported a data breach affecting 800,000 individuals, including 211 Maine residents. The breach, which occurred on May 28, 2023, and was discovered on May 31, 2023, was the result of an external system breach (hacking). The compromised information includes names and driver's license or non-driver identification card numbers. The university offered 12 months of complimentary access to Experian IdentityWorks for fraud detection and identity restoration services.
Affected (this filing): 211
ME AG >90d · 342d
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.