trio.so
MSP

NIS2 for MSPs and IT Service Providers: What Applies

NIS2 covers managed service providers across the EU. See when it applies to your MSP, what Germany's law says, and what clients will ask you to show.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on

Yes. The EU directive lists managed service providers (MSPs) and managed security service providers (MSSPs) as covered entity types, and whether your company is covered directly depends on its size and on the member state where it is based. If you are not covered yourself, your regulated clients probably are, and they will start asking what you can show them.

This post is for MSP owners and IT service companies in or selling into the EU. It explains what is law and what is client expectation, uses Germany as the worked example, and ends with where trio.so helps with the device side of the evidence.

Does NIS2 apply to managed service providers?

NIS2 is Directive (EU) 2022/2555. A directive is not law by itself. Each member state writes its own national law from it, so registration, deadlines and fines differ by country. The directive names "ICT service management (business to business)" as a sector, and that sector includes managed service providers and managed security service providers. Size matters too. Under the directive's size rule, a company in a listed sector is in scope if it has 50 or more staff, or if its annual turnover and its balance sheet each exceed €10 million. The EU's definition of company size (Recommendation 2003/361/EC) sets the tests, and the staff and revenue of linked or partner companies can be added to yours.

Which country's law applies to you depends on the member state where your company has its main establishment, usually your headquarters. If you provide managed IT services under contract, you almost certainly count as a managed service provider, and size then decides whether the rules reach you. Your lawyer confirms the edge cases.

Source: Directive (EU) 2022/2555, Articles 2, 26 and Annex I (EUR-Lex, read 12 November 2026).

Example: how Germany applies it

Germany transposed NIS2 in its amended BSI Act (BSIG). Secondary sources, including the law firms Heuking and usd, report that it came into force on 6 December 2025 with no grace period before the duties applied, though registration had its own three-month window. Annex 1 of the BSIG lists "Managed Services Provider" (no. 6.1.10) and "Managed Security Services Provider" (no. 6.1.11) under the sector digital infrastructure. Section 28 sets a headcount test and a financial test.

Germany's size tests (section 28 BSIG):

ClassThreshold under section 28 BSIG
Essential entity250 or more staff, or (more than €50 million turnover and more than €43 million balance sheet)
Important entity50 or more staff, or (more than €10 million turnover and more than €10 million balance sheet)

In the table above, meeting the first row makes you an essential entity; meeting only the second makes you an important entity. Essential entities face stricter supervision than important ones.

Source: BSIG section 28 (gesetze-im-internet.de, read 4 November 2026).

A service company with 30 employees is unlikely to reach these thresholds on its own, but group structures and holdings can count, so check before you rely on it.

Covered entities had to register with the Federal Office for Information Security (BSI) within three months of the law taking effect, so by early March 2026 for existing entities (section 33 BSIG). That deadline has passed. If you are covered and have not registered, do it now. In Germany the BSI portal needs an organization certificate from ELSTER, the German tax authority's online portal. It works as a digital company ID, and you request it there. Other member states set their own dates and procedures.

NIS2 requirements for IT service providers

For covered entities, the directive asks for appropriate and proportionate technical and organizational risk measures, and German law repeats this in section 30 BSIG. The law lists minimum measures. Four of them sit close to daily MSP work.

  • Supply chain security, including your relationships with direct suppliers such as software vendors.
  • Vulnerability handling: managing and disclosing vulnerabilities in the systems you buy, build and maintain.
  • Access control, including how ICT systems are administered.
  • Documentation: you must be able to show that the measures are in place.

Incident reporting comes with deadlines. For a significant incident, the directive and section 32 BSIG set an early warning within 24 hours of becoming aware, a fuller notification within 72 hours, and a final report one month after the 72-hour notification. Management must approve and oversee the measures and complete training (section 38 BSIG).

Fines are set nationally. In Germany section 65 BSIG sets maximums of €10 million for essential and €7 million for important entities, or 2% and 1.4% of worldwide annual turnover respectively, whichever is higher. These match the minimum maximums the directive sets in Article 34.

A separate EU regulation (2024/2690) adds more detailed technical rules for MSPs and MSSPs on top of NIS2; ask your counsel which parts apply. For a checklist, see our NIS2 compliance checklist. If you run a security-focused service, our post on managed security service providers covers that provider type.

What clients will ask an MSP under NIS2

Covered clients must look at the security of their own supply chain. An IT provider with administrator access to their systems is part of that chain, so expect questions in contracts and audits. The law does not give a fixed list for providers, so these are typical questions, not legal requirements:

  • How fast do security updates reach our devices, and where can we see that?
  • Who on your side can access our systems, and how is that controlled?
  • How do you report an incident so that we can meet our own 24 hours?
  • What evidence can you hand over on request?

What an MSP should check now

  1. Work out your size and group links: staff, turnover and balance sheet under the EU recommendation, including partner and linked companies.
  2. Ask your counsel whether your services count as managed services or managed security services in your member state, and whether you must register.
  3. Set an incident reporting route with named people and cover, so that 24 and 72 hours are realistic.
  4. Make patch status and access provable per client, not just known to your technicians (see our post on patch management).
  5. List your own suppliers and tools, such as remote access, your management console and backup, because clients will ask.
  6. Read client contracts for security clauses, reporting duties and evidence requests.

Managing devices and evidence across many clients

trio.so lets an MSP manage several client companies in one console, with each client's devices, users and policies kept separate. It finds open vulnerabilities on managed devices and gives each device a risk score from 0 to 100. CVSS and EPSS score how severe a vulnerability is and how likely it is to be exploited. CISA KEV lists vulnerabilities already exploited in attacks. You can sort findings by urgency with all three. Auto Patch policies handle operating system updates, and for third-party software trio.so builds remediation plans, each a written, step by step plan for closing a vulnerability in that software. The patch audit trail can be exported as evidence. No tool makes you NIS2 compliant, because that depends on how you run your whole business: policies, people, suppliers and incident handling. trio.so gives you the device and patch data that risk management needs. Plans start at $5 per device. Read more about trio.so for MSPs and MSSPs.

This post is not legal advice. Directive checked at EUR-Lex on 12 November 2026; German law (BSIG) checked on 4 November 2026.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Start your free trial

No credit card required
Full access to all features

Get Ahead of the Curve

Every organization today needs a solution to automate time-consuming tasks and strengthen security. Without the right tools, manual processes drain resources and leave gaps in protection. trio.so is designed to solve this problem, automating key tasks, boosting security, and ensuring compliance with ease.

Don't let inefficiencies hold you back.

Every organization today needs a solution to automate time-consuming tasks and strengthen security. Without the right tools, manual processes drain resources and leave gaps in protection. trio.so is designed to solve this problem, automating key tasks, boosting security, and ensuring compliance with ease.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently asked questions

Yes, the directive lists managed service providers and managed security service providers as entity types. Whether your company is covered also depends on its size and on national law in the member state where it is based.

Essential entities are the larger ones and important entities the mid-sized ones, within the sectors the directive lists. In Germany, essential means 250 or more staff, or more than €50 million turnover and €43 million balance sheet; important means 50 or more staff, or more than €10 million turnover and balance sheet (section 28 BSIG).

Reported as 6 December 2025 (Heuking and usd). Registration is due within three months of the law taking effect (section 33 BSIG).

The law sets no fixed evidence list for providers. Because covered clients must consider their supply chain, they typically ask about patch status, access control and incident reporting routes.

Covered entities must report significant incidents: early warning within 24 hours, notification within 72 hours and a final report after one month.

Related

From the blog

The related industry news, interviews, technologies, and resources.