DORA is now an operating framework
DORA (Digital Operational Resilience Act) has applied since 17 January 2025. In 2026, a useful DORA engagement should therefore test whether governance, risk management, incident processes, continuity, resilience testing and third-party oversight work in practice. Rewriting generic policies is not an adequate substitute for operational evidence.
Management accountability is central
ICT risk cannot remain an exclusively technical matter. The governance model should define who approves the framework, receives risk information, accepts residual risk, prioritises remediation and challenges critical dependencies. Board reporting needs decision context rather than unfiltered technical metrics.
Resilience requires testing and records
Continuity plans and backups are only as useful as the evidence that they can support recovery. Exercise results, restoration evidence, failures, corrective actions and re-testing should be traceable. Similar discipline applies to security and resilience testing.
Third-party risk is both contractual and operational
Financial entities remain responsible when ICT services are outsourced. Provider inventories, critical-function mapping, due diligence, contractual rights, ongoing monitoring, concentration risk and exit planning need to align. Legal contract review and operational provider governance should therefore be tested together.
Evidence-first remediation
A finding should move through requirement, gap, risk, owner, action, evidence, reassessment and closure. This creates an audit trail that is useful to management, internal assurance and supervisors. A newly written procedure is not evidence that the underlying control is operating.
The commercial lifecycle
DORA can be productized as an applicability and evidence diagnostic, a remediation programme, focused modules such as Register of Information or incident governance, and an annual assurance retainer. The recurring value comes from maintaining control effectiveness as systems and providers change.
Turning the analysis into a controlled mandate
In a live mandate concerning DORA implementation, the work cannot stop at high-level advisory language. The legal conclusion should be translated into a controlled workplan covering ICT governance, continuity, testing, third-party oversight and management accountability. Each material issue receives a factual owner and legal owner, required documents, decision point, dependencies and a completion criterion. This allows the team to distinguish true blockers from parallel workstreams and from tasks requiring a specialist or local counsel. It also provides disciplined change-control when the client alters a business assumption during the project, rather than allowing scope and responsibility to expand informally.
Failure modes to identify before they become regulatory statements
The most expensive problems are not always difficult points of law. They are often policy-only compliance, tests with no corrective action, weak provider rights and risk reporting with no decision context. Those inconsistencies should be found before they become a filing, supervisory statement, board representation or contractual commitment. The delivery model uses an issue log recording severity, legal implication, business impact, owner and required decision. Where a gap cannot responsibly be closed in time, it should be disclosed internally and managed through an informed decision rather than hidden by drafting that creates a larger problem later.
Evidence, quality control and later review
A strong project file allows an independent reviewer to trace the path from requirement to decision and implementation. Depending on the matter, the record should include test results, restoration records, provider assessments, RoI data, incident records and closure evidence. Evidence should not sit in an unstructured folder: it should be linked to a requirement or action and carry an owner, date, version and review status. Before filing, closure or management assurance, a second consistency review should test whether claims, contracts, governance records and operational proof remain aligned.
Cross-border and professional-practice controls
In cross-border work, the language of a deliverable does not determine the governing law. the EU core is common while contract, privacy, employment and supervisory interfaces can remain local. Each country therefore passes a separate jurisdiction, practice-rights and professional-conduct gate. OIKONOMAKIS LAW may coordinate the overall matter, while local-law opinions or representation are allocated to appropriately qualified professionals where required. The same distinction applies to marketing: a service that can be delivered into a market is not automatically eligible for every form of paid targeting or personalized solicitation in that jurisdiction.
Level 2 measures belong inside the diagnostic
DORA implementation cannot be tested against Regulation 2022/2554 alone. The controlled source pack should include the current measures on ICT risk management, incident classification/materiality, incident reporting and the Register of Information. A diagnostic should map requirements to the entity’s category and proportionality rather than use one universal checklist. The same control objective may require materially different governance and evidence in a small regulated entity and a complex financial group.
Board accountability and risk acceptance
Management needs more than technical dashboards. It should understand material ICT risks, critical provider dependencies, failed tests, overdue remediation and residual risk that requires acceptance. Risk acceptance should be an explicit decision, not the unintended result of inactivity. This is why DORA should be treated as a governance and evidence framework rather than an IT documentation exercise.
Deeper analysis and implementation
DORA is a management-accountability system
DORA cannot be reduced to an IT implementation project. Management needs a reliable view of ICT risk appetite, critical dependencies, material incidents, testing outcomes and overdue remediation. Reporting must translate technical facts into decisions: which business service is exposed, what residual risk remains, what resource or approval is required and who has accepted the position.
Governance is tested by the decision trail. A dashboard without clear decision rights and documented escalation does not establish accountability. The same point applies to group ICT models: the regulated entity remains responsible for understanding and governing the services on which it depends.
Evidence-first control testing
For each material requirement, the operating model should record control objective, owner, procedure, frequency, input, output record, testing method and escalation. Reviewers should sample actual periods and records rather than treating the existence of a policy as evidence of operation. Findings should be classified as design gaps, execution gaps, evidence gaps or legal-interpretation issues because each category requires a different remediation response.
Closure is similarly evidence-based. A finding moves from open to closed only after the required corrective action has been performed and new evidence has been reviewed. Management should be able to see partial remediation and residual exposure rather than a binary status supplied by the action owner.
The 2026 supervisory dataset matters
The first annual ESA report on major ICT-related incidents provides a factual supervisory context after DORA became operational. System failures, external events, cross-border impact and third-party dependencies demonstrate why incident management, continuity, provider governance and contracts have to operate as one resilience system. The service should therefore be recurring, with periodic evidence reviews, Register of Information quality checks, testing oversight and remediation follow-up.
Contract review is a central legal workstream. Service descriptions, locations, access and information rights, incident cooperation, subcontracting, continuity, termination and exit assistance must support the operational processes expected under DORA. A contract that does not deliver the information or cooperation required by the control framework creates a legal-operational gap.
Primary / official sources for publication verification
Regulation (EU) 2022/2554 (DORA) — https://eur-lex.europa.eu/eli/reg/2022/2554/oj/eng — Core DORA framework.
Commission Implementing Regulation (EU) 2024/2956 — https://eur-lex.europa.eu/eli/reg_impl/2024/2956/oj/eng — Register of Information.
Prepared by Christos Oikonomakis, Chairman, OIKONOMAKIS LAW
