Clustered 4 filings across 1 jurisdiction · filing window Oct 17, 2013 → Dec 20, 2013. View entity profile → Other incidents for this victim →
incident inc_5932f850ee3f4f67 · merge_method deterministic · confidence 100%
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.
CA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
California AG portal entry for Discover Financial Services. This is a sample notification form (SB24) and does not contain specific breach details, dates, or affected individual counts.
California Attorney General's office received a submitted breach notification sample from Discover Financial Services on October 13, 2024. The filing is a sample form; no specific incident details, attack vectors, or affected individual counts are provided in the source document.
California Attorney General's Office received a submitted breach notification from Discover Financial Services on October 13, 2024. The filing is a sample notification under SB 24. The document does not contain specific details regarding the nature of the breach, the number of affected individuals, or the types of data compromised.
California Attorney General's Office data security breach notification form submitted by Discover Financial Services. The filing is a sample notification (SB24) and does not contain specific details regarding the incident type, affected data, or number of individuals impacted.
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.