One linked filing — more sources may join as they report · filed Feb 27, 2024. View entity profile → Other incidents for this victim →
incident inc_4dc6c3b68bff4455 · merge_method deterministic
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.
FEDERAL
all SEC 10-K Item 1C
Earliest sighting first · deep chronology in Litigation Timeline
Form 10-K Item 1C disclosure describing the company's cybersecurity risk management program and governance. The filer states it has not identified any cybersecurity incidents that have materially affected, or are reasonably likely to materially affect, the company, but notes that it and its third-party vendors have from time to time experienced threats and security incidents.
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.