All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed2 filings · 1 stateUnverified claimConfirmedEnforcedlow sensitivity

Merged incident · 2 filings

National Experienced Workforce Solutions, Inc. — March 2024 breach

Clustered 2 filings across 1 jurisdiction · filed May 21, 2024. View entity profile → Other incidents for this victim →

✓ data types, discovery date agreeMerge90%

Determination

Confirmed

Members

2 filings

States

Affected · reported

—

First → last filing

May 21, 2024

Merge confidence

90%

incident inc_0c1a98b4502f4d44 · merged by deterministic · confidence 90%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe a misconfiguration. Intrusion Mar 14, 2024–Mar 18, 2024, discovered Mar 18, 2024 — the first regulatory filing landed 64 days later. Data reported: Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

64days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

0days

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 >14 bdayFull clock table in Litigation Timeline

Incident timeline

Mar 14, 2024breach begins

Mar 18, 2024discovered

notification delay · 64 days

May 21, 2024first filing

—watching for filings

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

Member cascade — every filing about this breach

MAY 21VT AGVT AG noticefirst filing · no count statedday 0
MAY 21VT AGVT AG noticemost recent · no count statedday 0
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Mar 14, 2024 – Mar 18, 2024
Discovered: Mar 18, 2024· 4d undetected
Data types: Identity (basic)
Attack vector: Misconfiguration

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: deterministic
Confidence: 0.90 · above the 0.85 auto-merge floor
Audit: Every link edge records its method, confidence and model + prompt versions (90% is the strongest edge).

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

Filing velocity

Spread

0 days

vs. multi-state median

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