> DORA vs PSD2 side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# DORA vs PSD2

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

[DORA](https://grc.plus/regulation/digital-operational-resilience-act-dora/)Financial entities

[PSD2](https://grc.plus/regulation/revised-payment-services-directive-psd2/)Payment 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

| Topic | DORA | PSD2 | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Management accountability | DORA: 3 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Roles and independence | DORA: 1 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Security policy | DORA: 3 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Awareness and training | DORA: 2 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Risk management |  |  |  |
| Risk management framework | DORA: 2 | PSD2: 1 | **Both cover it**read the wording below |
| Risk assessment | DORA: 3 | PSD2: 2 | **Both cover it**read the wording below |
| Review, audit and improvement | DORA: 4 | PSD2: 2 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Asset management | DORA: 3 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | DORA: 3 | PSD2: 2 | **Both cover it**read the wording below |
| Authentication | DORA: 2 | PSD2: 14 | **PSD2 more detailed**more requirements on this, not necessarily stricter |
| Cryptography and encryption | DORA: 2 | PSD2: 2 | **Both cover it**read the wording below |
| Data security | DORA: 3 | PSD2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Network security | DORA: 3 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Secure communications | DORA: – | PSD2: 4 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Secure acquisition and development | DORA: 2 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Configuration, change and patch management | DORA: 5 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Vulnerability handling | DORA: 3 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Human resources security | DORA: 1 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Physical and environmental security | DORA: 1 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Monitoring and detection | DORA: 3 | PSD2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Incident handling | DORA: 3 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Incident classification | DORA: 1 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Reporting to authorities | DORA: 5 | PSD2: 3 | **Both cover it**read the wording below |
| Informing customers and the public | DORA: 2 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Threat intelligence and information sharing | DORA: 2 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | DORA: 3 | PSD2: 1 | **DORA more detailed**more requirements on this, not necessarily stricter |
| Backup and recovery | DORA: 1 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Security testing | DORA: 3 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Threat-led penetration testing | DORA: 1 | PSD2: – | **Only DORA**no 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 it**read the wording below |
| Contract requirements | DORA: 2 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Register of third-party arrangements | DORA: 1 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Exit and termination | DORA: 1 | PSD2: – | **Only DORA**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Registration with authorities | DORA: – | PSD2: 7 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Penalties and liability | DORA: 1 | PSD2: 1 | **Both cover it**read 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](https://grc.plus/regulation/digital-operational-resilience-act-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](https://grc.plus/regulation/dora-rts-ict-risk-management/) 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](https://grc.plus/regulation/dora-guidelines-incident-costs-and-losses/) 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

- [DORA Third-Party Policy RTS](https://grc.plus/regulation/dora-rts-ict-third-party-policy/)
- [DORA Subcontracting RTS](https://grc.plus/regulation/dora-rts-subcontracting/)
- [DORA Register of Information ITS](https://grc.plus/regulation/dora-its-register-of-information/)
- [DORA Incident Classification RTS](https://grc.plus/regulation/dora-rts-incident-classification/)
- [DORA Incident Reporting RTS](https://grc.plus/regulation/dora-rts-incident-reporting/)
- [DORA Incident Reporting ITS](https://grc.plus/regulation/dora-its-incident-reporting-templates/)
- [DORA TLPT RTS](https://grc.plus/regulation/dora-rts-tlpt/)
- [DORA Critical Provider Criteria](https://grc.plus/regulation/dora-da-critical-provider-criteria/)
- [DORA Oversight Conditions RTS](https://grc.plus/regulation/dora-rts-oversight-conditions/)

Status

Reviewed against the official texts.

Included

- [PSD2](https://grc.plus/regulation/revised-payment-services-directive-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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/) 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](https://grc.plus/regulation/psd2-guidelines-fraud-reporting/) 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](https://grc.plus/regulation/eba-guidelines-ict-and-security-risk-management/) 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 DORA 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 DORA 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 analysis exemption is used (Payment service providers)

### Review of the risk framework

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

PSD2: Risk assessment to the authority at least once a year

### Testing of critical systems

DORA: At least yearly, for systems supporting critical or important 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 ICT 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 risk; 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 risk management framework, and bears ultimate responsibility for managing ICT risk.
  [DORA, Article 5(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Budget for resilience
  The management body allocates and reviews the budget for digital operational resilience, including awareness programmes, training and ICT skills for all staff.
  [DORA, Article 5(2)(g)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Governance (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Governance and organisation of the simplified ICT risk management framework.
  [DORA ICT Risk Management RTS, Article 28](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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 risk (not required of microenterprises). Risk management, control and internal audit functions are kept appropriately segregated and independent.
  [DORA, Article 6(4)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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 availability, authenticity, integrity and confidentiality of data and assets, including customers' where applicable.
  [DORA, Article 9(4)(a)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT security policies
  Applies to: Financial entities, except those on the simplified framework
  ICT 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](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Information security policy (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  An information security policy and measures.
  [DORA ICT Risk Management RTS, Article 29](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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 risk up to date, including by following specific training regularly.
  [DORA, Article 5(4)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Staff awareness and training
  ICT security awareness programmes and digital operational resilience training are compulsory for all employees and senior management.
  [DORA, Article 13(6)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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 risk management framework within the overall risk management system, with the strategies, policies, procedures, protocols and tools to protect all information and ICT assets.
  [DORA, Article 6(1) and (2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Simplified ICT risk management framework
  Applies to: Entities on the simplified framework (DORA Article 16)
  Small and non-interconnected investment firms, exempted payment and e-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)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Operational and security risk management
  Mitigation measures and controls for operational and security risks, with a yearly risk assessment to the authority.
  [PSD2, Article 95](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

### 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 risk continuously, assess cyber threats and vulnerabilities, and review risk scenarios at least yearly.
  [DORA, Article 8(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT risk management policy
  Applies to: Financial entities, except those on the simplified framework
  A policy and procedures for ICT risk management: risk tolerance, identification, assessment and treatment of risks, and the monitoring of residual risk.
  [DORA ICT Risk Management RTS, Article 3](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- ICT risk management (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Identification and management of ICT risk.
  [DORA ICT Risk Management RTS, Article 31](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Risk measures and yearly assessment
  Mitigation measures and controls, and a comprehensive risk assessment to the authority at least yearly. For banks, payment and e-money institutions and account information providers, without prejudice to DORA Chapter II since 17 January 2025.
  [PSD2, Article 95(1)-(2)](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### 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 microenterprises), after major ICT-related incidents and following supervisory instructions or conclusions from testing or audits, and improved continuously.
  [DORA, Article 6(5)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Internal audit
  Auditors with sufficient ICT risk expertise audit the framework regularly, in line with the audit plan. Not required of microenterprises.
  [DORA, Article 6(6)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- 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 risk management framework.
  [DORA ICT Risk Management RTS, Article 27](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Framework review report (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  The format and content of the report on the review of the simplified framework.
  [DORA ICT Risk Management RTS, Article 41](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- 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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Audit of security measures
  Applies to: Payment service providers
  The audit follows the provider's statutory audit cycle; where the transaction risk analysis exemption is used, its methodology, model and fraud rates are audited at least once a year.
  [PSD2 SCA RTS, Article 3](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### 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 ICT-supported business functions, information and ICT assets and their dependencies, and review the classification at least yearly.
  [DORA, Article 8(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT asset management
  Applies to: Financial entities, except those on the simplified framework
  An ICT asset management policy and procedure, including an inventory of assets and their criticality.
  [DORA ICT Risk Management RTS, Articles 4 and 5](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Asset classification (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Classification of information assets and ICT assets.
  [DORA ICT Risk Management RTS, Article 30](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Identity management and access control
  Applies to: Financial entities, except those on the simplified framework
  Identity management and access control policies, including authentication.
  [DORA ICT Risk Management RTS, Articles 20 and 21](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Access control (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  Access control.
  [DORA ICT Risk Management RTS, Article 33](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- 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](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

### 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 authentication based on relevant standards, and protection of cryptographic keys, with encryption decided by data classification and risk assessment.
  [DORA, Article 9(4)(d)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Identity management and access control
  Applies to: Financial entities, except those on the simplified framework
  Identity management and access control policies, including authentication.
  [DORA ICT Risk Management RTS, Articles 20 and 21](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- 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](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Strong customer authentication
  Strong customer authentication when the payer goes online, pays electronically or acts remotely with a risk of fraud, with dynamic linking for remote payments.
  [PSD2, Articles 97-98](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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 linking to amount and payee for remote payments, and protection of credentials.
  [PSD2, Article 97](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Technical standards
  The details, exemptions and the communication standards are in Delegated Regulation (EU) 2018/389, reviewed by the EBA with regard to DORA.
  [PSD2, Article 98](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Strong customer authentication
  Applies to: Payment service providers
  Authentication codes built from two or more independent elements (knowledge, possession, inherence) that cannot be forged or derived, with dynamic linking to amount and payee for remote payments.
  [PSD2 SCA RTS, Articles 4-9](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- 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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- 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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- 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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Exemptions from strong customer authentication
  Applies to: Payment service providers
  Providers may skip strong customer authentication in defined cases; the aggregator exemption for account information is mandatory.
  [PSD2 SCA RTS, Articles 10-18](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Account information
  Applies to: Payment service providers
  Limited access to balance and the last 90 days of transactions without SCA, 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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Contactless payments
  Applies to: Payment service providers
  Up to EUR 50 per payment, while the cumulative amount since the last SCA stays under EUR 150 or there have been no more than five payments.
  [PSD2 SCA RTS, Article 11](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- 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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Low-value remote payments
  Applies to: Payment service providers
  Up to EUR 30 per payment, while the cumulative amount since the last SCA stays under EUR 100 or there have been no more than five payments.
  [PSD2 SCA RTS, Article 16](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- 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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### 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 authentication based on relevant standards, and protection of cryptographic keys, with encryption decided by data classification and risk assessment.
  [DORA, Article 9(4)(d)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Encryption and key management
  Applies to: Financial entities, except those on the simplified framework
  Encryption and cryptographic controls, and the management of cryptographic keys through their whole life cycle.
  [DORA ICT Risk Management RTS, Articles 6 and 7](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Protection of personalised security credentials
  Applies to: Payment service providers
  Confidentiality and integrity of credentials and authentication devices through their life cycle: creation, association with the user, delivery, renewal, destruction and revocation.
  [PSD2 SCA RTS, Articles 22-27](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Certificates and session security
  Applies to: Payment service providers
  Qualified eIDAS certificates for electronic seals or website authentication, and secure encryption of the communication session.
  [PSD2 SCA RTS, Articles 34-35](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### 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)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT operations and data security
  Applies to: Financial entities, except those on the simplified framework
  Policies and procedures for ICT operations, capacity and performance management, and data and system security.
  [DORA ICT Risk Management RTS, Articles 8, 9 and 11](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Operations, data and network security (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT operations security, and data, system and network security.
  [DORA ICT Risk Management RTS, Articles 34 and 35](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- 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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### 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)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- 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](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Operations, data and network security (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT operations security, and data, system and network security.
  [DORA ICT Risk Management RTS, Articles 34 and 35](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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 eIDAS certificates and protect the session.
  [PSD2 SCA RTS, Articles 28-36](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- 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](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### 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
  ICT project management, and the acquisition, development and maintenance of ICT systems.
  [DORA ICT Risk Management RTS, Articles 15 and 16](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Development and change (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT systems acquisition, development and maintenance, and ICT project and change management.
  [DORA ICT Risk Management RTS, Articles 37 and 38](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Patches and updates
  Documented policies for patches and updates.
  [DORA, Article 9(4)(f)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Vulnerability and patch management
  Applies to: Financial entities, except those on the simplified framework
  Procedures to identify and fix vulnerabilities and to apply patches and updates.
  [DORA ICT Risk Management RTS, Article 10](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- ICT change management
  Applies to: Financial entities, except those on the simplified framework
  ICT change management procedures.
  [DORA ICT Risk Management RTS, Article 17](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Development and change (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT systems acquisition, development and maintenance, and ICT project and change management.
  [DORA ICT Risk Management RTS, Articles 37 and 38](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Tests to run
  Appropriate tests such as vulnerability assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.
  [DORA, Article 25](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Vulnerability and patch management
  Applies to: Financial entities, except those on the simplified framework
  Procedures to identify and fix vulnerabilities and to apply patches and updates.
  [DORA ICT Risk Management RTS, Article 10](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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 ICT security.
  [DORA ICT Risk Management RTS, Article 19](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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

- Physical and environmental security
  Applies to: Financial entities, except those on the simplified framework
  A physical and environmental security policy.
  [DORA ICT Risk Management RTS, Article 18](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- 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](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Incident management and detection
  Applies to: Financial entities, except those on the simplified framework
  An ICT-related incident management policy, and criteria to detect anomalous activity and trigger incident response.
  [DORA ICT Risk Management RTS, Articles 22 and 23](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- 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 analysis exemption and tells the authority. Fraud data on exemptions is recorded and monitored.
  [PSD2 SCA RTS, Articles 19-21](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### 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 incident disrupts core activities, to find the causes and the improvements needed.
  [DORA, Article 13(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Incident management process
  A process to detect, manage and notify ICT-related incidents: record all incidents and significant cyber threats, assign roles, escalate, and find and fix root causes.
  [DORA, Article 17](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Incident management and detection
  Applies to: Financial entities, except those on the simplified framework
  An ICT-related incident management policy, and criteria to detect anomalous activity and trigger incident response.
  [DORA ICT Risk Management RTS, Articles 22 and 23](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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 incidents to the competent authority, using the common templates.
  [DORA, Article 19(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Initial notification
  An initial notification once the incident is classified as major.
  [DORA, Article 19(4)(a); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Intermediate report
  An intermediate report, updated when regular activities have been recovered.
  [DORA, Article 19(4)(b); Delegated Regulation (EU) 2025/301, Article 5](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Final report
  A final report once the root cause analysis 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](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Voluntary notice of cyber threats Optional
  Significant cyber threats may be notified to the competent authority.
  [DORA, Article 19(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Incident reporting and fraud statistics
  Major incidents are reported (under DORA for most providers since 2025) and fraud data is sent at least yearly.
  [PSD2, Article 96](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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 DORA's scope, which report under DORA.
  [PSD2, Article 96(1)-(5)](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Fraud statistics
  Statistical data on fraud by means of payment, at least yearly, to the authority.
  [PSD2, Article 96(6)](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

### 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 vulnerabilities to clients, counterparts and the public, and a person in charge of public and media communication.
  [DORA, Article 14](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- 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)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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 vulnerabilities, cyber threats and incidents and to analyse their likely impact.
  [DORA, Article 13(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Information-sharing arrangements Optional
  Financial entities may exchange cyber threat information within trusted communities, under arrangements that protect confidentiality and personal data. They must tell the competent authority when they join or leave.
  [DORA, Article 45](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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 ICT business continuity policy, response and recovery plans that are tested at least yearly and after substantive changes to systems supporting critical or important functions, and a business impact analysis.
  [DORA, Article 11](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- ICT business continuity
  Applies to: Financial entities, except those on the simplified framework
  The components of the ICT business continuity policy, the testing of continuity plans, and ICT response and recovery plans.
  [DORA ICT Risk Management RTS, Articles 24 to 26](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)
- Business continuity (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  An ICT business continuity plan and its testing.
  [DORA ICT Risk Management RTS, Articles 39 and 40](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

- Dedicated interface and fallback
  Applies to: Payment service providers
  The same availability 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 EBA.
  [PSD2 SCA RTS, Articles 32-33](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### 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
  Backup policies setting scope and minimum frequency, restoration on own systems segregated from the source, periodic testing, and redundant ICT capacity (microenterprises assess the need based on their risk profile).
  [DORA, Article 12](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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 ICT systems and applications supporting critical or important functions tested at least yearly. Not required of microenterprises.
  [DORA, Article 24](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Tests to run
  Appropriate tests such as vulnerability assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.
  [DORA, Article 25](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Security testing (simplified)
  Applies to: Entities on the simplified framework (DORA Article 16)
  ICT security testing.
  [DORA ICT Risk Management RTS, Article 36](https://grc.plus/regulation/dora-rts-ict-risk-management/#requirements)

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 microenterprises 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)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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 risk is managed within the ICT risk management framework, and the entity stays fully responsible for compliance.
  [DORA, Article 28(1)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Third-party risk strategy
  A regularly reviewed strategy on ICT third-party risk, with a policy on ICT services supporting critical or important functions. The management body regularly reviews the risks from those arrangements. Not required of microenterprises or Article 16 entities.
  [DORA, Article 28(2)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Agents and outsourcing
  Agents are notified and registered before they start. Outsourcing of important operational functions, including ICT systems, must not impair internal control or supervision.
  [PSD2, Article 19](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

### 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)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)
- Terms for critical or important functions
  Contracts for services supporting critical or important functions add full service level descriptions, notice periods, business contingency plans, participation in TLPT, unrestricted rights of access, inspection and audit (microenterprises may agree to delegate these to an independent third party), and exit strategies with a transition period.
  [DORA, Article 30(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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 ICT 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 functions.
  [DORA, Article 28(3)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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 ICT services supporting critical or important functions, covering provider failure, falling quality and business disruption.
  [DORA, Article 28(8)](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

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 institution is authorised by its home authority before it starts, holds initial capital and own funds, and keeps users' funds safe.
  [PSD2, Articles 5-12](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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 continuity, a security policy and risk assessment, AML controls, owners and directors. The authority decides within three months; the authorisation is valid across the EU.
  [PSD2, Articles 5, 11, 12](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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 institutions fair access to accounts.
  [PSD2, Articles 14-15, 19, 28, 36](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Public registers
  Each member state keeps a public register of payment institutions, their agents and branches, exempt institutions and account information providers; the EBA keeps a central register.
  [PSD2, Articles 14-15](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Small payment institutions and account information providers
  Member states may register small payment institutions instead of authorising them; account information providers are registered.
  [PSD2, Articles 32-33](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

### 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](https://grc.plus/regulation/digital-operational-resilience-act-dora/#requirements)

- Penalties
  Member states set effective, proportionate and dissuasive penalties.
  [PSD2, Article 103](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

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

- [Compare DORA](https://grc.plus/compare/dora/)
- [Compare PSD2](https://grc.plus/compare/psd2/)

Source: https://grc.plus/compare/dora-vs-psd2/
