We use privacy-by-default, cookieless analytics.

Optional analytics cookies are used only if you accept them.

Read our Terms of Use and Privacy Policy.

FAQEU DORA

EU DORA Proportionality FAQ

DORA lets financial entities calibrate ICT risk management, testing, incident handling, and third-party oversight to their size, risk profile, and business complexity. It does not waive the underlying duties.

This FAQ helps separate scalable controls from mandatory DORA duties, including simplified-framework entities, , management-body accountability, ICT incident reporting, and selection.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
4 sections3 primary sources
Overview

DORA has applied since 17 January 2025. It uses to calibrate how in-scope financial entities implement digital operational resilience duties. The entity's size, overall ICT risk profile, services, activities, operations, and dependencies must justify the chosen level of governance, controls, testing, incident process, and supplier oversight.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

What does proportionality mean under EU DORA?

DORA Article 4 says financial entities must implement ICT risk management rules proportionately, taking into account their size and overall risk profile and the nature, scale, and complexity of their services, activities, and operations. The same lens also applies to ICT-related incident management, digital operational resilience testing, and ICT third-party risk management where the relevant chapters provide for it.

A smaller, lower-complexity entity may justify simpler governance, fewer layers of documentation, less extensive testing within the applicable programme, or less complex supplier oversight than a large systemic entity. The entity must still meet express duties and minimum frequencies, including annual testing of ICT systems and applications supporting critical or important functions where Article 24 applies. The justification must be tied to the entity's ICT risk facts.

  • Start with DORA scope and role: determine whether the organisation is a financial entity, an ICT third-party service provider, both, or excluded. Apply Article 4 to an in-scope financial entity's duties rather than using it to scale away a provider's contractual commitments or critical-provider oversight duties.
  • For an in-scope financial entity, record the factors: size, overall ICT risk profile, nature of services, scale of operations, complexity, critical or important functions, outsourced ICT services, and exposure to disruption.
  • Map what is being scaled: governance detail, control depth, documentation, test type and scope, remediation sequencing, supplier monitoring, or evidence retained for supervisory review. Do not reduce an express minimum frequency unless DORA or the competent authority permits it.
  • Do not treat as a waiver of the core obligation to manage ICT risk, handle incidents, report major ICT-related incidents, maintain required third-party records, or meet requirements when identified by the competent authority.

Does EU DORA let a financial entity opt out of DORA?

No. affects how DORA requirements are applied and evidenced; it does not remove DORA for an entity that is in scope. Separate scope exclusions are listed in DORA Article 2, and the in Article 16 still contains mandatory ICT risk, monitoring, continuity, testing, dependency, and training duties.

Which DORA facts should be documented before relying on ?

Document the entity type, whether any Article 2 exclusion or Article 16 simplified-framework status applies, the entity's size and overall ICT risk profile, the nature and scale of its services, the complexity of operations, critical or important functions, key ICT assets, outsourced ICT services, major ICT-related incident history, and any supervisory instruction or testing result that changes the risk picture.

Question 2

Who can use DORA's simplified ICT risk management framework?

DORA Article 16 replaces Articles 5 to 15 with a for specified categories: small and non-interconnected investment firms, exempted payment institutions, specified exempted institutions under Directive 2013/36/EU, exempted electronic money institutions, and small institutions for occupational retirement provision. Size by itself is not an eligibility test; the entity must fit one of those legal categories.

The simplified framework is still a real framework. These entities must maintain documented ICT risk management, monitor ICT systems, protect availability, authenticity, integrity, and confidentiality of data, detect and handle ICT incidents, identify key ICT third-party dependencies, ensure continuity of critical or important functions, regularly test continuity measures and controls, and feed test and incident lessons back into ICT risk assessment.

  • Use Article 16 only when the entity fits one of the listed categories; do not apply it merely because the entity is small or resource-constrained.
  • Keep one clear evidence file showing the Article 16 basis, the simplified ICT framework, the information security policy required by Delegated Regulation (EU) 2024/1774, and the periodic review report content where requested.
  • For , do not assume there is no testing duty: DORA Article 25 still requires ICT testing using a risk-based approach balanced against resources, urgency, type of risk, criticality of information assets, and services provided.
  • When the entity relies on ICT third-party services, keep the register and contract evidence proportionate to the criticality or importance of the service, dependency complexity, and potential impact on continuity and availability.

Does the remove DORA governance and testing duties?

No. It changes the framework for the Article 16 entity, but it still requires documented ICT risk management, monitoring, continuity, testing, incident handling, key dependency identification, staff and management awareness where needed, and periodic review. Delegated Regulation (EU) 2024/1774 adds detailed simplified-framework elements such as governance, information security policy, asset classification, ICT risk assessment, access control, vulnerability handling, business continuity, and review reporting.

Are exempt from all DORA testing?

No. DORA excludes from the Article 24 testing programme and from , but Article 25 requires them to perform appropriate ICT tests using a risk-based approach and strategic planning that balances available resources with urgency, risk type, asset criticality, services provided, and other relevant factors. For DORA, a microenterprise generally employs fewer than 10 people and has annual turnover and/or an annual balance-sheet total no higher than EUR 2 million; the definition excludes trading venues, central counterparties, trade repositories, and central securities depositories.

Question 3

What evidence supports a defensible DORA proportionality decision?

A defensible decision connects the scaled measure to the risk facts DORA names. The evidence should show why the selected control, test, policy, supplier-monitoring depth, or remediation timetable is adequate for the entity's size, risk profile, services, activities, operations, and ICT dependencies.

Delegated Regulation (EU) 2024/1774 gives useful evidence categories: the context of the entity's services and operations, identified critical functions, major projects or activities, relationships, dependence on in-house and outsourced ICT services and systems, the effect of severe degradation or loss, current and near-term ICT risk, threat landscape, control effectiveness, and security posture.

  • Entity and scope evidence: legal entity, DORA Article 2 category, any exclusion considered, and any Article 16 simplified-framework basis.
  • Risk profile evidence: ICT-supported critical or important functions, information and ICT asset classification, business impact analysis, current and near-term ICT risks, threat landscape, incident history, and testing findings.
  • Scaling evidence: what was made lighter or heavier, why the change remains adequate, who approved it, and what supervisory instruction, audit finding, incident, test, or supplier change would trigger review.
  • Third-party evidence: register entries, critical or important function classification, contract clauses, service-level monitoring, exit or continuity evidence, and a record that outsourcing does not transfer the financial entity's DORA responsibility.
  • Testing evidence: the risk basis for test type, frequency, scope, independence, remediation priorities, and any authority determination or attestation where advanced testing applies.
Question 4

What cannot be waived by calling it proportional under DORA?

does not erase DORA's core control points. It cannot be used to avoid having an ICT risk management framework, to ignore major ICT-related incidents, to skip required reporting, to transfer responsibility to a supplier, or to decline after the relevant authority identifies the entity as required to perform it.

It also cannot replace supervisory judgment. DORA says competent authorities consider how financial entities apply when reviewing ICT risk management framework reports submitted under Articles 6(5) and 16(2). For , competent authorities identify the financial entities required to perform advanced testing based on impact-related factors, financial stability concerns, and ICT risk profile, maturity, or technology features.

  • In-scope financial entities remain responsible for DORA compliance even when ICT services are outsourced or a third party assists with incident reporting.
  • Major ICT-related incidents must be reported to the relevant competent authority through the required notification and report sequence; does not turn mandatory reporting into an optional escalation.
  • ICT third-party risk remains part of the financial entity's own ICT risk management framework, including the register of information and contract evidence for ICT services.
  • is not self-selected by preference: DORA requires competent authorities to identify entities required to perform TLPT, and the TLPT RTS adds criteria and process requirements for scope, providers, risk management, findings, remediation, and attestation.
  • Simplified-framework entities and receive lighter or different obligations in defined places, but they still need evidence that the lighter approach matches their ICT risk profile and does not leave critical or important functions unmanaged.

Can a supplier or group policy satisfy DORA for a financial entity?

Only as supporting evidence. DORA keeps the financial entity responsible for compliance and for managing ICT third-party risk within its own ICT risk management framework. A group policy, supplier report, pooled test, or outsourced reporting arrangement should be tied back to the entity's own critical or important functions, register entries, contracts, incidents, controls, and supervisory obligations.

Can a financial entity decide on its own that is disproportionate?

No. DORA requires for financial entities, other than Article 16 entities and , that are identified by competent authorities. The identification is based on impact on the financial sector, possible financial stability concerns, systemic character, ICT risk profile, ICT maturity, and technology features. The TLPT RTS further explains when TLPT is justified and how authorities may release entities from TLPT after an overall assessment.

Recommended next step

Use proportionality without losing the mandatory DORA control points

Sorena can help connect a DORA proportionality position to entity scope, ICT risk evidence, simplified-framework status, incident and supplier records, testing scope, and supervisory-ready review notes.

Research workflow
Open Research Copilot for EU DORA

Ask official source questions about DORA proportionality, simplified-framework status, ICT risk evidence, incident duties, and TLPT selection.

Explore next step
Talk to Sorena
Talk through implementation

Review whether a proposed DORA proportionality position is supported by the entity's scope, risk profile, services, controls, suppliers, and testing evidence.

Explore next step
Primary sources

References and citations

Regulation (EU) 2022/2554 (DORA)
eur-lex.europa.eu5 citations
Referenced sections
  • Primary DORA text for scope, proportionality, ICT risk management, incident handling, reporting, testing, TLPT, simplified framework, and ICT third-party risk responsibilities.
  • Article 4 defines DORA proportionality and Article 2 defines covered financial entities and exclusions.
  • Article 16 lists the entities subject to the simplified ICT risk management framework and preserves core ICT risk, continuity, dependency, and testing obligations.
Show 2 more
  • Articles 6, 17, 19, 24, 25, 26, and 28 anchor evidence for ICT risk management, incidents, testing, TLPT, and ICT third-party risk.
  • Articles 17, 19, 26, and 28 show non-waivable incident, TLPT, and ICT third-party responsibility points despite proportional application.
"Proportionality principle"
More quoted passages
"size and overall risk profile"
"simplified ICT risk management framework"
"fully responsible for compliance"
"remain fully responsible"
Delegated Regulation (EU) 2024/1774 on ICT risk management tools and the simplified framework
eur-lex.europa.eu3 citations
Referenced sections
  • RTS source for proportional ICT security policies, procedures, controls, simplified-framework governance, ICT risk assessment, testing, continuity, and review-report evidence.
  • Specifies proportionality factors and detailed simplified-framework requirements for governance, information security, ICT risk assessment, controls, continuity, testing, and review reporting.
  • Article 1 and the review-report provisions identify the size, risk, complexity, dependency, threat, control-effectiveness, and security-posture evidence useful for proportionality records.
"simplified ICT risk management framework"
More quoted passages
"Overall risk profile and complexity"
"nature, scale and complexity"
Delegated Regulation (EU) 2025/1190 on DORA TLPT
eur-lex.europa.eu2 citations
Referenced sections
  • RTS source for TLPT identification criteria, authority involvement, scope documents, scenario selection, active testing duration, remediation, and attestation.
  • Specifies TLPT identification, scope, testing methodology, provider requirements, remediation, attestation, and authority cooperation criteria.
"threat-led penetration testing"
More quoted passages
"criteria used for identifying financial entities"

Related guides

DORA ICT Third-Party Contracts FAQ

What DORA requires in ICT third-party contracts, including critical or important functions, audit and access rights, termination, exit, subcontracting, register updates, and evidence.

DORA major ICT incident thresholds: what triggers reporting?

FAQ on DORA major ICT-related incident classification thresholds, recurring incidents, reporting triggers, and evidence inputs based on EU DORA RTS and ITS texts.

DORA Register of Information FAQ: ICT Third-Party Arrangements

FAQ on the DORA register of information: who maintains it, which ICT third-party arrangements it covers, template fields, critical functions, reporting, data quality, and evidence.

DORA TLPT selection: who can be required to test?

FAQ on DORA threat-led penetration testing selection: who identifies financial entities, what criteria are used, what the TLPT authority validates, and what evidence to keep.

DORA Critical or Important Functions: mapping ICT dependencies and evidence

How DORA critical or important functions affect ICT service mapping, third-party contracts, register-of-information records, incidents, testing, and evidence.

DORA deadlines and compliance calendar for financial entities

Track DORA dates and recurring evidence: 17 January 2025 application, incident reporting clocks, register updates, annual reporting, TLPT cadence, and critical-provider oversight milestones.

Show all related guides (33)

DORA ICT Third-Party Contract Remediation Workflow

A DORA workflow for remediating ICT third-party contracts covering critical or important functions, subcontracting, audit rights, exits, register updates, and evidence.

DORA ICT third-party risk and contract clauses guide

Official source DORA guide for financial entities in scope, ICT third-party risk, contract clauses, subcontracting controls, register evidence, audit rights, exit planning, and oversight.

DORA incident classification forms: criteria, fields, and reporting clocks

Official source guide to DORA ICT incident classification forms: major-incident criteria, significant cyber-threat notifications, report fields, time limits, evidence, and reclassification records.

DORA incident clock workflow: classification, reports, deadlines, and evidence

Official source DORA workflow for starting the major-incident reporting clock, classifying ICT incidents, submitting initial, intermediate, and final reports, and preserving authority evidence.

DORA major ICT incident reporting: classification, reports, and timing

Official source DORA guide to major ICT-related incident classification, initial notifications, intermediate and final reports, competent authority routing, and significant cyber threat notifications.

DORA Register of Information Import and Build Workflow

Build a DORA register of information from procurement, vendor, contract, service, function, and subcontractor data using the official register templates and validation checks.

DORA Register of Information Template: ICT Provider Fields and Evidence

Map DORA register fields to official templates for ICT contracts, provider chains, critical functions, dates, statuses, reporting, and evidence.

DORA vs EBA outsourcing guidelines: ICT third-party risk comparison

Compare binding DORA ICT third-party risk duties with the EBA outsourcing baseline for registers, critical functions, contracts, subcontracting, exit, incident reporting, and evidence.

DORA vs ISO 22301: ICT resilience and business continuity compared

Compare DORA's binding ICT operational resilience duties for financial entities with ISO 22301's business continuity management system requirements.

DORA vs ISO/IEC 27001: legal ICT resilience obligations and ISMS controls

Compare EU DORA and ISO/IEC 27001 across scope, governance, incident reporting, testing, ICT third-party risk, certification, evidence, overlap, and gaps.

DORA vs NIS2: financial-sector obligations, overlap, and evidence

Compare DORA and NIS2 for financial entities, ICT providers, incident reporting, management accountability, third-party risk, supervisory routes, and reusable evidence.

DORA vs PSD2 incident reporting: major ICT and payment incidents

Compare DORA major ICT-related incident reporting with PSD2 major operational or security payment incident reporting, including scope, triggers, report stages, recipients, and evidence.

EU DORA Applicability Test for Financial Entities and ICT Providers

Test DORA applicability against official sources for financial-entity scope, ICT services, critical or important functions, exclusions, proportionality, and evidence.

EU DORA Compliance Checklist for Financial Entities

Check DORA operating evidence against official sources for ICT risk governance, major-incident reporting, resilience testing, TLPT, third-party contracts, and the register of information.

EU DORA Compliance Obligations and Evidence Guide

Map DORA obligations to official sources and operating evidence for ICT risk management, incident reporting, testing, third-party risk, registers, governance, and oversight.

EU DORA FAQ: scope, incidents, ICT contracts, testing, and evidence

Concise DORA FAQ covering who is in scope, proportionality, ICT third-party contracts, register-of-information records, major ICT incident thresholds and reporting, TLPT, testing, enforcement, and evidence.

EU DORA ICT risk management control baseline

An official source DORA control baseline for ICT risk governance, asset and dependency mapping, protection, detection, response, recovery, testing, third-party risk, and evidence.

EU DORA ICT subcontracting chain controls for critical functions

DORA guide to ICT subcontracting chains for critical or important functions: prior assessment, contract conditions, register fields, monitoring, exit rights, and evidence.

EU DORA penalties and fines: enforcement powers and limits

Official source guide to DORA enforcement: competent-authority powers, administrative penalties, remedial measures, publication rules, and Lead Overseer penalty payments for critical ICT third-party providers.

EU DORA Register of Information Data Model: templates, fields, and evidence

Field-level guide to the EU DORA register of information data model: templates B_01 to B_07, provider identifiers, contract links, subcontracting chains, critical-function assessments, dates, and export evidence.

EU DORA Requirements Overview: ICT risk, incidents, testing, and third-party risk

An official source overview of the main EU DORA requirements for financial entities: governance, ICT risk management, incident reporting, resilience testing, TLPT, ICT third-party risk, register of information, oversight, proportionality, and evidence.

EU DORA Scope and Covered Entities: financial entities and ICT providers

Classify whether DORA applies to a financial entity, ICT third-party provider, group arrangement, branch, or critical ICT service dependency.

EU DORA Scope and Proportionality Workflow

Classify DORA covered entities, simplified-framework status, critical or important functions, ICT dependencies, evidence records, and governance approvals.

EU DORA testing and TLPT readiness guide

An official source DORA guide for resilience testing, TLPT eligibility, authority interaction, test evidence, remediation plans, and avoiding unsupported testing cadence.

EU DORA TLPT eligibility workflow for financial entities

Check how DORA TLPT authorities identify financial entities for threat-led penetration testing and what evidence supports scope, readiness, providers, and governance.

EU DORA TLPT Runbook: scope, providers, reports, and remediation

Build a DORA threat-led penetration testing runbook around authority coordination, scope validation, provider controls, active testing, closure reports, remediation, and attestation.

How to build a DORA register of information

Build a DORA register of information from contracts, ICT services, providers, functions, subcontractors, risk assessments, audit evidence, exit plans, and export checks.