Article 8, paragraph 3, of Regulation (EU) 2022/2554 requires financial entities, other than microenterprises, to carry out a risk assessment “upon each major change in the network and information system infrastructure, in the processes or procedures” affecting their business functions supported by information and communication technologies (ICT). Replacing a payment engine, changing hosting provider, opening an online credit journey: a banking IT project is, more often than not, a change of this kind. The DORA question for banks therefore plays out less in a compliance programme than in the running of each project.
The regulation has applied since 17 January 2025 (Article 64). Together with the technical standards that supplement it, it expects a banking project to include a risk assessment of the change, testing and approval before go-live, compliant provider contracts and, if it affects a critical or important function, information of the management body. Its definition and its five pillars are set out in our entry on the DORA regulation.
What the text says about changes and projects
Two other provisions of the regulation address what a project does to the information system.
- Article 8, paragraphs 6 and 7. Inventories of assets and dependencies are updated upon each major change. Legacy ICT systems, at end of life or no longer supported but still in use, are subject to a specific assessment “in any event before and after connecting technologies, applications or systems”.
- Article 9, paragraph 4, point (e). A documented change management policy ensures that all changes to systems are “recorded, tested, assessed, approved, implemented and verified in a controlled manner”.
Delegated Regulation (EU) 2024/1774, which supplements DORA, goes into detail. Its Article 15 requires an ICT project management policy: governance and roles, planning, project risk assessment, milestones, change management, testing of all requirements, security included, and approval upon deployment to production. Its Articles 16 and 17 govern development, maintenance and change management.
DORA for banks: who is concerned, from the institution to its providers
Article 2, paragraph 1, opens the list of financial entities with credit institutions. A banking group may bring together others: payment institution, investment firm, management company, insurance undertaking. Each one is subject to the text in its own right.
Credit institutions are not among the entities eligible for the simplified framework of Article 16, which covers in particular institutions exempted from Directive 2013/36/EU: a bank applies the full framework, adjusted by the proportionality principle of Article 4. Article 5 assigns to the management body “the ultimate responsibility for managing the financial entity’s ICT risk”. Supervision falls to the authority designated under Directive 2013/36/EU and, for institutions classified as significant, to the European Central Bank (Article 46).
On the supplier side, Article 3, point 19, defines the ICT third-party service provider as “an undertaking providing ICT services”. Article 3, point 20, separately defines the “ICT intra-group service provider”. Recital 63, which sheds light on the text without creating an obligation, states that undertakings in a financial group that provide these services predominantly to their parent undertaking or its subsidiaries should be considered ICT third-party service providers: a group’s IT subsidiary is therefore not, in principle, out of scope. The qualification of a given service (integration, development, hosting) with regard to Article 3, point 21, is checked with your legal and compliance functions.
The critical or important function, the first question at framing
Article 3, point 22, calls critical or important a function whose disruption would materially impair the financial performance of the entity, the soundness or continuity of its services, or its ability to comply with the conditions of its authorisation. This qualification governs the heaviest requirements:
- appropriate tests, at least once a year, on all systems and applications that support the function (Article 24, paragraph 6);
- reinforced contractual clauses: precise service level objectives, rights of access, inspection and audit, transition period in the event of exit (Article 30, paragraph 3);
- a documented and tested exit strategy (Article 28, paragraph 8);
- information of the competent authority, “in a timely manner”, on any planned contractual arrangement for ICT services supporting the function (Article 28, paragraph 3);
- information of the management body on the launch of the project, its progress and its risks (Delegated Regulation 2024/1774, Article 15, paragraph 5).
The project does not decide this qualification. It follows from the inventory the bank keeps under Article 8, and is obtained in writing, at the framing stage, from the function responsible for it.
From framing to operation: what changes in a banking project
| Project stage | What the text expects | Reference |
|---|---|---|
| Framing | Affected functions qualified; risks of the change assessed; roles, milestones and tests planned | DORA, Art. 8(3); Delegated Regulation 2024/1774, Art. 15 |
| Choosing a provider | Prior risk analysis, including concentration; mandatory clauses; register of information | DORA, Art. 28(3) and (4), Arts. 29 and 30 |
| Design and build | Security requirements approved by the business and the asset owner; source code review; anonymised, pseudonymised or randomised production data outside production | Delegated Regulation 2024/1774, Art. 16 |
| Acceptance and go-live | Testing and approval before use; approval of the change independent of its request and its implementation; fallback procedure | Delegated Regulation 2024/1774, Art. 16(2) and Art. 17 |
| After go-live | Inventories updated; continuity plans retested in the event of substantial change; at least annual testing of systems supporting a critical or important function; incidents classified and reported | DORA, Art. 8(6), Art. 11(6), Arts. 17 to 19, Art. 24(6) |
These rows shift the schedule on four points. The project team does not approve its own go-live alone: an independent function must have time to examine the file. Copying the production database ceases to be the default solution in acceptance testing, and the test data set becomes a work package at the start of the project, the subject of our article on data anonymisation. The audit rights and the exit clause of a contract are negotiated before signature.
Finally, monitoring and escalation for the new system work from day one. Delegated Regulation (EU) 2025/301 sets, in its Article 5, the initial notification of a major incident at no more than four hours after its classification, and no more than twenty-four hours after the entity became aware of it. Our page on banking and insurance places these requirements among the other texts that frame a financial project.
What DORA does not settle
Neither the regulation nor Article 15 of the delegated regulation prescribes a project method. The required elements fit a sequential cycle as well as continuous delivery; in the latter case, independent approval and the record of tests are designed into the delivery pipeline, with the control function.
The relationship with Directive (EU) 2022/2555, known as NIS2, comes down to one provision. According to Article 1, paragraph 2, of DORA, the regulation is, for financial entities identified as essential or important under that directive, a sector-specific Union legal act for the purposes of its Article 4. The latter sets aside the corresponding provisions of the directive where the sector-specific act imposes requirements at least equivalent in effect. Our entry on the NIS2 directive develops this point.
Interpretation is for your legal and compliance functions, on the consolidated version of the texts. Translating it into continuity plans, tests and provider monitoring falls under cyber resilience.
The commitment decision, reread in the light of DORA
The committee that commits to the project first rules on one document: the written list of the critical or important functions affected, drawn up with the agreement of the ICT risk control function. If this list is not empty, the file already provides, for the ICT services supporting these functions, the reinforced clauses of Article 30, paragraph 3, and an exit strategy, as well as information of the management body on the project and of the competent authority on any planned contract.
Whatever this qualification, the plan submitted provides for the risk assessment of the change and its update at milestones, the review of each ICT service contract against Article 30 and its entry in the register of information, anonymised, pseudonymised or randomised test data (or an approved derogation), approval of the go-live by a function that neither requested nor implemented the change, a fallback, then the classification and reporting of incidents from the first day of operation.
Without this list, neither the budget nor the schedule presented can be judged: it is obtained before committing to the build.