The Digital Operational Resilience Act, Regulation (EU) 2022/2554, has applied since 17 January 2025. It covers a wide range of EU financial entities. A&L Goodbody lists credit institutions, payment institutions, investment firms, crypto-asset service providers, trading venues, and insurers and reinsurers among them.
Most have done the first round of work. The harder part is reviewing, testing and reporting every year, in a way a supervisor can follow.
What DORA asks for
DORA has four main areas: ICT risk management, ICT-related incidents, resilience testing and ICT third-party risk. These are the requirements that recur, from the regulation’s text.
The management body is accountable. Under Article 5, it carries ultimate responsibility for ICT risk. It approves the digital operational resilience strategy and the ICT risk tolerance. It also approves the business continuity policy, ICT audit plans and the ICT third-party policy, and is kept informed of major incidents.
The framework is documented and reviewed. Article 6 asks for an ICT risk management framework, reviewed at least once a year and after major incidents. Internal auditors review it regularly, and critical audit findings must be followed up promptly.
You know what you have. Article 8 asks you to identify and document business functions, their owners, and the information and ICT assets behind them. You review this at least yearly. You also identify the processes that depend on ICT third-party providers.
You learn from incidents. Article 13 asks for a review after each major ICT-related incident, looking at causes and the improvements needed. Senior ICT staff report findings to the management body at least yearly.
Major incidents are reported on a clock. Under Article 19, you send an initial notification, an intermediate report and a final report to your competent authority. The technical standards set the timings. The initial notification is due 4 hours after classifying an incident as major, and within 24 hours of detecting it. The intermediate report follows within 72 hours, and the final report within one month.
Systems are tested. Article 24 asks for a testing programme. Systems supporting critical or important functions are tested at least once a year, and every weakness found is fixed and checked.
Suppliers are managed throughout. Article 28 asks for an ICT third-party risk strategy and a register of information covering every ICT contract. You assess risks and carry out due diligence before signing. For critical or important functions, you need documented and tested exit plans. Article 30 sets out what contracts must contain. For critical or important functions, that includes audit rights and exit strategies.
What it means for you
Much of DORA is about showing your working: why a risk was accepted, which supplier supports which function, and what changed after an incident. Many duties come back every year. Keeping them in one place, with owners and dates, makes each round easier.
How RiskWitness helps
This is how those recurring duties look in RiskWitness.
Know your assets and who owns them. Record your ICT assets with owners, where they are kept or hosted, and the risks, controls and suppliers linked to them.
Assess ICT risk consistently. Each risk has an owner, likelihood and impact before and after controls, a treatment decision and a review date. Set them so every risk comes back at least yearly.
Stay within your tolerance. Accepting a risk is recorded with a reason and an expiry. If it’s outside your tolerance, a named approver signs it off.
Test controls, then fix what fails. Record control tests and their results. Turn every weakness into an action with an owner and a due date.
Report incidents on time. Record an incident, link it to the risks, controls and assets involved, and choose DORA as a rule that applies. RiskWitness shows each report’s deadline and reminds you as it gets close. Afterwards, turn the lessons from the review into actions.
Manage ICT suppliers. Rate each supplier’s criticality and link it to the assets and risks it affects. Send questionnaires and keep assurance evidence with its expiry date. Check contracts for clauses such as audit rights, incident notification and exit, and record regular reviews.
Keep policies approved and current. Hold your business continuity and third-party policies with owners, review dates, and a record of which version leadership approved and when.
Follow up audits. Record internal audit findings and non-conformities, and give each one an action until it’s closed.
Keep the management body informed. Record committee meetings, minutes and decisions. Give the management body a PDF report or slide deck on risks, incidents and open actions.
Every step is kept in a history that records who did what, and when. Nobody can edit or delete it. When leadership, an auditor, a customer or your supervisor asks how a decision was made, the record is there to show them.
Sources
- Regulation (EU) 2022/2554 (DORA), EUR-Lex, published 27 December 2022
- Text of DORA Articles 5, 6, 8, 13, 19, 24 and 28, Springlex, from the Official Journal of 27 December 2022
- Joint technical standards on major incident reporting, European Banking Authority
- DORA: Management of ICT third-party risk, William Fry, 8 May 2023
- Digital Operational Resilience Act (DORA), A&L Goodbody
- DORA, Financial Market Authority Liechtenstein
