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

AETNA INC. — August 2020 breach

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

✓ affected count agreeMerge100%

Determination

Confirmed

Members

3 filings

States

3

Affected · reported

8,664

First → last filing

Jul 13, 2021 → Jul 26, 2021

Merge confidence

100%

incident inc_4c42333e608e41de · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. The filing describes unauthorized access. Intrusion Aug 6, 2020–Oct 2, 2020, discovered Jun 21, 2021 — the first regulatory filing landed 22 days later. 8,664 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 1 more. Notifications rolled out on a 13-day schedule across 3 filings beginning Jul 13, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
22days

Discovered → first regulatory filing

Filing span
13days

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 clocksHIPAA✓ HHS notifiedOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 6, 2020breach begins
Jun 21, 2021discovered
notification delay · 22 days
Jul 13, 2021first filing
Jul 26, 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 13IN AGIN AG noticefirst filing · states nationwide total 8,664day 0
  2. JUL 14HHS OCRHHS OCR noticestates nationwide total 8,664+1d
  3. JUL 26OR AGOR AG noticemost recent · states nationwide total 8,664+13d
  4. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 6, 2020
IN AG
Discovered
Jun 21, 2021· 319d undetected
OR AG
Data types
PHI · Health (basic) · Identity (basic) · Government ID
HHS OCR
Attack vector
Unauthorized Access
HHS OCR

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)

8,664

Sum of filed state slices

5· 0.1% of stated

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

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 filing3 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
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

13 days

Cadence

~1 / 6.5d

vs. multi-state median

1.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.