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

# CRA vs NIS2 Spain

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

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

[NIS2 Spain](https://grc.plus/regulation/nis2/spain/)Essential and important entities

## At a Glance

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

- **CRA** Asks more on 0 topics Alone on 3 topics More detailed on 3 topics
- **NIS2 Spain** Asks more on 0 topics Alone on 0 topics More detailed on 1 topic

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

## What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

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

Status

Reviewed against the official texts.

Included

- [NIS2](https://grc.plus/regulation/nis2/) Directive (EU) 2022/2555 Articles 3, 20, 21, 23, 27, 29, 34 · 31 requirements
- [NIS2 Implementing Regulation](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/) Commission Implementing Regulation (EU) 2024/2690 Articles 3 to 14 · Annex · 17 requirements Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

National requirements

None recorded yet, so the Directive is shown as it is. The national law may go further.

Status

Reviewed against the official texts.

## Key Numbers

### Deadline

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

NIS2 Spain: Not in the acts covered

### Threshold

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

NIS2 Spain: Not in the acts covered

### Goes to

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

NIS2 Spain: Not in the acts covered

### Evidence to keep

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

NIS2 Spain: Not in the acts covered

### Incident reports go to

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

NIS2 Spain: CSIRT or competent authority

### First notice of an incident

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

NIS2 Spain: Without undue delay and in any event within 24 hours of becoming aware

### Incident notification

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

NIS2 Spain: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust service providers, for incidents affecting their trust services)

### Intermediate report

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

NIS2 Spain: On request

### Final report

CRA: Within one month of the incident notification

NIS2 Spain: Within one month of the incident notification

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

NIS2 Spain: Not in the acts covered

### Review of the risk framework

CRA: Not in the acts covered

NIS2 Spain: Risk assessment and treatment plan at planned intervals, at least annually, and after significant incidents or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

### Register of third-party arrangements

CRA: Not in the acts covered

NIS2 Spain: Directory of direct suppliers and service providers (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

### Registration with the authority

CRA: Not in the acts covered

NIS2 Spain: Required; changes without delay and in any event within two weeks

### Management body training

CRA: Not in the acts covered

NIS2 Spain: Required

### Management body liability

CRA: Not in the acts covered

NIS2 Spain: Yes, for infringements of Article 21

### 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) Highest stated

NIS2 Spain: Essential entities: maximum of at least EUR 10 million or 2% of the undertaking's total worldwide annual turnover in the preceding financial year, whichever is higher. Important entities: maximum of at least EUR 7 million or 1.4%, whichever is higher.

## Governance

### 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 cybersecurity is affected.
  [CRA, Articles 21, 22](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- Roles, responsibilities and authorities
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Security roles assigned and communicated to the management bodies, at least one person reporting directly to them, conflicting duties segregated where applicable, and the assignment reviewed by the management bodies at planned intervals and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

## Risk management

### Risk assessment

**Both cover it** read the wording below

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

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

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Risk management framework
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

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

- Assessing effectiveness
  Policies and procedures to assess whether the cybersecurity risk-management measures work.
  [NIS2, Article 21(2)(f)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Corrective measures
  An entity that finds it does not comply with the measures takes the necessary corrective measures without undue delay.
  [NIS2, Article 21(4)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Independent review
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Independent reviews of network and information security at planned intervals and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### Asset management

**Both cover it** read the wording below

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

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

- Asset management
  Asset management.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Asset inventory
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A complete, accurate, up-to-date and consistent inventory of assets, with changes recorded in a traceable way.
  [NIS2 Implementing Regulation, Annex, point 12.4](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

## Protection

### Access control

**Both cover it** read the wording below

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

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

- Access control policies
  Access control policies.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Access rights and privileged accounts
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Management of access rights, and stricter controls on privileged and system administration accounts.
  [NIS2 Implementing Regulation, Annex, points 11.2 and 11.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### 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 authentication, identity or access management, and report possible unauthorised access.
  [CRA, Annex I, Part I, point (2)(d)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- Multi-factor authentication
  Multi-factor or continuous authentication solutions, where appropriate.
  [NIS2, Article 21(2)(j)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Multi-factor authentication
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Multi-factor or continuous authentication where appropriate, in line with the classification of the asset accessed.
  [NIS2 Implementing Regulation, Annex, point 11.7](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### Cryptography and encryption

**Both cover it** read the wording below

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

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

- Cryptography
  Policies and procedures on the use of cryptography and, where appropriate, encryption.
  [NIS2, Article 21(2)(h)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

### Data security

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

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

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

Nothing in the acts covered.

### 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 cybersecurity requirements in Annex I, Part I.
  [CRA, Article 13(1)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)
- No known vulnerabilities, secure by default and reduced attack surface
  Where applicable on the basis of the risk assessment, supply the product without known exploitable vulnerabilities and with a secure-by-default configuration that can be reset. Limit attack surfaces and reduce the impact of incidents with exploitation mitigation.
  [CRA, Annex I, Part I, point (2)(a), (b), (j), (k)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- Secure acquisition, development and maintenance
  Security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure.
  [NIS2, Article 21(2)(e)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

### Configuration, change and patch management

**Both cover it** read the wording below

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

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

- Configuration, change and patch management
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Secure configurations, controlled changes, repairs and maintenance, and security patches applied within a reasonable time after release, unless the disadvantages outweigh the cybersecurity benefits and the reasons are documented.
  [NIS2 Implementing Regulation, Annex, points 6.3, 6.4 and 6.6](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

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

- Secure acquisition, development and maintenance
  Security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure.
  [NIS2, Article 21(2)(e)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

## Detection and response

### Monitoring and detection

**Both cover it** read the wording below

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

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

- Monitoring and logging
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Monitoring and logging of network and information systems to detect events that could be incidents.
  [NIS2 Implementing Regulation, Annex, point 3.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### Incident classification

**NIS2 Spain more detailed** more requirements on this, not necessarily stricter

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

- When an incident is severe
  Treat an incident as severe if it harms or could harm the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or if it has introduced or could introduce malicious code into the product or a user's systems.
  [CRA, Article 14(5)](https://grc.plus/regulation/cyber-resilience-act-cra/#requirements)

- When an incident is significant
  An incident is significant when it has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to others.
  [NIS2, Article 23(3)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Event assessment and classification
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Suspicious events are assessed to decide whether they are incidents and, if so, their nature and severity. Recurring incidents under Article 4 are checked quarterly.
  [NIS2 Implementing Regulation, Annex, point 3.4](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive
- When an incident is significant
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Criteria that make an incident significant: general criteria for all these providers (Article 3), recurring incidents (Article 4) and criteria for each kind of provider (Articles 5 to 14).
  [NIS2 Implementing Regulation, Articles 3 to 14](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

### Reporting to authorities

**Both cover it** read the wording below

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

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

- Notify significant incidents
  Notify the CSIRT or competent authority without undue delay of any significant incident, with the information needed to judge any cross-border impact.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Early warning
  An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.
  [NIS2, Article 23(4)(a)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Incident notification
  An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.
  [NIS2, Article 23(4)(b)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Intermediate report
  An intermediate report on status updates, when the CSIRT or authority asks for one.
  [NIS2, Article 23(4)(c)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Final report
  A final report with a detailed description, the likely type of threat or root cause, the applied and ongoing mitigation and any cross-border impact. For an ongoing incident, a progress report at that time and the final report within one month of handling it.
  [NIS2, Article 23(4)(d) and (e)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

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

- Inform affected recipients
  Where appropriate, notify recipients of the services without undue delay of significant incidents likely to affect the provision of those services.
  [NIS2, Article 23(1)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Warn of significant cyber threats
  Where applicable, tell recipients potentially affected by a significant cyber threat, without undue delay, what they can do about it and, where appropriate, about the threat itself.
  [NIS2, Article 23(2)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

### Threat intelligence and information sharing

**Both cover it** read the wording below

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

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

- Information-sharing arrangements Optional
  Entities may exchange cybersecurity information such as threats, vulnerabilities and indicators of compromise within information-sharing arrangements. Essential and important entities notify the competent authority when they join or withdraw.
  [NIS2, Article 29](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

## Continuity and resilience

### Business continuity and crisis management

**Both cover it** read the wording below

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

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

- Business continuity and crisis management
  Business continuity, such as backup management and disaster recovery, and crisis management.
  [NIS2, Article 21(2)(c)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

### Security testing

**Both cover it** read the wording below

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

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

- Security testing
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A policy and procedures for security testing of network and information systems.
  [NIS2 Implementing Regulation, Annex, point 6.5](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive

## Third parties and supply chain

### Supplier and third-party risk

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

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

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

- Supply chain security
  Supply chain security, including the security aspects of the relationship with each direct supplier and service provider.
  [NIS2, Article 21(2)(d)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- What to weigh for each supplier and service provider
  Entities weigh the specific vulnerabilities of each direct supplier and service provider, the quality of their products and cybersecurity practices, including secure development, and the results of EU coordinated risk assessments of critical supply chains.
  [NIS2, Article 21(3)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

## Privacy and data protection

### Privacy by design and by default

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

NIST Privacy Framework CT.DP-P

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

Nothing in the acts covered.

## Supervision and enforcement

### Cooperation with supervisors

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

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

Nothing in the acts covered.

### Penalties and liability

**Both cover it** read the wording below

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

- Management approves and oversees the measures
  The management body approves the cybersecurity risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
  [NIS2, Article 20(1)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Administrative fines
  Infringements of Article 21 or 23 can be fined. Member States set maximums of at least the amounts below, whichever is higher.
  [NIS2, Article 34(4) and (5)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

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. 12 topics where all apply the Directive as it is are not shown.

## More Comparisons

- [Compare CRA](https://grc.plus/compare/cra/)
- [Compare NIS2 Spain](https://grc.plus/compare/nis2-spain/)

Source: https://grc.plus/compare/cra-vs-nis2-spain/
