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

Professional Benefit Services, Inc. — September 2020 breach

Clustered 2 filings across 2 jurisdictions · filing window Jul 2, 2021 → Jul 28, 2021. View entity profile → Other incidents for this victim →

Agreement not assessableMerge100%

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

10

First → last filing

Jul 2, 2021 → Jul 28, 2021

Merge confidence

100%

incident inc_2659dd85db8846c6 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filing describes unauthorized access. Intrusion Sep 18, 2020–Oct 14, 2020, discovered Jun 1, 2021 — the first regulatory filing landed 31 days later (flagged late). 10 individuals reported across the linked filings. Data reported: PII. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
31days

Discovered → first regulatory filing

Filing span
26days

Time between earliest and latest filing

Not recorded for this incident

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 clocksOregon✗ OR AG >45dFull clock table in Litigation Timeline

Incident timeline

Sep 18, 2020breach begins
Jun 1, 2021discovered
notification delay · 31 days
Jul 2, 2021first filing
Jul 28, 2021most 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. JUL 2MT AGMT AG noticefirst filing · 10 MT residentsday 0
  2. JUL 28OR AGOR AG noticemost recent · no count stated+26d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 18, 2020 – Oct 14, 2020
OR AG
Discovered
Jun 1, 2021· 256d undetected
OR AG
Data types
PII
MT AG
Attack vector
Unauthorized Access
MT AG

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

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 filing2 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
human
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

26 days

vs. multi-state median

3.3× 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.