NIS2 Research Organisations: Which Clients Are In Scope, and Which Universities Are Not

A biotech spin-off with 80 staff, a contract research lab and a university institute share one thing: all three call themselves "research". Under NIS2, only one of them is certain to be in scope.
If you advise research-heavy clients, the question is not "do they do research?". It is "are they a research organisation as the Directive defines it, and has their member state extended the rules to anyone else?" The answer changes country by country.
What NIS2 means by a research organisation
Annex II of NIS2 lists research organisations as a sector. Entities in Annex II sectors are classed as important entities, which means supervision is reactive (after evidence or an incident) rather than proactive.
The definition sits in Article 6(41). A research organisation is an entity whose primary goal is to conduct applied research or experimental development, with a view to exploiting the results for commercial purposes. The definition expressly excludes educational institutions.
Three tests follow from that wording:
- Applied research or experimental development is the primary goal, not a side activity.
- The results are meant to be exploited commercially.
- The entity is not an educational institution.
A private R&D lab selling findings to industry passes all three. A university faculty with a few industry contracts does not, because the institution as a whole is educational.
The size rule still applies
Article 2(1) applies the EU size-cap rule. Medium-sized enterprises and above are covered, which in practice means at least 50 staff, or turnover and balance sheet above €10 million.
A 12-person research start-up is therefore out of scope unless the member state applies a size-independent rule. This is the first filter to run on every research client, and it removes more of them than most consultants expect.
Universities: out by default, in by national choice
Article 2(5) lets member states choose to extend NIS2 to education institutions, in particular where they carry out critical research activities. It is an option, not an obligation.
That produces a patchwork. Two universities with identical research programmes can face different obligations on either side of a border. Never assume an answer from the Directive alone. Check the national law.
Country by country: what we could verify
Germany. The NIS2UmsuCG has been in force since 6 December 2025, with the BSI as competent authority. Research organisations fall under the important-entity category (§ 28 BSIG). Secondary sources report that Germany did not make a general extension to universities, though individual Länder rules may apply.
Netherlands. The Cyberbeveiligingswet (Stb. 2026, 187) is in force since 15 August 2026. It covers research for commercial purposes and also addresses education institutions. Which category an institution lands in depends on its sector ministry, so confirm the designation in writing.
Italy. D.Lgs. 138/2024 goes further than the Directive. Research organisations sit in Annex II, while "enti e istituzioni di ricerca" appear in Annex III and "istituti di istruzione che svolgono attività di ricerca" in Annex IV. ACN is the competent authority and sector authority for the Annex III research bodies. The ministry for university and research (MUR) is the sector authority for the other two.
Poland. The amended KSC Act took effect on 2 April 2026 and lists scientific research as an important sector. Registration runs through the Minister of Digital Affairs. Whether a given university counts as a public entity under the Act needs a case-by-case check.
France. The transposition bill is still not law. The deadline was 17 October 2024, and National Assembly examination was postponed again in October 2026. Until it passes, there is no French research-organisation rule to point at.
Spain. The Anteproyecto de Ley de Coordinación y Gobernanza de la Ciberseguridad is still a draft, and the Commission has taken Spain to the Court of Justice. The older Real Decreto-ley 12/2018 continues to apply.
NIS2 transposition by country
- AustriaIn force
- In force since October 1, 2026
- Act: NISG 2026 (BGBl. I Nr. 94/2025)
- Registration due December 31, 2026
Authority: Federal Office for Cybersecurity · Source
- NetherlandsIn force
- In force since August 15, 2026
- Act: Cyberbeveiligingswet (Stb. 2026, 187)
- Registration required, no transition period
Authority: NCSC (MijnNCSC) · Source
- LuxembourgIn force
- In force since May 10, 2026
- Act: Law of 5 May 2026
- Registration due July 10, 2026
Authority: ILR (CSSF for finance) · Source
- PolandIn force
- In force since April 3, 2026
- Act: UKSC (Dz.U. 2026 poz. 252)
- Registration due October 3, 2026
- Measures due April 3, 2027
Authority: Minister Cyfryzacji (Wykaz KSC) · Source
- PortugalIn force
- In force since April 3, 2026
- Act: Decree-Law 125/2025 (RJC)
Authority: CNCS · Source
- BulgariaIn force
- In force since February 13, 2026
- Act: Cybersecurity Act amendment (State Gazette No 17/2026)
Authority: Ministry of e-Government · Source
- MaltaIn force
- In force since January 23, 2026
- Act: S.L. 460.41
Authority: Critical Infrastructure Protection Department · Source
- SwedenIn force
- In force since January 15, 2026
- Act: SFS 2025:1506
Authority: NCSC-SE · Source
- EstoniaIn force
- In force since January 1, 2026
- Act: Cybersecurity Act (KüTS) amendment
- Registration within 3 months
Authority: RIA · Source
- GermanyIn force
- In force since December 6, 2025
- Act: NIS2UmsuCG
- Registration due March 6, 2026
- 17,729 registered by June 30, 2026
Authority: BSI · Source
- CzechiaIn force
- In force since November 1, 2025
- Act: Act No 264/2025 Coll.
- Registration within 60 days
Authority: NÚKIB · Source
- DenmarkIn force
- In force since July 1, 2025
- Act: NIS 2 Act No 434 of 6 May 2025
- Registration due October 1, 2025
Authority: Danish Agency for Societal Security · Source
- SloveniaIn force
- In force since June 19, 2025
- Act: ZInfV-1 (OG 40/25)
- Registration within 30 days
Authority: URSIV · Source
- CyprusIn force
- In force since April 25, 2025
- Act: Law 60(I)/2025
Authority: Digital Security Authority · Source
- FinlandIn force
- In force since April 8, 2025
- Act: Cybersecurity Act 124/2025
- Registration due May 8, 2025
- Measures due July 8, 2025
Authority: Traficom (NCSC-FI) · Source
- HungaryIn force
- In force since January 1, 2025
- Act: Act LXIX of 2024
Authority: SZTFH · Source
- SlovakiaIn force
- In force since January 1, 2025
- Act: Act No 366/2024 Coll.
- Registration within 60 days
Authority: NBÚ · Source
- RomaniaIn force
- In force since December 31, 2024
- Act: GEO 155/2024 (Law 124/2025)
- Registration within 30 days
Authority: DNSC · Source
- GreeceIn force
- In force since November 27, 2024
- Act: Law 5160/2024 (Gazette A' 195)
Authority: National Cybersecurity Authority · Source
- BelgiumIn force
- In force since October 18, 2024
- Registration due March 18, 2025
Authority: CCB · Source
- LithuaniaIn force
- In force since October 18, 2024
- Act: Law No XIV-2902
Authority: NCSC (MoND) · Source
- ItalyIn force
- In force since October 16, 2024
- Act: D.Lgs. 138/2024
- Baseline measures due by October 2026 (entities listed in 2025)
Authority: ACN · Source
- LatviaIn force
- In force since September 1, 2024
- Act: National Cybersecurity Law
Authority: National Cybersecurity Centre · Source
- CroatiaIn force
- In force since February 15, 2024
- Act: Cybersecurity Act (OG 14/2024)
Authority: NCSC (SOA) · Source
- FranceNot yet transposed
- Senate adopted the law on March 12, 2025
- Regulator published its framework on March 17, 2026
- Referred to the Court of Justice on July 8, 2026
- Pre-registration open
Authority: ANSSI · Source
- SpainNot yet transposed
- Draft bill approved on January 14, 2025
- Referred to the Court of Justice on July 8, 2026
- The NIS1 regime still applies
Authority: CCN / INCIBE · Source
- IrelandNot yet transposed
- Referred to the Court of Justice on July 8, 2026
- Bill not yet enacted
Authority: NCSC Ireland · Source
Status as of September 28, 2026. Other member states: see the country-by-country timeline.
What important-entity status means in practice
Important entities carry the same Article 21 risk-management duties as essential entities. They must also report significant incidents under Article 23 (early warning within 24 hours, notification within 72 hours, final report within one month).
The difference is supervision and penalties. Maximum administrative fines for important entities are €7 million or 1.4% of worldwide annual turnover, whichever is higher. Supervision is ex post.
For a research client, the exposed areas are predictable: research data and IP, access control for external collaborators, and lab or instrument networks that nobody classed as IT. See the Article 21 ten measures guide for the full list.
Article 21 — 10 NIS2 Cybersecurity Measures
Article 21
10 Cybersecurity Measures
Governance & Strategy
Incident & Continuity
Supply Chain & Systems
Technical Controls
People & Assets
How to scope a research client in four questions
- Is research the primary goal of the entity? If it is an educational institution first, stop and check national extension rules.
- Is the research applied, with commercial exploitation intended? If not, the Article 6(41) definition likely fails.
- Does the entity clear the size threshold? Under 50 staff and under €10 million turnover usually means out of scope.
- Does the national law add anything? Italy, the Netherlands and Poland all do something beyond a plain copy of Annex II.
Document the answers and the date. If the client's regulator later disagrees, a dated scoping note shows good faith. For multi-country groups, Article 26 jurisdiction rules decide which regulator you face.
The takeaway
Do not scope on the word "research". Scope on Article 6(41), the size rule and the national statute, in that order.
A fast way to turn that into evidence is to run a readiness assessment per client and keep the result on file. Start a quick scan at NIS2Certify to see where a research client's compliance posture stands against Article 21.
This article is general information, not legal advice. Verify scope against the national law and your client's regulator.
Still have a question?
Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.
