FEDERALUnknownTechnologyTransportation & LogisticsInformationLowContained

SCANSOURCE, INC.

bd_94e32d5ef83030c4 · schema v1 · pii pii-v1

Severity

Low

Discovered

May 14, 2023

Filed

Aug 22, 2023

To disclose

14 weeks

Affected

Not disclosed

Linked

3 filings

Confidence

58%

Full breach record for SCANSOURCE, INC. →

ScanSource, Inc. disclosed a cyberattack discovered on May 14, 2023, which impacted core systems for its hardware business. The company launched its incident response plan and engaged external cybersecurity experts. Core systems were restored and operations resumed by May 26, 2023. The filing does not specify the attack vector, data types affected, or number of individuals impacted.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 14 weeks / 100 days

May 14, 2023

Discovered

Aug 22, 2023

Filed

vs. sector median

4 wks faster

This filing is one of 3 about the same incident.View merged incident

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitecactusbd_6a943a8292a9b35d2023-07-20 · +33dVerified by operator

Regulatory filings (1) · sorted by filing gap

Presscactusbd_4fc6c8360fd9d1a12023-05-14 · +100dCandidate

Name: SCANSOURCE, INC.
norm: scansource
Domain: scansource.com

Name: SCANSOURCE, INC.
norm: scansource
Domain: scansource.com
Industry: TechnologyllmTransportation & Logisticsllm

Discovered: May 14, 2023
Materiality determined: Aug 22, 2023
Notification sent: —
Affected individuals: Not disclosed
Data types: —
Attack vector: Unknown

During the incident: Launched its incident response plan
Engaged external cybersecurity experts
Restored core systems and resumed operations
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 14 weeks(100 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings

View merged incident ↗

PressMay 14 · first

SEC 8-K+100d · this page

Pattern: first filing May 14, last Aug 22 — a 100-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statementThis record

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://www.sec.gov/Archives/edgar/data/918965/000091896523000021/
DisclosureLens renders the full SEC/HHS filing inline below from the originating regulator’s public record (§4.5 fair report privilege).
Filed at: Aug 22, 2023
Raw hash: 4bb10982aa04ce4c8dc96028cb3d1f656500a2dc31349ad9e3388a55089a90b6

AI-assisted summary above. The structured extract on this page was generated from the document below. Inspect the source to verify or correct any field.

text/html489.8 KB

Download View at source

Linked disclosures

Ransomware claims (1)

Regulatory filings (1) · sorted by filing gap

Reporting entitySCANSOURCE, INC.

Victim entitySCANSOURCE, INC.

Incidentdiscovered May 14, 2023

Stated responseLaunched its incident response plan

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancewww.sec.gov

Source filing