Incident to report to a regulator?Incident to report? Intake Line

CER Denmark vs ePrivacy

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

CER DenmarkCritical entities identified by Member States

ePrivacyProviders of publicly available electronic communications services; Article 5(3) and Article 13 also reach other organisations

At a Glance

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

  • CER Denmark Asks more on 0 topics Alone on 0 topics More detailed on 2 topics
  • ePrivacy Asks more on 0 topics Alone on 5 topics More detailed on 0 topics
Requirements per topic and verdict
Topic CER DenmarkePrivacy Verdict
Governance
Security policy CER Denmark: 1 ePrivacy: 1 Both cover itread the wording below
Protection
Access control CER Denmark: 1 ePrivacy: 1 Both cover itread the wording below
Data security CER Denmark: – ePrivacy: 1 Only ePrivacyno specific requirement on the other side in the acts covered
Network security CER Denmark: – ePrivacy: 1 Only ePrivacyno specific requirement on the other side in the acts covered
Secure communications CER Denmark: – ePrivacy: 1 Only ePrivacyno specific requirement on the other side in the acts covered
Detection and response
Incident handling CER Denmark: 1 ePrivacy: 1 Both cover itread the wording below
Reporting to authorities CER Denmark: 3 ePrivacy: 4 Both cover itread the wording below
Informing customers and the public CER Denmark: 1 ePrivacy: 2 Both cover itread the wording below
Third parties and supply chain
Supplier and third-party risk CER Denmark: 3 ePrivacy: 1 CER Denmark more detailedmore requirements on this, not necessarily stricter
Privacy and data protection
Lawful processing CER Denmark: – ePrivacy: 4 Only ePrivacyno specific requirement on the other side in the acts covered
Transparency CER Denmark: – ePrivacy: 3 Only ePrivacyno specific requirement on the other side in the acts covered
Supervision and enforcement
Cooperation with supervisors CER Denmark: 4 ePrivacy: 1 CER Denmark more detailedmore requirements on this, not necessarily stricter
Penalties and liability CER Denmark: 1 ePrivacy: 1 Both cover itread 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 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

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.

Included

  • ePrivacy Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002, as amended by Directive 2009/136/EC; Commission Regulation (EU) No 611/2013 Articles 2, 4 to 6, 9, 13, 15 · 18 requirements

Status

Reviewed against the official texts.

Key Numbers

Deadline

CER Denmark: 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)

ePrivacy: Without undue delay after detection (Providers of publicly available electronic communications services); Immediately (Providers contracted by a provider of publicly available electronic communications services)

How often

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

ePrivacy: Not in the acts covered

Threshold

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

ePrivacy: Not in the acts covered

Goes to

CER Denmark: Competent authority

ePrivacy: Subscribers (Providers of publicly available electronic communications services); Subscribers and individuals affected (Providers of publicly available electronic communications services); Contracting provider (Providers contracted by a provider of publicly available electronic communications services)

Evidence to keep

CER Denmark: Resilience planIn critical infrastructure regulation, a document explaining how an organisation will protect and maintain services that society depends on, and restore them after disruption. It connects identified risks with practical safeguards, responsibilities and arrangements for prevention, response and recovery. The required contents, approval process and use of equivalent existing documents depend on the applicable national law. or equivalent documents; Information and evidence on the Article 13 measures (Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555)

ePrivacy: Inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive (Providers of publicly available electronic communications services)

Incident reports go to

CER Denmark: Competent authority

ePrivacy: Competent national authority (Providers of publicly available electronic communications services)

First notice of an incident

CER Denmark: Within 24 hours of becoming aware

ePrivacy: Within 24 hours of detection, where feasible (Providers of publicly available electronic communications services)

Incident notification

CER Denmark: Not in the acts covered

ePrivacy: Within three days of the initial notification (Providers of publicly available electronic communications services)

Final report

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

ePrivacy: Not in the acts covered

Deadline to have the measures in place

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

ePrivacy: Not in the acts covered

External assessment or certification

CER Denmark: Audit by an independent and qualified auditor, where the authority requires evidence (Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555)

ePrivacy: Not in the acts covered

Maximum fines

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

ePrivacy: Set by each Member State; no EU maximum (Member States and competent national authorities)

Governance

Security policy

Both cover it read the wording below

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) · applies as in the Directive

  • Secure the service

    Applies to: Providers of publicly available electronic communications services

    Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.

    ePrivacy, Article 4(1) and (1a)

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 infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. 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 · applies as in the Directive

  • Secure the service

    Applies to: Providers of publicly available electronic communications services

    Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.

    ePrivacy, Article 4(1) and (1a)

Data security

Only ePrivacy 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.

  • Secure the service

    Applies to: Providers of publicly available electronic communications services

    Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.

    ePrivacy, Article 4(1) and (1a)

Network security

Only ePrivacy no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22

Nothing in the acts covered.

  • Secure the service

    Applies to: Providers of publicly available electronic communications services

    Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.

    ePrivacy, Article 4(1) and (1a)

Secure communications

Only ePrivacy no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

  • Confidentiality of communications

    Applies to: Anyone other than the users of the communication

    Do not listen to, tap, store or otherwise intercept communications and related traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. without the users' consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard., unless legally authorised under Article 15(1). Technical storage needed for transmission remains allowed. Regulation (EU) 2026/1881 gives a temporary exception, until 3 April 2028, for number-independent interpersonal communications services detecting online child sexual abuse under its conditions.

    ePrivacy, Article 5(1)

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) · applies as in the Directive

  • Keep a breach inventory

    Applies to: Providers of publicly available electronic communications services

    Keep an inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive recording the facts, effects and remedial action, with only the information authorities need to check compliance. Authorities may issue guidelines and instructions, can audit compliance and must impose appropriate sanctions for failures.

    ePrivacy, Article 4(4)

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 · applies as in the Directive

  • Detailed incident report

    Where relevant, follow the initial notification with a detailed report within one month.

    CER, Article 15(1), first subparagraph · applies as in the Directive

  • 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) · applies as in the Directive

  • Notify the authority of a personal data breach

    Applies to: Providers of publicly available electronic communications services

    For providers of publicly available electronic communications services only: report every personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms. to the competent national authority without undue delay, within 24 hours of detection where feasible. Detection means enough awareness to make a meaningful notification, not a mere suspicion. Describe the breach, contact points, recommended mitigation, the consequences and the measures taken.

    ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Article 2(1) and (2)

  • Second notification to the authority

    Applies to: Providers of publicly available electronic communications services

    For providers of publicly available electronic communications services only: where full information is not yet available and further investigation is needed, send an initial notification within 24 hours of detection. Send a second notification as soon as possible and at the latest within three days of the initial one. If information is still missing then, send what is held with a reasoned justification for the delay and the rest as soon as possible.

    ePrivacy, Regulation (EU) No 611/2013, Article 2(3)

  • Tell subscribers and individuals

    Applies to: Providers of publicly available electronic communications services

    For providers of publicly available electronic communications services only: where a breach is likely to harm a person's data or privacy, tell them without undue delay after detection, in clear language and without promoting services. This is not needed if the provider satisfies the authority that the data was unintelligible, for example securely encrypted with the key uncompromised. Delay is allowed only in exceptional cases where telling them could put the investigation at risk, and only with the authority's agreement.

    ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Articles 3 and 4

  • Subcontracted provider informs the contracting provider

    Applies to: Providers contracted by a provider of publicly available electronic communications services

    A provider contracted to deliver part of an electronic communications service, with no direct contract with subscribers, immediately tells the contracting provider of a personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms..

    ePrivacy, Regulation (EU) No 611/2013, Article 5

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) · applies as in the Directive

  • Warn of a network security risk

    Applies to: Providers of publicly available electronic communications services

    Where there is a particular risk of a breach of network security, tell subscribers about the risk. Where the risk lies outside the provider's own measures, also tell them of any possible remedies and their likely cost.

    ePrivacy, Article 4(2)

  • Tell subscribers and individuals

    Applies to: Providers of publicly available electronic communications services

    For providers of publicly available electronic communications services only: where a breach is likely to harm a person's data or privacy, tell them without undue delay after detection, in clear language and without promoting services. This is not needed if the provider satisfies the authority that the data was unintelligible, for example securely encrypted with the key uncompromised. Delay is allowed only in exceptional cases where telling them could put the investigation at risk, and only with the authority's agreement.

    ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Articles 3 and 4

Third parties and supply chain

Supplier and third-party risk

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

  • 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) · applies as in the Directive

  • Recover and resume the essential service

    Recover from incidents and resume the essential serviceIn the EU Critical Entities Resilience Directive, a service needed to keep society's vital functions, economic activity, public health and safety or the environment functioning. Examples include services in energy, transport, health and drinking water. The concept concerns the service people depend on. National authorities identify the critical entities that provide such services. The Directive requires reporting of incidents that significantly disrupt or could significantly disrupt essential services, with details implemented through national requirements., considering business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice. measures and alternative supply chains.

    CER, Article 13(1)(d) · applies as in the Directive

  • Employee security management

    Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. 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 · applies as in the Directive

  • Subcontracted provider informs the contracting provider

    Applies to: Providers contracted by a provider of publicly available electronic communications services

    A provider contracted to deliver part of an electronic communications service, with no direct contract with subscribers, immediately tells the contracting provider of a personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms..

    ePrivacy, Regulation (EU) No 611/2013, Article 5

Privacy and data protection

Lawful processing

Only ePrivacy no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

Nothing in the acts covered.

  • Storing or reading data on a device

    Applies to: Any organisation storing or reading information on a user's device

    Before storing or reading information on a user's device, give clear and comprehensive information and obtain consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. This does not apply to storage or access solely to carry a communication, or strictly necessary for a service the user explicitly asked for.

    ePrivacy, Article 5(3)

  • Traffic data

    Applies to: Providers of public communications networks and publicly available electronic communications services

    Erase or anonymise traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. once it is no longer needed for transmission, apart from billing until the challenge period ends and marketing or value added services with prior, withdrawable consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. Tell subscribers what is processed and for how long, and limit handling to authorised staff.

    ePrivacy, Article 6(1) to (5)

  • Location data other than traffic data

    Applies to: Providers of public communications networks and publicly available electronic communications services, and third parties providing value added services that process location data

    Process location data only anonymised, or with consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. for a value added service for as long as that service needs. Tell users first about the data, purpose, duration and any third-party transfer. Let them withdraw consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. at any time and refuse temporarily, simply and free of charge.

    ePrivacy, Article 9

  • Unsolicited direct marketing

    Applies to: Any organisation sending electronic direct marketing

    Use automated calling, fax or email for direct marketing only with prior consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. A customer's email details may be used for the seller's own similar products if the customer can object easily and free of charge at collection and in each message. Other marketing follows the national choice of opt-in or opt-out. Marketing emails must not hide the sender's identity or lack a valid address for opt-out requests. The consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. and opt-outAn opt-out is a way for a person to refuse an activity or stop further participation. In direct marketing, it means taking a step such as unsubscribing from messages. In a default-on arrangement, the activity proceeds unless the person refuses. Having an opt-out does not establish valid consent where the applicable law requires a positive agreement beforehand. requirements protect subscribers who are natural persons; Member States protect the interests of other subscribers.

    ePrivacy, Article 13(1) to (5)

Transparency

Only ePrivacy no specific requirement on the other side in the acts covered

NIST Privacy Framework CM.AW-P

Nothing in the acts covered.

  • Storing or reading data on a device

    Applies to: Any organisation storing or reading information on a user's device

    Before storing or reading information on a user's device, give clear and comprehensive information and obtain consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. This does not apply to storage or access solely to carry a communication, or strictly necessary for a service the user explicitly asked for.

    ePrivacy, Article 5(3)

  • Traffic data

    Applies to: Providers of public communications networks and publicly available electronic communications services

    Erase or anonymise traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. once it is no longer needed for transmission, apart from billing until the challenge period ends and marketing or value added services with prior, withdrawable consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. Tell subscribers what is processed and for how long, and limit handling to authorised staff.

    ePrivacy, Article 6(1) to (5)

  • Location data other than traffic data

    Applies to: Providers of public communications networks and publicly available electronic communications services, and third parties providing value added services that process location data

    Process location data only anonymised, or with consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. for a value added service for as long as that service needs. Tell users first about the data, purpose, duration and any third-party transfer. Let them withdraw consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. at any time and refuse temporarily, simply and free of charge.

    ePrivacy, Article 9

Supervision and enforcement

Cooperation with supervisors

CER Denmark 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) · applies as in the Directive

  • Report services in six or more Member States

    After being notified as a critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities., 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) · applies as in the Directive

  • Inspections, audits and remedial orders

    Applies to: Competent authorities

    Competent authorities can inspect critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential 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) · applies as in the Directive

  • Provide information and audit evidence

    Applies to: Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential 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) · applies as in the Directive

  • Procedures for access requests

    Applies to: Providers of publicly available electronic communications services

    Set internal procedures for answering requests for access to users' personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. made under national law adopted under Article 15(1). On demand, give the competent national authority information on those procedures, the number of requests received, the legal justification invoked and the response given.

    ePrivacy, Article 15(1b)

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 · applies as in the Directive

  • Penalties set nationally

    Applies to: Member States and competent national authorities

    Member States set penalties for infringements, including criminal sanctions where appropriate, which are effective, proportionate and dissuasive. Competent authorities can order infringements to stop and have investigative powers and resources, including to obtain information.

    ePrivacy, Article 15a(1) to (3)

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

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…