DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed11 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmeowhigh sensitivity
Merged incident · 11 filings

CBIZ, INC. — May 2023 breach

Clustered 11 filings across 9 jurisdictions · filing window Sep 1, 2023 → Dec 29, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

9

Affected · reported

436,198

First → last filing

Sep 1, 2023 → Dec 29, 2023

Merge confidence

100%

incident inc_3752e331f4554f4d · merged by deterministic · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 89 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe hacking. Intrusion May 29, 2023–Jun 5, 2023, discovered May 31, 2023 — the first regulatory filing landed 93 days later (flagged late). 436,198 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 4 more. Notifications rolled out on a 119-day schedule across 11 filings beginning Sep 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
93days

Discovered → first regulatory filing

Discovery variance
71days

Range of discovered_at dates across filings

Filing span
119days

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 >30d · 141dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

May 29, 2023breach begins
May 31, 2023discovered · members disagree
notification delay · 93 days
Sep 1, 2023first filing
Dec 29, 2023most 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. SEP 1VT AGVT AG noticefirst filing · no count statedday 0
  2. SEP 1NH AGNH AG notice77 NH residentsday 0
  3. SEP 1ME AGME AG noticestates nationwide total 35,843day 0
  4. SEP 1IN AGIN AG noticestates nationwide total 35,843day 0
  5. SEP 1CA AGCA AG noticeno count statedday 0
  6. SEP 1MA AGMA AG notice31,370 MA residentsday 0
  7. SEP 1MT AGMT AG notice149 MT residentsday 0
  8. SEP 5SC AGSC AG notice1,190 SC residents+4d
  9. NOV 10HHS OCRHHS OCR noticestates nationwide total 436,198+70d
  10. DEC 29NH AGNH AG notice3,238 NH residents+119d
  11. DEC 29ME AGME AG noticemost recent · 482 affected+119d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 29, 2023 – Jun 5, 2023
VT AG
Discovered
May 31, 2023VT AG + CA AG + MT AG +1Aug 10, 2023ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + NH AG + ME AG +5
Attack vector
Third-Party / Supply Chain
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)

436,198

Sum of filed state slices

37,640· 8.6% of stated

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

US436,198
MA31,370
NH3,238
IN1,211
SC1,190
ME482
MT149

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 filing11 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 Oct 22, 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

119 days

Cadence

~1 / 11.9d

vs. multi-state median

19.8× slower

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.