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

CITIZENS FINANCIAL GROUP, INC. — December 2017 breach

Clustered 5 filings across 2 jurisdictions · filing window Feb 2, 2018 → Apr 3, 2018. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

2

Affected · reported

not comparable

First → last filing

Feb 2, 2018 → Apr 3, 2018

Merge confidence

100%

incident inc_9fa6b47dc7754b25 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe a physical incident. Intrusion Dec 1, 2017–Feb 28, 2018, discovered Jan 23, 2018 — the first regulatory filing landed 10 days later. Data reported: Identity (basic), Financial account, Authentication, and 1 more. Notifications rolled out on a 60-day schedule across 5 filings beginning Feb 2, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
10days

Discovered → first regulatory filing

Discovery variance
35days

Range of discovered_at dates across filings

Filing span
60days

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.

Sensitive data

authentication

Incident timeline

Dec 1, 2017breach begins
Jan 23, 2018discovered · members disagree
notification delay · 10 days
Feb 2, 2018first filing
Apr 3, 2018most 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. FEB 2NH AGNH AG noticefirst filing · 2 NH residentsday 0
  2. FEB 6MA AGMA AG notice2 MA residents+4d
  3. MAR 5MA AGMA AG notice3 MA residents+31d
  4. MAR 6NH AGNH AG notice1 NH residents+32d
  5. APR 3MA AGMA AG noticemost recent · 2 MA residents+60d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 18, 2018 – Jan 23, 2018
NH AG
Discovered
Jan 23, 2018NH AGFeb 27, 2018NH AGfilings disagree on discovery
Data types
Authentication · Financial account · Identity (basic) · PCI
NH AG + MA 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 filing5 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

60 days

Cadence

~1 / 15d

vs. multi-state median

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