> CER vs GDPR 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.

# CER vs GDPR Spain

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

[GDPR Spain](https://grc.plus/regulation/general-data-protection-regulation-gdpr/spain/)Controllers and processors

## At a Glance

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

- **CER** Asks more on 0 topics Alone on 9 topics More detailed on 2 topics
- **GDPR Spain** Asks more on 0 topics Alone on 0 topics More detailed on 0 topics

| Topic | CER | GDPR Spain | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Roles and independence | CER: 1 | GDPR Spain: 2 | **Both cover it**read the wording below |
| Security policy | CER: 1 | GDPR Spain: – | **Only CER**no specific requirement on the other side in the acts covered |
| Awareness and training | CER: 1 | GDPR Spain: – | **Only CER**no specific requirement on the other side in the acts covered |
| Risk management |  |  |  |
| Risk management framework | CER: 2 | GDPR Spain: 1 | **Both cover it**read the wording below |
| Risk assessment | CER: 2 | GDPR Spain: 1 | **Both cover it**read the wording below |
| Review, audit and improvement | CER: 2 | GDPR Spain: – | **Only CER**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | CER: 1 | GDPR Spain: – | **Only CER**no specific requirement on the other side in the acts covered |
| Human resources security | CER: 3 | GDPR Spain: 1 | **CER more detailed**more requirements on this, not necessarily stricter |
| Physical and environmental security | CER: 1 | GDPR Spain: – | **Only CER**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Incident handling | CER: 1 | GDPR Spain: 1 | **Both cover it**read the wording below |
| Incident classification | CER: 1 | GDPR Spain: – | **Only CER**no specific requirement on the other side in the acts covered |
| Reporting to authorities | CER: 3 | GDPR Spain: 3 | **Both cover it**read the wording below |
| Informing customers and the public | CER: 1 | GDPR Spain: 1 | **Both cover it**read the wording below |
| Threat intelligence and information sharing | CER: 1 | GDPR Spain: – | **Only CER**no specific requirement on the other side in the acts covered |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | CER: 3 | GDPR Spain: – | **Only CER**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | CER: 3 | GDPR Spain: 2 | **Both cover it**read the wording below |
| Supervision and enforcement |  |  |  |
| Registration with authorities | CER: 4 | GDPR Spain: – | **Only CER**no specific requirement on the other side in the acts covered |
| Cooperation with supervisors | CER: 4 | GDPR Spain: 1 | **CER more detailed**more requirements on this, not necessarily stricter |
| Penalties and liability | CER: 1 | GDPR 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

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

- [GDPR](https://grc.plus/regulation/general-data-protection-regulation-gdpr/) Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

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

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)

GDPR Spain: At the time the data are obtained (Controllers); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (Controllers); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (Controllers); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (Controllers); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (Controllers)

### How often

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

GDPR Spain: 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

GDPR Spain: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)

### Goes to

CER: Competent authority

GDPR Spain: Controller (Processors); Data subjects (Controllers)

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

GDPR Spain: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (Controllers)

### Incident reports go to

CER: Competent authority

GDPR Spain: Competent supervisory authority (Controllers)

### First notice of an incident

CER: Within 24 hours of becoming aware Shortest stated

GDPR Spain: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

### Intermediate report

CER: Not in the acts covered

GDPR Spain: In phases, without undue further delay (Controllers)

### Final report

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

GDPR Spain: Not in the acts covered

### Deadline to have the measures in place

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

GDPR Spain: 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)

GDPR Spain: Approved code of conduct or certification may help show compliance (Controllers)

### Review of the risk framework

CER: Not in the acts covered

GDPR Spain: Where necessary (Controllers)

### Testing of critical systems

CER: Not in the acts covered

GDPR Spain: Regularly

### Maximum fines

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

GDPR Spain: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, 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

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

- Joint controllers
  Applies to: Joint controllers
  Joint controllers set out their respective responsibilities in an arrangement, unless EU or Member State law determines them, including who handles rights requests and information duties, and make its essence available to people. A person may exercise their rights against any of them regardless of the arrangement.
  [GDPR, Article 26](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- EU representative
  Applies to: Controllers and processors not established in the EU, under Article 3(2)
  A controller or processor outside the EU that falls under Article 3(2) designates a representative in writing, established in a Member State where the affected people are. Occasional low-risk processing without large-scale special category or criminal data, and public bodies, are exempt.
  [GDPR, Article 27](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

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

**Both cover it** read the wording below

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)

- Measures to ensure and show compliance
  Applies to: Controllers
  Put in place technical and organisational measures suited to the risks of the processing, so that it complies and the controller can show it does. Review and update them where needed. Where proportionate, these include data protection policies.
  [GDPR, Article 24](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

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

- Assess security risk
  When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.
  [GDPR, Article 32(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

### Review, audit and improvement

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

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)

Nothing in the acts covered.

## Protection

### Access control

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

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)

Nothing in the acts covered.

### Human resources security

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

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)

- Staff act only on instructions
  Processors, and anyone with access to personal data under the authority of a controller or processor, process it only on the controller's instructions unless EU or Member State law requires otherwise. Controllers and processors take steps to ensure this.
  [GDPR, Articles 29 and 32(4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

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

### Incident handling

**Both cover it** read the wording below

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)

- Document every breach
  Applies to: Controllers
  Record each personal data breach, whether notified or not, with its facts, effects and remedial action, so the authority can check compliance.
  [GDPR, Article 33(5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

### Incident classification

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

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)

Nothing in the acts covered.

### Reporting to authorities

**Both cover it** read the wording below

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

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

- Notify a personal data breach
  Applies to: Controllers
  Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.
  [GDPR, Article 33(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Processor tells the controller
  Applies to: Processors
  Tell the controller of a personal data breach without undue delay after becoming aware of it.
  [GDPR, Article 33(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- What the breach notice contains
  Applies to: Controllers
  Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.
  [GDPR, Article 33(3) and (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

### Informing customers and the public

**Both cover it** read the wording below

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)

- Tell the people affected
  Applies to: Controllers
  Where a breach is likely to cause high risk to people, tell them in plain language without undue delay, with the contact point, likely consequences and measures. This is not needed where the data was unintelligible, for example encrypted, where later measures remove the high risk, or where a public notice replaces disproportionate effort. The authority may require notice.
  [GDPR, Article 34(1) to (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

### Threat intelligence and information sharing

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

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

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

Nothing in the acts covered.

## Continuity and resilience

### Business continuity and crisis management

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

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)

Nothing in the acts covered.

## Third parties and supply chain

### Supplier and third-party risk

**Both cover it** read the wording below

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

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

- Use only processors with sufficient guarantees
  Applies to: Controllers
  Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.
  [GDPR, Article 28(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Sub-processors
  Applies to: Processors
  Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.
  [GDPR, Article 28(2) and (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

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

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

- 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 supervisory authority powers
  Cooperate with the supervisory authority on request. The authority can order information, audit, access data and premises, and issue warnings, reprimands and orders, including a processing ban, suspension of data flows or a fine.
  [GDPR, Articles 31 and 58](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

### Penalties and liability

**Both cover it** read the wording below

- 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 operational obligations
  Infringing the duties of controllers and processors in Articles 8, 11, 25 to 39, 42 and 43, or of certification and monitoring bodies, can be fined, and fines are set case by case to be effective, proportionate and dissuasive. Several infringements in the same or linked processing operations are capped at the amount for the gravest one.
  [GDPR, Article 83(1) to (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Fines for principles, rights and transfers
  Infringing the principles and consent requirements in Articles 5, 6, 7 and 9, rights in Articles 12 to 22, transfer requirements in Articles 44 to 49, Member State law adopted under Chapter IX, or ignoring an authority's order or denying it access can be fined at the higher level.
  [GDPR, Article 83(5) and (6)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#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. 13 topics where all apply the Directive as it is are not shown.

## More Comparisons

- [Compare CER](https://grc.plus/compare/cer/)
- [Compare GDPR Spain](https://grc.plus/compare/gdpr-spain/)

Source: https://grc.plus/compare/cer-vs-gdpr-spain/
