Incident to report to a regulator?Incident to report? Intake Line

DORA vs GDPR

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

DORAFinancial entities

GDPRControllers and processors

At a Glance

They differ on 31 of 42 topics. Each verdict names what it rests on; read the wording before relying on it.

  • DORA Asks more on 0 topics Alone on 19 topics More detailed on 3 topics
  • GDPR Asks more on 0 topics Alone on 9 topics More detailed on 0 topics
Requirements per topic and verdict
Topic DORAGDPR Verdict
Governance
Management accountability DORA: 3 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Roles and independence DORA: 1 GDPR: 2 Both cover itread the wording below
Security policy DORA: 3 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Awareness and training DORA: 2 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Risk management
Risk management framework DORA: 2 GDPR: 1 Both cover itread the wording below
Risk assessment DORA: 3 GDPR: 1 DORA more detailedmore requirements on this, not necessarily stricter
Review, audit and improvement DORA: 4 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Asset management DORA: 3 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Protection
Access control DORA: 3 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Authentication DORA: 2 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Cryptography and encryption DORA: 2 GDPR: 1 Both cover itread the wording below
Data security DORA: 3 GDPR: 2 Both cover itread the wording below
Network security DORA: 3 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Secure acquisition and development DORA: 2 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Configuration, change and patch management DORA: 5 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Vulnerability handling DORA: 3 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Human resources security DORA: 1 GDPR: 1 Both cover itread the wording below
Physical and environmental security DORA: 1 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Detection and response
Monitoring and detection DORA: 3 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Incident handling DORA: 3 GDPR: 1 DORA more detailedmore requirements on this, not necessarily stricter
Incident classification DORA: 1 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Reporting to authorities DORA: 5 GDPR: 3 Both cover itread the wording below
Informing customers and the public DORA: 2 GDPR: 1 Both cover itread the wording below
Threat intelligence and information sharing DORA: 2 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Continuity and resilience
Business continuity and crisis management DORA: 3 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Backup and recovery DORA: 1 GDPR: 1 Both cover itread the wording below
Security testing DORA: 3 GDPR: 1 DORA more detailedmore requirements on this, not necessarily stricter
Threat-led penetration testing DORA: 1 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Third parties and supply chain
Supplier and third-party risk DORA: 2 GDPR: 2 Both cover itread the wording below
Contract requirements DORA: 2 GDPR: 1 Both cover itread the wording below
Register of third-party arrangements DORA: 1 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Exit and termination DORA: 1 GDPR: – Only DORAno specific requirement on the other side in the acts covered
Privacy and data protection
Lawful processing DORA: – GDPR: 7 Only GDPRno specific requirement on the other side in the acts covered
Transparency DORA: – GDPR: 2 Only GDPRno specific requirement on the other side in the acts covered
Rights of individuals DORA: – GDPR: 7 Only GDPRno specific requirement on the other side in the acts covered
Privacy by design and by default DORA: – GDPR: 2 Only GDPRno specific requirement on the other side in the acts covered
Impact assessment DORA: – GDPR: 3 Only GDPRno specific requirement on the other side in the acts covered
Records of processing DORA: – GDPR: 2 Only GDPRno specific requirement on the other side in the acts covered
Data protection officer DORA: – GDPR: 2 Only GDPRno specific requirement on the other side in the acts covered
International transfers DORA: – GDPR: 4 Only GDPRno specific requirement on the other side in the acts covered
Supervision and enforcement
Cooperation with supervisors DORA: – GDPR: 1 Only GDPRno specific requirement on the other side in the acts covered
Penalties and liability DORA: 1 GDPR: 2 Both cover itread the wording below

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 Articles 5, 6, 8 to 14, 16 to 19, 24 to 26, 28, 30, 45, 50 · 43 requirements
  • DORA ICT Risk Management RTS Commission Delegated Regulation (EU) 2024/1774 Articles 2 to 31, 33 to 41 · 26 requirements 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 5 requirements

Not yet included

Status

Reviewed against the official texts.

Included

  • GDPR Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

Status

Reviewed against the official texts.

Key Numbers

Deadline

DORA: Not in the acts covered

GDPR: At the time the data are obtained (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Threshold

DORA: Not in the acts covered

GDPR: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)

Goes to

DORA: Not in the acts covered

GDPR: Controller (Processors); Data subjects (Controllers)

Evidence to keep

DORA: Not in the acts covered

GDPR: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Incident reports go to

DORA: Financial supervisor (competent authority)

GDPR: Competent supervisory authority (Controllers)

First notice of an incident

DORA: 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 Shortest stated

GDPR: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

Intermediate report

DORA: Within 72 hours of the initial notification

GDPR: In phases, without undue further delay (Controllers)

Final report

DORA: Within one month of the latest intermediate report

GDPR: Not in the acts covered

External assessment or certification

DORA: Not in the acts covered

GDPR: Approved code of conduct or certification may help show compliance (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Review of the risk framework

DORA: At least once a year (periodically for microenterprisesMicroenterprise Under DORA), and after major incidents

GDPR: Where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

Testing of critical systems

DORA: 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.

GDPR: Regularly

Threat-led penetration testing

DORA: At least every 3 years, for entities the authority identifies; the authority may request a lower or higher frequency

GDPR: Not in the acts covered

Register of third-party arrangements

DORA: Required, for every ICTInformation and Communication Technology service arrangement

GDPR: Not in the acts covered

Management body training

DORA: Required, on a regular basis

GDPR: Not in the acts covered

Management body liability

DORA: 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))

GDPR: Not in the acts covered

Maximum fines

DORA: Set by each Member State (Competent authorities and Member States)

GDPR: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher

Governance

Management accountability

Only DORA no specific requirement on the other side in the acts covered

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)

  • 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)

  • 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

Nothing in the acts covered.

Roles and independence

Both cover it read the wording below

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

  • Independent control function

    A control function with appropriate independence manages and oversees 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. (not required of microenterprisesMicroenterprise Under DORA). Risk management, control and internal audit functions are kept appropriately segregated and independent.

    DORA, Article 6(4)

  • Joint controllers

    Applies to: Joint controllers

    Joint controllers set out their respective responsibilities in an arrangement, unless EU or Member State law determines them, including who handles rights requests and information duties, and make its essence available to people. A person may exercise their rights against any of them regardless of the arrangement.

    GDPR, Article 26

  • EU representative

    Applies to: Controllers and processors not established in the EU, under Article 3(2)

    A controller or processor outside the EU that falls under Article 3(2) designates a representative in writing, established in a Member State where the affected people are. Occasional low-risk processing without large-scale special category or criminal data, and public bodies, are exempt.

    GDPR, Article 27

Security policy

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

  • Information security policy

    A documented information security policy with requirements to protect the availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable., authenticity, integrity and confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of data and assets, including customers' where applicable.

    DORA, Article 9(4)(a)

  • ICT security policies

    Applies to: Financial entities, except those on the simplified framework

    ICTInformation and Communication Technology security policies, procedures, protocols and tools, with their general elements, approved and reviewed as part of the framework.

    DORA ICT Risk Management RTS, Article 2

  • Information security policy (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    An information securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. policy and measures.

    DORA ICT Risk Management RTS, Article 29

Nothing in the acts covered.

Awareness and training

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

  • Management body training

    Members of the management body keep their knowledge and skills on 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. up to date, including by following specific training regularly.

    DORA, Article 5(4)

  • Staff awareness and training

    ICTInformation and Communication Technology security awareness programmes and 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. training are compulsory for all employees and senior management.

    DORA, Article 13(6)

Nothing in the acts covered.

Risk management

Risk management framework

Both cover it read the wording below

NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1

  • ICT risk management framework

    A sound, comprehensive and well-documented 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 within the overall risk management system, with the strategies, policies, procedures, protocols and tools to protect all information and ICTInformation and Communication Technology assets.

    DORA, Article 6(1) and (2)

  • Simplified ICT risk management framework

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Small and non-interconnected investment firms, exempted payment and e-moneyElectronic Money institutions, small occupational pension funds, and institutions exempted under Directive 2013/36/EU that their Member State has not excluded under Article 2(4) follow a simplified framework instead of Articles 5 to 15.

    DORA, Article 16(1)

  • Measures to ensure and show compliance

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Put in place technical and organisational measures suited to the risks of the processing, so that it complies and the controller can show it does. Review and update them where needed. Where proportionate, these include data protection policies.

    GDPR, Article 24

Risk assessment

DORA more detailed more requirements on this, not necessarily stricter

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

  • Identify ICT risk

    Identify all sources of 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. continuously, assess cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. and vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., and review risk scenarios at least yearly.

    DORA, Article 8(2)

  • ICT risk management policy

    Applies to: Financial entities, except those on the simplified framework

    A policy and procedures 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. management: risk toleranceAn organisation's or other actor's readiness to bear a risk in order to achieve its objectives. Risk tolerance can be shaped by legal or regulatory requirements and changes with context, so frameworks ask organisations to state it rather than prescribing it., identification, assessment and treatment of risks, and the monitoring of residual riskThe risk that remains after risk treatment has been applied. The NIST AI RMF notes that residual risk directly affects end users and affected communities, and asks system providers to document it so users understand the possible negative impacts..

    DORA ICT Risk Management RTS, Article 3

  • ICT risk management (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Identification and management of 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 ICT Risk Management RTS, Article 31

  • Assess security risk

    When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.

    GDPR, Article 32(2)

Review, audit and improvement

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

  • Yearly review of the framework

    The framework is documented and reviewed at least once a year (periodically for microenterprisesMicroenterprise Under DORA), after 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. and following supervisory instructions or conclusions from testing or audits, and improved continuously.

    DORA, Article 6(5)

  • Internal audit

    Auditors with sufficient 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. expertise audit the framework regularly, in line with the audit plan. Not required of microenterprisesMicroenterprise Under DORA.

    DORA, Article 6(6)

  • Report on the framework review

    Applies to: Financial entities, except those on the simplified framework

    The format and content of the report on the review 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.

    DORA ICT Risk Management RTS, Article 27

  • Framework review report (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    The format and content of the report on the review of the simplified framework.

    DORA ICT Risk Management RTS, Article 41

Nothing in the acts covered.

Asset management

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13

  • Identify and classify assets

    Identify, classify and document all ICTInformation and Communication Technology-supported business functions, information and ICTInformation and Communication Technology assets and their dependencies, and review the classification at least yearly.

    DORA, Article 8(1)

  • ICT asset management

    Applies to: Financial entities, except those on the simplified framework

    An ICTInformation and Communication Technology asset managementAsset Management in Information Security policy and procedure, including an inventory of assets and their criticality.

    DORA ICT Risk Management RTS, Articles 4 and 5

  • Asset classification (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Classification of information assets and ICTInformation and Communication Technology assets.

    DORA ICT Risk Management RTS, Article 30

Nothing in the acts covered.

Protection

Access control

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3

  • Limit access

    Limit physical and logical access to what legitimate and approved functions need, with policies, procedures and controls for access rights.

    DORA, Article 9(4)(c)

  • Identity management and access control

    Applies to: Financial entities, except those on the simplified framework

    Identity management and access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies, including authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence..

    DORA ICT Risk Management RTS, Articles 20 and 21

  • Access control (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    Access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements..

    DORA ICT Risk Management RTS, Article 33

Nothing in the acts covered.

Authentication

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5

  • Strong authentication and key protection

    Strong authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. based on relevant standards, and protection of cryptographic keys, with encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. decided by data classification and risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    DORA, Article 9(4)(d)

  • Identity management and access control

    Applies to: Financial entities, except those on the simplified framework

    Identity management and access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies, including authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence..

    DORA ICT Risk Management RTS, Articles 20 and 21

Nothing in the acts covered.

Cryptography and encryption

Both cover it read the wording below

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24

  • Strong authentication and key protection

    Strong authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. based on relevant standards, and protection of cryptographic keys, with encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. decided by data classification and risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..

    DORA, Article 9(4)(d)

  • Encryption and key management

    Applies to: Financial entities, except those on the simplified framework

    EncryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. and cryptographic controls, and the management of cryptographic keys through their whole life cycle.

    DORA ICT Risk Management RTS, Articles 6 and 7

  • Pseudonymisation and encryption

    Apply pseudonymisation and encryption of personal data, as appropriate to the risk.

    GDPR, Article 32(1)(a)

Data security

Both cover it read the wording below

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)

  • 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

  • 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

  • Integrity and confidentiality

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.

    GDPR, Article 5(1)(f)

  • Security of systems and services

    Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.

    GDPR, Article 32(1)(b)

Network security

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22

  • Network and infrastructure management

    Network and infrastructure management on a risk basis, designed so that connections can be severed or segmented instantly to stop contagion.

    DORA, Article 9(4)(b)

  • Network security

    Applies to: Financial entities, except those on the simplified framework

    Network security management and the protection of information in transit.

    DORA ICT Risk Management RTS, Articles 13 and 14

  • 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

Nothing in the acts covered.

Secure acquisition and development

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31

  • Projects, acquisition and development

    Applies to: Financial entities, except those on the simplified framework

    ICTInformation and Communication Technology project management, and the acquisition, development and maintenance of ICTInformation and Communication Technology systems.

    DORA ICT Risk Management RTS, Articles 15 and 16

  • Development and change (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology systems acquisition, development and maintenance, and ICTInformation and Communication Technology project and change management.

    DORA ICT Risk Management RTS, Articles 37 and 38

Nothing in the acts covered.

Configuration, change and patch management

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.9, A.8.19, A.8.32

  • Change management

    Documented change management, so that every change to software, hardware, firmware, systems or security parameters is recorded, tested, assessed, approved, implemented and verified.

    DORA, Article 9(4)(e)

  • Patches and updates

    Documented policies for patches and updates.

    DORA, Article 9(4)(f)

  • Vulnerability and patch management

    Applies to: Financial entities, except those on the simplified framework

    Procedures to identify and fix vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and to apply patches and updates.

    DORA ICT Risk Management RTS, Article 10

  • ICT change management

    Applies to: Financial entities, except those on the simplified framework

    ICTInformation and Communication Technology change management procedures.

    DORA ICT Risk Management RTS, Article 17

  • Development and change (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology systems acquisition, development and maintenance, and ICTInformation and Communication Technology project and change management.

    DORA ICT Risk Management RTS, Articles 37 and 38

Nothing in the acts covered.

Vulnerability handling

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8

  • Patches and updates

    Documented policies for patches and updates.

    DORA, Article 9(4)(f)

  • Tests to run

    Appropriate tests such as vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.

    DORA, Article 25

  • Vulnerability and patch management

    Applies to: Financial entities, except those on the simplified framework

    Procedures to identify and fix vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and to apply patches and updates.

    DORA ICT Risk Management RTS, Article 10

Nothing in the acts covered.

Human resources security

Both cover it read the wording below

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

  • Human resources policy

    Applies to: Financial entities, except those on the simplified framework

    A human resources policy covering ICTInformation and Communication Technology security.

    DORA ICT Risk Management RTS, Article 19

  • Staff act only on instructions

    Processors, and anyone with access to personal data under the authority of a controller or processor, process it only on the controller's instructions unless EU or Member State law requires otherwise. Controllers and processors take steps to ensure this.

    GDPR, Articles 29 and 32(4)

Physical and environmental security

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14

Nothing in the acts covered.

Detection and response

Monitoring and detection

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16

  • Detect anomalous activity

    Mechanisms to detect anomalous activity promptly, with several layers of control, alert thresholds and automatic alerts, tested regularly.

    DORA, Article 10

  • Logging

    Applies to: Financial entities, except those on the simplified framework

    Logging procedures, protocols and tools: what is logged, how logs are protected and how long they are kept.

    DORA ICT Risk Management RTS, Article 12

  • Incident management and detection

    Applies to: Financial entities, except those on the simplified framework

    An ICT-related incidentA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. management policy, and criteria to detect anomalous activity and trigger incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state..

    DORA ICT Risk Management RTS, Articles 22 and 23

Nothing in the acts covered.

Incident handling

DORA more detailed more requirements on this, not necessarily stricter

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

  • Post-incident reviews

    A review after a major ICT-related incidentAn 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. disrupts core activities, to find the causes and the improvements needed.

    DORA, Article 13(2)

  • Incident management process

    A process to detect, manage and notify ICT-related incidentsA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident.: record all incidents and 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., assign roles, escalate, and find and fix root causes.

    DORA, Article 17

  • Incident management and detection

    Applies to: Financial entities, except those on the simplified framework

    An ICT-related incidentA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. management policy, and criteria to detect anomalous activity and trigger incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state..

    DORA ICT Risk Management RTS, Articles 22 and 23

  • Document every breach

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Record each personal data breach, whether notified or not, with its facts, effects and remedial action, so the authority can check compliance.

    GDPR, Article 33(5)

Incident classification

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.MA · ISO/IEC 27001:2022 A.5.25

  • Classify incidents

    Classify incidents by the clients affected, reputational impact, duration, geographical spread, data losses, critical services affected and economic impact. The thresholds are in Delegated Regulation (EU) 2024/1772.

    DORA, Article 18(1)

Nothing in the acts covered.

Reporting to authorities

Both cover it read the wording below

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)

  • Initial notification

    An initial notification once the incident is classified as major.

    DORA, Article 19(4)(a); Delegated Regulation (EU) 2025/301, Article 5

  • Intermediate report

    An intermediate report, updated when regular activities have been recovered.

    DORA, Article 19(4)(b); Delegated Regulation (EU) 2025/301, Article 5

  • 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

  • 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)

  • Notify a personal data breach

    Applies to: Controllers

    Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.

    GDPR, Article 33(1)

  • Processor tells the controller

    Applies to: Processors

    Tell the controller of a personal data breach without undue delay after becoming aware of it.

    GDPR, Article 33(2)

  • What the breach notice contains

    Applies to: Controllers

    Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.

    GDPR, Article 33(3) and (4)

Informing customers and the public

Both cover it read the wording below

NIST CSF 2.0 RS.CO, RC.CO

  • Crisis communication

    Crisis communication plans to disclose major incidents or vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. to clients, counterparts and the public, and a person in charge of public and media communication.

    DORA, Article 14

  • Inform affected clients

    When a major incident affects clients' financial interests, inform them without undue delay of the incident and the measures taken.

    DORA, Article 19(3)

  • Tell the people affected

    Applies to: Controllers

    Where a breach is likely to cause high risk to people, tell them in plain language without undue delay, with the contact point, likely consequences and measures. This is not needed where the data was unintelligible, for example encrypted, where later measures remove the high risk, or where a public notice replaces disproportionate effort. The authority may require notice.

    GDPR, Article 34(1) to (4)

Threat intelligence and information sharing

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.5.6, A.5.7

  • Threat and vulnerability intelligence

    Capabilities and staff to gather information on vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. and incidents and to analyse their likely impact.

    DORA, Article 13(1)

  • Information-sharing arrangements Optional

    Financial entities may exchange cyber threatAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. information within trusted communities, under arrangements that protect confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. and personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity.. They must tell the competent authority when they join or leave.

    DORA, Article 45

Nothing in the acts covered.

Continuity and resilience

Business continuity and crisis management

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30

  • ICT business continuity

    An ICTInformation and Communication Technology business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. policy, response and recovery plans that are tested at least yearly and after substantive changes to 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., and a business impact analysisThe process of analysing operational functions and the effect a disruption might have on them. Its results inform recovery priorities in continuity planning..

    DORA, Article 11

  • ICT business continuity

    Applies to: Financial entities, except those on the simplified framework

    The components of the ICTInformation and Communication Technology business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. policy, the testing of continuity plans, and ICTInformation and Communication Technology response and recovery plans.

    DORA ICT Risk Management RTS, Articles 24 to 26

  • Business continuity (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    An ICTInformation and Communication Technology business continuity planThe documented, predetermined instructions or procedures that keep an organisation's core operations running during and after a significant disruption. DORA, for example, requires financial entities to have an ICT business continuity policy. and its testing.

    DORA ICT Risk Management RTS, Articles 39 and 40

Nothing in the acts covered.

Backup and recovery

Both cover it read the wording below

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

  • Backup and restoration

    BackupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. policies setting scope and minimum frequency, restoration on own systems segregated from the source, periodic testing, and redundant ICTInformation and Communication Technology capacity (microenterprisesMicroenterprise Under DORA assess the need based on their risk profile).

    DORA, Article 12

  • Restoring access after an incident

    Be able to restore availability of and access to personal data in a timely way after a physical or technical incident, as appropriate to the risk.

    GDPR, Article 32(1)(c)

Security testing

DORA more detailed more requirements on this, not necessarily stricter

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

  • Resilience testing programme

    A risk-based testing programme run by independent testers, with all ICTInformation and Communication Technology systems and applications 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. tested at least yearly. Not required of microenterprisesMicroenterprise Under DORA.

    DORA, Article 24

  • Tests to run

    Appropriate tests such as vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.

    DORA, Article 25

  • Security testing (simplified)

    Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)

    ICTInformation and Communication Technology security testing.

    DORA ICT Risk Management RTS, Article 36

  • Testing the measures

    Have a process to test and evaluate regularly whether the technical and organisational security measures work, as appropriate to the risk.

    GDPR, Article 32(1)(d)

Threat-led penetration testing

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM

  • Threat-led penetration testing

    Entities identified by the competent authority, other than microenterprisesMicroenterprise Under DORA and Article 16(1) entities, run threat-led penetration tests on live production systems. Details are in Delegated Regulation (EU) 2025/1190.

    DORA, Article 26(1), (2) and (8)

Nothing in the acts covered.

Third parties and supply chain

Supplier and third-party risk

Both cover it read the wording below

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23

  • Manage ICT third-party risk

    ICT third-party riskIn the Digital Operational Resilience Act context, the technology risk a financial organisation faces when it uses Information and Communication Technology services supplied by another organisation or that supplier's subcontractors. This concerns the organisation's dependence on externally provided technology, including outsourced services. Managing it involves assessing suppliers, documenting service arrangements, setting suitable contract terms, monitoring risks and planning how to leave an arrangement while keeping services running. is managed within 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 the entity stays fully responsible for compliance.

    DORA, Article 28(1)

  • Third-party risk strategy

    A regularly reviewed strategy on ICT third-party riskIn the Digital Operational Resilience Act context, the technology risk a financial organisation faces when it uses Information and Communication Technology services supplied by another organisation or that supplier's subcontractors. This concerns the organisation's dependence on externally provided technology, including outsourced services. Managing it involves assessing suppliers, documenting service arrangements, setting suitable contract terms, monitoring risks and planning how to leave an arrangement while keeping services running., with a policy on ICTInformation and Communication Technology services 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.. The management body regularly reviews the risks from those arrangements. Not required of microenterprisesMicroenterprise Under DORA or Article 16 entities.

    DORA, Article 28(2)

  • Use only processors with sufficient guarantees

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.

    GDPR, Article 28(1)

  • Sub-processors

    Applies to: Processors

    Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.

    GDPR, Article 28(2) and (4)

Contract requirements

Both cover it read the wording below

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20

  • Minimum contract terms

    Contracts set out the services, locations of service and data, data protection, access and return of data, service levels, incident assistance, cooperation with authorities, termination rights and participation in training.

    DORA, Article 30(2)

  • Terms for critical or important functions

    Contracts for services 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. add full service level descriptions, notice periods, business contingency plans, participation in TLPTThreat-Led Penetration Testing, unrestricted rights of access, inspection and audit (microenterprisesMicroenterprise Under DORA may agree to delegate these to an independent third party), and exit strategies with a transition period.

    DORA, Article 30(3)

  • Processing contract

    Govern processing by a written contract or other legal act covering subject matter, duration, nature and purpose, data types, the people concerned and the controller's obligations and rights. It requires the processor to act on documented instructions, keep staff bound to confidentiality, secure the data, follow the sub-processor requirements, help with rights and Articles 32 to 36, delete or return data at the end at the controller's choice, provide compliance information and allow audits. The processor warns the controller at once if an instruction appears to breach data protection law.

    GDPR, Article 28(3) and (9)

Register of third-party arrangements

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC

  • Register of information

    A register of all contractual arrangements for ICTInformation and Communication Technology services, at entity, sub-consolidated and consolidated level, given to the competent authority on request, with a report at least yearly on new arrangements and timely notice of planned arrangements 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..

    DORA, Article 28(3)

Nothing in the acts covered.

Exit and termination

Only DORA no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC

  • Exit strategies

    Exit strategies for ICTInformation and Communication Technology services 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., covering provider failure, falling quality and business disruption.

    DORA, Article 28(8)

Nothing in the acts covered.

Privacy and data protection

Lawful processing

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

Nothing in the acts covered.

  • Purpose limitation and data minimisation

    Applies to: Controllers

    Collect personal data for specified, explicit and legitimate purposes and do not use it later in a way that conflicts with them. Keep the data adequate, relevant and limited to what those purposes need.

    GDPR, Article 5(1)(b) and (c)

  • Accuracy and storage limitation

    Applies to: Controllers

    Keep personal data accurate and, where needed, up to date, and take every reasonable step to erase or correct inaccurate data without delay. Keep data in a form that identifies people only for as long as the purpose needs, or longer solely for archiving, research or statistics under Article 89(1) with safeguards.

    GDPR, Article 5(1)(d) and (e)

  • Accountability

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    The controller is responsible for meeting the data protection principles and must be able to demonstrate that it does.

    GDPR, Article 5(2)

  • Lawful basis

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Process personal data lawfully, fairly and transparently, and only where at least one basis applies: consent, contract, legal obligation, vital interests, a public-interest task or official authority, or legitimate interests. Legitimate interests do not apply where the person's interests or rights override them, and are not open to public authorities performing their tasks.

    GDPR, Articles 5(1)(a) and 6(1)

  • Conditions for consent

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Be able to prove consent, and keep a written consent request separate from other matters and in plain language. Let people withdraw at any time, as easily as they gave consent, and tell them so beforehand. Consent tied to a contract for data the contract does not need may not count as freely given.

    GDPR, Article 7

  • Children's consent to online services

    Applies to: Controllers offering information society services directly to children

    Where consent is the basis for processing in relation to offering an information society service directly to a child under the age limit, make sure consent is given or authorised by the holder of parental responsibility. Make reasonable efforts, given the available technology, to verify it.

    GDPR, Article 8(1) and (2)

  • Special category and criminal offence data

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Do not process special category data, such as health, biometric identification or genetic data, unless a condition in Article 9(2) applies. Process criminal conviction and offence data only under official authority or where EU or Member State law authorises it with safeguards.

    GDPR, Articles 9 and 10

Transparency

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CM.AW-P

Nothing in the acts covered.

  • Information when collecting from the person

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Tell people, concisely and in plain language, who the controller and any DPO are, the purposes and legal basis, any legitimate interests relied on, recipients, transfers, retention, their rights, whether they must provide the data, and any automated decision-making. Before using the data for a new purpose, give information on that purpose and any relevant further details. This is not needed where the person already has the information.

    GDPR, Articles 12(1) and 13

  • Information when data comes from elsewhere

    Applies to: Controllers

    Give the same information, plus the categories of data and their source, when the data was not obtained from the person. Exceptions include where the person already has it, where this proves impossible or takes disproportionate effort, in which case take appropriate measures to protect the person, including making the information public, or where law requires the obtaining or disclosure or professional secrecy applies.

    GDPR, Article 14

Rights of individuals

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DM-P

Nothing in the acts covered.

  • Answer rights requests in time

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Act on a request under Articles 15 to 22 and tell the person the outcome free of charge. If more time is needed for complex or numerous requests, say so and why within the first month. If no action will be taken, say why without delay and within the first month, and explain the right to complain to an authority and seek a judicial remedy. Manifestly unfounded or excessive requests may be charged for or refused, and the controller must show why.

    GDPR, Article 12(3) to (5)

  • Right of access

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Confirm whether personal data about the person is processed and give access to it, with a copy and information on purposes, data categories, recipients, retention, rights, source and automated decision-making. A reasonable fee may be charged for further copies. The right to a copy must not adversely affect the rights and freedoms of others.

    GDPR, Article 15

  • Rectification, restriction and telling recipients

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Correct inaccurate data without undue delay and, taking account of the purposes, complete incomplete data. On request, restrict processing while accuracy is contested or an Article 21(1) objection is being checked, where processing is unlawful and the person prefers restriction to erasure, or where the controller no longer needs the data but the person needs it for legal claims. Tell each recipient of any rectification, erasure or restriction unless this proves impossible or takes disproportionate effort, and tell the person who the recipients are if asked.

    GDPR, Articles 16, 18 and 19

  • Right to erasure

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Erase personal data without undue delay where it is no longer needed, consent is withdrawn with no other basis, the person objects under Article 21(1) without overriding grounds or objects to direct marketing, processing was unlawful, law requires it, or it was collected for an information society service under Article 8(1). If the data was made public, take reasonable steps to tell other controllers of the request. The right does not apply where processing is needed for freedom of expression, a legal obligation or public task, public health, archiving, research or statistics where erasure would seriously impair them, or legal claims.

    GDPR, Article 17

  • Right to data portability

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Where processing is automated and rests on consent or contract, give people, on request, the data they provided in a structured, commonly used, machine-readable format. On request, send it directly to another controller where technically feasible. The right does not apply to public-task processing and must not adversely affect the rights of others.

    GDPR, Article 20

  • Right to object

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Stop processing based on a public task or legitimate interests when the person objects on grounds of their particular situation, unless the controller demonstrates compelling legitimate grounds that override the person's interests, or legal claims. Stop direct marketing, and related profiling, on objection without exception. Present this right clearly and separately, at the latest at first communication.

    GDPR, Article 21

  • Solely automated decisions

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Do not subject people to decisions based solely on automated processing, including profiling, with legal or similarly significant effects, unless a contract need, law or explicit consent allows it. In the contract and consent cases, provide human intervention, a chance to give a view and a way to contest the decision. Special category data needs further conditions and safeguards.

    GDPR, Article 22

Privacy by design and by default

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DP-P

Nothing in the acts covered.

  • Data protection by design

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    When deciding how to process and during processing, apply measures such as pseudonymisation that put the data protection principles into effect and build safeguards into the processing. Take account of the state of the art, cost and risk.

    GDPR, Article 25(1)

  • Data protection by default

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    By default, process only the data needed for each purpose, in amount, extent, storage period and accessibility. Do not make personal data available to an indefinite number of people without the person's intervention.

    GDPR, Article 25(2)

Impact assessment

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.RA-P

Nothing in the acts covered.

  • When an impact assessment is needed

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Assess the impact on personal data before processing that is likely to cause high risk, especially with new technologies. It is required for systematic and extensive automated evaluation with legal or similarly significant effects, large-scale special category or criminal data, and large-scale systematic monitoring of a publicly accessible area.

    GDPR, Article 35(1) and (3)

  • What the assessment contains

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Describe the processing and its purposes, assess necessity and proportionality, assess the risks to people, and set out the measures to address them. Seek the advice of the DPO where one is designated, and where appropriate the views of those affected. Where necessary, review whether processing follows the assessment, at least when the risk changes.

    GDPR, Article 35(2), (7), (9) and (11)

  • Prior consultation

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Consult the supervisory authority before processing if the assessment shows the processing would result in a high risk in the absence of measures taken by the controller to mitigate it. Provide responsibilities, purposes and means, safeguards, DPO contact details, the assessment and anything else the authority asks for.

    GDPR, Article 36(1) to (3)

Records of processing

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.IM-P

Nothing in the acts covered.

  • Controller's record of processing

    Applies to: Controllers

    Keep a written or electronic record of the name and contact details of the controller and any joint controller, representative and DPO, purposes, categories of people, data and recipients, transfers, erasure time limits and security measures where possible, and show it to the authority on request. The duty does not apply to organisations under 250 persons, unless the processing is likely to risk people's rights, is not occasional, or includes special category or criminal data.

    GDPR, Article 30(1), (3), (4) and (5)

  • Processor's record of processing

    Applies to: Processors

    Keep a written or electronic record of the name and contact details of the processor, each controller served and any representative and DPO, the categories of processing for each controller, transfers and, where possible, security measures. Show it to the authority on request. The same 250-person exemption applies.

    GDPR, Article 30(2) to (5)

Data protection officer

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework GV.PO-P

Nothing in the acts covered.

  • Designate a data protection officer

    Designate a DPO if the organisation is a public body, except courts acting in their judicial capacity, if its core activities need regular and systematic large-scale monitoring of people, or if they involve large-scale special category or criminal data. Choose the DPO for expertise in data protection law and practice. Publish the DPO's contact details and give them to the authority.

    GDPR, Article 37(1), (5) and (7)

  • Position and tasks of the DPO

    Involve the DPO promptly in all data protection issues and give the resources and access needed. The DPO takes no instructions on these tasks, cannot be dismissed or penalised for doing them, and reports to the highest management level, and other duties must not create a conflict of interests. The DPO advises, monitors compliance including staff training and audits, advises on impact assessments and acts as contact point for the authority.

    GDPR, Articles 38 and 39

International transfers

Only GDPR no specific requirement on the other side in the acts covered

Nothing in the acts covered.

  • Transfers need a Chapter V ground

    Transfer personal data to a third country or international organisation, including onward transfers, only under the conditions of Chapter V. A Commission adequacy decision allows a transfer without specific authorisation.

    GDPR, Articles 44 and 45

  • Appropriate safeguards

    Without an adequacy decision, transfer only with appropriate safeguards and enforceable rights and remedies for people. Options without specific authority approval include binding corporate rules approved under Article 47, standard data protection clauses, and approved codes or certification with binding commitments. Bespoke contractual clauses need the authority's authorisation.

    GDPR, Articles 46 and 47

  • Third-country orders

    Treat a third-country court or authority order to transfer or disclose personal data as recognised or enforceable only where it rests on an international agreement, such as a mutual legal assistance treaty, without prejudice to other Chapter V grounds.

    GDPR, Article 48

  • Derogations for specific situations

    Without adequacy or safeguards, transfer only on a listed ground such as explicit informed consent, contract need, important public interest, legal claims or vital interests. As a last resort, a non-repetitive transfer about few people may rest on compelling legitimate interests not overridden by the person's interests or rights, if the controller assesses it, applies safeguards, informs the authority and the people concerned, and records it. Public authorities exercising public powers cannot use the consent, contract or last-resort grounds.

    GDPR, Article 49

Supervision and enforcement

Cooperation with supervisors

Only GDPR no specific requirement on the other side in the acts covered

Nothing in the acts covered.

  • Cooperate with supervisory authority powers

    Cooperate with the supervisory authority on request. The authority can order information, audit, access data and premises, and issue warnings, reprimands and orders, including a processing ban, suspension of data flows or a fine.

    GDPR, Articles 31 and 58

Penalties and liability

Both cover it read the wording below

  • Administrative penalties

    Applies to: Competent authorities and Member States

    Competent authorities have supervisory, investigatory and sanctioning powers; Member States set the administrative penalties and remedial measures.

    DORA, Article 50

  • Fines for operational obligations

    Infringing the duties of controllers and processors in Articles 8, 11, 25 to 39, 42 and 43, or of certification and monitoring bodies, can be fined, and fines are set case by case to be effective, proportionate and dissuasive. Several infringements in the same or linked processing operations are capped at the amount for the gravest one.

    GDPR, Article 83(1) to (4)

  • Fines for principles, rights and transfers

    Infringing the principles and consent requirements in Articles 5, 6, 7 and 9, rights in Articles 12 to 22, transfer requirements in Articles 44 to 49, Member State law adopted under Chapter IX, or ignoring an authority's order or denying it access can be fined at the higher level.

    GDPR, Article 83(5) and (6)

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.

More Comparisons

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…