CRA vs DORA
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 27 of 35 topics. Each verdict names what it rests on; read the wording before relying on it.
- CRA Asks more on 0 topics Alone on 2 topics More detailed on 4 topics
- DORA Asks more on 1 topic Alone on 13 topics More detailed on 7 topics
| Topic | CRA | DORA | Verdict |
|---|---|---|---|
| Governance | |||
| Management accountability | CRA: – | DORA: 3 | Only DORAno specific requirement on the other side in the acts covered |
| Roles and independence | CRA: 1 | DORA: 1 | Both cover itread the wording below |
| Security policy | CRA: – | DORA: 3 | Only DORAno specific requirement on the other side in the acts covered |
| Awareness and training | CRA: – | DORA: 2 | Only DORAno specific requirement on the other side in the acts covered |
| Risk management | |||
| Risk management framework | CRA: – | DORA: 2 | Only DORAno specific requirement on the other side in the acts covered |
| Risk assessment | CRA: 1 | DORA: 3 | DORA more detailedmore requirements on this, not necessarily stricter |
| Review, audit and improvement | CRA: 5 | DORA: 4 | Both cover itread the wording below |
| Asset management | CRA: 1 | DORA: 3 | DORA more detailedmore requirements on this, not necessarily stricter |
| Protection | |||
| Access control | CRA: 1 | DORA: 3 | DORA more detailedmore requirements on this, not necessarily stricter |
| Authentication | CRA: 1 | DORA: 2 | Both cover itread the wording below |
| Cryptography and encryption | CRA: 1 | DORA: 2 | Both cover itread the wording below |
| Data security | CRA: 2 | DORA: 3 | Both cover itread the wording below |
| Network security | CRA: – | DORA: 3 | Only DORAno specific requirement on the other side in the acts covered |
| Secure acquisition and development | CRA: 2 | DORA: 2 | Both cover itread the wording below |
| Configuration, change and patch management | CRA: 2 | DORA: 5 | DORA more detailedmore requirements on this, not necessarily stricter |
| Vulnerability handling | CRA: 7 | DORA: 3 | CRA more detailedmore requirements on this, not necessarily stricter |
| Human resources security | CRA: – | DORA: 1 | Only DORAno specific requirement on the other side in the acts covered |
| Physical and environmental security | CRA: – | DORA: 1 | Only DORAno specific requirement on the other side in the acts covered |
| Detection and response | |||
| Monitoring and detection | CRA: 1 | DORA: 3 | DORA more detailedmore requirements on this, not necessarily stricter |
| Incident handling | CRA: – | DORA: 3 | Only DORAno specific requirement on the other side in the acts covered |
| Incident classification | CRA: 1 | DORA: 1 | Both cover itread the wording below |
| Reporting to authorities | CRA: 4 | DORA: 5 | Both cover itread the wording below |
| Informing customers and the public | CRA: 4 | DORA: 2 | CRA more detailedmore requirements on this, not necessarily stricter |
| Threat intelligence and information sharing | CRA: 1 | DORA: 2 | DORA asks morebinding, where the other is optional |
| Continuity and resilience | |||
| Business continuity and crisis management | CRA: 1 | DORA: 3 | DORA more detailedmore requirements on this, not necessarily stricter |
| Backup and recovery | CRA: – | DORA: 1 | Only DORAno specific requirement on the other side in the acts covered |
| Security testing | CRA: 1 | DORA: 3 | DORA more detailedmore requirements on this, not necessarily stricter |
| Threat-led penetration testing | CRA: – | DORA: 1 | Only DORAno specific requirement on the other side in the acts covered |
| Third parties and supply chain | |||
| Supplier and third-party risk | CRA: 4 | DORA: 2 | CRA more detailedmore requirements on this, not necessarily stricter |
| Contract requirements | CRA: – | DORA: 2 | Only DORAno specific requirement on the other side in the acts covered |
| Register of third-party arrangements | CRA: – | DORA: 1 | Only DORAno specific requirement on the other side in the acts covered |
| Exit and termination | CRA: – | DORA: 1 | Only DORAno specific requirement on the other side in the acts covered |
| Privacy and data protection | |||
| Privacy by design and by default | CRA: 1 | DORA: – | Only CRAno specific requirement on the other side in the acts covered |
| Supervision and enforcement | |||
| Cooperation with supervisors | CRA: 7 | DORA: – | Only CRAno specific requirement on the other side in the acts covered |
| Penalties and liability | CRA: 3 | DORA: 1 | CRA more detailedmore 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 Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024
- CRA 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)
- Kamerstuk 36875 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)
- S.L. 591.06 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
Status
Reviewed against the official texts.
Included
- DORA Regulation (EU) 2022/2554
- DORA ICT Risk Management RTS Commission Delegated Regulation (EU) 2024/1774 Applies to: Financial entities, except those on the simplified framework
- JC 2024 34 Joint Guidelines on the estimation of aggregated annual costs and losses caused by major ICT-related incidents under Regulation (EU) 2022/2554, JC 2024 34 (Final Report of 17 July 2024), issued under Article 11(11) of Regulation (EU) 2022/2554
Not yet included
- DORA Third-Party Policy RTS
- DORA Subcontracting RTS
- DORA Register of Information ITS
- DORA Incident Classification RTS
- DORA Incident Reporting RTS
- DORA Incident Reporting ITS
- DORA TLPT RTS
- DORA Critical Provider Criteria
- DORA Oversight Conditions RTS
Status
Reviewed against the official texts.
Key Numbers
Deadline
CRA: Final report within 14 days of a corrective or mitigating measure being available
DORA: Not in the acts covered
Threshold
CRA: Harm to protection of sensitive or important data or functions, or malicious code
DORA: Not in the acts covered
Goes to
CRA: Manufacturer and market surveillance authorities (Importers); Manufacturer and market surveillance authorities (Distributors)
DORA: Not in the acts covered
Evidence to keep
CRA: Documented risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. in the technical documentation; EU declaration of conformity, at least 10 years or the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer (Importers); Technical documentation and EU declaration, at least 10 years or the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer; Software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies.
DORA: Not in the acts covered
Incident reports go to
CRA: Coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity, via the single reporting platform; Coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity, via the single reporting platform; Coordinating CSIRTComputer Security Incident Response Team of the main establishment and ENISAEuropean Union Agency for Cybersecurity
DORA: Financial supervisor (competent authority)
First notice of an incident
CRA: Within 24 hours of becoming aware; Within 24 hours of becoming aware
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
Incident notification
CRA: Within 72 hours of becoming aware; Within 72 hours of becoming aware
DORA: Not in the acts covered
Intermediate report
CRA: On request of the coordinating CSIRTComputer Security Incident Response Team; On request of the coordinating CSIRTComputer Security Incident Response Team
DORA: Within 72 hours of the initial notification
Final report
CRA: Within one month of the incident notification
DORA: Within one month of the latest intermediate report
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)
DORA: Not in the acts covered
Review of the risk framework
CRA: Not in the acts covered
DORA: At least once a year (periodically for microenterprisesMicroenterprise Under DORA), and after major incidents
Testing of critical systems
CRA: Not in the acts covered
DORA: At least yearly, for systems supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions.
Threat-led penetration testing
CRA: Not in the acts covered
DORA: At least every 3 years, for entities the authority identifies; the authority may request a lower or higher frequency
Register of third-party arrangements
CRA: Not in the acts covered
DORA: Required, for every ICTInformation and Communication Technology service arrangement
Management body training
CRA: Not in the acts covered
DORA: Required, on a regular basis
Management body liability
CRA: Not in the acts covered
DORA: Ultimate responsibility for ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment.; penalties on members are subject to national law (Article 50(5))
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)
DORA: Set by each Member State (Competent authorities and Member States)
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
Nothing in the acts covered.
Management body responsibility
The management body defines, approves, oversees and is responsible for implementing every arrangement of the ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework, and bears ultimate responsibility for managing ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment..
Budget for resilience
The management body allocates and reviews the budget for digital operational resilienceThe ability of a financial entity to build, assure and review its operational integrity and reliability by securing all the ICT capabilities it needs, directly or through ICT third-party service providers, so that it can keep providing financial services, including during disruptions. It is the overall goal of DORA., including awareness programmes, training and ICTInformation and Communication Technology skills for all staff.
Governance (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
Governance and organisation of the simplified ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework.
Roles and independence
Both cover it read the wording below
NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3
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 cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. is affected.
Independent control function
A control function with appropriate independence manages and oversees ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. (not required of microenterprisesMicroenterprise Under DORA). Risk management, control and internal audit functions are kept appropriately segregated and independent.
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
Nothing in the acts covered.
Information security policy
A documented information security policy with requirements to protect the availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable., authenticity, integrity and confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of data and assets, including customers' where applicable.
ICT security policies
Applies to: Financial entities, except those on the simplified framework
ICTInformation and Communication Technology security policies, procedures, protocols and tools, with their general elements, approved and reviewed as part of the framework.
Information security policy (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
An information securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. policy and measures.
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
Nothing in the acts covered.
Management body training
Members of the management body keep their knowledge and skills on ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. up to date, including by following specific training regularly.
Staff awareness and training
ICTInformation and Communication Technology security awareness programmes and digital operational resilienceThe ability of a financial entity to build, assure and review its operational integrity and reliability by securing all the ICT capabilities it needs, directly or through ICT third-party service providers, so that it can keep providing financial services, including during disruptions. It is the overall goal of DORA. training are compulsory for all employees and senior management.
Risk management
Risk management framework
Only DORA 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.
ICT risk management framework
A sound, comprehensive and well-documented ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework within the overall risk management system, with the strategies, policies, procedures, protocols and tools to protect all information and ICTInformation and Communication Technology assets.
Simplified ICT risk management framework
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
Small and non-interconnected investment firms, exempted payment and e-moneyElectronic Money institutions, small occupational pension funds, and institutions exempted under Directive 2013/36/EU that their Member State has not excluded under Article 2(4) follow a simplified framework instead of Articles 5 to 15.
Risk assessment
DORA more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2
Cybersecurity risk assessment
Assess the product's cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risks and use the result across planning, design, development, production, delivery and maintenance. Document it, update it during the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years., base it on intended and foreseeable use, and include it in the technical documentation with a justification for any requirement that does not apply.
Identify ICT risk
Identify all sources of ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. continuously, assess cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. and vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., and review risk scenarios at least yearly.
ICT risk management policy
Applies to: Financial entities, except those on the simplified framework
A policy and procedures for ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management: risk toleranceAn organisation's or other actor's readiness to bear a risk in order to achieve its objectives. Risk tolerance can be shaped by legal or regulatory requirements and changes with context, so frameworks ask organisations to state it rather than prescribing it., identification, assessment and treatment of risks, and the monitoring of residual riskThe risk that remains after risk treatment has been applied. The NIST AI RMF notes that residual risk directly affects end users and affected communities, and asks system providers to document it so users understand the possible negative impacts..
ICT risk management (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
Identification and management of ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment..
Review, audit and improvement
Both cover it read the wording below
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.
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.
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 periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years.. 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 periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer.
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 schemeA comprehensive set of requirements, technical requirements, standards and procedures set at EU level for the certification or conformity assessment of specific ICT products, services or processes. Schemes are adopted under the Cybersecurity Act, and NIS2 and the CRA can require their use. where available and applicable.
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.
Yearly review of the framework
The framework is documented and reviewed at least once a year (periodically for microenterprisesMicroenterprise Under DORA), after major ICT-related incidentsAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. and following supervisory instructions or conclusions from testing or audits, and improved continuously.
Internal audit
Auditors with sufficient ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. expertise audit the framework regularly, in line with the audit plan. Not required of microenterprisesMicroenterprise Under DORA.
Report on the framework review
Applies to: Financial entities, except those on the simplified framework
The format and content of the report on the review of the ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework.
Framework review report (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
The format and content of the report on the review of the simplified framework.
Asset management
DORA more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13
Software bill of materials
Identify and document vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and components, including a software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies. in a commonly used, machine-readable format covering at least the top-level dependencies.
Identify and classify assets
Identify, classify and document all ICTInformation and Communication Technology-supported business functions, information and ICTInformation and Communication Technology assets and their dependencies, and review the classification at least yearly.
ICT asset management
Applies to: Financial entities, except those on the simplified framework
An ICTInformation and Communication Technology asset managementAsset Management in Information Security policy and procedure, including an inventory of assets and their criticality.
Asset classification (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
Classification of information assets and ICTInformation and Communication Technology assets.
Protection
Access control
DORA more detailed more requirements on this, not necessarily stricter
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 authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence., identity or access management, and report possible unauthorised access.
Limit access
Limit physical and logical access to what legitimate and approved functions need, with policies, procedures and controls for access rights.
Identity management and access control
Applies to: Financial entities, except those on the simplified framework
Identity management and access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies, including authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence..
Access control (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
Access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements..
Authentication
Both cover it read the wording below
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 authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence., identity or access management, and report possible unauthorised access.
Strong authentication and key protection
Strong authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. based on relevant standards, and protection of cryptographic keys, with encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. decided by data classification and risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..
Identity management and access control
Applies to: Financial entities, except those on the simplified framework
Identity management and access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies, including authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence..
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 confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of stored, transmitted or processed data, such as by state-of-the-art encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. at rest and in transit. Protect data, commands, programs and configuration against unauthorised change, and report corruption.
Strong authentication and key protection
Strong authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. based on relevant standards, and protection of cryptographic keys, with encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. decided by data classification and risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change..
Encryption and key management
Applies to: Financial entities, except those on the simplified framework
EncryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. and cryptographic controls, and the management of cryptographic keys through their whole life cycle.
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 confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of stored, transmitted or processed data, such as by state-of-the-art encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. at rest and in transit. Protect data, commands, programs and configuration against unauthorised change, and report corruption.
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.
Protect data
Policies, protocols and tools that keep data available, authentic, intact and confidential at rest, in use and in transit.
ICT operations and data security
Applies to: Financial entities, except those on the simplified framework
Policies and procedures for ICTInformation and Communication Technology operations, capacity and performance management, and data and system security.
Operations, data and network security (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
ICTInformation and Communication Technology operations security, and data, system and network security.
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
Nothing in the acts covered.
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.
Network security
Applies to: Financial entities, except those on the simplified framework
Network security management and the protection of information in transit.
Operations, data and network security (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
ICTInformation and Communication Technology operations security, and data, system and network security.
Secure acquisition and development
Both cover it read the wording below
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 cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. requirements in Annex I, Part I.
No known vulnerabilities, secure by default and reduced attack surface
Where applicable on the basis of the risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change., supply the product without known exploitable vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and with a secure-by-default configuration that can be reset. Limit attack surfaces and reduce the impact of incidents with exploitation mitigation.
Projects, acquisition and development
Applies to: Financial entities, except those on the simplified framework
ICTInformation and Communication Technology project management, and the acquisition, development and maintenance of ICTInformation and Communication Technology systems.
Development and change (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
ICTInformation and Communication Technology systems acquisition, development and maintenance, and ICTInformation and Communication Technology project and change management.
Configuration, change and patch management
DORA more detailed more requirements on this, not necessarily stricter
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 periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. available for at least 10 years after it is issued, or for the rest of the support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer.
Test, fix and disclose vulnerabilities
Remediate vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. 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 disclosureA process in which someone who discovers a security weakness reports it to the system owner or product supplier and works with them to address it. The parties coordinate investigation, a fix and the timing and content of any public disclosure, reducing the chance of exposing users before protection is available. A national cybersecurity centre may help coordinate when several parties are involved or contact fails. policy, provide a reporting contact, and publish information on fixed vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition..
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.
Patches and updates
Documented policies for patches and updates.
Vulnerability and patch management
Applies to: Financial entities, except those on the simplified framework
Procedures to identify and fix vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and to apply patches and updates.
ICT change management
Applies to: Financial entities, except those on the simplified framework
ICTInformation and Communication Technology change management procedures.
Development and change (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
ICTInformation and Communication Technology systems acquisition, development and maintenance, and ICTInformation and Communication Technology project and change management.
Vulnerability handling
CRA more detailed more requirements on this, not necessarily stricter
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 vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. in a component, report it to whoever makes or maintains the component and remediate it, sharing your fix where you developed one.
Set and state the support period
Handle vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. effectively for a support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. 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.
Report actively exploited vulnerabilities
Notify any actively exploited vulnerabilityA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. you become aware of to the coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity at the same time. Send an early warning within 24 hours and a vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. notification with general information and mitigations within 72 hours. Send a final report describing the vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., any malicious actor and the fix no later than 14 days after a corrective or mitigating measure is available. The coordinating CSIRTComputer Security Incident Response Team may ask for an intermediate report.
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 vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. without undue delay, and where a product presents a significant cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk, immediately inform the market surveillance authorities.
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 vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. without undue delay. Immediately inform market surveillance authorities of a significant cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk. If the manufacturer has ceased operations, inform the authorities without undue delay and, as far as possible, users.
Software bill of materials
Identify and document vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and components, including a software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies. in a commonly used, machine-readable format covering at least the top-level dependencies.
Test, fix and disclose vulnerabilities
Remediate vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. 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 disclosureA process in which someone who discovers a security weakness reports it to the system owner or product supplier and works with them to address it. The parties coordinate investigation, a fix and the timing and content of any public disclosure, reducing the chance of exposing users before protection is available. A national cybersecurity centre may help coordinate when several parties are involved or contact fails. policy, provide a reporting contact, and publish information on fixed vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition..
Patches and updates
Documented policies for patches and updates.
Tests to run
Appropriate tests such as vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.
Vulnerability and patch management
Applies to: Financial entities, except those on the simplified framework
Procedures to identify and fix vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and to apply patches and updates.
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
Nothing in the acts covered.
Human resources policy
Applies to: Financial entities, except those on the simplified framework
A human resources policy covering ICTInformation and Communication Technology security.
Physical and environmental security
Only DORA no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14
Nothing in the acts covered.
Physical and environmental security
Applies to: Financial entities, except those on the simplified framework
A physical and environmental security policy.
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
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-outAn opt-out is a way for a person to refuse an activity or stop further participation. In direct marketing, it means taking a step such as unsubscribing from messages. In a default-on arrangement, the activity proceeds unless the person refuses. Having an opt-out does not establish valid consent where the applicable law requires a positive agreement beforehand..
Detect anomalous activity
Mechanisms to detect anomalous activity promptly, with several layers of control, alert thresholds and automatic alerts, tested regularly.
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.
Incident management and detection
Applies to: Financial entities, except those on the simplified framework
An ICT-related incidentA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. management policy, and criteria to detect anomalous activity and trigger incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state..
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
Nothing in the acts covered.
Post-incident reviews
A review after a major ICT-related incidentAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. disrupts core activities, to find the causes and the improvements needed.
Incident management process
A process to detect, manage and notify ICT-related incidentsA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident.: record all incidents and significant cyber threatsA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident., assign roles, escalate, and find and fix root causes.
Incident management and detection
Applies to: Financial entities, except those on the simplified framework
An ICT-related incidentA single event or series of linked events, not planned by the financial entity, that compromises the security of network and information systems and adversely affects the availability, authenticity, integrity or confidentiality of data or the entity's services. DORA requires financial entities to record and classify every such incident. management policy, and criteria to detect anomalous activity and trigger incident responseThe coordinated work an organisation carries out to deal with a cybersecurity incident and limit its consequences. An incident is an event that compromises, or threatens to compromise, the security of systems or information. Response can include investigating what happened, containing the problem, removing its cause and restoring affected services. It helps reduce damage and return operations to a controlled state..
Incident classification
Both cover it read the wording below
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 availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable., authenticity, integrity or confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. of sensitive or important data or functions, or if it has introduced or could introduce malicious code into the product or a user's systems.
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.
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 vulnerabilityA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. you become aware of to the coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity at the same time. Send an early warning within 24 hours and a vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. notification with general information and mitigations within 72 hours. Send a final report describing the vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., any malicious actor and the fix no later than 14 days after a corrective or mitigating measure is available. The coordinating CSIRTComputer Security Incident Response Team may ask for an intermediate report.
Report severe incidents
Notify any severe incident affecting the product's security to the coordinating CSIRTComputer Security Incident Response Team and ENISAEuropean Union Agency for Cybersecurity 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 CSIRTComputer Security Incident Response Team may ask for an intermediate report.
Reporting route
Submit notifications through ENISAEuropean Union Agency for Cybersecurity's single reporting platform, using the end-point of the coordinating CSIRTComputer Security Incident Response Team 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 cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. grounds.
Voluntary reporting Optional
Applies to: Manufacturers and any other natural or legal person
Any person may voluntarily notify a coordinating CSIRTComputer Security Incident Response Team or ENISAEuropean Union Agency for Cybersecurity of vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition., incidents and near missesAn event that could have compromised the availability, authenticity, integrity or confidentiality of data or of services offered by network and information systems, but was prevented or did not materialise. NIS2 allows voluntary reporting of near misses, and the CRA uses the same definition.. Doing so creates no additional obligations for the person notifying.
Report major incidents
Report major ICT-related incidentsAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. to the competent authority, using the common templates.
Initial notification
An initial notification once the incident is classified as major.
DORA, Article 19(4)(a); Delegated Regulation (EU) 2025/301, Article 5
Intermediate report
An intermediate report, updated when regular activities have been recovered.
DORA, Article 19(4)(b); Delegated Regulation (EU) 2025/301, Article 5
Final report
A final report once the root cause analysisA structured investigation into the underlying causes of a problem or incident, rather than only its visible effects. For an IT incident, it examines how technical failures, working practices or other conditions combined to cause the disruption. The findings help an organisation choose corrective measures that address those causes and reduce the chance of recurrence. is complete, whether or not mitigation is in place, and actual impact figures are available to replace estimates.
DORA, Article 19(4)(c); Delegated Regulation (EU) 2025/301, Article 5
Voluntary notice of cyber threats Optional
Significant cyber threatsA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident. may be notified to the competent authority.
Informing customers and the public
CRA more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 RS.CO, RC.CO
Set and state the support period
Handle vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. effectively for a support periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. 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.
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 periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years., whichever is longer.
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.
Inform users
After becoming aware of an actively exploited vulnerabilityA vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. Under the CRA, manufacturers must send an early warning within 24 hours of becoming aware of one in their product, through the single reporting platform. 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.
Crisis communication
Crisis communication plans to disclose major incidents or vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. to clients, counterparts and the public, and a person in charge of public and media communication.
Inform affected clients
When a major incident affects clients' financial interests, inform them without undue delay of the incident and the measures taken.
Threat intelligence and information sharing
DORA asks more binding, where the other is optional
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 CSIRTComputer Security Incident Response Team or ENISAEuropean Union Agency for Cybersecurity of vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition., incidents and near missesAn event that could have compromised the availability, authenticity, integrity or confidentiality of data or of services offered by network and information systems, but was prevented or did not materialise. NIS2 allows voluntary reporting of near misses, and the CRA uses the same definition.. Doing so creates no additional obligations for the person notifying.
Threat and vulnerability intelligence
Capabilities and staff to gather information on vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition., cyber threatsAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. and incidents and to analyse their likely impact.
Information-sharing arrangements Optional
Financial entities may exchange cyber threatAny potential circumstance, event or action that could damage, disrupt or otherwise harm network and information systems, their users or other persons. NIS2, DORA, the CRA, the Network Code on Cybersecurity and the Cyber Solidarity Act all use this Cybersecurity Act definition. information within trusted communities, under arrangements that protect confidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. and personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity.. They must tell the competent authority when they join or leave.
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
Availability of essential functions
Where applicable, protect the availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable. 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.
ICT business continuity
An ICTInformation and Communication Technology business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. policy, response and recovery plans that are tested at least yearly and after substantive changes to systems supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions., and a business impact analysisThe process of analysing operational functions and the effect a disruption might have on them. Its results inform recovery priorities in continuity planning..
ICT business continuity
Applies to: Financial entities, except those on the simplified framework
The components of the ICTInformation and Communication Technology business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. policy, the testing of continuity plans, and ICTInformation and Communication Technology response and recovery plans.
Business continuity (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
An ICTInformation and Communication Technology business continuity planThe documented, predetermined instructions or procedures that keep an organisation's core operations running during and after a significant disruption. DORA, for example, requires financial entities to have an ICT business continuity policy. and its testing.
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
Nothing in the acts covered.
Backup and restoration
BackupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. policies setting scope and minimum frequency, restoration on own systems segregated from the source, periodic testing, and redundant ICTInformation and Communication Technology capacity (microenterprisesMicroenterprise Under DORA assess the need based on their risk profile).
Security testing
DORA more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34
Test, fix and disclose vulnerabilities
Remediate vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. 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 disclosureA process in which someone who discovers a security weakness reports it to the system owner or product supplier and works with them to address it. The parties coordinate investigation, a fix and the timing and content of any public disclosure, reducing the chance of exposing users before protection is available. A national cybersecurity centre may help coordinate when several parties are involved or contact fails. policy, provide a reporting contact, and publish information on fixed vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition..
Resilience testing programme
A risk-based testing programme run by independent testers, with all ICTInformation and Communication Technology systems and applications supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions. tested at least yearly. Not required of microenterprisesMicroenterprise Under DORA.
Tests to run
Appropriate tests such as vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. assessments and scans, network security assessments, source code reviews where feasible, scenario-based tests and penetration tests.
Security testing (simplified)
Applies to: Entities on the simplified framework (DORADigital Operational Resilience Act Article 16)
ICTInformation and Communication Technology security testing.
Threat-led penetration testing
Only DORA no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.IM
Nothing in the acts covered.
Threat-led penetration testing
Entities identified by the competent authority, other than microenterprisesMicroenterprise Under DORA and Article 16(1) entities, run threat-led penetration tests on live production systems. Details are in Delegated Regulation (EU) 2025/1190.
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 vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. in a component, report it to whoever makes or maintains the component and remediate it, sharing your fix where you developed one.
Importer checks
Applies to: Importers
Place on the market only products and manufacturer processes that meet Annex I. First ensure the conformity assessmentThe process of verifying whether a product, service or system meets the requirements set by the applicable EU act, for example the essential cybersecurity requirements of the CRA or the high-risk requirements of the AI Act. Depending on the risk class, the manufacturer does it alone or with a notified body. and technical documentation exist, the product has CE markingA marking by which a manufacturer or provider indicates that a product conforms to the applicable EU harmonisation legislation. Under the AI Act, high-risk AI systems must bear the CE marking, and the same mechanism applies under other product laws., 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.
Distributor checks and cooperation
Applies to: Distributors
Act with due care. Before making a product available, verify the CE markingA marking by which a manufacturer or provider indicates that a product conforms to the applicable EU harmonisation legislation. Under the AI Act, high-risk AI systems must bear the CE marking, and the same mechanism applies under other product laws. 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.
Software bill of materials
Identify and document vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and components, including a software bill of materialsA formal record of the details and supply chain relationships of the components included in the software of a product. Under the CRA, manufacturers must draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies. in a commonly used, machine-readable format covering at least the top-level dependencies.
Manage ICT third-party risk
ICT third-party riskIn the Digital Operational Resilience Act context, the technology risk a financial organisation faces when it uses Information and Communication Technology services supplied by another organisation or that supplier's subcontractors. This concerns the organisation's dependence on externally provided technology, including outsourced services. Managing it involves assessing suppliers, documenting service arrangements, setting suitable contract terms, monitoring risks and planning how to leave an arrangement while keeping services running. is managed within the ICT riskUnder DORA, any reasonably identifiable circumstance in the use of network and information systems that, if it materialises, could compromise their security, technology-dependent tools or processes, operations or the provision of services, with adverse effects in the digital or physical environment. management framework, and the entity stays fully responsible for compliance.
Third-party risk strategy
A regularly reviewed strategy on ICT third-party riskIn the Digital Operational Resilience Act context, the technology risk a financial organisation faces when it uses Information and Communication Technology services supplied by another organisation or that supplier's subcontractors. This concerns the organisation's dependence on externally provided technology, including outsourced services. Managing it involves assessing suppliers, documenting service arrangements, setting suitable contract terms, monitoring risks and planning how to leave an arrangement while keeping services running., with a policy on ICTInformation and Communication Technology services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions.. The management body regularly reviews the risks from those arrangements. Not required of microenterprisesMicroenterprise Under DORA or Article 16 entities.
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
Nothing in the acts covered.
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.
Terms for critical or important functions
Contracts for services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions. add full service level descriptions, notice periods, business contingency plans, participation in TLPTThreat-Led Penetration Testing, unrestricted rights of access, inspection and audit (microenterprisesMicroenterprise Under DORA may agree to delegate these to an independent third party), and exit strategies with a transition period.
Register of third-party arrangements
Only DORA no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.SC
Nothing in the acts covered.
Register of information
A register of all contractual arrangements for ICTInformation and Communication Technology services, at entity, sub-consolidated and consolidated level, given to the competent authority on request, with a report at least yearly on new arrangements and timely notice of planned arrangements supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions..
Exit and termination
Only DORA no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.SC
Nothing in the acts covered.
Exit strategies
Exit strategies for ICTInformation and Communication Technology services supporting critical or important functionsA function whose disruption would materially impair a financial entity's financial performance, the soundness or continuity of its services, or its ongoing compliance with its authorisation and financial services law. Many DORA requirements, such as contract terms and testing, are stricter for these functions., covering provider failure, falling quality and business disruption.
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.
Nothing in the acts covered.
Supervision and enforcement
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.
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 vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. without undue delay, and where a product presents a significant cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk, immediately inform the market surveillance authorities.
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 periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. 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.
Distributor checks and cooperation
Applies to: Distributors
Act with due care. Before making a product available, verify the CE markingA marking by which a manufacturer or provider indicates that a product conforms to the applicable EU harmonisation legislation. Under the AI Act, high-risk AI systems must bear the CE marking, and the same mechanism applies under other product laws. 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.
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 vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. without undue delay. Immediately inform market surveillance authorities of a significant cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk. If the manufacturer has ceased operations, inform the authorities without undue delay and, as far as possible, users.
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 periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years.. 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 periodThe period during which a manufacturer must ensure that vulnerabilities of a product with digital elements are handled effectively and in line with the CRA vulnerability handling requirements. It must reflect the expected time of use and is generally at least five years. if longer.
Fines for misleading information
Applies to: Economic operators
Supplying incorrect, incomplete or misleading information to notified bodiesA conformity assessment body that a Member State has notified to the Commission as competent to carry out third-party assessment under EU legislation. Whether a manufacturer or provider must involve one depends on the applicable act, system or product classification and conformity assessment route; not every high-risk AI system requires a notified body. 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.
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 stewardsA legal person, other than a manufacturer, that systematically provides sustained support for the development of free and open-source software intended for commercial activities and ensures its viability, such as a foundation. The CRA gives stewards a lighter regime instead of full manufacturer obligations. are not fined for any infringement.
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.
Fines for misleading information
Applies to: Economic operators
Supplying incorrect, incomplete or misleading information to notified bodiesA conformity assessment body that a Member State has notified to the Commission as competent to carry out third-party assessment under EU legislation. Whether a manufacturer or provider must involve one depends on the applicable act, system or product classification and conformity assessment route; not every high-risk AI system requires a notified body. 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.
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.
Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.