C811 - Digital ICT Third-Party Service Disruptions and Operational Resilience Obligations under the Digital Operational Resilience Act (DORA)
RegCanary analysis of a CySEC publication
Why it matters
RegCanary's analysis of what this means for regulated firms.
It is not a new rulemaking, but a supervisory signal: firms should be able to show that cloud and software dependencies supporting critical or important functions are identified, contracted, tested and backed by credible continuity and exit arrangements. Compliance teams should review third-party registers, concentration risk, incident escalation and reporting, and evidence of senior-management oversight. Practical steps include mapping Microsoft 365 and similar services to critical functions, reassessing impact tolerances, validating backup and alternative communication channels, and updating testing and remediation plans.
Firms should also confirm that contractual service levels, audit rights and termination support are documented. Smaller entities can apply proportionality but still need auditable controls; larger groups should focus on group-wide concentration and cross-border dependencies. The likely supervisory focus is demonstrable resilience rather than paper policies.
Stronger vendor governance can reduce disruption exposure, protect client communications and support confidence during DORA reviews.
Who this affects
Sectors and firm types identified in the analysis.
- General Regulation
Source
CySEC
Original publication, 17 November 2026
Read the original publication cysec.gov.cyThis is RegCanary's analysis, not the regulator's text. It summarises and interprets the publication above; it is not the CySEC's original wording, and it is not legal advice. Always rely on the original source.