Founded in 1992, ScanSource, Inc is an international distributor of technology products and solutions, focusing on point-of-sale (POS), payments, barcode, physical security, unified communications and collaboration, cloud and telecom services.
Clustered 2 filings across 2 jurisdictions · filing window Jul 20, 2023 → Aug 22, 2023. View entity profile → Other incidents for this victim →
incident inc_0484977628ae48ae · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Discovery to SEC materiality determination
Materiality determination to SEC 8-K filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance — needs two dated filings.
FEDERAL
Leak Site · SEC 8-K
Earliest sighting first · deep chronology in Litigation Timeline
May 14, 2023 → May 26, 2023
When the intrusion reportedly occurred, per the linked filings
May 14, 2023
Reported by SEC 8-K filing
Founded in 1992, ScanSource, Inc is an international distributor of technology products and solutions, focusing on point-of-sale (POS), payments, barcode, physical security, unified communications and collaboration, cloud and telecom services.
Aug 22, 2023
Registrant determined the incident material — starts the SEC 4-business-day clock
ScanSource, Inc. disclosed a cyberattack discovered on May 14, 2023, that impacted its core hardware systems. The incident involved ransomware, leading to system disruption until restoration on May 26, 2023. The company launched its incident response plan and engaged external experts. No specific data types or individual counts were disclosed in this financial results filing.
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.