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

RadNet Inc. data breach (2026) · DisclosureLens

All incidents View linkage analytics →

Incident · single filing

RadNet Inc.

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

incident inc_a1a4a6019cf84f71 · 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 claimConfirmedEnforcedmoderate sensitivity

Affected (total reported)

—

Data types

PHI · PII

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 Mar 2, 2026bd_9df64c8d902ea326
RadNet, Inc. (RadNet) disclosed in its 10-K Item 1C that it operates a Cybersecurity and Data Protection Program aligned with NIST and HIPAA. The company maintains 24/7 detection via internal teams and a third-party SOC, conducts tabletop exercises, and performs vendor risk assessments. No specific breach, incident, or material impact was reported; the filing serves as a risk disclosure regarding potential future threats.

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.