DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed7 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcritical sensitivity
Merged incident · 7 filings

CSC SERVICEWORKS, INC. — September 2023 breach

Clustered 7 filings across 7 jurisdictions · filing window Aug 9, 2024 → Aug 14, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

35,340

First → last filing

Aug 9, 2024 → Aug 14, 2024

Merge confidence

100%

incident inc_5914472b1eba401f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe unauthorized access. Intrusion Sep 23, 2023–Feb 4, 2024, discovered Feb 4, 2024 — the first regulatory filing landed 187 days later (flagged late). 35,340 individuals reported across the linked filings. Data reported: Government ID, Minor, Identity (basic), and 5 more. Notifications rolled out on a 5-day schedule across 7 filings beginning Aug 9, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
187days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
5days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 187dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_governmentminor

Incident timeline

Sep 23, 2023breach begins
Feb 4, 2024discovered
notification delay · 187 days
Aug 9, 2024first filing
Aug 14, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 9IN AGIN AG noticefirst filing · states nationwide total 35,340day 0
  2. AUG 9VT AGVT AG noticeno count statedday 0
  3. AUG 9ME AGME AG noticestates nationwide total 35,340day 0
  4. AUG 9MT AGMT AG notice6 MT residentsday 0
  5. AUG 9CA AGCA AG noticeno count statedday 0
  6. AUG 12NH AGNH AG notice54 NH residents+3d
  7. AUG 14MA AGMA AG noticemost recent · 762 MA residents+5d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 23, 2023
IN AG
Discovered
Feb 4, 2024· 134d undetected
VT AG + ME AG + MT AG +2
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · Minor · PCI · PHI · PII
VT AG + ME AG + MT AG +3
Attack vector
Unauthorized Access
VT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

35,340

Sum of filed state slices

1,657· 4.7% of stated

95% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US35,340
MA762
IN734
ME101
NH54
MT6

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing7 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

5 days

Cadence

~1 / 0.8d

vs. multi-state median

1.6× faster

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.