Which existing processes at financial entities and ICT suppliers does DORA plug into?
DORA (Regulation (EU) 2022/2554) has applied since 17 January 2025. It does not ask you to build a separate "resilience department". It asks that the processes you already run can prove ICT risk is being managed. In practice we start by finding five existing processes and then hang the articles onto them one by one:
- IT operations and change management: asset changes, patching and releases carry the Chapter II ICT risk management framework and the detailed asset, vulnerability and change requirements in Delegated Regulation (EU) 2024/1774.
- Security incident response and customer service: monitoring alerts, transaction anomalies and customer complaints should be classified under Article 18 on the same ticket, and move into Article 19 reporting when needed.
- Procurement and supplier management: due diligence, contract clauses, renewal and exit map to Chapter V on ICT third-party risk and to the register of information under Article 28(3).
- Business continuity and disaster recovery: backups, failover and exercises carry the ICT business continuity policy and its testing.
- Internal audit and management reporting: Article 5 makes the management body ultimately responsible for ICT risk, so the reporting line has to put numbers in front of it.
If you are a Taiwanese ICT supplier serving EU financial clients, the same processes connect the other way round: your clients' demands for audit rights, exit strategies and register data arrive at your sales, legal and operations desks. Our rule is to start from the system you already have and fold the requirements into it, rather than building a parallel one.
Which implementation and security technologies put DORA's articles into practice?
The Regulation sets principles; most technical detail sits in the delegated acts. These are the mappings we implement most often, and every article in the left column can be checked in the Official Journal:
| Requirement (article / control) | Implementing technology | Evidence left behind |
|---|---|---|
| DORA Art. 5 and 6: governance and the ICT risk management framework | Risk register, version-controlled framework documents, periodic reporting to the management body | Framework approved by the management body, review records |
| Delegated Regulation (EU) 2024/1774 Art. 4–5: ICT asset management policy and procedure | CMDB and automated asset discovery, tagging assets that support critical or important functions and their dependencies | Asset inventory, classification results, dependency maps |
| 2024/1774 Art. 6–7: encryption and cryptographic key management | Encryption in transit and at rest; KMS/HSM for the key lifecycle | Encryption policy; key generation, rotation and destruction records |
| 2024/1774 Art. 10: vulnerability and patch management | Vulnerability scanning, dependency scanning, patch scheduling with approved exceptions | Scan reports, patch-time statistics, exception list |
| 2024/1774 Art. 20–21: identity management and access control | IAM, multi-factor authentication, privileged access management (PAM) | Account reconciliation and access review records |
| 2024/1774 Art. 12, 22, 23: logging, incident management policy, anomaly detection | Centralised SIEM logging, detection rules, SOC on-call | Alert and response records, detection-rule versions |
| DORA Art. 18–19; Delegated Regulations (EU) 2024/1772 and (EU) 2025/301: classifying and reporting major incidents | Classification rules and a timed reporting workflow (initial notification within 4 hours of classification and 24 hours of awareness, intermediate report within 72 hours, final report within one month) | Classification rationale, the three reports with timestamps |
| DORA Art. 24, 26, 28; Implementing Regulation (EU) 2024/2956: resilience testing and the register of information | Annual test programme, vulnerability assessments and penetration tests, TLPT planning; register maintained on the official templates | Test reports with remediation tracking, register data files |
Two points are often misread. First, TLPT (threat-led penetration testing) applies only to financial entities identified by the competent authorities under Article 26(8), at least every three years; other financial entities (except microenterprises) test systems supporting critical or important functions at least yearly under Article 24. Second, whether an incident is "major" is not a judgement call. It 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. Only once those rules are built into the workflow do the 4-hour and 24-hour clocks have a clear starting point.
How does ICT risk flow through to DORA articles, technical controls and metrics?
DORA projects most often fail when risk, compliance and IT each write their own documents. We tie them into one chain. Take a payment service that depends on a single cloud region:
- Risk identification: a business impact analysis shows that an outage of the core transaction system beyond its tolerance would hit customer payments, and the system sits in one region of one cloud provider.
- Regulatory requirement: Article 28 requires managing ICT third-party risk and keeping the register of information; Articles 24 to 26 of Delegated Regulation 2024/1774 require an ICT business continuity policy, testing of the continuity plans and response and recovery plans; Article 18 requires classification criteria.
- Technical control: cross-region failover, backup-and-restore exercises, a supplier exit strategy with portable data formats, and SIEM monitoring of cloud service health that opens incident tickets.
- Metrics: measured failover time against the recovery objective, the share of critical providers with an exit strategy, and time from detection to completed classification.
The chain can be walked in one pass because the same team plans the regulatory assessment, the processes and the technical controls together. Risk management, international standards and legal compliance, implementation and security technology, and process improvement do not need translating between four different vendors. The same evidence also answers several requirements: continuity work feeds ISO 22301 and security controls feed ISO 27001, which cuts duplicated effort.
Which departments, systems, data and evidence must DORA integrate vertically?
DORA evidence is not a single report. It is system records spread across six or seven departments. The key to vertical integration is making the label "critical or important function" mean the same thing in the CMDB, the contracts, the continuity plans and the incident classification. This is the mapping we usually build:
| Department | System | Data | Evidence |
|---|---|---|---|
| Board / management body | Governance reporting | ICT risk status, major-incident summaries, test results | Framework approval and annual review resolutions |
| IT operations | CMDB, change management | Asset inventory, change tickets, dependencies | Change approvals and traceability records |
| Security / SOC | SIEM, vulnerability scanners | Logs, alerts, vulnerability lists | Detection and response records, patch statistics |
| Procurement and legal | Contract management | Contract clauses, subcontractor details, LEI | Register of information, exit strategy documents |
| Business units and continuity | Backup and disaster recovery platform | Critical or important functions, recovery objectives | Continuity test and exercise reports |
| Risk and compliance | Incident reporting workflow | Classification data, reporting timestamps | The three reports and correspondence with authorities |
In practice we first agree a list of critical or important functions and use it as the primary key, then map down to the ICT assets that support each function, the third parties that provide them and the matching recovery objectives. The benefit is concrete. When an incident happens, the SOC does not have to ask the business whether a system matters. When a financial client or an authority asks for the register, the supplier list from procurement and legal matches the asset inventory from IT operations.
For ICT suppliers the same table shrinks into a client-requirements list: which contract clauses legal owns, which audit evidence operations provides, and which incident information must be passed to the client and how fast. Agreeing this up front means renewals and audits no longer depend on last-minute assembly.
What does Ahura do in a DORA engagement, and how does data flow?
Ahura is a Taiwan-born RegTech platform for enterprise risk and compliance developed by Winners Consulting. It is currently at POC (proof-of-concept) stage. In a DORA engagement it acts as the evidence retention and sign-off layer; it does not replace your SIEM, CMDB or contract system.
The data flow is: consultant deliverables (the ICT risk management framework, incident reporting procedure, register field mapping) and records produced by your systems (SIEM reports, test reports, register exports) → imported into Ahura on-premises → signed off step by step by the responsible owners, each sign-off entering the chain → available to internal audit, financial clients, certification bodies or authorities.
Capabilities in the POC version that matter for DORA:
- 100% on-premises: ICT risk assessments, vulnerability and incident records never go to the cloud or leave your environment.
- End-to-end evidence chain: every sign-off enters the chain, compatible with EU eIDAS certificates.
- Group-wide distributed architecture: one HQ policy with locally compliant sites.
- EU multilingual interface: German, French, Dutch, Czech and more, plus Traditional Chinese and English.
To be clear: DORA-specific modules (for example incident classification or the register of information) are planned under the modular extension design. For now the platform focuses on the evidence chain, sign-off and on-premises retention. Document upload with compliance gap analysis, cross-standard comparison and regulatory change tracking are in development and will open as the POC progresses.
What verifiable governance, risk, efficiency and continuous-compliance gains follow?
We do not promise a "first-time pass". We describe changes you can check once the work is done:
- Governance: the management body sees one set of ICT risk figures that can be traced back to the asset inventory, incident records and test reports, rather than slides assembled separately by each department. Article 5's "ultimate responsibility" then has something concrete to rest on.
- Risk: third-party concentration becomes visible. Which critical or important functions depend on the same provider or the same cloud region can be read from the register and the CMDB together, and exit strategies can be prioritised accordingly.
- Efficiency: one body of evidence answers several requirements. Financial clients' audit questionnaires, DORA's register and testing duties, and ISO 27001 and ISO 22301 certification draw on the same records. New requirements are folded into the existing system rather than a parallel one, which also lowers long-term maintenance.
- Continuous compliance: annual resilience testing, periodic register submissions and the three-stage reports after an incident become routine processes with clocks, owners and trails.
Indicators you can test include the match rate between the asset inventory and the register, actual hours from awareness to initial notification for major incidents, and the closure rate of annual test findings. Engagements are led in person by vice-president and director-level consultants, never outsourced; Winners provides consulting only and does not certify. To scope your case, contact us.
Technical integration for related services
Official sources
- Regulation (EU) 2022/2554 (Digital Operational Resilience Act, DORA) — EUR-Lex
- Commission Delegated Regulation (EU) 2024/1774 — RTS on ICT risk management tools, methods, processes and policies — EUR-Lex
- FMA (Austrian Financial Market Authority) — DORA: ICT-related incidents (reporting time limits under Delegated Regulation (EU) 2025/301)
