Why does DORA require ICT risk governance, process and technology to work as one?
Article 5 of DORA places ultimate responsibility for ICT risk on the management body. A management body can only oversee what it can see, and it can only see clearly when governance, process and technology describe the same reality.
We look at DORA in three layers:
- Governance: the ICT risk management framework, the ICT third-party risk strategy and the authority to classify major incidents, all anchored in your existing governance and delegation structure.
- Process: IT operations, incident response, procurement, business continuity and internal audit each take on the requirements that naturally land on them.
- Technology: CMDB, SIEM, access control, backup and failover testing keep producing records you can trace.
The most common break point is that critical or important functions are defined one way in the CMDB, another in contracts and a third in the business continuity plan. Integration means each piece of data is created once, then serves the management body upstream and operations and security teams downstream.
We start from the framework you already operate and build the DORA requirements into it rather than creating a parallel one, cutting duplicated effort now and maintenance cost later. One team covers risk management, standards and regulatory compliance, implementation and security engineering, and process improvement, and VP- and director-level consultants lead the engagement end to end, never outsourced. For the technical controls, see DORA technical integration.
How does Ahura keep DORA evidence shared with ISO 27001 and ISO 22301?
DORA resilience testing, incident records and third-party assessments overlap heavily with ISO 27001 and ISO 22301 records, and financial customers' due diligence questionnaires ask for the same material. Continuous integration starts from one principle: a single evidence record and a single sign-off chain should be referenced by every framework that needs it.
The Ahura enterprise risk management platform is currently at proof-of-concept (POC) stage, and everything below refers to the POC version. In a DORA programme it is the evidence and sign-off layer; it does not replace your SIEM, CMDB or contract management system.
- Available in the POC: 100% on-premises deployment; an end-to-end evidence chain in which every sign-off is recorded and compatible with EU eIDAS certificates; a group-wide distributed architecture; EU multilingual interface; modular extension for EU regulations and international standards.
- In development, released as the POC progresses: cross-standard comparison, gap analysis on uploaded documents, regulatory version timelines and regulatory change tracking. There is no DORA-specific module today.
Today, test reports, three-stage incident reports and third-party assessments can be signed off on one chain and cited across DORA, ISO certification audits and customer audits. Once the development features ship, the goal is to show which evidence needs a second look when technical standards are updated.
How can you outsource the ICT internal audit DORA Article 6 requires, and keep it independent?
Article 6(6) of DORA requires the ICT risk management framework to be subject to internal audit by auditors with sufficient knowledge, skills and expertise in ICT risk and appropriate independence; Article 6(4) requires appropriate segregation and independence of ICT risk management, control and internal audit functions. Our internal audit outsourcing service performs ICT audit work for you, while the audit plan and conclusions remain owned by your internal audit function, a co-sourcing model. ICT providers serving EU financial customers also use it as a readiness check before customer audits.
Under ISO 9000:2015, 3.13.1, an internal audit may be conducted by the organisation itself or on its behalf, and independence can be demonstrated by freedom from responsibility for the activity being audited. Our principle follows directly: a consultant never audits a process they designed. The audit is performed by a consultant who had no part in that design.
After the audit we work through the findings with your management body and sort them into three horizons: fixes that cannot wait, items for next year's testing programme, and longer-term capability building. The result is a roadmap you can track. An internal audit is not third-party certification and does not stand in for a supervisory conclusion; Winners Consulting provides consulting only and does not issue certifications.
How do supplier audits of ICT third-party providers protect your supply chain under DORA Article 28 onwards?
Article 28 of DORA requires financial entities to manage ICT third-party risk: assess before contracting (paragraph 4), contract only with providers that comply with appropriate information security standards (paragraph 5), and pre-determine the frequency and scope of audits and inspections on a risk-based approach (paragraph 6). Where services support critical or important functions, Article 30(3)(e)(i) requires the contract to grant unrestricted rights of access, inspection and audit.
Our DORA supplier audit service audits ICT third-party service providers on your behalf. Under ISO 9000:2015, 3.13.1, that makes it a second-party audit. It is not certification: the findings belong to you and feed directly into contract terms, the register of information and exit planning, giving you supply chain assurance you can evidence.
| Supplier type | Audit focus (DORA requirement) | Evidence retained |
|---|---|---|
| Cloud service providers | Art. 30(3)(e)(i): access, inspection and audit rights | Audit report, contractual audit clauses |
| Core system and software vendors | Art. 28(4): pre-contract assessment | Pre-contract assessment record |
| Data centre and colocation providers | Art. 28(5): information security standards | Standards evidence, on-site review record |
| Outsourced SOC and MSSPs | Art. 28(6): risk-based audit frequency and scope | Annual audit plan, audit reports |
| All ICT third-party providers | Art. 28(3) and 28(8): register of information, exit strategies | Register of information, exit strategy documents |
To scope an ICT third-party audit programme, contact us.
Official sources
- Regulation (EU) 2022/2554 (Digital Operational Resilience Act, DORA) — EUR-Lex
- EIOPA — Q&A DORA 228-3317 on Article 28(6) and Article 30(3)(e)(i) access, inspection and audit rights
- ISO/TC 176 — Terms and definitions in TC 176 standards (ISO 9000:2015, 3.13.1 audit, Notes 1–4)
- ISO CASCO — Conformity assessment techniques: Auditing (first-, second-, third-party audits)
