vendorapp logo

Docs

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

GDPRNIS2
ProtectsRights and freedoms of natural personsSecurity and continuity of network and information systems
InstrumentRegulation, directly applicableDirective, transposed into national law
Who is coveredAny controller or processor of personal data, including outside the EU where targeting EU individualsMedium and large entities in 18 Annex I/II sectors, plus size-independent cases
Trigger for dutiesProcessing personal dataOperating in a listed sector at the relevant size
RegulatorData protection authoritiesCompetent authorities and CSIRTs
Role divisionController / processorEssential / important entity

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

TopicGDPRNIS2
Core provisionArticle 28 — processor obligations and mandatory contract termsArticle 21(2)(d) and 21(3) — supply chain security
Selection dutyUse only processors providing sufficient guarantees of appropriate technical and organisational measuresTake account of each direct supplier's vulnerabilities and the quality of their products and practices
ContractPrescribed Article 28(3) terms, including sub-processor consent and assistance dutiesNot prescribed — but security, notification, audit and exit terms are the practical requirement
Scope of relationshipOnly where personal data is processedAny supplier relationship relevant to the security of your systems
Sub-suppliersSub-processor authorisation and flow-down of equivalent obligationsFramed at the direct supplier; fourth parties addressed via contractual flow-down

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

GDPRNIS2
First deadline72 hours to the supervisory authority, from becoming aware, unless unlikely to result in risk to individuals24 hours early warning to the CSIRT or competent authority, from becoming aware of a significant incident
Follow-upInformation may be provided in phases72-hour incident notification; final report within one month
Individuals / recipientsNotify data subjects without undue delay where high risk to their rights and freedomsNotify recipients of services where appropriate, including of significant cyber threats
Processor / supplier dutyProcessor notifies controller without undue delayNo directive-level supplier duty — you create it by contract

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

GDPRNIS2
Upper tier€20 million or 4% of total worldwide annual turnover, whichever is higherEssential entities: €10 million or 2%, whichever is higher
Lower tier€10 million or 2%Important entities: €7 million or 1.4%
Personal consequencesGenerally none directly on individualsManagement liability; temporary management ban for essential entities

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

  1. One supplier register, with attributes for personal data processed and for service dependency and access — not two lists maintained by two teams.
  2. One assessment, with GDPR-specific and NIS2-specific question blocks, producing one dated record per supplier.
  3. One contract template with a security schedule covering both regimes.
  4. One incident pipeline with a dual significance test at triage and a single timestamped log.
  5. Separate registers of authorities — DPAs and CSIRTs, per member state, with contacts and portals confirmed in advance.
  6. 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.

Frequently asked questions

What is the difference between NIS2 and GDPR?
GDPR protects personal data and applies to any organisation processing it. NIS2 protects the security and continuity of network and information systems in 18 listed sectors, regardless of whether personal data is involved.
Do I have to report an incident under both NIS2 and GDPR?
Often yes, to different authorities on different clocks. A ransomware attack exposing personal data can require a NIS2 early warning to the CSIRT within 24 hours and a GDPR notification to the data protection authority within 72 hours.
Does a data processing agreement satisfy NIS2 supplier requirements?
No. A GDPR Article 28 processor agreement covers personal data processing. NIS2 Article 21(2)(d) covers the security of the relationship regardless of personal data, so it needs security requirements, incident notification windows and continuity terms a DPA does not provide.