DisclosureLens
State AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 2 filings

PRINCIPAL FINANCIAL GROUP, INC. — May 2021 breach

Clustered 2 filings across 1 jurisdiction · filing window May 26, 2021 Jul 22, 2021. View entity profile → Other incidents for this victim →

✓ 0 discrepancies — filings agreeMerge88%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

First → last filing

May 26, 2021 Jul 22, 2021

Merge confidence

88%

incident inc_9eaa73d762fb4d21 · merged by deterministic · confidence 88%

Confirmed breach. One breach, 2 legal records. Intrusion May 11, 2021. This page is the deduped roll-up; each member filing remains the legal record for its jurisdiction.

Litigation Timing

Filing span
57days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Sensitive data

identity_government

Incident timeline

May 11, 2021breach begins
May 26, 2021first filing
Jul 22, 2021most recent filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing about this breach

  1. MAY 26NH AGNH AG noticefirst filing · no count statedday 0
  2. JUL 22NH AGNH AG noticemost recent · no count stated+57d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 11, 2021
NH AG
Discovered
Data types
Government ID · Identity (basic)
NH AG
Attack vector
Misconfiguration
NH AG
Response
Contacted the recipient and confirmed that they permanently deleted the file from their records and network · Extended an offer to pay for a one-year subscription to Equifax Complete Premier, a credit monitoring service
NH 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
deterministic
Confidence
0.88 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (88% is the strongest edge).

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

Filing velocity

Spread

57 days

vs. multi-state median

11.4× 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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.