Disclosures Claims Reports Entities Incidents Pulse

Feed live

DisclosureLens

Structured extracts of public breach disclosures — regulator filings (SEC, HHS, state AGs, EU DPAs) alongside threat-actor leak-site claims and press reports. SEC and HHS filings render inline from the originating regulator’s public record under the fair report privilege; other sources link out to the source URL. AI-extracted with full per-record audit trail (model, prompt version, confidence).

ai_assisted: true · Article 50 disclosure on every record

Product

Disclosures feed
Pulse · analytics
Entities
Breach notifications by state

Methodology

How extraction works
Confidence & review
About the bot

Trust

Security
Self-disclosure commitment
API documentation
API keys

v0.1.0 · coverage growing weekly

U.S. Bancorp data breach (2026) · DisclosureLens

All incidents View linkage analytics →

Incident · single filing

U.S. BANCORP

One linked filing — more sources may join as they report · filed Feb 23, 2026. View entity profile → Other incidents for this victim →

incident inc_a73720e8da834175 · merge_method deterministic

Litigation Timing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; needs two dated filings.

SEC 10-K Item 1CConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced

Affected (total reported)

—

Data types

—

Jurisdictions

FEDERAL

Linked filings

all SEC 10-K Item 1C

Timeline

Earliest sighting first · deep chronology in Litigation Timeline

FEDERALSEC 10-K Item 1CFirst filing
Filed Feb 23, 2026bd_5854a01531db232d
U.S. Bancorp's 2025 10-K filing (Exhibit 13) discloses 'Breaches in data security' and 'Failures or disruptions in or breaches of U.S. Bancorp's operational, technology or security systems' as standard risk factors. No specific incident, date, or victim entity is identified in the provided text.

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.