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

# ePrivacy vs NIS2

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

[ePrivacy](https://grc.plus/regulation/eprivacy-directive/)Providers of publicly available electronic communications services; Article 5(3) and Article 13 also reach other organisations

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

## At a Glance

They differ on 26 of 35 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** Asks more on 0 topics Alone on 22 topics More detailed on 0 topics

| Topic | ePrivacy | NIS2 | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Management accountability | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Roles and independence | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Security policy | ePrivacy: 1 | NIS2: 2 | **Both cover it**read the wording below |
| Awareness and training | ePrivacy: – | NIS2: 2 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Risk management |  |  |  |
| Risk management framework | ePrivacy: – | NIS2: 3 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Risk assessment | ePrivacy: – | NIS2: 2 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Review, audit and improvement | ePrivacy: – | NIS2: 3 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Asset management | ePrivacy: – | NIS2: 2 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | ePrivacy: 1 | NIS2: 2 | **Both cover it**read the wording below |
| Authentication | ePrivacy: – | NIS2: 2 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Cryptography and encryption | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Data security | ePrivacy: 1 | NIS2: – | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Network security | ePrivacy: 1 | NIS2: 1 | **Both cover it**read the wording below |
| Secure communications | ePrivacy: 1 | NIS2: 1 | **Both cover it**read the wording below |
| Secure acquisition and development | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Configuration, change and patch management | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Vulnerability handling | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Human resources security | ePrivacy: – | NIS2: 2 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Physical and environmental security | ePrivacy: – | NIS2: 2 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Monitoring and detection | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Incident handling | ePrivacy: 1 | NIS2: 1 | **Both cover it**read the wording below |
| Incident classification | ePrivacy: – | NIS2: 3 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Reporting to authorities | ePrivacy: 4 | NIS2: 5 | **Both cover it**read the wording below |
| Informing customers and the public | ePrivacy: 2 | NIS2: 2 | **Both cover it**read the wording below |
| Threat intelligence and information sharing | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Backup and recovery | ePrivacy: – | NIS2: 2 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Security testing | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | ePrivacy: 1 | NIS2: 2 | **Both cover it**read the wording below |
| Register of third-party arrangements | ePrivacy: – | NIS2: 1 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Privacy and data protection |  |  |  |
| Lawful processing | ePrivacy: 4 | NIS2: – | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Transparency | ePrivacy: 3 | NIS2: – | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Registration with authorities | ePrivacy: – | NIS2: 2 | **Only NIS2**no specific requirement on the other side in the acts covered |
| Cooperation with supervisors | ePrivacy: 1 | NIS2: – | **Only ePrivacy**no specific requirement on the other side in the acts covered |
| Penalties and liability | ePrivacy: 1 | NIS2: 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

- [ePrivacy](https://grc.plus/regulation/eprivacy-directive/) 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.

Included

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

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: 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: Not in the acts covered

### Evidence to keep

ePrivacy: Inventory of personal data breaches (Providers of publicly available electronic communications services)

NIS2: Not in the acts covered

### Incident reports go to

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

NIS2: CSIRT or competent authority

### First notice of an incident

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

NIS2: 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: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust service providers, for incidents affecting their trust services)

### Intermediate report

ePrivacy: Not in the acts covered

NIS2: On request

### Final report

ePrivacy: Not in the acts covered

NIS2: Within one month of the incident notification

### Review of the risk framework

ePrivacy: Not in the acts covered

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

### Register of third-party arrangements

ePrivacy: Not in the acts covered

NIS2: 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: Required; changes without delay and in any event within two weeks

### Management body training

ePrivacy: Not in the acts covered

NIS2: Required

### Management body liability

ePrivacy: Not in the acts covered

NIS2: Yes, for infringements of Article 21

### Maximum fines

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

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

## Governance

### Management accountability

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

NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4

Nothing in the acts covered.

- Management approves and oversees the measures
  The management body approves the cybersecurity risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.
  [NIS2, Article 20(1)](https://grc.plus/regulation/nis2/#requirements)

### Roles and independence

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

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

Nothing in the acts covered.

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

### 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 data 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements)
- 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 incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Awareness and training

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

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

Nothing in the acts covered.

- Management body training
  Members of the management body follow training to identify risks and assess cybersecurity risk-management practices. Entities are encouraged to offer similar training to employees regularly.
  [NIS2, Article 20(2)](https://grc.plus/regulation/nis2/#requirements)
- Cyber hygiene and training
  Basic cyber hygiene practices and cybersecurity training.
  [NIS2, Article 21(2)(g)](https://grc.plus/regulation/nis2/#requirements)

## Risk management

### Risk management framework

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

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

Nothing in the acts covered.

- Appropriate and proportionate measures
  Technical, operational and organisational measures to manage the risks to network and information systems, set by the state of the art, relevant standards, cost, the entity's exposure and size, and the likelihood and severity of incidents.
  [NIS2, Article 21(1)](https://grc.plus/regulation/nis2/#requirements)
- All-hazards approach
  The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
  [NIS2, Article 21(2)](https://grc.plus/regulation/nis2/#requirements)
- Risk management framework
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Risk assessment

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

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

Nothing in the acts covered.

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

### Review, audit and improvement

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

Nothing in the acts covered.

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

### Asset management

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

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

Nothing in the acts covered.

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

## 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 data 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)

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

### Authentication

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

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

Nothing in the acts covered.

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

### Cryptography and encryption

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

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

Nothing in the acts covered.

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

### 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 data 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)

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 data 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)

- 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](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### 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 data without the users' consent, 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)

- Secured communications
  Secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate.
  [NIS2, Article 21(2)(j)](https://grc.plus/regulation/nis2/#requirements)

### Secure acquisition and development

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

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

Nothing in the acts covered.

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

### Configuration, change and patch management

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

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

Nothing in the acts covered.

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

### Vulnerability handling

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

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

Nothing in the acts covered.

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

### Human resources security

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

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

Nothing in the acts covered.

- Human resources security
  Human resources security.
  [NIS2, Article 21(2)(i)](https://grc.plus/regulation/nis2/#requirements)
- Background verification
  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
  Background checks on employees, and where applicable on direct suppliers and service providers, to the extent feasible and where the role needs it.
  [NIS2 Implementing Regulation, Annex, point 10.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Physical and environmental security

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

Nothing in the acts covered.

- All-hazards approach
  The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.
  [NIS2, Article 21(2)](https://grc.plus/regulation/nis2/#requirements)
- Physical and environmental security
  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
  Supporting utilities, protection against physical and environmental threats, and perimeter and physical access control.
  [NIS2 Implementing Regulation, Annex, points 13.1 to 13.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

## Detection and response

### Monitoring and detection

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

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

Nothing in the acts covered.

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

### 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 breaches 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)

- Incident handling
  Procedures to handle incidents.
  [NIS2, Article 21(2)(b)](https://grc.plus/regulation/nis2/#requirements)

### Incident classification

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

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

Nothing in the acts covered.

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

### 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 breach 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- 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](https://grc.plus/regulation/eprivacy-directive/#requirements)
- 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 breach.
  [ePrivacy, Regulation (EU) No 611/2013, Article 5](https://grc.plus/regulation/eprivacy-directive/#requirements)

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

### 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.
  [ePrivacy, Article 4(2)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- 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](https://grc.plus/regulation/eprivacy-directive/#requirements)

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

### Threat intelligence and information sharing

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

Nothing in the acts covered.

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

## Continuity and resilience

### Business continuity and crisis management

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

Nothing in the acts covered.

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

### Backup and recovery

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

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

Nothing in the acts covered.

- Business continuity and crisis management
  Business continuity, such as backup management and disaster recovery, and crisis management.
  [NIS2, Article 21(2)(c)](https://grc.plus/regulation/nis2/#requirements)
- Backup and redundancy
  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
  Backup copies and sufficient redundancy, with regular integrity checks on the copies and regular testing of recovery of copies and redundancies.
  [NIS2 Implementing Regulation, Annex, point 4.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

### Security testing

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

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

Nothing in the acts covered.

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

## 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 breach.
  [ePrivacy, Regulation (EU) No 611/2013, Article 5](https://grc.plus/regulation/eprivacy-directive/#requirements)

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

### Register of third-party arrangements

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

NIST CSF 2.0 GV.SC

Nothing in the acts covered.

- Directory of suppliers
  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 directory of direct suppliers and service providers, kept up to date.
  [NIS2 Implementing Regulation, Annex, point 5.2](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements)

## 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 consent. 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Traffic data
  Applies to: Providers of public communications networks and publicly available electronic communications services
  Erase or anonymise traffic data 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 consent. Tell subscribers what is processed and for how long, and limit handling to authorised staff.
  [ePrivacy, Article 6(1) to (5)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- 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 consent 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 consent at any time and refuse temporarily, simply and free of charge.
  [ePrivacy, Article 9](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Unsolicited direct marketing
  Applies to: Any organisation sending electronic direct marketing
  Use automated calling, fax or email for direct marketing only with prior consent. 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 consent and opt-out requirements protect subscribers who are natural persons; Member States protect the interests of other subscribers.
  [ePrivacy, Article 13(1) to (5)](https://grc.plus/regulation/eprivacy-directive/#requirements)

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 consent. 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- Traffic data
  Applies to: Providers of public communications networks and publicly available electronic communications services
  Erase or anonymise traffic data 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 consent. Tell subscribers what is processed and for how long, and limit handling to authorised staff.
  [ePrivacy, Article 6(1) to (5)](https://grc.plus/regulation/eprivacy-directive/#requirements)
- 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 consent 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 consent at any time and refuse temporarily, simply and free of charge.
  [ePrivacy, Article 9](https://grc.plus/regulation/eprivacy-directive/#requirements)

Nothing in the acts covered.

## Supervision and enforcement

### Registration with authorities

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

Nothing in the acts covered.

- Register with the authority
  Submit to the competent authority the entity's name, address, contact details including IP ranges and, where applicable, its sector and the Member States where it provides services. Report changes without delay and within two weeks.
  [NIS2, Article 3(4)](https://grc.plus/regulation/nis2/#requirements)
- Registry of digital providers
  DNS, TLD, domain name registration, cloud, data centre, content delivery, managed (security) service providers, marketplaces, search engines and social networks submit their details to the competent authority by 17 January 2025 for the ENISA registry, and report changes without delay and within three months. The authority is that of their main establishment or EU representative (Article 26).
  [NIS2, Article 27](https://grc.plus/regulation/nis2/#requirements)

### 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 data 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)](https://grc.plus/regulation/eprivacy-directive/#requirements)

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.
  [ePrivacy, Article 15a(1) to (3)](https://grc.plus/regulation/eprivacy-directive/#requirements)

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

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

## More Comparisons

- [Compare ePrivacy](https://grc.plus/compare/eprivacy/)
- [Compare NIS2](https://grc.plus/compare/nis2/)

Source: https://grc.plus/compare/eprivacy-vs-nis2/
