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

DORA vs PSD2

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

DORAFinancial entities

PSD2Payment service providers; authorisation requirements for payment institutions

At a Glance

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

  • DORA Asks more on 0 topics Alone on 21 topics More detailed on 4 topics
  • PSD2 Asks more on 0 topics Alone on 2 topics More detailed on 1 topic
Requirements per topic and verdict
Topic DORAPSD2 Verdict
Governance
Management accountability DORA: 3 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Roles and independence DORA: 1 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Security policy DORA: 3 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Awareness and training DORA: 2 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Risk management
Risk management framework DORA: 2 PSD2: 1 Both cover itread the wording below
Risk assessment DORA: 3 PSD2: 2 Both cover itread the wording below
Review, audit and improvement DORA: 4 PSD2: 2 DORA more detailedmore requirements on this, not necessarily stricter
Asset management DORA: 3 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Protection
Access control DORA: 3 PSD2: 2 Both cover itread the wording below
Authentication DORA: 2 PSD2: 14 PSD2 more detailedmore requirements on this, not necessarily stricter
Cryptography and encryption DORA: 2 PSD2: 2 Both cover itread the wording below
Data security DORA: 3 PSD2: 1 DORA more detailedmore requirements on this, not necessarily stricter
Network security DORA: 3 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Secure communications DORA: – PSD2: 4 Only PSD2no specific requirement on the other side in the acts covered
Secure acquisition and development DORA: 2 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Configuration, change and patch management DORA: 5 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Vulnerability handling DORA: 3 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Human resources security DORA: 1 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Physical and environmental security DORA: 1 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Detection and response
Monitoring and detection DORA: 3 PSD2: 1 DORA more detailedmore requirements on this, not necessarily stricter
Incident handling DORA: 3 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Incident classification DORA: 1 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Reporting to authorities DORA: 5 PSD2: 3 Both cover itread the wording below
Informing customers and the public DORA: 2 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Threat intelligence and information sharing DORA: 2 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Continuity and resilience
Business continuity and crisis management DORA: 3 PSD2: 1 DORA more detailedmore requirements on this, not necessarily stricter
Backup and recovery DORA: 1 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Security testing DORA: 3 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Threat-led penetration testing DORA: 1 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Third parties and supply chain
Supplier and third-party risk DORA: 2 PSD2: 1 Both cover itread the wording below
Contract requirements DORA: 2 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Register of third-party arrangements DORA: 1 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Exit and termination DORA: 1 PSD2: – Only DORAno specific requirement on the other side in the acts covered
Supervision and enforcement
Registration with authorities DORA: – PSD2: 7 Only PSD2no specific requirement on the other side in the acts covered
Penalties and liability DORA: 1 PSD2: 1 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

  • PSD2 Directive (EU) 2015/2366, OJ L 337, 23.12.2015, p. 35 Articles 5, 11, 12, 14, 15, 19, 28, 32, 33, 36, 65 to 68, 70, 95 to 98, 103 · 22 requirements
  • PSD2 SCA RTS Commission Delegated Regulation (EU) 2018/389, OJ L 69, 13.3.2018, p. 23 Articles 1, 3 to 6, 9 to 12, 15 to 19, 21, 22, 27, 28, 30 to 36 · Annex · 20 requirements Applies to: Payment service providers
  • EBA/GL/2018/05 EBA/GL/2018/05 of 18 July 2018, Guidelines on fraud reporting under the Payment Services Directive 2 (PSD2), as amended by EBA/GL/2020/01 of 22 January 2020 6 requirements
  • EBA ICT Guidelines EBA/GL/2019/04 (November 2019), as amended by EBA/GL/2025/02 of 11 February 2025; consolidated version of 19 May 2026 5 requirements

Status

Reviewed against the official texts.

Key Numbers

Threshold

DORA: Not in the acts covered

PSD2: Member state option, at most EUR 3 million a month

Incident reports go to

DORA: Financial supervisor (competent authority)

PSD2: Competent authority (providers outside DORADigital Operational Resilience Act only)

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

PSD2: Without undue delay (providers outside DORADigital Operational Resilience Act only)

Intermediate report

DORA: Within 72 hours of the initial notification

PSD2: Not in the acts covered

Final report

DORA: Within one month of the latest intermediate report

PSD2: Not in the acts covered

External assessment or certification

DORA: Not in the acts covered

PSD2: Independent audit of the security measures; yearly where the transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption is used (Payment service providers)

Review of the risk framework

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

PSD2: 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. to the authority at least once a year

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.

PSD2: Not in the acts covered

Threat-led penetration testing

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

PSD2: Not in the acts covered

Register of third-party arrangements

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

PSD2: Not in the acts covered

Registration with the authority

DORA: Not in the acts covered

PSD2: Authorisation by the home authority before providing payment services

Management body training

DORA: Required, on a regular basis

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

PSD2: Not in the acts covered

Maximum fines

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

PSD2: Set by each member state

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

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

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)

Nothing in the acts covered.

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)

  • Operational and security risk management

    Mitigation measures and controls for operational and security risks, with a yearly 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. to the authority.

    PSD2, Article 95

Risk assessment

Both cover it read the wording below

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

  • Risk measures and yearly assessment

    Mitigation measures and controls, and a comprehensive 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. to the authority at least yearly. For banks, payment and e-moneyElectronic Money institutions and account information providers, without prejudice to DORADigital Operational Resilience Act Chapter II since 17 January 2025.

    PSD2, Article 95(1)-(2)

  • Transaction risk analysis

    Applies to: Payment service providers

    Remote payments assessed as low risk in real time, up to EUR 100, 250 or 500 where the provider's fraud rate stays under the reference rate for that band (for cards 0.13%, 0.06% and 0.01%; for credit transfers 0.015%, 0.01% and 0.005%).

    PSD2 SCA RTS, Article 18 and Annex

Review, audit and improvement

DORA more detailed more requirements on this, not necessarily stricter

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

  • Transaction monitoring and review of security measures

    Applies to: Payment service providers

    Monitor transactions to detect unauthorised or fraudulent payments. Document, test and evaluate the security measures, and have them audited by operationally independent internal or external auditors; the report is available to the authority on request.

    PSD2 SCA RTS, Articles 1-3

  • Audit of security measures

    Applies to: Payment service providers

    The audit follows the provider's statutory audit cycle; where the transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption is used, its methodology, model and fraud rates are audited at least once a year.

    PSD2 SCA RTS, Article 3

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

Both cover it read the wording below

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

  • Access for third-party providers

    Account servicing providers confirm funds and give payment initiation and account information providers access without discrimination.

    PSD2, Articles 65-67

  • Confirmation of funds

    With the payer's explicit consent, the account servicing provider answers a card issuer's request with a yes or no only.

    PSD2, Article 65

Authentication

PSD2 more detailed more requirements on this, not necessarily stricter

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

  • Instruments and credentials

    Users keep their credentials safe and report loss or theft without undue delay; providers offer a free way to report and block use after it.

    PSD2, Articles 68-70

  • Strong customer authentication

    Strong customer authenticationAuthentication based on two or more independent elements from knowledge, possession and inherence. PSD2 requires payment service providers to apply it, for example when a payer accesses an account online or starts an electronic payment, subject to the applicable exemptions. when the payer goes online, pays electronically or acts remotely with a risk of fraud, with dynamic linkingA payment-authentication safeguard that binds approval to a specific payment amount and recipient. The payer is shown those details, and the authentication code must correspond to what the payer agreed. Changing the amount or recipient invalidates that code. Under the PSD2 technical requirements, this protects remote electronic payments against approval being redirected to a different transaction; it does not prescribe one particular technology. for remote payments.

    PSD2, Articles 97-98

  • When strong customer authentication applies

    When the payer accesses an account online, initiates an electronic payment, or acts remotely in a way that may imply a risk of fraud; with dynamic linkingA payment-authentication safeguard that binds approval to a specific payment amount and recipient. The payer is shown those details, and the authentication code must correspond to what the payer agreed. Changing the amount or recipient invalidates that code. Under the PSD2 technical requirements, this protects remote electronic payments against approval being redirected to a different transaction; it does not prescribe one particular technology. to amount and payee for remote payments, and protection of credentials.

    PSD2, Article 97

  • Technical standards

    The details, exemptions and the communication standards are in Delegated Regulation (EU) 2018/389, reviewed by the EBAEuropean Banking Authority with regard to DORADigital Operational Resilience Act.

    PSD2, Article 98

  • Strong customer authentication

    Applies to: Payment service providers

    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. codes built from two or more independent elements (knowledge, possession, inherence) that cannot be forged or derived, with dynamic linkingA payment-authentication safeguard that binds approval to a specific payment amount and recipient. The payer is shown those details, and the authentication code must correspond to what the payer agreed. Changing the amount or recipient invalidates that code. Under the PSD2 technical requirements, this protects remote electronic payments against approval being redirected to a different transaction; it does not prescribe one particular technology. to amount and payee for remote payments.

    PSD2 SCA RTS, Articles 4-9

  • Authentication code

    Applies to: Payment service providers

    No more than five failed attempts in a row before the instrument is blocked, protected sessions and at most five minutes of inactivity for online account access.

    PSD2 SCA RTS, Article 4

  • Dynamic linking

    Applies to: Payment service providers

    The payer sees the amount and the payee, and the code works only for them; any change invalidates it.

    PSD2 SCA RTS, Article 5

  • The elements and their independence

    Applies to: Payment service providers

    Measures against disclosure of knowledge elements, replication of possession elements and abuse of inherence elements; the breach of one element does not compromise the others, including on multi-purpose devices.

    PSD2 SCA RTS, Articles 6-9

  • Exemptions from strong customer authentication

    Applies to: Payment service providers

    Providers may skip strong customer authenticationAuthentication based on two or more independent elements from knowledge, possession and inherence. PSD2 requires payment service providers to apply it, for example when a payer accesses an account online or starts an electronic payment, subject to the applicable exemptions. in defined cases; the aggregator exemption for account information is mandatory.

    PSD2 SCA RTS, Articles 10-18

  • Account information

    Applies to: Payment service providers

    Limited access to balance and the last 90 days of transactions without SCAStrong Customer Authentication, renewed at least every 180 days; mandatory for access through an account information provider since 25 July 2023 (Delegated Regulation 2022/2360).

    PSD2 SCA RTS, Articles 10 and 10a

  • Contactless payments

    Applies to: Payment service providers

    Up to EUR 50 per payment, while the cumulative amount since the last SCAStrong Customer Authentication stays under EUR 150 or there have been no more than five payments.

    PSD2 SCA RTS, Article 11

  • Unattended terminals, trusted beneficiaries, recurring payments and own accounts

    Applies to: Payment service providers

    Transport fares and parking fees at unattended terminals, payees on the payer's trusted list, a series of payments of the same amount to the same payee after the first, and transfers between the payer's own accounts at the same provider.

    PSD2 SCA RTS, Articles 12-15

  • Low-value remote payments

    Applies to: Payment service providers

    Up to EUR 30 per payment, while the cumulative amount since the last SCAStrong Customer Authentication stays under EUR 100 or there have been no more than five payments.

    PSD2 SCA RTS, Article 16

  • Secure corporate payments

    Applies to: Payment service providers

    Dedicated payment processes and protocols for payers that are not consumers, where the authority is satisfied they give equivalent security.

    PSD2 SCA RTS, Article 17

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

  • Protection of personalised security credentials

    Applies to: Payment service providers

    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 integrity of credentials and 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. devices through their life cycle: creation, association with the user, delivery, renewal, destruction and revocation.

    PSD2 SCA RTS, Articles 22-27

  • Certificates and session security

    Applies to: Payment service providers

    Qualified eIDASRegulation (EU) No 910/2014 on Electronic Identification and Trust Services for Electronic Transactions in the Internal Market certificates for electronic seals or website 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., and secure 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. of the communication session.

    PSD2 SCA RTS, Articles 34-35

Data security

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

  • 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

  • Data exchange

    Applies to: Payment service providers

    Without the user actively requesting it, account information providers access the data no more than four times in 24 hours, unless agreed otherwise.

    PSD2 SCA RTS, Article 36

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 communications

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

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

Nothing in the acts covered.

  • Payment initiation services

    The account servicing provider treats orders from a payment initiation provider like its own; the initiator never holds the funds, identifies itself and changes nothing in the order.

    PSD2, Article 66

  • Account information services

    Only with the user's explicit consent, only for the designated accounts, with secure communication and no use of data beyond the service.

    PSD2, Article 67

  • Common and secure communication

    Applies to: Payment service providers

    Identification and traceability of communication between providers. Account servicing providers offer an access interface for third-party providers, either a dedicated interface or an adapted customer interface, identify them with eIDASRegulation (EU) No 910/2014 on Electronic Identification and Trust Services for Electronic Transactions in the Internal Market certificates and protect the session.

    PSD2 SCA RTS, Articles 28-36

  • Access interface

    Applies to: Payment service providers

    Technical documentation and a testing facility (published from 14 March 2019), and a choice between a dedicated interface and the customer interface.

    PSD2 SCA RTS, Articles 30-31

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

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

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

Nothing in the acts covered.

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

DORA more detailed more requirements on this, not necessarily stricter

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

  • Fraud rates and monitoring of exemptions

    Applies to: Payment service providers

    Fraud rates are calculated per quarter; a provider whose rate exceeds the reference rate for two consecutive quarters stops using the transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption and tells the authority. Fraud data on exemptions is recorded and monitored.

    PSD2 SCA RTS, Articles 19-21

Incident handling

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

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

Nothing in the acts covered.

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)

  • Incident reporting and fraud statistics

    Major incidents are reported (under DORADigital Operational Resilience Act for most providers since 2025) and fraud data is sent at least yearly.

    PSD2, Article 96

  • Major incident reporting

    Report major operational or security incidents to the home authority without undue delay and inform affected users. Since 17 January 2025 it no longer applies to providers in DORADigital Operational Resilience Act's scope, which report under DORADigital Operational Resilience Act.

    PSD2, Article 96(1)-(5)

  • Fraud statistics

    Statistical data on fraud by means of payment, at least yearly, to the authority.

    PSD2, Article 96(6)

Informing customers and the public

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

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)

Nothing in the acts covered.

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

DORA more detailed more requirements on this, not necessarily stricter

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

  • Dedicated interface and fallback

    Applies to: Payment service providers

    The same 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. and performance as the customer interface, without obstacles, with indicators published quarterly; a fallback to the customer interface unless the authority grants an exemption after consulting the EBAEuropean Banking Authority.

    PSD2 SCA RTS, Articles 32-33

Backup and recovery

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

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

Nothing in the acts covered.

Security testing

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

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

Nothing in the acts covered.

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)

  • Agents and outsourcing

    Agents are notified and registered before they start. Outsourcing of important operational functions, including ICTInformation and Communication Technology systems, must not impair internal control or supervision.

    PSD2, Article 19

Contract requirements

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

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)

Nothing in the acts covered.

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.

Supervision and enforcement

Registration with authorities

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

Nothing in the acts covered.

  • Authorisation, capital and safeguarding

    A payment institutionIn the EU payment-services framework, a legal entity authorised under PSD2 to provide and execute payment services. Depending on its permission, these can include transferring money, processing card payments or providing payment-initiation services. It is one category of payment service provider, alongside other categories such as banks and electronic money institutions, which are authorised to issue electronically stored monetary value accepted for payments by someone other than the issuer. Its authorisation covers specified services rather than every financial activity. is authorised by its home authority before it starts, holds initial capital and own funds, and keeps users' funds safe.

    PSD2, Articles 5-12

  • Application for authorisation

    The application covers the programme of operations, a three-year business plan, capital, safeguarding, governance, incident and complaint procedures, sensitive payment data, 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., a security policy 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., AMLAnti-Money Laundering controls, owners and directors. The authority decides within three months; the authorisation is valid across the EU.

    PSD2, Articles 5, 11, 12

  • Registers, agents, passporting and bank account access

    Authorised and registered providers are listed in public registers; agents and outsourcing are notified; a passport opens the EU; banks give payment institutionsPayment Institution fair access to accounts.

    PSD2, Articles 14-15, 19, 28, 36

  • Public registers

    Each member state keeps a public register of payment institutionsPayment Institution, their agents and branches, exempt institutions and account information providers; the EBAEuropean Banking Authority keeps a central register.

    PSD2, Articles 14-15

  • Small payment institutions and account information providers

    Member states may register small payment institutionsPayment Institution instead of authorising them; account information providers are registered.

    PSD2, Articles 32-33

  • Small payment institutions

    A member state may exempt institutions whose monthly average of payment transactions over 12 months stays under a national limit of at most EUR 3 million; they are registered and cannot passport.

    PSD2, Article 32

  • Account information providers

    Registered instead of authorised, with professional indemnity insurance; most of Titles III and IV does not apply to them.

    PSD2, Article 33

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

  • Penalties

    Member states set effective, proportionate and dissuasive penalties.

    PSD2, Article 103

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…