Administration du district d'Oberspreewald-Lausitz
bd_3fac9ac852b5eb50 · schema v1 · pii pii-v2
Full breach record for Administration du district d'Oberspreewald-Lausitz →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 and machine-translated to English — verify against the source.
Summary
machine-translatedSuspected cyberattack: OSL district administration largely paralyzed | NIEDERLAUSITZ aktuell. Administration of the Oberspreewald-Lausitz district: The district administration of Oberspreewald-Lausitz was paralyzed by a cybersecurity incident. Technical systems were taken offline on Tuesday evening. Although a cyberattack is not officially confirmed, internal rumors suggest this possibility. Services are severely limited, and the office is closed on Thursday, October 22. Citizens are advised to use the helpline for requests.
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.