DORA readiness for financial entities and their ICT providers
DORA treats ICT failure as a financial-stability risk and puts it on the management body. For a supplier, it is the reason a bank’s questionnaire changed.
The short version
DORA readiness is preparing a financial entity, or an ICT provider that serves one, for the Regulation’s ICT risk framework, incident reporting, resilience testing and third-party requirements, with the evidence behind each.
Whether you are a financial entity under DORA, and what a competent authority expects of you, are questions for your counsel and your authority; we prepare the framework documents, the register, the playbooks and the evidence. As of November 2026 the points below are from the Regulation as published and the Commission’s delegated and implementing acts linked on this page.
Who it covers
DORA applies from 17 January 2025 to credit institutions, payment and electronic money institutions, investment firms, crypto-asset service providers, insurers and reinsurers, trading venues, fund managers and the other financial entities listed in Article 2, and it also applies to ICT third-party service providers, with exceptions listed in that Article.
A provider of ICT services to a financial entity is therefore covered in two ways: through the contract terms the financial entity must obtain, and, where the European Supervisory Authorities designate it as critical, through direct EU oversight.
The ICT risk framework
The management body defines, approves and oversees the ICT risk management framework and bears the ultimate responsibility for managing ICT risk. The framework is organized around identification, protection and prevention, detection, response and recovery, backup and restoration, learning and evolving, and communication, in Articles 8 to 14; the Commission’s Delegated Regulation (EU) 2024/1774 sets the tools, methods and policies and the simplified framework.
We turn that into the policy set, the asset and dependency inventory and the evidence register, using cyber risk and governance, business impact analysis and vulnerability management.
Incident reporting
A financial entity must classify ICT-related incidents and report major ones: an initial notification as early as possible and within four hours of classifying the incident as major and no later than 24 hours from becoming aware of it, an intermediate report within 72 hours of the initial notification, and a final report no later than one month after the intermediate report. The time limits are in Article 5 of Commission Delegated Regulation (EU) 2025/301; the classification criteria and materiality thresholds are in Delegated Regulation (EU) 2024/1772.
We write the classification procedure and the playbook, and rehearse it with the people who would use it, in incident readiness and tabletop exercises. Which incident is major, and what is filed, is decided by the entity.
Testing
Financial entities other than microenterprises must make sure at least yearly that appropriate tests are conducted on the ICT systems and applications that support critical or important functions, and entities identified by their authority must carry out threat-led penetration testing at least every three years. The detailed requirements are in Delegated Regulation (EU) 2025/1190.
The threat-led penetration test itself is carried out by testers who meet the Regulation’s requirements; we prepare the scope, the evidence and the provider coordination around it, and do not perform it. The adversary simulation is described on red teaming; the yearly tests are usually a penetration testing and vulnerability management schedule that we help set up.
Third parties and the register
A financial entity must maintain a register of information on all its contractual arrangements for ICT services from third-party providers, distinguishing those that support critical or important functions, and report at least yearly to its competent authority on new arrangements and the categories of providers. The templates are in Implementing Regulation (EU) 2024/2956.
Contracts for ICT services must include at least a description of the services and any subcontracting, the locations of services and data, provisions on availability, authenticity, integrity and confidentiality, access to and return of data on insolvency or termination, service levels, assistance in incidents, cooperation with authorities, and termination rights; contracts for critical or important functions add further terms.
The European Supervisory Authorities designate the ICT third-party service providers that are critical for financial entities and appoint a Lead Overseer for each, which gives those providers a direct EU supervisor. The ESAs describe the framework on the ESMA and EBA pages.
For a financial entity we build the register from the contracts and the systems, with vendor risk management. For a provider we map the entity’s expected terms to your contract and your controls; our article sets out the clauses.
What you get
- A gap view against the framework, incident, testing and third-party chapters, with the evidence that exists.
- An incident classification and reporting playbook, rehearsed.
- A register of information and the supplier tiering behind it, or, for a provider, the control and contract map a customer will ask for.
- A testing calendar and the scope notes for the testers.
DORA sits beside the EU’s other laws: NIS2 for entities outside the financial sector, and the GDPR for the personal data in every incident.
How the work is bounded
The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.
SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.
Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.
Questions we are asked
What does DORA readiness cover?
DORA readiness is preparing a financial entity, or an ICT provider that serves one, for the Regulation’s ICT risk framework, incident reporting, resilience testing and third-party requirements, with the evidence behind each.
Who does DORA apply to?
DORA applies from 17 January 2025 to credit institutions, payment and electronic money institutions, investment firms, crypto-asset service providers, insurers and reinsurers, trading venues, fund managers and the other financial entities listed in Article 2, and it also applies to ICT third-party service providers, with exceptions listed in that Article.
What are the DORA incident reporting stages?
A financial entity must classify ICT-related incidents and report major ones: an initial notification as early as possible and within four hours of classifying the incident as major and no later than 24 hours from becoming aware of it, an intermediate report within 72 hours of the initial notification, and a final report no later than one month after the intermediate report.
What testing does DORA require?
Financial entities other than microenterprises must make sure at least yearly that appropriate tests are conducted on the ICT systems and applications that support critical or important functions, and entities identified by their authority must carry out threat-led penetration testing at least every three years.
What is the register of information?
A financial entity must maintain a register of information on all its contractual arrangements for ICT services from third-party providers, distinguishing those that support critical or important functions, and report at least yearly to its competent authority on new arrangements and the categories of providers.
What must a contract with an ICT provider contain?
Contracts for ICT services must include at least a description of the services and any subcontracting, the locations of services and data, provisions on availability, authenticity, integrity and confidentiality, access to and return of data on insolvency or termination, service levels, assistance in incidents, cooperation with authorities, and termination rights; contracts for critical or important functions add further terms.
Do you carry out the threat-led penetration test?
The threat-led penetration test itself is carried out by testers who meet the Regulation’s requirements; we prepare the scope, the evidence and the provider coordination around it, and do not perform it.
Tell us which side of the contract you are on
Say whether you are a financial entity or a provider, which services and which authority. The reply says what a scope would cover. Related: the European Union page.