DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed13 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedrevilhigh sensitivity
Merged incident · 13 filings

NATIONAL WESTERN LIFE INSURANCE COMPANY — August 2020 breach

Clustered 13 filings across 12 jurisdictions · filing window Aug 1, 2020 → Jan 29, 2021. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 filings

States

11

Affected · reported

720,875

First → last filing

Aug 1, 2020 → Jan 29, 2021

Merge confidence

100%

incident inc_1b4c501976074246 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. The filings describe a ransomware attack. Intrusion Aug 7, 2020–Aug 10, 2020, discovered Aug 15, 2020 — the first regulatory filing landed 152 days later (flagged late). 720,875 individuals reported across the linked filings. Data reported: Government ID, PII, Financial, and 3 more. Notifications rolled out on a 181-day schedule across 12 filings beginning Aug 1, 2020. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
152days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
166days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
181days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dWashington✗ WA AG >90dOregon✗ OR AG >45dHawaii✓ HI CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 7, 2020breach begins
Aug 15, 2020discovered
notification delay · 152 days
Jan 14, 2021first filing
Jan 29, 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. AUG 1Leak siterevil postfirst filing · attacker claim · unverifiedday 0
  2. JAN 14ID AGID AG noticeno count stated+166d
  3. JAN 14SC AGSC AG notice14,427 SC residents+166d
  4. JAN 14WA AGWA AG notice15,556 WA residents+166d
  5. JAN 14HI AGHI AG notice8,373 HI residents+166d
  6. JAN 19OR AGOR AG noticeno count stated+171d
  7. JAN 20NH AGNH AG noticeno count stated+172d
  8. JAN 25MT AGMT AG notice3,425 MT residents+177d
  9. JAN 25MA AGMA AG notice2,416 MA residents+177d
  10. JAN 25DE AGDE AG notice585 DE residents+177d
  11. JAN 25IN AGIN AG noticestates nationwide total 720,875+177d
  12. JAN 25CA AGCA AG noticeno count stated+177d
  13. JAN 29NH AGNH AG noticemost recent · 664 NH residents+181d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 7, 2020 – Aug 10, 2020
SC AG
Discovered
Aug 15, 2020· 8d undetected
ID AG + SC AG + WA AG +6
Data types
Financial · Financial account · Identity (basic) · Government ID · PCI · PII
ID AG + SC AG + HI AG +6
Attack vector
Ransomware
ID 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)

720,875

Sum of filed state slices

59,497· 8.3% of stated

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

US720,875
WA15,556
SC14,427
IN14,051
HI8,373
MT3,425
MA2,416
NH664
DE585

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing12 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 Aug 23, 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

181 days

Cadence

~1 / 15.1d

vs. multi-state median

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