Lancaster
bd_6cbab825e1f7e7bf · schema v1 · pii pii-v2
Full breach record for Lancaster →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.
Ransomware forces Lancaster, Ohio, to take city computers offline. Lancaster: The city of Lancaster, Ohio, had to take its municipal computers offline on August 6 following ransomware alerts on several machines. Although essential systems (911, water, etc.) were not directly affected, the incident caused disruptions. On August 28, a committee confirmed that 90% of data and programs had been recovered, but the recovery process was incomplete, and 10% of the data remained under processing for security reasons. The city did not specify whether personal or financial information had been compromised, nor how the attacker accessed the network.
P pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Aug 6, 2026
Press report
—
No filing yet · watching
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Attack → press
—
Compliance clock
Not assessable
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
If an SEC 8-K, state-AG notice or victim statement lands, DisclosureLens merges it into an incident and links it here.
Source ceiling
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.