One linked filing — more sources may join as they report · filed Mar 6, 2026. View entity profile → Other incidents for this victim →
incident inc_3f0c714c3f844599 · 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
Item 1C of a 10-K filing for a community bank describing general cybersecurity risks, including threats from external and internal sources. The company states it has implemented security measures, incident response programs, and insurance, but cannot guarantee prevention of all incidents. No specific breach or material impact is disclosed.
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.