A technical failure cannot automatically erase or suspend law, identity, a vote, a record, an official balance or a decision.
Cybersecurity and continuity
Technical security protects availability, integrity and confidentiality without creating new public powers. Incident containment is different from investigation, sanctions or legal decisions.
What must remain protected
Critical records need versioning, audit trails, privilege segregation and secure recovery.
Technical protection does not authorize general surveillance or collection unrelated to the necessary security purpose.
Incident response
Alerts and evidence proportionate to risk.
Reduce harm without turning containment into legal punishment.
Maintain evidence, versions and chain of custody.
Restore function and validate official state.
Correct the cause, review controls and publish what can safely be disclosed.
Governance without concentration of power
| Actor | Responsibility | Limit |
|---|---|---|
| Cybersecurity Centre | Alerts, vulnerabilities, containment, response and recovery. | Technical containment capability is not equivalent to authority to investigate or sanction people. |
| Body responsible for the system | Preserve continuity and correct failures. | It cannot conceal a material incident where notification or transparency duties apply. |
| Data Protection | Oversee incidents and processing involving personal data. | Does not assume the substantive competence of other bodies. |
| Independent oversight | Audit legality, governance and risks where applicable. | Does not replace legitimate technical architecture within legal limits. |
There is not yet a verifiable public source for real-time availability, production incidents, recovery times or completed audits. Those indicators are therefore not invented.