ePrivacy vs NIS2 Denmark
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 4 of 13 topics. Each verdict names what it rests on; read the wording before relying on it.
- ePrivacy Asks more on 0 topics Alone on 4 topics More detailed on 0 topics
- NIS2 Denmark Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
| Topic | ePrivacy | NIS2 Denmark | Verdict |
|---|---|---|---|
| Governance | |||
| Security policy | ePrivacy: 1 | NIS2 Denmark: 2 | Both cover itread the wording below |
| Protection | |||
| Access control | ePrivacy: 1 | NIS2 Denmark: 2 | Both cover itread the wording below |
| Data security | ePrivacy: 1 | NIS2 Denmark: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Network security | ePrivacy: 1 | NIS2 Denmark: 1 | Both cover itread the wording below |
| Secure communications | ePrivacy: 1 | NIS2 Denmark: 1 | Both cover itread the wording below |
| Detection and response | |||
| Incident handling | ePrivacy: 1 | NIS2 Denmark: 1 | Both cover itread the wording below |
| Reporting to authorities | ePrivacy: 4 | NIS2 Denmark: 5 | Both cover itread the wording below |
| Informing customers and the public | ePrivacy: 2 | NIS2 Denmark: 2 | Both cover itread the wording below |
| Third parties and supply chain | |||
| Supplier and third-party risk | ePrivacy: 1 | NIS2 Denmark: 2 | Both cover itread the wording below |
| Privacy and data protection | |||
| Lawful processing | ePrivacy: 4 | NIS2 Denmark: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Transparency | ePrivacy: 3 | NIS2 Denmark: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Supervision and enforcement | |||
| Cooperation with supervisors | ePrivacy: 1 | NIS2 Denmark: – | Only ePrivacyno specific requirement on the other side in the acts covered |
| Penalties and liability | ePrivacy: 1 | NIS2 Denmark: 2 | 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
- 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
Status
Reviewed against the official texts.
Included
- NIS2 Directive (EU) 2022/2555
- NIS2 Implementing Regulation Commission Implementing Regulation (EU) 2024/2690 Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
National requirements
None recorded yet, so the Directive is shown as it is. The national law may go further.
Status
Reviewed against the official texts.
Key Numbers
Deadline
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)
NIS2 Denmark: Not in the acts covered
Goes to
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)
NIS2 Denmark: Not in the acts covered
Evidence to keep
ePrivacy: Inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive (Providers of publicly available electronic communications services)
NIS2 Denmark: Not in the acts covered
Incident reports go to
ePrivacy: Competent national authority (Providers of publicly available electronic communications services)
NIS2 Denmark: CSIRTComputer Security Incident Response Team or competent authority
First notice of an incident
ePrivacy: Within 24 hours of detection, where feasible (Providers of publicly available electronic communications services)
NIS2 Denmark: Without undue delay and in any event within 24 hours of becoming aware
Incident notification
ePrivacy: Within three days of the initial notification (Providers of publicly available electronic communications services)
NIS2 Denmark: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust serviceAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2. providers, for incidents affecting their trust servicesAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2.)
Intermediate report
ePrivacy: Not in the acts covered
NIS2 Denmark: On request
Final report
ePrivacy: Not in the acts covered
NIS2 Denmark: Within one month of the incident notification
Review of the risk framework
ePrivacy: Not in the acts covered
NIS2 Denmark: Risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. and treatment plan at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)
Register of third-party arrangements
ePrivacy: Not in the acts covered
NIS2 Denmark: Directory of direct suppliers and service providers (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)
Registration with the authority
ePrivacy: Not in the acts covered
NIS2 Denmark: Required; changes without delay and in any event within two weeks
Management body training
ePrivacy: Not in the acts covered
NIS2 Denmark: Required
Management body liability
ePrivacy: Not in the acts covered
NIS2 Denmark: Yes, for infringements of Article 21
Maximum fines
ePrivacy: Set by each Member State; no EU maximum (Member States and competent national authorities)
NIS2 Denmark: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities.: maximum of at least EUR 10 million or 2% of the undertaking's total worldwide annual turnover in the preceding financial year, whichever is higher. Important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance.: maximum of at least EUR 7 million or 1.4%, whichever is higher.
Governance
Security policy
Both cover it read the wording below
NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1
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.
Risk analysis and security policies
Policies on risk analysis and on information system security.
NIS2, Article 21(2)(a) · applies as in the Directive
Network and information system security policy
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
A security policy approved by the management body, reviewed at least annually and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.
NIS2 Implementing Regulation, Annex, point 1.1 · applies as in the Directive
Protection
Access control
Both cover it read the wording below
NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3
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.
Access control policies
Access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies.
NIS2, Article 21(2)(i) · applies as in the Directive
Access rights and privileged accounts
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Management of access rights, and stricter controls on privileged and system administration accounts.
NIS2 Implementing Regulation, Annex, points 11.2 and 11.3 · applies as in the Directive
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
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.
Nothing in the acts covered.
Network security
Both cover it read the wording below
NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22
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.
Network security and segmentation
Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
Network security measures, and systems segmented into networks or zones by risk and from third parties' systems.
NIS2 Implementing Regulation, Annex, points 6.7 and 6.8 · applies as in the Directive
Secure communications
Both cover it read the wording below
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14
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.
Secured communications
Secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate.
NIS2, Article 21(2)(j) · applies as in the Directive
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
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.
Incident handling
Procedures to handle incidents.
NIS2, Article 21(2)(b) · applies as in the Directive
Reporting to authorities
Both cover it read the wording below
NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5
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.
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..
Notify significant incidents
Notify the CSIRTComputer Security Incident Response Team or competent authority without undue delay of any significant incidentUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident., with the information needed to judge any cross-border impact.
NIS2, Article 23(1) · applies as in the Directive
Early warning
An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.
NIS2, Article 23(4)(a) · applies as in the Directive
Incident notification
An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.
NIS2, Article 23(4)(b) · applies as in the Directive
Intermediate report
An intermediate report on status updates, when the CSIRTComputer Security Incident Response Team or authority asks for one.
NIS2, Article 23(4)(c) · applies as in the Directive
Final report
A final report with a detailed description, the likely type of threat or root cause, the applied and ongoing mitigation and any cross-border impact. For an ongoing incident, a progress report at that time and the final report within one month of handling it.
NIS2, Article 23(4)(d) and (e) · 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
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.
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
Inform affected recipients
Where appropriate, notify recipients of the services without undue delay of significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. likely to affect the provision of those services.
NIS2, Article 23(1) · applies as in the Directive
Warn of significant cyber threats
Where applicable, tell recipients potentially affected by a significant cyber threatA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident., without undue delay, what they can do about it and, where appropriate, about the threat itself.
NIS2, Article 23(2) · applies as in the Directive
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
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..
Supply chain security
Supply chain security, including the security aspects of the relationship with each direct supplier and service provider.
NIS2, Article 21(2)(d) · applies as in the Directive
What to weigh for each supplier and service provider
Entities weigh the specific vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. of each direct supplier and service provider, the quality of their products and cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. practices, including secure development, and the results of EU coordinated risk assessmentsRisk Assessment of critical supply chains.
NIS2, Article 21(3) · applies as in the Directive
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
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.
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.
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.
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.
Nothing in the acts covered.
Transparency
Only ePrivacy no specific requirement on the other side in the acts covered
NIST Privacy Framework CM.AW-P
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.
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.
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.
Nothing in the acts covered.
Supervision and enforcement
Cooperation with supervisors
Only ePrivacy no specific requirement on the other side in the acts covered
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.
Nothing in the acts covered.
Penalties and liability
Both cover it read the wording below
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.
Management approves and oversees the measures
The management body approves the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
NIS2, Article 20(1) · applies as in the Directive
Administrative fines
Infringements of Article 21 or 23 can be fined. Member States set maximums of at least the amounts below, whichever is higher.
NIS2, Article 34(4) and (5) · 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. 22 topics where all apply the Directive as it is are not shown.
More Comparisons
Subject to more than one?
We run one control set for both, without doing the work twice. Ask what that saves you.