NIS2 and GDPR: which obligations overlap and how to articulate them?
Two texts, two objects, common ground
| GDPR | NIS2 | |
|---|---|---|
| Protected object | Personal data and individuals' rights | Network and information systems and continuity of services |
| Who is concerned | Any organisation processing personal data | Essential and important entities in the sectors listed in Annexes I and II |
| Authority in France | the French data protection authority (CNIL) | the French cybersecurity agency (ANSSI) |
| Security provision | Article 32: appropriate technical and organisational measures | Article 21: 10 families of risk management measures |
| Incident | Data breach: notification to the French data protection authority (CNIL) within 72 hours, to individuals if high risk | Significant incident: early warning 24 hours, notification 72 hours, final report 1 month |
| Governance | Controller's responsibility, DPO | Approval and oversight by the management body, training of senior management |
| Maximum fine | €20m or 4% of global turnover | €10m or 2% of global turnover (essential entities) |
The common ground is obvious: access control, encryption, backups, vulnerability management, awareness, crisis management appear on both sides. What differs is the perspective: the GDPR assesses risk to individuals, NIS2 assesses risk to the service.
The practical case: a ransomware attack on a Friday evening
A regulated mid-sized healthcare company suffers a ransomware attack that encrypts its servers and exfiltrates files.
- H+0 to H+24: qualification. Significant NIS2 incident (serious disruption): early warning to the French cybersecurity agency (ANSSI). Probable data breach (exfiltration): the French data protection authority (CNIL) clock also starts.
- H+72: completed NIS2 notification (severity, impact, indicators) and CNIL notification (Article 33: nature of the breach, categories and volumes, probable consequences, measures).
- If high risk to individuals: individual notification of patients (Article 34), in addition to notifying service recipients on the NIS2 side.
- D+30: final ANSSI report; on the CNIL side, complete documentation of the breach in the record of processing activities for breaches.
Two desks, two forms, two clocks: the only way to manage is a single incident procedure that addresses both from qualification (see the detail of NIS2 deadlines).
Do fines stack?
No for the same infringement: Article 35 of NIS2 organises cooperation between cyber authorities and data protection authorities and provides that, where a fine has been imposed under Article 83 of the GDPR for a data breach, no NIS2 fine is added for the same conduct. However, separate infringements (lack of NIS2 measures on one side, failure to inform individuals on the other) remain sanctionable each, and corrective measures (injunctions, periodic penalty payments, or even suspension for essential entities) are added to the fines.
Pooling without conflating: the method
- A single risk analysis, dual-read: each risk is scored for the service (NIS2) and for individuals (GDPR).
- A single set of measures mapped to both frameworks: an access control policy serves Article 21 and Article 32; no need to write two documents.
- Two linked inventories: the asset and service mapping (NIS2) and the record of processing activities (GDPR) correspond: each processing activity relies on assets, each critical asset carries processing activities.
- Common governance: a quarterly compliance-security committee before management, which fulfils both the NIS2 supervisory obligation of the executive and GDPR accountability.
- A single incident procedure with a decision tree: significant incident? data breach? both? and notification templates for both desks.
- A single training plan: cyber hygiene (NIS2), data protection (GDPR) and, now, AI literacy (AI Act) in the same programme.
This is precisely the wager of tool-supported multi-regulatory compliance: a common framework, pooled evidence, and views by regulation for each authority.
Take action
Manage your compliance with Data Comply One: all-in-one software and outsourced DPO/CISO experts.
Discover the NIS2 software →Test my NIS2 compliance →Sources
- Directive (EU) 2022/2555 (NIS2), Articles 20, 21, 23, 32, 34 and 35, EUR-Lex.
- Regulation (EU) 2016/679 (GDPR), Articles 32, 33, 34, 37 and 83, EUR-Lex.
- CNIL and ANSSI, joint publications on data security and incident management.