DORA: paperwork compliance or real operational resilience?
DORA now applies to Monaco's financial institutions through the Monetary Agreement with the EU. The risk is turning it into a documentation project rather than a stress test.
Editorial theme E / F
Technology dependency is managed in the boardroom, not just by the IT department. DORA says so in black and white — and it now applies to Monaco's institutions too.
Thesis — Responsibility for a technology risk cannot be delegated to the IT department or to the provider.
DORA covers five areas: ICT risk management (Articles 5 to 16), incidents (17 to 23), resilience testing (24 to 27), third-party providers (28 to 44) and information sharing (45). Article 5 places ultimate responsibility for ICT risk management on the management body.
A serious discussion of governance separates three things that are often confused.
| Level | Examples |
|---|---|
| Legal obligation | DORA; Law No. 1.565 (personal data); Law No. 1.362 (anti-money laundering) |
| Regulatory guidance | EBA Guidelines on outsourcing; Financial Stability Board work |
| Good practice | Regular exit tests; compliance data hosted in Monaco; encryption keys held by the bank |
The choice of critical providers, starting with those that process compliance data. The register of ICT third-party arrangements required by Article 28. An exit strategy for every service supporting a critical or important function (Article 28(8)). Continuity test results. And the reasoned, dated acceptance of residual risks: if the bank chooses a provider hosted on a US cloud for its KYC data, the board should have decided so knowingly — not learn of it after an incident.
DORA now applies to Monaco's financial institutions through the Monetary Agreement with the EU. The risk is turning it into a documentation project rather than a stress test.