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

# GDPR vs NIS2

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

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

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

## At a Glance

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

- **GDPR** Asks more on 0 topics Alone on 11 topics More detailed on 0 topics
- **NIS2** Asks more on 0 topics Alone on 19 topics More detailed on 1 topic

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

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

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

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

NIS2: Not in the acts covered

### Threshold

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

NIS2: Not in the acts covered

### Goes to

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

NIS2: Not in the acts covered

### Evidence to keep

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

NIS2: Not in the acts covered

### Incident reports go to

GDPR: Competent supervisory authority (Controllers)

NIS2: CSIRT or competent authority

### First notice of an incident

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

NIS2: Without undue delay and in any event within 24 hours of becoming aware Shortest stated

### Incident notification

GDPR: Not in the acts covered

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

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

NIS2: On request

### Final report

GDPR: Not in the acts covered

NIS2: Within one month of the incident notification

### External assessment or certification

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

NIS2: Not in the acts covered

### Review of the risk framework

GDPR: Where necessary (Controllers)

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)

### Testing of critical systems

GDPR: Regularly

NIS2: Not in the acts covered

### Register of third-party arrangements

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

GDPR: Not in the acts covered

NIS2: Required; changes without delay and in any event within two weeks

### Management body training

GDPR: Not in the acts covered

NIS2: Required

### Management body liability

GDPR: Not in the acts covered

NIS2: Yes, for infringements of Article 21

### Maximum fines

GDPR: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher Highest stated

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

**Both cover it** read the wording below

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

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

- 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

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

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

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

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

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

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

- 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

**Both cover it** read the wording below

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

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

- 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

**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.15, A.5.18, A.8.2, A.8.3

Nothing in the acts covered.

- 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

**Both cover it** read the wording below

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

- Pseudonymisation and encryption
  Apply pseudonymisation and encryption of personal data, as appropriate to the risk.
  [GDPR, Article 32(1)(a)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

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

- Integrity and confidentiality
  Applies to: Controllers
  Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.
  [GDPR, Article 5(1)(f)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Security of systems and services
  Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.
  [GDPR, Article 32(1)(b)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

Nothing in the acts covered.

### Network 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.8.20 to A.8.22

Nothing in the acts covered.

- 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

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

- 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

**Both cover it** read the wording below

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

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

- 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

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

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

- 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

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

- 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

**Both cover it** read the wording below

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

- Restoring access after an incident
  Be able to restore availability of and access to personal data in a timely way after a physical or technical incident, as appropriate to the risk.
  [GDPR, Article 32(1)(c)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

- 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

**Both cover it** read the wording below

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

- Testing the measures
  Have a process to test and evaluate regularly whether the technical and organisational security measures work, as appropriate to the risk.
  [GDPR, Article 32(1)(d)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

- 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

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

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

### Contract requirements

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

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20

- Processing contract
  Govern processing by a written contract or other legal act covering subject matter, duration, nature and purpose, data types, the people concerned and the controller's obligations and rights. It requires the processor to act on documented instructions, keep staff bound to confidentiality, secure the data, follow the sub-processor requirements, help with rights and Articles 32 to 36, delete or return data at the end at the controller's choice, provide compliance information and allow audits. The processor warns the controller at once if an instruction appears to breach data protection law.
  [GDPR, Article 28(3) and (9)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

Nothing in the acts covered.

### 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 GDPR** no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

- Purpose limitation and data minimisation
  Applies to: Controllers
  Collect personal data for specified, explicit and legitimate purposes and do not use it later in a way that conflicts with them. Keep the data adequate, relevant and limited to what those purposes need.
  [GDPR, Article 5(1)(b) and (c)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Accuracy and storage limitation
  Applies to: Controllers
  Keep personal data accurate and, where needed, up to date, and take every reasonable step to erase or correct inaccurate data without delay. Keep data in a form that identifies people only for as long as the purpose needs, or longer solely for archiving, research or statistics under Article 89(1) with safeguards.
  [GDPR, Article 5(1)(d) and (e)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Accountability
  Applies to: Controllers
  The controller is responsible for meeting the data protection principles and must be able to demonstrate that it does.
  [GDPR, Article 5(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Lawful basis
  Applies to: Controllers
  Process personal data lawfully, fairly and transparently, and only where at least one basis applies: consent, contract, legal obligation, vital interests, a public-interest task or official authority, or legitimate interests. Legitimate interests do not apply where the person's interests or rights override them, and are not open to public authorities performing their tasks.
  [GDPR, Articles 5(1)(a) and 6(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Conditions for consent
  Applies to: Controllers
  Be able to prove consent, and keep a written consent request separate from other matters and in plain language. Let people withdraw at any time, as easily as they gave consent, and tell them so beforehand. Consent tied to a contract for data the contract does not need may not count as freely given.
  [GDPR, Article 7](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Children's consent to online services
  Applies to: Controllers offering information society services directly to children
  Where consent is the basis for processing in relation to offering an information society service directly to a child under the age limit, make sure consent is given or authorised by the holder of parental responsibility. Make reasonable efforts, given the available technology, to verify it.
  [GDPR, Article 8(1) and (2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Special category and criminal offence data
  Applies to: Controllers
  Do not process special category data, such as health, biometric identification or genetic data, unless a condition in Article 9(2) applies. Process criminal conviction and offence data only under official authority or where EU or Member State law authorises it with safeguards.
  [GDPR, Articles 9 and 10](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

Nothing in the acts covered.

### Transparency

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

NIST Privacy Framework CM.AW-P

- Information when collecting from the person
  Applies to: Controllers
  Tell people, concisely and in plain language, who the controller and any DPO are, the purposes and legal basis, any legitimate interests relied on, recipients, transfers, retention, their rights, whether they must provide the data, and any automated decision-making. Before using the data for a new purpose, give information on that purpose and any relevant further details. This is not needed where the person already has the information.
  [GDPR, Articles 12(1) and 13](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Information when data comes from elsewhere
  Applies to: Controllers
  Give the same information, plus the categories of data and their source, when the data was not obtained from the person. Exceptions include where the person already has it, where this proves impossible or takes disproportionate effort, in which case take appropriate measures to protect the person, including making the information public, or where law requires the obtaining or disclosure or professional secrecy applies.
  [GDPR, Article 14](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

Nothing in the acts covered.

### Rights of individuals

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

NIST Privacy Framework CT.DM-P

- Answer rights requests in time
  Applies to: Controllers
  Act on a request under Articles 15 to 22 and tell the person the outcome free of charge. If more time is needed for complex or numerous requests, say so and why within the first month. If no action will be taken, say why without delay and within the first month, and explain the right to complain to an authority and seek a judicial remedy. Manifestly unfounded or excessive requests may be charged for or refused, and the controller must show why.
  [GDPR, Article 12(3) to (5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right of access
  Applies to: Controllers
  Confirm whether personal data about the person is processed and give access to it, with a copy and information on purposes, data categories, recipients, retention, rights, source and automated decision-making. A reasonable fee may be charged for further copies. The right to a copy must not adversely affect the rights and freedoms of others.
  [GDPR, Article 15](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Rectification, restriction and telling recipients
  Applies to: Controllers
  Correct inaccurate data without undue delay and, taking account of the purposes, complete incomplete data. On request, restrict processing while accuracy is contested or an Article 21(1) objection is being checked, where processing is unlawful and the person prefers restriction to erasure, or where the controller no longer needs the data but the person needs it for legal claims. Tell each recipient of any rectification, erasure or restriction unless this proves impossible or takes disproportionate effort, and tell the person who the recipients are if asked.
  [GDPR, Articles 16, 18 and 19](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right to erasure
  Applies to: Controllers
  Erase personal data without undue delay where it is no longer needed, consent is withdrawn with no other basis, the person objects under Article 21(1) without overriding grounds or objects to direct marketing, processing was unlawful, law requires it, or it was collected for an information society service under Article 8(1). If the data was made public, take reasonable steps to tell other controllers of the request. The right does not apply where processing is needed for freedom of expression, a legal obligation or public task, public health, archiving, research or statistics where erasure would seriously impair them, or legal claims.
  [GDPR, Article 17](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right to data portability
  Applies to: Controllers
  Where processing is automated and rests on consent or contract, give people, on request, the data they provided in a structured, commonly used, machine-readable format. On request, send it directly to another controller where technically feasible. The right does not apply to public-task processing and must not adversely affect the rights of others.
  [GDPR, Article 20](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right to object
  Applies to: Controllers
  Stop processing based on a public task or legitimate interests when the person objects on grounds of their particular situation, unless the controller demonstrates compelling legitimate grounds that override the person's interests, or legal claims. Stop direct marketing, and related profiling, on objection without exception. Present this right clearly and separately, at the latest at first communication.
  [GDPR, Article 21](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Solely automated decisions
  Applies to: Controllers
  Do not subject people to decisions based solely on automated processing, including profiling, with legal or similarly significant effects, unless a contract need, law or explicit consent allows it. In the contract and consent cases, provide human intervention, a chance to give a view and a way to contest the decision. Special category data needs further conditions and safeguards.
  [GDPR, Article 22](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

Nothing in the acts covered.

### Privacy by design and by default

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

NIST Privacy Framework CT.DP-P

- Data protection by design
  Applies to: Controllers
  When deciding how to process and during processing, apply measures such as pseudonymisation that put the data protection principles into effect and build safeguards into the processing. Take account of the state of the art, cost and risk.
  [GDPR, Article 25(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Data protection by default
  Applies to: Controllers
  By default, process only the data needed for each purpose, in amount, extent, storage period and accessibility. Do not make personal data available to an indefinite number of people without the person's intervention.
  [GDPR, Article 25(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

Nothing in the acts covered.

### Impact assessment

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

NIST Privacy Framework ID.RA-P

- When an impact assessment is needed
  Applies to: Controllers
  Assess the impact on personal data before processing that is likely to cause high risk, especially with new technologies. It is required for systematic and extensive automated evaluation with legal or similarly significant effects, large-scale special category or criminal data, and large-scale systematic monitoring of a publicly accessible area.
  [GDPR, Article 35(1) and (3)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- What the assessment contains
  Applies to: Controllers
  Describe the processing and its purposes, assess necessity and proportionality, assess the risks to people, and set out the measures to address them. Seek the advice of the DPO where one is designated, and where appropriate the views of those affected. Where necessary, review whether processing follows the assessment, at least when the risk changes.
  [GDPR, Article 35(2), (7), (9) and (11)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Prior consultation
  Applies to: Controllers
  Consult the supervisory authority before processing if the assessment shows the processing would result in a high risk in the absence of measures taken by the controller to mitigate it. Provide responsibilities, purposes and means, safeguards, DPO contact details, the assessment and anything else the authority asks for.
  [GDPR, Article 36(1) to (3)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

Nothing in the acts covered.

### Records of processing

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

NIST Privacy Framework ID.IM-P

- Controller's record of processing
  Applies to: Controllers
  Keep a written or electronic record of the name and contact details of the controller and any joint controller, representative and DPO, purposes, categories of people, data and recipients, transfers, erasure time limits and security measures where possible, and show it to the authority on request. The duty does not apply to organisations under 250 persons, unless the processing is likely to risk people's rights, is not occasional, or includes special category or criminal data.
  [GDPR, Article 30(1), (3), (4) and (5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Processor's record of processing
  Applies to: Processors
  Keep a written or electronic record of the name and contact details of the processor, each controller served and any representative and DPO, the categories of processing for each controller, transfers and, where possible, security measures. Show it to the authority on request. The same 250-person exemption applies.
  [GDPR, Article 30(2) to (5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

Nothing in the acts covered.

### Data protection officer

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

NIST Privacy Framework GV.PO-P

- Designate a data protection officer
  Designate a DPO if the organisation is a public body, except courts acting in their judicial capacity, if its core activities need regular and systematic large-scale monitoring of people, or if they involve large-scale special category or criminal data. Choose the DPO for expertise in data protection law and practice. Publish the DPO's contact details and give them to the authority.
  [GDPR, Article 37(1), (5) and (7)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Position and tasks of the DPO
  Involve the DPO promptly in all data protection issues and give the resources and access needed. The DPO takes no instructions on these tasks, cannot be dismissed or penalised for doing them, and reports to the highest management level, and other duties must not create a conflict of interests. The DPO advises, monitors compliance including staff training and audits, advises on impact assessments and acts as contact point for the authority.
  [GDPR, Articles 38 and 39](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

Nothing in the acts covered.

### International transfers

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

- Transfers need a Chapter V ground
  Transfer personal data to a third country or international organisation, including onward transfers, only under the conditions of Chapter V. A Commission adequacy decision allows a transfer without specific authorisation.
  [GDPR, Articles 44 and 45](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Appropriate safeguards
  Without an adequacy decision, transfer only with appropriate safeguards and enforceable rights and remedies for people. Options without specific authority approval include binding corporate rules approved under Article 47, standard data protection clauses, and approved codes or certification with binding commitments. Bespoke contractual clauses need the authority's authorisation.
  [GDPR, Articles 46 and 47](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Third-country orders
  Treat a third-country court or authority order to transfer or disclose personal data as recognised or enforceable only where it rests on an international agreement, such as a mutual legal assistance treaty, without prejudice to other Chapter V grounds.
  [GDPR, Article 48](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Derogations for specific situations
  Without adequacy or safeguards, transfer only on a listed ground such as explicit informed consent, contract need, important public interest, legal claims or vital interests. As a last resort, a non-repetitive transfer about few people may rest on compelling legitimate interests not overridden by the person's interests or rights, if the controller assesses it, applies safeguards, informs the authority and the people concerned, and records it. Public authorities exercising public powers cannot use the consent, contract or last-resort grounds.
  [GDPR, Article 49](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#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 GDPR** no specific requirement on the other side in the acts covered

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

Nothing in the acts covered.

### Penalties and liability

**Both cover it** read the wording below

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

- 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 GDPR](https://grc.plus/compare/gdpr/)
- [Compare NIS2](https://grc.plus/compare/nis2/)

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