Confirmed breach. Intrusion Nov 5, 2023, discovered Nov 12, 2023 — the first regulatory filing landed 173 days later (flagged late). 1,546 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 clocksMaine✗ ME AG >90d · 173dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
1,546
Data types
2
PII · 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
Nov 5, 2023
When the intrusion reportedly occurred, per the linked filings
Breach discovered
Nov 12, 2023
Reported by MAINE AG filing
173 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Directive Communication Systems, Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-11-05 and was reported on 2024-05-03. 21 Indiana residents were affected. 1,546 individuals affected in total.
On November 5, 2023, Directive Communication Systems Inc. experienced a data breach due to insider wrongdoing, which was discovered on November 12, 2023. The breach affected 3 Maine residents, compromising their names and Social Security numbers. The company notified the affected individuals on May 3, 2024, and offered 12 months of credit and identity monitoring services through Experian.
Affected (this filing): 3
ME AG >90d · 173d
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.