DORA Spain vs POPA
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 5 of 5 topics. Each verdict names what it rests on; read the wording before relying on it.
- DORA Spain Asks more on 0 topics Alone on 0 topics More detailed on 3 topics
- POPA Asks more on 0 topics Alone on 2 topics More detailed on 0 topics
| Topic | DORA Spain | POPA | Verdict |
|---|---|---|---|
| Governance | |||
| Management accountability | DORA Spain: 3 | POPA: 1 | DORA Spain more detailedmore requirements on this, not necessarily stricter |
| Protection | |||
| Data security | DORA Spain: 3 | POPA: 1 | DORA Spain more detailedmore requirements on this, not necessarily stricter |
| Detection and response | |||
| Reporting to authorities | DORA Spain: 5 | POPA: 1 | DORA Spain more detailedmore requirements on this, not necessarily stricter |
| Privacy and data protection | |||
| Lawful processing | DORA Spain: – | POPA: 2 | Only POPAno specific requirement on the other side in the acts covered |
| Impact assessment | DORA Spain: – | POPA: 1 | Only POPAno specific requirement on the other side in the acts covered |
What This Covers
The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.
Included
- DORA Regulation (EU) 2022/2554
- DORA ICT Risk Management RTS Commission Delegated Regulation (EU) 2024/1774 Applies to: Financial entities, except those on the simplified framework
- JC 2024 34 Joint Guidelines on the estimation of aggregated annual costs and losses caused by major ICT-related incidents under Regulation (EU) 2022/2554, JC 2024 34 (Final Report of 17 July 2024), issued under Article 11(11) of Regulation (EU) 2022/2554
National requirements
None recorded yet, so the Directive is shown as it is. The national law may go further.
Not yet included
- DORA Third-Party Policy RTS
- DORA Subcontracting RTS
- DORA Register of Information ITS
- DORA Incident Classification RTS
- DORA Incident Reporting RTS
- DORA Incident Reporting ITS
- DORA TLPT RTS
- DORA Critical Provider Criteria
- DORA Oversight Conditions RTS
Status
Reviewed against the official texts.
Included
- POPA Protection of Privacy Act, SA 2024, c P-28.5
Status
Reviewed against the official texts.
Key Numbers
Incident reports go to
DORA Spain: Financial supervisor (competent authority)
POPA: Not in the acts covered
First notice of an incident
DORA Spain: Within 4 hours of classifying it as major, and no later than 24 hours of becoming aware; if classified as major after that, within 4 hours of classifying it
POPA: Not in the acts covered
Intermediate report
DORA Spain: Within 72 hours of the initial notification
POPA: Not in the acts covered
Final report
DORA Spain: Within one month of the latest intermediate report
POPA: Not in the acts covered
Review of the risk framework
DORA Spain: At least once a year (periodically for microenterprisesMicroenterprise Under DORA), and after major incidents
POPA: Not in the acts covered
Testing of critical systems
DORA Spain: At least yearly, for systems supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions.
POPA: Not in the acts covered
Threat-led penetration testing
DORA Spain: At least every 3 years, for entities the authority identifies; the authority may request a lower or higher frequency
POPA: Not in the acts covered
Register of third-party arrangements
DORA Spain: Required, for every ICTInformation and Communication Technology service arrangement
POPA: Not in the acts covered
Management body training
DORA Spain: Required, on a regular basis
POPA: Not in the acts covered
Management body liability
DORA Spain: Ultimate responsibility for ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment.; penalties on members are subject to national law (Article 50(5))
POPA: Not in the acts covered
Maximum fines
DORA Spain: Set by each Member State (Competent authorities and Member States)
POPA: Not in the acts covered
Governance
Management accountability
DORA Spain more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4
Management body responsibility
The management body defines, approves, oversees and is responsible for implementing every arrangement of the ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework, and bears ultimate responsibility for managing ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment..
DORA, Article 5(2) · applies as in the Directive
Budget for resilience
The management body allocates and reviews the budget for digital operational resilienceThe ability of a financial entity to build, assure and review its operational integrity and reliability by securing all the ICT capabilities it needs, directly or through ICT third-party service providers, so that it can keep providing financial services, including during disruptions. It is the overall goal of DORA., including awareness programmes, training and ICTInformation and Communication Technology skills for all staff.
DORA, Article 5(2)(g) · applies as in the Directive
Governance (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
Governance and organisation of the simplified ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework.
DORA ICT Risk Management RTS, Article 28 · applies as in the Directive
Privacy management program
Establish and implement a documented privacy management program proportional to the volume and sensitivity of the personal information held, meeting the Ministerial Regulation (section 6: a privacy officer, policies and procedures, a security classification system, mandatory training and periodic review); give anyone who asks a copy within 30 business days.
Protection
Data security
DORA Spain more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12
Protect data
Policies, protocols and tools that keep data available, authentic, intact and confidential at rest, in use and in transit.
DORA, Article 9(2) and (3) · applies as in the Directive
ICT operations and data security
Applies to: Financial entities, except those on the simplified framework
Policies and procedures for ICTInformation and Communication Technology operations, capacity and performance management, and data and system security.
DORA ICT Risk Management RTS, Articles 8, 9 and 11 · applies as in the Directive
Operations, data and network security (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
ICTInformation and Communication Technology operations security, and data, system and network security.
DORA ICT Risk Management RTS, Articles 34 and 35 · applies as in the Directive
Security arrangements
Protect personal information with reasonable security arrangements against unauthorized access, collection, use, disclosure or destruction.
Detection and response
Reporting to authorities
DORA Spain more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5
Report major incidents
Report major ICT-related incidentsAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. to the competent authority, using the common templates.
DORA, Article 19(1) · applies as in the Directive
Initial notification
An initial notification once the incident is classified as major.
DORA, Article 19(4)(a); Delegated Regulation (EU) 2025/301, Article 5 · applies as in the Directive
Intermediate report
An intermediate report, updated when regular activities have been recovered.
DORA, Article 19(4)(b); Delegated Regulation (EU) 2025/301, Article 5 · applies as in the Directive
Final report
A final report once the root cause analysisA structured investigation into the underlying causes of a problem or incident, rather than only its visible effects. For an IT incident, it examines how technical failures, working practices or other conditions combined to cause the disruption. The findings help an organisation choose corrective measures that address those causes and reduce the chance of recurrence. is complete, whether or not mitigation is in place, and actual impact figures are available to replace estimates.
DORA, Article 19(4)(c); Delegated Regulation (EU) 2025/301, Article 5 · applies as in the Directive
Voluntary notice of cyber threats Optional
Significant cyber threatsA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident. may be notified to the competent authority.
DORA, Article 19(2) · applies as in the Directive
Breach notification
Notify the individual, the Commissioner and the Minister without unreasonable delay when an incident creates a real risk of significant harm; the notices are written and contain the information set by the Protection of Privacy (Ministerial) Regulation (section 4).
Privacy and data protection
Lawful processing
Only POPA no specific requirement on the other side in the acts covered
NIST Privacy Framework CT.PO-P
Nothing in the acts covered.
Accuracy for decisions
Make every reasonable effort to keep personal information used for decisions, including automated ones, accurate and complete, and keep it for at least one year after using it, or a shorter period agreed in writing by the individual, the public body and any body that approves its retention schedule.
No sale of personal information
Never sell personal information.
Impact assessment
Only POPA no specific requirement on the other side in the acts covered
NIST Privacy Framework ID.RA-P
Nothing in the acts covered.
Privacy impact assessment
Prepare a privacy impact assessment for a new or substantially changed practice, program, project or service involving personal information where a loss could cause significant harm or a submission factor applies, and submit it to the Commissioner where the information is highly sensitive, a significant share of the population is involved, data is matched between public bodies, the program is common or integrated, it uses innovative technology or the Commissioner asks (Ministerial Regulation, section 7).
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022. 30 topics where all apply the Directive as it is are not shown.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.