NIS2 vs GDPR: two regimes, two clocks
Short answer. GDPR protects personal data and applies to anyone processing it. NIS2 protects the security and continuity of network and information systems in 18 listed sectors, whether or not personal data is involved. Both can apply to the same incident, with different authorities and different deadlines — 24 hours under NIS2, 72 hours under GDPR.
Last reviewed: 31 July 2026.
NIS vs GDPR in one paragraph
They are not competing frameworks and neither supersedes the other. GDPR asks whether individuals' rights are protected. NIS2 asks whether the service keeps running and the systems stay secure. An outage that exposes no personal data is a NIS2 matter and not a GDPR one; a mis-sent email exposing customer records is the reverse; ransomware is usually both.
Different objectives
The role division matters more than it first appears. GDPR allocates duties by who decides purposes and means. NIS2 does not care: an entity is responsible for the security of its own systems and services, including where a provider operates them on its behalf.
Third party duties compared
The trap: teams treat the DPA register as the supplier register. It is not. Your cloud backup provider, your OT maintenance contractor and your software vendor may process no personal data at all and still sit at the top of your NIS2 supplier tiering. Building the register from DPAs guarantees an incomplete one — see Who counts as a direct supplier under NIS2?
The two notification clocks
Running both from one incident process is the only sane approach. The practical pattern: a single intake and triage, one timeline log with timestamps of awareness and of each filing, and a decision gate that asks both questions — "is this a significant incident?" and "is this a personal data breach?" — at the same moment.
Note the last row. GDPR gives you a statutory processor notification duty. NIS2 gives you nothing equivalent for suppliers, so the 24-hour supplier notification window has to come from the contract. See What contract clauses does NIS2 require with suppliers?
Fines compared
GDPR's ceiling is higher. NIS2's personal consequences are sharper. See NIS2 fines and penalties.
Where the regimes overlap
Genuine overlap sits in a few places, and each is an opportunity to do work once:
- Security measures. GDPR Article 32 requires appropriate technical and organisational measures. NIS2 Article 21(2) enumerates ten. The Article 21(2) set will generally satisfy Article 32 for the systems it covers.
- Supplier due diligence. The Article 28 "sufficient guarantees" assessment and the Article 21(3) supplier assessment can be one exercise with one output, provided the NIS2 version does not stop at personal data.
- Contracts. One security schedule can carry both the Article 28(3) terms and the NIS2 clause set. Keep them in one document with clearly labelled sections.
- Incident response. One plan, one timeline, two notification branches.
- Training and awareness. Article 21(2)(g) training can absorb data protection content, as long as the NIS2-specific management training under Article 20(2) is separately recorded.
Running both without duplicating work
- One supplier register, with attributes for personal data processed and for service dependency and access — not two lists maintained by two teams.
- One assessment, with GDPR-specific and NIS2-specific question blocks, producing one dated record per supplier.
- One contract template with a security schedule covering both regimes.
- One incident pipeline with a dual significance test at triage and a single timestamped log.
- Separate registers of authorities — DPAs and CSIRTs, per member state, with contacts and portals confirmed in advance.
- Joint governance. The DPO and the security function should see the same supplier data. Where they do not, the two registers diverge within a quarter.
Background reading in these docs: GDPR and GDPR regulations and what are data breaches.