NIS2 Proportionality: How Article 21(1) Scales Measures for Small Clients

A 45-person logistics firm and a 900-bed hospital group both get the same question from their regulator: show me your backup and recovery evidence. The hospital answers with a tested, segmented, 24/7 recovery capability. The logistics firm answers with a nightly immutable backup and a restore test it ran in September. Both can be compliant. That is NIS2 proportionality at work, and it is the most misread phrase in Article 21.
Many MSPs hear "proportionate" and read "optional for small clients". That reading fails the first audit. Proportionality changes how deep a measure goes. It never changes whether the measure exists.
What NIS2 proportionality actually says
Article 21(1) of Directive (EU) 2022/2555 requires essential and important entities to take "appropriate and proportionate" technical, operational and organisational measures. The text then lists what decides proportionality: the entity's degree of exposure to risk, its size, the likelihood of incidents and their severity, including societal and economic impact. State of the art, relevant standards and the cost of implementation also count.
Read that list carefully. Size is one factor among several. A 30-person managed hosting provider serving hospitals has a high exposure and a high societal impact. Its size does not buy it a lighter regime.
Proportionality scales depth, not scope
Article 21(2) sets out ten measures that must be covered at a minimum, built on an all-hazards approach. Risk analysis and security policies, incident handling, business continuity, supply chain security, secure acquisition and development, effectiveness assessment, basic cyber hygiene and training, cryptography, access control and asset management, and multi-factor authentication with secured communications. Our guide to the ten measures walks through each one.
No size exemption appears anywhere in that list. A small client does not skip incident handling. It runs a shorter, cheaper, well-evidenced version of it.
Article 21 β 10 NIS2 Cybersecurity Measures
Article 21
10 Cybersecurity Measures
Governance & Strategy
Incident & Continuity
Supply Chain & Systems
Technical Controls
People & Assets
In practice, depth varies along four dials:
- Frequency. A restore test every quarter for a hospital, every six months for a 45-person firm with simple systems.
- Coverage. Monitoring across every endpoint and log source versus the systems that carry the business-critical process.
- Tooling. A dedicated SIEM versus managed detection from the MSP plus cloud-native logging.
- Formality. A full ISMS versus a short policy set that a director can actually read and approve.
Where MSPs get proportionality wrong
Three failures show up repeatedly in client assessments.
Treating the headcount as the verdict. "They have 40 staff, so they are fine with a basic setup" ignores exposure. A 40-person firm that processes payroll for 200 employers, or runs remote access into a water utility, carries risk far above its size.
Copying the enterprise template. The opposite error is just as costly. Handing a 25-person client a 140-page policy pack it will never maintain produces documents that contradict how the firm really works. Auditors read that contradiction as a finding.
Leaving no record of the reasoning. The measure may be sensible, but if nobody wrote down why it is enough, the client cannot defend it. Under Article 20, the management body approves the risk-management measures and oversees their implementation. A director cannot approve a decision that was never written down.
Build a proportionality record per measure
The fix is a short decision record for each of the ten measures. One page per client is often enough. Capture:
- The risk. What could go wrong for this service, and who would be hurt?
- The factors. The client's exposure, size, incident likelihood and severity, and what the measure costs.
- The chosen level. What the client does, with the frequency and scope.
- The reasoning. Why that level is adequate for this risk, in two or three sentences.
- Owner and review date. A named person and the next review.
Some national laws make this explicit. Germany's BSI Act, in Β§ 30(1), tells entities to document that they meet the duty and repeats the same proportionality factors. Even where your client's country does not, the record is the cheapest evidence you can produce. It is also what regulators ask for first, as we describe in the supervisory audit evidence checklist.
Proportionality does not stop at the client's own perimeter
Supply chain security is one of the ten measures. Article 21(3) tells entities to consider the vulnerabilities specific to each direct supplier and the overall quality of their products and cybersecurity practices. For an MSP, that makes you the supplier being assessed. A client may be perfectly proportionate on its own estate and still be asked to show how it judged your risk. Our piece on supplier risk assessment covers what that evidence looks like.
Which regulator will test your reasoning also depends on the client's status. Essential entities face proactive supervision. Important entities are supervised after the fact. See essential vs important entities for how that changes the evidence timeline.
Where national law stands
Proportionality is written in the directive, but it is enforced through national law, and that law is not equally advanced everywhere. Germany's amended BSI Act is in force and spells out the factors. The Netherlands' Cyberbeveiligingswet took effect on 15 August 2026, with the RDI among the supervisors. Poland's amended KSC Act entered into force on 3 April 2026 and ties measures to the size and nature of the entity. Italy's Legislative Decree 138/2024 is in force, with ACN determination 379907/2025 setting baseline measures that existing entities must have in place by 31 October 2026. France and Spain have not yet transposed the directive, and the Commission referred both to the Court of Justice on 8 July 2026. For their clients, the directive text and the existing national regimes are the working reference.
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 to do this month
Pick your three smallest in-scope clients. For each, write the one-page record for the measures where you currently have no written reasoning, starting with incident handling, backup and access control. Have the director sign it. You will find that most of the work was already done. It just was never written down in a form an auditor can read.
If you want to see where a client stands against all ten measures before you write the records, run a quick scan. It is a readiness assessment, not a guarantee of compliance. It shows which measures have no evidence yet, so you know where the proportionality record needs to start.
Still have a question?
Answers are generated from our articles and are not legal advice. Do not enter personal or confidential data.
