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

# CER vs CRA

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

[CER](https://grc.plus/regulation/critical-entities-resilience-directive-cer/)Critical entities identified by Member States

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

## At a Glance

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

- **CER** Asks more on 1 topic Alone on 7 topics More detailed on 1 topic
- **CRA** Asks more on 0 topics Alone on 10 topics More detailed on 3 topics

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

## What This Covers

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

Included

- [CER](https://grc.plus/regulation/critical-entities-resilience-directive-cer/) Directive (EU) 2022/2557 of the European Parliament and of the Council of 14 December 2022 Articles 6, 8, 12 to 17, 21, 22 · 29 requirements

Status

Reviewed against the official texts.

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.

## Key Numbers

### Deadline

CER: By 17 July 2026 (Member States); Member State notifies within one month of identification (Member States); Within nine months of receiving the notification; Central authorities reply within 10 working days of receiving the request (Member States); Rules notified to the Commission by 17 October 2024 (Member States)

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

### How often

CER: List reviewed at least every four years (Member States); Whenever necessary, and at least every four years

CRA: Not in the acts covered

### Threshold

CER: Actual or potential significant disruption of essential services; Essential services to or in six or more Member States

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

### Goes to

CER: Competent authority

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

### Evidence to keep

CER: Resilience plan or equivalent documents; Information and evidence on the Article 13 measures (Critical entities that are also entities under Directive (EU) 2022/2555)

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

### Incident reports go to

CER: Competent authority

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

### First notice of an incident

CER: Within 24 hours of becoming aware

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

### Incident notification

CER: Not in the acts covered

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

### Intermediate report

CER: Not in the acts covered

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

### Final report

CER: Within one month of the initial notification, where relevant

CRA: Within one month of the incident notification

### Deadline to have the measures in place

CER: 10 months after the date of the notification (Member States)

CRA: Not in the acts covered

### External assessment or certification

CER: Audit by an independent and qualified auditor, where the authority requires evidence (Critical entities that are also entities under Directive (EU) 2022/2555)

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)

### Maximum fines

CER: Set by each Member State; effective, proportionate and dissuasive (Member States)

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)

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

- Liaison officer
  Designate a liaison officer or equivalent as the point of contact with the competent authorities.
  [CER, Article 13(3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Security policy

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

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

- Resilience plan
  Have in place and apply a resilience plan or equivalent documents that describe the measures taken. Documents and measures produced under other legal acts may be reused where relevant, and the competent authority may declare them compliant in whole or in part.
  [CER, Article 13(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

Nothing in the acts covered.

### Awareness and training

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

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

- Raise staff awareness
  Raise awareness of the resilience measures among relevant personnel, considering training courses, information materials and exercises.
  [CER, Article 13(1)(f)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

Nothing in the acts covered.

## Risk management

### Risk management framework

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

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

- Proportionate measures and incident prevention
  Take appropriate and proportionate technical, security and organisational measures to ensure resilience, based on the Member State risk assessment and the entity's own. The measures include preventing incidents, with due regard to disaster risk reduction and climate adaptation.
  [CER, Article 13(1), opening words and point (a)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Encouraging standards
  Applies to: Member States
  Where useful, and without imposing or favouring a particular technology, Member States encourage the use of European and international standards and technical specifications relevant to the security and resilience measures of critical entities. The article places no duty on the entity itself to use them.
  [CER, Article 16](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

Nothing in the acts covered.

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

- Carry out a critical entity risk assessment
  Carry out a risk assessment within nine months of being notified as a critical entity, then whenever necessary and at least every four years. Assess all relevant risks that could disrupt the provision of the essential services, using the Member State risk assessments and other relevant sources of information.
  [CER, Article 12(1)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- All-hazards scope and dependencies
  Cover all relevant natural and man-made risks, including cross-sectoral and cross-border risks, accidents, natural disasters, public health emergencies, hybrid threats and other antagonistic threats such as terrorist offences. Take into account how other sectors depend on the entity and how it depends on other sectors, including, where relevant, in neighbouring Member States and third countries. Relevant assessments made under other legal acts may be reused, and the competent authority may declare them compliant in whole or in part.
  [CER, Article 12(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Review, audit and improvement

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

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

- Inspections, audits and remedial orders
  Applies to: Competent authorities
  Competent authorities can inspect critical infrastructure and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entities. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
  [CER, Article 21(1) and (3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Provide information and audit evidence
  Applies to: Critical entities that are also entities under Directive (EU) 2022/2555
  Where the competent authority requires it, and within the reasonable time limit it sets, provide the information needed to assess the Article 13 measures and evidence that they are effectively implemented. The evidence includes the results of an audit by an independent and qualified auditor, chosen by the entity and paid for by it.
  [CER, Article 21(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Asset management

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

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

Nothing in the acts covered.

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

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

- Employee security management
  Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructure and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
  [CER, Article 13(1)(e) and second subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Authentication

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

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5

Nothing in the acts covered.

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

### Cryptography and encryption

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

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

Nothing in the acts covered.

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

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

Nothing in the acts covered.

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

### Secure acquisition and development

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

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31

Nothing in the acts covered.

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

### Configuration, change and patch management

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

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

Nothing in the acts covered.

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

### Vulnerability handling

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

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

Nothing in the acts covered.

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

### Human resources security

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

- Employee security management
  Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructure and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
  [CER, Article 13(1)(e) and second subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Request background checks where permitted Optional
  Under conditions set by the Member State and in duly reasoned cases, the entity may request background checks on people in sensitive roles, people with direct or remote access to its premises, information or control systems, and candidates for those positions.
  [CER, Article 14(1)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Limits and content of background checks
  Applies to: Member States
  Checks are proportionate, strictly limited to what is necessary and carried out only to evaluate a potential security risk to the entity. At a minimum they confirm the person's identity and check criminal records for offences relevant to the position. Central authorities answer requests for criminal records held in other Member States within 10 working days.
  [CER, Article 14(2) and (3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

Nothing in the acts covered.

### Physical and environmental security

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

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14

- Physical protection of premises and infrastructure
  Ensure adequate physical protection of premises and critical infrastructure, considering for example fencing, barriers, perimeter monitoring, detection equipment and access controls.
  [CER, Article 13(1)(b)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

Nothing in the acts covered.

## Detection and response

### Monitoring and detection

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

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

Nothing in the acts covered.

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

### Incident handling

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

- Respond to and mitigate incidents
  Respond to, resist and mitigate the consequences of incidents, considering risk and crisis management procedures, protocols and alert routines.
  [CER, Article 13(1)(c)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

Nothing in the acts covered.

### Incident classification

**Both cover it** read the wording below

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

- Judging the significance of a disruption
  Determine significance by taking into account in particular the number and proportion of users affected, the duration of the disruption, and the geographical area affected, including whether it is geographically isolated.
  [CER, Article 15(1)(a) to (c)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Reporting to authorities

**Both cover it** read the wording below

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

- Initial incident notification
  Notify the competent authority without undue delay of incidents that significantly disrupt, or could significantly disrupt, the provision of essential services. Send the initial notification within 24 hours of becoming aware of the incident, unless operationally unable to do so.
  [CER, Article 15(1), first subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Detailed incident report
  Where relevant, follow the initial notification with a detailed report within one month.
  [CER, Article 15(1), first subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Content of the notification
  Include any available information that lets the competent authority understand the nature, cause and possible consequences of the incident, including any cross-border impact. Notifying does not expose the entity to increased liability.
  [CER, Article 15(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#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)
- 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)

### Informing customers and the public

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

NIST CSF 2.0 RS.CO, RC.CO

- Follow-up to the entity and informing the public
  Applies to: Competent authorities and Member States
  After a notification, the competent authority gives the entity relevant follow-up information as soon as possible, including information that could support its response. Member States inform the public where they determine that this is in the public interest.
  [CER, Article 15(4)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#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)
- 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)

### Threat intelligence and information sharing

**CER asks more** binding, where the other is optional

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

- Follow-up to the entity and informing the public
  Applies to: Competent authorities and Member States
  After a notification, the competent authority gives the entity relevant follow-up information as soon as possible, including information that could support its response. Member States inform the public where they determine that this is in the public interest.
  [CER, Article 15(4)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#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)

## Continuity and resilience

### Business continuity and crisis management

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

- Respond to and mitigate incidents
  Respond to, resist and mitigate the consequences of incidents, considering risk and crisis management procedures, protocols and alert routines.
  [CER, Article 13(1)(c)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Recover and resume the essential service
  Recover from incidents and resume the essential service, considering business continuity measures and alternative supply chains.
  [CER, Article 13(1)(d)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Resilience plan
  Have in place and apply a resilience plan or equivalent documents that describe the measures taken. Documents and measures produced under other legal acts may be reused where relevant, and the competent authority may declare them compliant in whole or in part.
  [CER, Article 13(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

### Security testing

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

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

Nothing in the acts covered.

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

## Third parties and supply chain

### Supplier and third-party risk

**Both cover it** read the wording below

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

- All-hazards scope and dependencies
  Cover all relevant natural and man-made risks, including cross-sectoral and cross-border risks, accidents, natural disasters, public health emergencies, hybrid threats and other antagonistic threats such as terrorist offences. Take into account how other sectors depend on the entity and how it depends on other sectors, including, where relevant, in neighbouring Member States and third countries. Relevant assessments made under other legal acts may be reused, and the competent authority may declare them compliant in whole or in part.
  [CER, Article 12(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Recover and resume the essential service
  Recover from incidents and resume the essential service, considering business continuity measures and alternative supply chains.
  [CER, Article 13(1)(d)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Employee security management
  Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructure and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
  [CER, Article 13(1)(e) and second subparagraph](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

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

Nothing in the acts covered.

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

## Supervision and enforcement

### Registration with authorities

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

- Identification of critical entities
  Applies to: Member States
  Each Member State identifies the critical entities in the sectors and subsectors of the Annex by 17 July 2026 and reviews the list at least every four years. An entity qualifies when it provides an essential service, operates on that territory with its critical infrastructure located there, and an incident would significantly disrupt that service or a dependent one.
  [CER, Article 6(1), (2) and (5)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Notification and start of obligations
  Applies to: Member States
  The Member State notifies each critical entity within one month of identifying it and tells it which obligations apply and from when. The resilience obligations in Chapter III apply to the entity from 10 months after the date of that notification.
  [CER, Article 6(3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Carve-out for banking, financial market and digital infrastructure
  Applies to: Member States, for critical entities in banking, financial market infrastructure and digital infrastructure
  Article 11 and Chapters III, IV and VI do not apply to critical entities identified in banking, financial market infrastructure and digital infrastructure (points 3, 4 and 8 of the Annex). Member States may keep or adopt national requirements for a higher level of resilience if they are consistent with Union law.
  [CER, Article 8](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Report services in six or more Member States
  After being notified as a critical entity, tell the competent authority if the entity provides essential services to or in six or more Member States, which services these are and in which Member States.
  [CER, Article 17(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

Nothing in the acts covered.

### Cooperation with supervisors

**Both cover it** read the wording below

- Liaison officer
  Designate a liaison officer or equivalent as the point of contact with the competent authorities.
  [CER, Article 13(3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Report services in six or more Member States
  After being notified as a critical entity, tell the competent authority if the entity provides essential services to or in six or more Member States, which services these are and in which Member States.
  [CER, Article 17(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Inspections, audits and remedial orders
  Applies to: Competent authorities
  Competent authorities can inspect critical infrastructure and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entities. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
  [CER, Article 21(1) and (3)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)
- Provide information and audit evidence
  Applies to: Critical entities that are also entities under Directive (EU) 2022/2555
  Where the competent authority requires it, and within the reasonable time limit it sets, provide the information needed to assess the Article 13 measures and evidence that they are effectively implemented. The evidence includes the results of an audit by an independent and qualified auditor, chosen by the entity and paid for by it.
  [CER, Article 21(2)](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#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)
- 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)

### Penalties and liability

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

- Penalties
  Applies to: Member States
  Member States lay down the penalties for infringements of the national measures and take the steps needed to implement them. The penalties are effective, proportionate and dissuasive. Member States notify the Commission of these provisions by 17 October 2024 and of any later change without delay.
  [CER, Article 22](https://grc.plus/regulation/critical-entities-resilience-directive-cer/#requirements)

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

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

## More Comparisons

- [Compare CER](https://grc.plus/compare/cer/)
- [Compare CRA](https://grc.plus/compare/cra/)

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