> CRA 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.

# CRA vs PSD2

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

[CRA](https://grc.plus/regulation/cyber-resilience-act-cra/)Manufacturers of products with digital elements

[PSD2](https://grc.plus/regulation/revised-payment-services-directive-psd2/)Payment service providers; authorisation requirements for payment institutions

## At a Glance

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

- **CRA** Asks more on 0 topics Alone on 11 topics More detailed on 3 topics
- **PSD2** Asks more on 0 topics Alone on 3 topics More detailed on 1 topic

| Topic | CRA | PSD2 | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Roles and independence | CRA: 1 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Risk management |  |  |  |
| Risk management framework | CRA: – | PSD2: 1 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Risk assessment | CRA: 1 | PSD2: 2 | **Both cover it**read the wording below |
| Review, audit and improvement | CRA: 5 | PSD2: 2 | **CRA more detailed**more requirements on this, not necessarily stricter |
| Asset management | CRA: 1 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | CRA: 1 | PSD2: 2 | **Both cover it**read the wording below |
| Authentication | CRA: 1 | PSD2: 14 | **PSD2 more detailed**more requirements on this, not necessarily stricter |
| Cryptography and encryption | CRA: 1 | PSD2: 2 | **Both cover it**read the wording below |
| Data security | CRA: 2 | PSD2: 1 | **Both cover it**read the wording below |
| Secure communications | CRA: – | PSD2: 4 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Secure acquisition and development | CRA: 2 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Configuration, change and patch management | CRA: 2 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Vulnerability handling | CRA: 7 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Monitoring and detection | CRA: 1 | PSD2: 1 | **Both cover it**read the wording below |
| Incident classification | CRA: 1 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Reporting to authorities | CRA: 4 | PSD2: 3 | **Both cover it**read the wording below |
| Informing customers and the public | CRA: 4 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Threat intelligence and information sharing | CRA: 1 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | CRA: 1 | PSD2: 1 | **Both cover it**read the wording below |
| Security testing | CRA: 1 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | CRA: 4 | PSD2: 1 | **CRA more detailed**more requirements on this, not necessarily stricter |
| Privacy and data protection |  |  |  |
| Privacy by design and by default | CRA: 1 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Registration with authorities | CRA: – | PSD2: 7 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Cooperation with supervisors | CRA: 7 | PSD2: – | **Only CRA**no specific requirement on the other side in the acts covered |
| Penalties and liability | CRA: 3 | PSD2: 1 | **CRA more detailed**more requirements on this, not necessarily stricter |

## 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

- [CRA](https://grc.plus/regulation/cyber-resilience-act-cra/) Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 Articles 13 to 16, 19 to 22, 28, 30 to 32, 64 · Annex · 42 requirements
- [CRA Product Categories](https://grc.plus/regulation/cra-implementing-regulation-product-categories/) Commission Implementing Regulation (EU) 2025/2392 of 28 November 2025 on the technical description of the categories of important and critical products with digital elements pursuant to Regulation (EU) 2024/2847 of the European Parliament and of the Council (OJ L, 2025/2392, 1.12.2025) Articles 2, 7, 8, 32 · Annex · 4 requirements
- [Kamerstuk 36875](https://grc.plus/regulation/netherlands-cra-implementation-act/) Kamerstukken 36875, Regels ter uitvoering van Verordening (EU) 2024/2847 (Uitvoeringswet verordening cyberweerbaarheid), voorstel van wet (36875, nr. 2) and memorie van toelichting (36875, nr. 3) Articles 1 to 3, 5, 7 · 5 requirements
- [S.L. 591.06](https://grc.plus/regulation/malta-cyber-resilience-regulations/) L.N. 238 of 2026, Cyber Resilience Regulations, 2026, made under article 58 of the Malta Digital Innovation Authority Act (Cap. 591); Government Gazette No. 21,717, 11 September 2026; S.L. 591.06 4 requirements

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

### Deadline

CRA: Final report within 14 days of a corrective or mitigating measure being available

PSD2: Not in the acts covered

### Threshold

CRA: Harm to protection of sensitive or important data or functions, or malicious code

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

### Goes to

CRA: Manufacturer and market surveillance authorities (Importers); Manufacturer and market surveillance authorities (Distributors)

PSD2: Not in the acts covered

### Evidence to keep

CRA: Documented risk assessment in the technical documentation; EU declaration of conformity, at least 10 years or the support period if longer (Importers); Technical documentation and EU declaration, at least 10 years or the support period if longer; Software bill of materials

PSD2: Not in the acts covered

### Incident reports go to

CRA: Coordinating CSIRT and ENISA, via the single reporting platform; Coordinating CSIRT and ENISA, via the single reporting platform; Coordinating CSIRT of the main establishment and ENISA

PSD2: Competent authority (providers outside DORA only)

### First notice of an incident

CRA: Within 24 hours of becoming aware; Within 24 hours of becoming aware

PSD2: Without undue delay (providers outside DORA only)

### Incident notification

CRA: Within 72 hours of becoming aware; Within 72 hours of becoming aware

PSD2: Not in the acts covered

### Intermediate report

CRA: On request of the coordinating CSIRT; On request of the coordinating CSIRT

PSD2: Not in the acts covered

### Final report

CRA: Within one month of the incident notification

PSD2: Not in the acts covered

### External assessment or certification

CRA: Module A, modules B and C, module H, or an EU certification scheme; Third-party assessment or certification, depending on class (Manufacturers of important and critical products)

PSD2: Independent audit of the security measures; yearly where the transaction risk analysis exemption is used (Payment service providers)

### Review of the risk framework

CRA: Not in the acts covered

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

### Registration with the authority

CRA: Not in the acts covered

PSD2: Authorisation by the home authority before providing payment services

### Maximum fines

CRA: Up to EUR 15,000,000 or 2.5% of worldwide annual turnover, whichever is higher (Manufacturers); Up to EUR 10,000,000 or 2% of worldwide annual turnover, whichever is higher (Economic operators and others subject to the listed articles); Up to EUR 5,000,000 or 1% of worldwide annual turnover, whichever is higher (Economic operators)

PSD2: Set by each member state

## Governance

### Roles and independence

**Only CRA** 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

- When others become the manufacturer
  Applies to: Importers and distributors who sell a product under their own name or trademark or substantially modify it, and others who substantially modify a product
  An importer or distributor that sells a product under its own name or trademark, or substantially modifies it, is treated as the manufacturer and is subject to Articles 13 and 14. Any other person who substantially modifies a product and makes it available is also a manufacturer, for the affected part or the whole product if its overall cybersecurity is affected.
  [CRA, Articles 21, 22](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

Nothing in the acts covered.

## Risk management

### Risk management framework

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

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

Nothing in the acts covered.

- 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

- Cybersecurity risk assessment
  Assess the product's cybersecurity risks and use the result across planning, design, development, production, delivery and maintenance. Document it, update it during the support period, base it on intended and foreseeable use, and include it in the technical documentation with a justification for any requirement that does not apply.
  [CRA, Article 13(2) to (4)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

**CRA 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

- Correct non-conformity
  If you know or have reason to believe the product or your processes do not meet Annex I, immediately take corrective measures, or withdraw or recall the product as appropriate.
  [CRA, Article 13(21)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- EU declaration of conformity
  Once conformity is shown, draw up the EU declaration, following the Annex V structure, and supply it or a simplified version with the product. Use a single declaration where several Union acts apply. By drawing it up you assume responsibility for the product's compliance.
  [CRA, Articles 13(12), (20), 28](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Technical documentation
  Draw up technical documentation with at least the Annex VII elements before placing the product on the market and update it as needed, at least during the support period. Keep it and the EU declaration available to the market surveillance authorities for at least 10 years after the product is placed on the market, or for the support period if longer.
  [CRA, Articles 13(13), 31(1), (2)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Choose a conformity route
  Assess the product and your processes against Annex I using internal control (module A), EU-type examination with conformity to type (modules B and C), full quality assurance (module H), or a European cybersecurity certification scheme where available and applicable.
  [CRA, Article 32(1)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Third-party assessment by product class
  Applies to: Manufacturers of important and critical products
  Important products in class I use modules B and C or module H unless harmonised standards, common specifications or a scheme at assurance level substantial were fully applied. Class II use modules B and C, module H or a scheme at that level. Critical products use a certification scheme under Article 8(1), or the class II procedures where its conditions are not met.
  [CRA, Article 32(2) to (4)](https://grc.plus/regulation/cyber-resilience-act-cra/#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 CRA** 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

- Software bill of materials
  Identify and document vulnerabilities and components, including a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies.
  [CRA, Annex I, Part II, point (1)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

- Protect against unauthorised access
  Where applicable, protect against unauthorised access with appropriate controls such as authentication, identity or access management, and report possible unauthorised access.
  [CRA, Annex I, Part I, point (2)(d)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

- Protect against unauthorised access
  Where applicable, protect against unauthorised access with appropriate controls such as authentication, identity or access management, and report possible unauthorised access.
  [CRA, Annex I, Part I, point (2)(d)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

- Confidentiality and integrity of data
  Where applicable, protect the confidentiality of stored, transmitted or processed data, such as by state-of-the-art encryption at rest and in transit. Protect data, commands, programs and configuration against unauthorised change, and report corruption.
  [CRA, Annex I, Part I, point (2)(e), (f)](https://grc.plus/regulation/cyber-resilience-act-cra/#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

**Both cover it** read the wording below

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

- Confidentiality and integrity of data
  Where applicable, protect the confidentiality of stored, transmitted or processed data, such as by state-of-the-art encryption at rest and in transit. Protect data, commands, programs and configuration against unauthorised change, and report corruption.
  [CRA, Annex I, Part I, point (2)(e), (f)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Minimise data and allow removal
  Where applicable, process only data that is adequate, relevant and limited to the product's purpose. Let users securely and easily remove all data and settings permanently, and make any transfer to other products secure.
  [CRA, Annex I, Part I, point (2)(g), (m)](https://grc.plus/regulation/cyber-resilience-act-cra/#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)

### 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 CRA** 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

- Meet the essential requirements
  When placing a product on the market, ensure it was designed, developed and produced in line with the cybersecurity requirements in Annex I, Part I.
  [CRA, Article 13(1)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- No known vulnerabilities, secure by default and reduced attack surface
  Where applicable on the basis of the risk assessment, supply the product without known exploitable vulnerabilities and with a secure-by-default configuration that can be reset. Limit attack surfaces and reduce the impact of incidents with exploitation mitigation.
  [CRA, Annex I, Part I, point (2)(a), (b), (j), (k)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

Nothing in the acts covered.

### Configuration, change and patch management

**Only CRA** 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

- Keep security updates available
  Keep each security update issued during the support period available for at least 10 years after it is issued, or for the rest of the support period if longer.
  [CRA, Article 13(9)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Test, fix and disclose vulnerabilities
  Remediate vulnerabilities without delay, with security updates separate from functional ones where feasible, distributed securely and free of charge unless agreed otherwise for tailor-made products. Test and review security regularly. Enforce a coordinated vulnerability disclosure policy, provide a reporting contact, and publish information on fixed vulnerabilities.
  [CRA, Annex I, Part II, points (2) to (8)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

Nothing in the acts covered.

### Vulnerability handling

**Only CRA** no specific requirement on the other side in the acts covered

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

- Third-party components
  Exercise due diligence when integrating third-party components, including open-source ones, so they do not compromise the product. If you find a vulnerability in a component, report it to whoever makes or maintains the component and remediate it, sharing your fix where you developed one.
  [CRA, Article 13(5), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Set and state the support period
  Handle vulnerabilities effectively for a support period that reflects expected use and is at least five years, or the expected use time if shorter. State the end date, at least month and year, clearly at the time of purchase, and notify users when support ends where technically feasible.
  [CRA, Article 13(8), (19)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Report actively exploited vulnerabilities
  Notify any actively exploited vulnerability you become aware of to the coordinating CSIRT and ENISA at the same time. Send an early warning within 24 hours and a vulnerability notification with general information and mitigations within 72 hours. Send a final report describing the vulnerability, any malicious actor and the fix no later than 14 days after a corrective or mitigating measure is available. The coordinating CSIRT may ask for an intermediate report.
  [CRA, Article 14(1), (2), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Importer corrective action and alerts
  Applies to: Importers
  Hold back non-conforming products and take corrective measures, withdraw or recall those already placed. Inform the manufacturer of any vulnerability without undue delay, and where a product presents a significant cybersecurity risk, immediately inform the market surveillance authorities.
  [CRA, Article 19(3), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Distributor corrective action and alerts
  Applies to: Distributors
  Make sure corrective measures, withdrawal or recall take place for non-conforming products. Inform the manufacturer of any vulnerability without undue delay. Immediately inform market surveillance authorities of a significant cybersecurity risk. If the manufacturer has ceased operations, inform the authorities without undue delay and, as far as possible, users.
  [CRA, Article 20(4), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Software bill of materials
  Identify and document vulnerabilities and components, including a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies.
  [CRA, Annex I, Part II, point (1)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Test, fix and disclose vulnerabilities
  Remediate vulnerabilities without delay, with security updates separate from functional ones where feasible, distributed securely and free of charge unless agreed otherwise for tailor-made products. Test and review security regularly. Enforce a coordinated vulnerability disclosure policy, provide a reporting contact, and publish information on fixed vulnerabilities.
  [CRA, Annex I, Part II, points (2) to (8)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

Nothing in the acts covered.

## Detection and response

### Monitoring and detection

**Both cover it** read the wording below

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

- Record and monitor activity
  Where applicable, provide security-related information by recording and monitoring relevant internal activity, including access to or changes of data, services or functions, with a user opt-out.
  [CRA, Annex I, Part I, point (2)(l)](https://grc.plus/regulation/cyber-resilience-act-cra/#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 classification

**Only CRA** no specific requirement on the other side in the acts covered

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

- When an incident is severe
  Treat an incident as severe if it harms or could harm the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or if it has introduced or could introduce malicious code into the product or a user's systems.
  [CRA, Article 14(5)](https://grc.plus/regulation/cyber-resilience-act-cra/#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 actively exploited vulnerabilities
  Notify any actively exploited vulnerability you become aware of to the coordinating CSIRT and ENISA at the same time. Send an early warning within 24 hours and a vulnerability notification with general information and mitigations within 72 hours. Send a final report describing the vulnerability, any malicious actor and the fix no later than 14 days after a corrective or mitigating measure is available. The coordinating CSIRT may ask for an intermediate report.
  [CRA, Article 14(1), (2), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Report severe incidents
  Notify any severe incident affecting the product's security to the coordinating CSIRT and ENISA at the same time. Send an early warning within 24 hours stating whether unlawful or malicious acts are suspected, and an incident notification with an initial assessment and mitigations within 72 hours. Send a final report with the root cause and measures within one month of the incident notification. The coordinating CSIRT may ask for an intermediate report.
  [CRA, Article 14(3), (4), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Reporting route
  Submit notifications through ENISA's single reporting platform, using the end-point of the coordinating CSIRT in the Member State of your main establishment. Manufacturers without one follow the order in Article 14(7). You may ask for dissemination of a sensitive notification to be delayed on justified cybersecurity grounds.
  [CRA, Articles 14(7), 16(1), (2)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Voluntary reporting Optional
  Applies to: Manufacturers and any other natural or legal person
  Any person may voluntarily notify a coordinating CSIRT or ENISA of vulnerabilities, cyber threats, incidents and near misses. Doing so creates no additional obligations for the person notifying.
  [CRA, Article 15(1), (2), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#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 CRA** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

- Set and state the support period
  Handle vulnerabilities effectively for a support period that reflects expected use and is at least five years, or the expected use time if shorter. State the end date, at least month and year, clearly at the time of purchase, and notify users when support ends where technically feasible.
  [CRA, Article 13(8), (19)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Product identity, contact point and instructions
  Give the product a type, batch or serial number and show your name and contact details. Designate a single point of contact for users that is not limited to automated tools. Supply the Annex II information and instructions and keep them available for at least 10 years or the support period, whichever is longer.
  [CRA, Article 13(15) to (18)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Cooperate with authorities and announce cessation
  On a reasoned request, give the market surveillance authority the information needed to show conformity and cooperate on measures to remove risks. If you are ceasing operations and cannot comply, inform the authorities and, as far as possible, users before this takes effect.
  [CRA, Article 13(22), (23)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Inform users
  After becoming aware of an actively exploited vulnerability or severe incident, inform impacted users, and where appropriate all users, and tell them about mitigations they can deploy, where appropriate in a structured, machine-readable format.
  [CRA, Article 14(8)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

Nothing in the acts covered.

### Threat intelligence and information sharing

**Only CRA** 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

- Voluntary reporting Optional
  Applies to: Manufacturers and any other natural or legal person
  Any person may voluntarily notify a coordinating CSIRT or ENISA of vulnerabilities, cyber threats, incidents and near misses. Doing so creates no additional obligations for the person notifying.
  [CRA, Article 15(1), (2), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

Nothing in the acts covered.

## Continuity and resilience

### Business continuity and crisis management

**Both cover it** read the wording below

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

- Availability of essential functions
  Where applicable, protect the availability of essential and basic functions, also after an incident, including resilience against denial-of-service attacks. Minimise the product's negative impact on services provided by other devices or networks.
  [CRA, Annex I, Part I, point (2)(h), (i)](https://grc.plus/regulation/cyber-resilience-act-cra/#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)

### Security testing

**Only CRA** 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

- Test, fix and disclose vulnerabilities
  Remediate vulnerabilities without delay, with security updates separate from functional ones where feasible, distributed securely and free of charge unless agreed otherwise for tailor-made products. Test and review security regularly. Enforce a coordinated vulnerability disclosure policy, provide a reporting contact, and publish information on fixed vulnerabilities.
  [CRA, Annex I, Part II, points (2) to (8)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

Nothing in the acts covered.

## Third parties and supply chain

### Supplier and third-party risk

**CRA more detailed** more requirements on this, not necessarily stricter

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

- Third-party components
  Exercise due diligence when integrating third-party components, including open-source ones, so they do not compromise the product. If you find a vulnerability in a component, report it to whoever makes or maintains the component and remediate it, sharing your fix where you developed one.
  [CRA, Article 13(5), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Importer checks
  Applies to: Importers
  Place on the market only products and manufacturer processes that meet Annex I. First ensure the conformity assessment and technical documentation exist, the product has CE marking, EU declaration and instructions, and the identification and support-date duties are met. Show your own contact details on the product, its packaging or an accompanying document.
  [CRA, Article 19(1), (2), (4)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Distributor checks and cooperation
  Applies to: Distributors
  Act with due care. Before making a product available, verify the CE marking and that the manufacturer and importer met their identification, instruction, support-date and declaration duties. Hold back non-conforming products and cooperate with the authority on reasoned request.
  [CRA, Article 20(1), (2), (3), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Software bill of materials
  Identify and document vulnerabilities and components, including a software bill of materials in a commonly used, machine-readable format covering at least the top-level dependencies.
  [CRA, Annex I, Part II, point (1)](https://grc.plus/regulation/cyber-resilience-act-cra/#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)

## Privacy and data protection

### Privacy by design and by default

**Only CRA** no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DP-P

- Minimise data and allow removal
  Where applicable, process only data that is adequate, relevant and limited to the product's purpose. Let users securely and easily remove all data and settings permanently, and make any transfer to other products secure.
  [CRA, Annex I, Part I, point (2)(g), (m)](https://grc.plus/regulation/cyber-resilience-act-cra/#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)

### Cooperation with supervisors

**Only CRA** no specific requirement on the other side in the acts covered

- Cooperate with authorities and announce cessation
  On a reasoned request, give the market surveillance authority the information needed to show conformity and cooperate on measures to remove risks. If you are ceasing operations and cannot comply, inform the authorities and, as far as possible, users before this takes effect.
  [CRA, Article 13(22), (23)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Importer corrective action and alerts
  Applies to: Importers
  Hold back non-conforming products and take corrective measures, withdraw or recall those already placed. Inform the manufacturer of any vulnerability without undue delay, and where a product presents a significant cybersecurity risk, immediately inform the market surveillance authorities.
  [CRA, Article 19(3), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Importer records and cooperation
  Applies to: Importers
  Keep the EU declaration of conformity for at least 10 years after the product is placed on the market, or for the support period if longer, and ensure the technical documentation can be made available on request. Provide information to the authority on reasoned request and cooperate. If the manufacturer has ceased operations, inform the authorities and, where possible, users.
  [CRA, Article 19(6) to (8)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Distributor checks and cooperation
  Applies to: Distributors
  Act with due care. Before making a product available, verify the CE marking and that the manufacturer and importer met their identification, instruction, support-date and declaration duties. Hold back non-conforming products and cooperate with the authority on reasoned request.
  [CRA, Article 20(1), (2), (3), (5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Distributor corrective action and alerts
  Applies to: Distributors
  Make sure corrective measures, withdrawal or recall take place for non-conforming products. Inform the manufacturer of any vulnerability without undue delay. Immediately inform market surveillance authorities of a significant cybersecurity risk. If the manufacturer has ceased operations, inform the authorities without undue delay and, as far as possible, users.
  [CRA, Article 20(4), (6)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Technical documentation
  Draw up technical documentation with at least the Annex VII elements before placing the product on the market and update it as needed, at least during the support period. Keep it and the EU declaration available to the market surveillance authorities for at least 10 years after the product is placed on the market, or for the support period if longer.
  [CRA, Articles 13(13), 31(1), (2)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Fines for misleading information
  Applies to: Economic operators
  Supplying incorrect, incomplete or misleading information to notified bodies and market surveillance authorities in reply to a request carries fines of up to EUR 5 million or 1% of total worldwide annual turnover, whichever is higher.
  [CRA, Article 64(4)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

Nothing in the acts covered.

### Penalties and liability

**CRA more detailed** more requirements on this, not necessarily stricter

- Fines for essential requirements and reporting
  Applies to: Manufacturers
  Breach of Annex I or of Articles 13 and 14 carries fines of up to EUR 15 million or 2.5% of total worldwide annual turnover, whichever is higher. Micro and small enterprises are not fined for missing the 24-hour early warning, and open-source software stewards are not fined for any infringement.
  [CRA, Article 64(2), (10)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Fines for other operator obligations
  Applies to: Economic operators and others subject to the listed articles
  Breach of Articles 18 to 23, 28, 30(1) to (4), 31(1) to (4), 32(1) to (3), 33(5) and certain other listed articles carries fines of up to EUR 10 million or 2% of total worldwide annual turnover, whichever is higher.
  [CRA, Article 64(3)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- Fines for misleading information
  Applies to: Economic operators
  Supplying incorrect, incomplete or misleading information to notified bodies and market surveillance authorities in reply to a request carries fines of up to EUR 5 million or 1% of total worldwide annual turnover, whichever is higher.
  [CRA, Article 64(4)](https://grc.plus/regulation/cyber-resilience-act-cra/#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 CRA](https://grc.plus/compare/cra/)
- [Compare PSD2](https://grc.plus/compare/psd2/)

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