DisclosureLens
SEC 10-K Item 1CNo incident reported1 filing · 1 state
Incident · single filing

SITEONE LANDSCAPE SUPPLY, INC. — July 2020 breach

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

Determination

No incident reported

Members

1 filing

States

1

Affected · reported

First → last filing

Feb 19, 2026

incident inc_b36b130e492648d7 · merged by deterministic

No incident reported. This record is an annual cybersecurity risk disclosure filed under SEC 10-K Item 1C — a description of the registrant's risk-management program, not a report of a breach. It is published here because the filing exists, not because anything was alleged.

Litigation Timing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing spanno leak-site claim in this cluster; needs two dated filings.

Incident timeline

Jul 1, 2020breach begins
Feb 19, 2026first & only filing
watching for filings

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing about this breach

  1. FEB 19SEC 10-K Item 1CSEC 10-K Item 1C noticeonly filing · no count statedday 0
  2. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 1, 2020
SEC 10-K Item 1C
Discovered
Attack vector
Ransomware
SEC 10-K Item 1C

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing

No regulator filing linked yet.

SEC 8-K / victim statement1 member

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

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.