Ville de Columbia
bd_8805684151611fe3 · schema v1 · pii pii-v2
Full breach record for Ville de Columbia →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.
Network security incident disrupts Columbia’s online services in South Carolina. Ville de Columbia: Un incident de sécurité réseau a perturbé les services en ligne de la ville de Columbia, en Caroline du Sud. Les services d'urgence, l'eau et les paiements en ligne sont restés opérationnels. Les perturbations ont affecté les demandes de services, les licences commerciales et les permis. Les autorités enquêtent, mais aucune compromission de données ou attribution d'attaquant n'a été confirmée.
P pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 20, 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.