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 →
incident inc_9eaa73d762fb4d21 · merged by deterministic · confidence 88%
Litigation Timing
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.
Sensitive data
identity_governmentIncident timeline
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
- MAY 26NH AGNH AG noticefirst filing · no count statedday 0
- JUL 22NH AGNH AG noticemost recent · no count stated+57d
- 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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
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.