DORA Digital Operational Resilience Compliance
Financial Entities × ICT Suppliers — Bilateral Applicability
DORA has applied since 17 January 2025. EU financial entities are now requiring ICT suppliers to provide audit rights, exit strategies, and Register of Information details. Taiwan tech vendors serving European banks, insurers, or payment institutions face de facto contractual obligations. Winners Consulting prepares both sides to reduce contract disruption risk.
⏱ DORA Phased Timeline
What is DORA? Why Are Taiwan ICT Vendors Affected?
DORA (Digital Operational Resilience Act) is the EU's financial sector digital resilience regulation, requiring financial entities to build systematic ICT risk management capabilities to maintain critical business operations during ICT disruptions or cyberattacks. Direct impact on Taiwan vendors: EU financial entities must include audit rights, exit strategies, and data portability clauses in ICT supplier contracts under DORA, and maintain detailed Register of Information supplier registers. Taiwan SaaS, cloud, and security service providers serving EU banks or insurers face de facto contractual obligations through their clients.
DORA Applicable Entities
- •Commercial banks / credit institutions
- •Insurance / reinsurance companies
- •Investment firms / fund managers
- •Payment institutions
- •Electronic money institutions
- •Crypto-asset service providers (CASP)
- •Central counterparties (CCP)
- •Credit rating agencies
- •Others: account information services, CSDs, trading venues, insurance intermediaries, IORPs and more (20 types in Art. 2(1))
General ICT Suppliers
Managed through contractual obligations: audit rights, SCCs, exit strategy, Register of Information cooperation
Critical Third-Party Providers (CTPP)
Designated by ESAs for direct supervision; fines up to 1% of daily global turnover (first 6 months)
Common Taiwan applicable vendors: core banking SaaS, cloud infrastructure, MSSP, data analytics platforms, payment processing services
DORA Five Compliance Pillars
Winners Consulting conducts gap analysis against this framework and builds compliant documentation for each chapter
Chapter II
ICT Risk Management Framework
- ·ICT asset inventory and classification
- ·Risk identification and assessment
- ·Protection and prevention measures
- ·Detection mechanism establishment
- ·Response and recovery procedures
- ·Learning from past incidents
Chapter III
Major Incident Reporting
- ·Incident severity assessment criteria
- ·Initial notification within 4h of classification as major (max 24h after awareness)
- ·Intermediate report within 72h of the initial notification
- ·Final report within 1 month of the intermediate report
- ·Reporting pathway to ESAs/NCA
- ·Cyber threat intelligence sharing
Chapter IV
Digital Operational Resilience Testing
- ·Annual basic testing plan
- ·Vulnerability assessment/penetration testing
- ·TLPT (entities identified by authorities, at least every 3 years)
- ·TIBER-EU framework execution
- ·Test result improvement feedback
- ·Third-party tester qualification confirmation
Chapter V
Third-Party ICT Risk Management
- ·Supplier risk assessment methodology
- ·Contractual mandatory clause review
- ·Audit rights clauses
- ·Exit strategy design
- ·Register of Information maintenance
- ·Critical supplier concentration risk monitoring
Chapter VI
Information Sharing
- ·Voluntary cyber threat intelligence sharing
- ·Industry information sharing arrangements
- ·Confidential information protection mechanism
✅ DORA Compliance Preparation Complete
- ✓ICT risk management framework established; financial client audits passed on first attempt
- ✓Complete Register of Information package meeting EU financial client requirements
- ✓Mandatory contract clauses prepared; new client negotiations accelerated, existing contract renewals smooth
- ✓Incident reporting SOP ready (4h after classification, within 24h of awareness); major incidents not delayed by unclear procedures
- ✓TLPT applicability confirmed; avoiding misdirected resource investment
- ✓Exit strategy documentation complete; strong basis for negotiating client contract risk clauses
× Risks of Unpreparedness
- ×European financial clients requiring DORA audit cooperation; no documents to submit leads to contract termination
- ×Incomplete Register of Information; client classifies vendor as unqualified supplier
- ×Contracts without audit rights clauses; new client negotiations collapse, orders lost
- ×Major incident not notified within 4 hours of classification (and 24 hours of awareness); may face penalties under national law
- ×Designated as CTPP without preparation; direct ESAs supervision catches vendor off guard
- ×No exit strategy documentation; clients unable to fulfill DORA business continuity obligations
Winners Consulting DORA Advisory Process
Five steps for financial entities and ICT suppliers to complete DORA obligations
Applicability Assessment & Scope Confirmation
Confirm whether the organization is a DORA-applicable financial entity type, or an ICT supplier to financial entities; assess direct obligations vs. indirect contractual obligation scope.
ICT Risk Management Framework
Build ICT risk management framework per DORA Chapter II: ICT asset inventory, risk identification and assessment, protection measures, detection mechanisms, response and recovery procedures.
Incident Reporting SOP
Establish major ICT incident reporting process per DORA Chapter III: initial notification within 4 hours of classifying the incident as major (no later than 24 hours after awareness), intermediate report within 72 hours of the initial notification, final report within one month of the intermediate report (Delegated Regulation (EU) 2025/301); design classification criteria under Delegated Regulation (EU) 2024/1772.
Third-Party ICT Risk Management
Build ICT third-party supplier risk management procedures: supplier risk assessment methodology, mandatory contract clauses (audit rights, data portability, exit strategy), Register of Information maintenance.
TLPT Planning & Ongoing Resilience Testing
Plan digital operational resilience testing program per DORA Chapter IV, including annual basic testing (vulnerability assessment/penetration testing) and, where the authorities identify the entity, TLPT at least every three years; ensure test results feed back into risk management improvement.
Frequently Asked Questions
What is DORA? Which organizations must comply?▾
DORA (Digital Operational Resilience Act, Regulation (EU) 2022/2554) is the EU financial sector digital operational resilience regulation. It entered into force on 16 January 2023 and has applied since 17 January 2025 (Article 64). It applies directly to the 20 types of EU financial entities listed in Article 2(1), such as credit institutions, insurance and reinsurance undertakings, investment firms, payment institutions, electronic money institutions, crypto-asset service providers, central counterparties and trading venues; Article 2(1)(u) also brings ICT third-party service providers into scope, mainly through the oversight framework for critical providers.
How are Taiwan ICT vendors affected by DORA?▾
Taiwan SaaS, cloud service, and security service vendors serving EU financial entities face DORA obligations through contractual requirements: audit rights, data portability, business continuity clauses, and exit strategies. Financial clients must also include vendors in their Register of Information, requiring detailed service information.
What are the DORA major ICT incident reporting timelines?▾
Article 19 of DORA requires three-stage reporting, with time limits set by Delegated Regulation (EU) 2025/301: (1) initial notification within 4 hours of classifying the incident as major, and no later than 24 hours after becoming aware of it; (2) intermediate report within 72 hours of the initial notification, updated when regular activities have been recovered; (3) final report within one month of the latest intermediate report. Whether an incident is major is decided under Article 18 and Delegated Regulation (EU) 2024/1772, using criteria such as clients and transactions affected, duration, geographical spread, data losses, criticality of services and economic impact.
What is TLPT? Do all financial institutions need it?▾
TLPT (Threat-Led Penetration Testing) is carried out under DORA Article 26 and Delegated Regulation (EU) 2025/1190, in line with the TIBER-EU framework. Only financial entities identified by the competent authorities under Article 26(8) must perform it, at least every three years (authorities may change the frequency); by default these include G-SII and O-SII credit institutions, central securities depositories, central counterparties, payment and e-money institutions above thresholds, certain trading venues and large insurers. Other financial entities (except microenterprises) must test systems supporting critical or important functions at least yearly (Article 24). Neither DORA nor that regulation sets a 2027 deadline for a first TLPT cycle. Winners Consulting provides TLPT applicability assessment and testing planning.
What is the DORA Register of Information? How is it built?▾
The register of information is the register of contractual arrangements for ICT services from third-party providers that financial entities must keep under Article 28(3), using the templates in Implementing Regulation (EU) 2024/2956. It records the services, contracts, whether they support critical or important functions and the relevant subcontractors; providers outside the EU are identified by LEI. For the first submission in 2025, national competent authorities had to forward the registers to the European Supervisory Authorities by 30 April 2025, with financial entities submitting earlier to their own authority on national timelines; reporting is now annual. Taiwan ICT suppliers must help EU financial clients provide this information.
What is the difference between DORA and NIS2? Do they need separate compliance?▾
DORA is the lex specialis for the financial sector. Under DORA Article 1(2), NIS2 Article 4 and recital 28, and the Commission guidelines (C/2023/6068), Member States should not apply NIS2's cybersecurity risk-management and reporting obligations (including governance and management liability, and supply chain security) or its supervision and enforcement provisions to DORA financial entities; DORA Article 5 and Articles 28 to 30 apply instead. NIS2 Article 9 (national cyber crisis management frameworks) and Article 16 (EU-CyCLONe) continue to apply. Group companies or ICT suppliers that are not DORA financial entities may still fall under NIS2 in their own right. Winners Consulting provides integrated DORA + NIS2 assessment.
Which enterprises is Winners' DORA advisory suitable for? How long does it take?▾
Suitable for: (1) Taiwan SaaS/cloud/security vendors serving EU financial clients; (2) Taiwan fintech enterprises with EU operations. ICT supplier contractual obligation preparation typically takes 2-3 months; full DORA framework for financial institutions takes 6-9 months; substantially shorter for organizations with existing ISO 27001/BCM foundations.
We have already completed an DORA compliance project. How can Winners Consulting help us keep improving?▾
Several DORA obligations recur on a fixed cycle. Winners Consulting can help you check, before each annual Register of Information submission, the ICT third-party contracts, whether they support critical or important functions, and subcontractor details (or prepare this information for your financial-sector clients); plan the annual testing under Article 24 and, if your competent authority designates you, TLPT at least every three years; review your major-incident classification criteria against Delegated Regulation (EU) 2024/1772 and rehearse the initial notification within 4 hours of classification and no later than 24 hours after awareness; and update exit strategies and required contract clauses as contracts change. See our DORA compliance service.
We completed an DORA compliance project with another consultancy's support. How can Winners Consulting help us embed the system fully into day-to-day operations and make sure it genuinely prevents these risks?▾
We first review the gap between the documents and day-to-day practice: whether the incident classification criteria are actually used by on-call staff, whether procurement checks audit-right and exit-strategy clauses when buying new ICT services, and whether the Register of Information is updated when contracts change. We then build the DORA requirements into your existing IT operations, procurement and incident response processes: once an incident is classified as major, the clocks for the initial, intermediate and final reports start; required clauses are checked before a new contract is signed; and test results feed back into risk management improvements. The Ahura enterprise risk management platform (at POC stage) keeps the evidence and sign-off records on premises in your own environment. See how DORA technical integration works.
Confirm Your DORA Obligation Scope
Free assessment: determine if your company is a financial entity or ICT supplier, confirm contractual obligation scope, evaluate Register of Information preparation status, provide shortest-path compliance planning.
Related Deep Insights
In-depth analysis by Winners consultants, 6,000+ words per article
