vendorapp logo

Docs

How does NIS2 treat MSPs and ICT service providers?


Short answer. NIS2 covers managed service providers and managed security service providers twice over: ICT service management is an Annex I sector, so MSPs are in scope as entities in their own right, and they are simultaneously the highest-priority supplier category for every customer performing Article 21(2)(d) due diligence.

Last reviewed: 31 July 2026.

How NIS treats MSPs

The original NIS Directive largely missed the MSP channel. NIS2 corrects that deliberately, following a run of incidents in which attackers compromised a provider once and reached dozens of customers through legitimate administrative tooling.

The result is a two-sided obligation. If you are an MSP you have your own compliance programme. If you use one, they belong at the top of your supplier register.

MSPs are in scope in their own right

Annex I includes ICT service management (business-to-business), covering:

  • Managed service providers — entities providing services related to the installation, management, operation or maintenance of ICT products, networks, infrastructure, applications or other network and information systems, via assistance or active administration carried out either on customers' premises or remotely.
  • Managed security service providers — MSPs carrying out or providing assistance for activities relating to cybersecurity risk management.

Applying the standard rules: a large MSP is an essential entity; a medium-sized one is an important entity. Small MSPs generally fall outside the size cap unless a size-independent exception applies — for instance, if they are the sole provider of a service essential to critical societal or economic activity in a member state.

Separately, MSPs and MSSPs are named in Article 27's registry provisions, which required certain entity types to submit registration information by 17 January 2025.

Why MSPs get special attention

Three properties make the channel structurally risky:

  1. Privileged access at scale. RMM tooling, domain admin credentials and always-on VPNs into many customers simultaneously.
  2. Trusted paths. MSP traffic and MSP accounts are frequently excluded from the monitoring and conditional access rules applied to everyone else.
  3. Concentration. A regional MSP may serve most of a sector's mid-market. Its compromise is a sector event, not a customer event.

This is exactly the kind of dependency Article 22 coordinated risk assessments exist to examine, and exactly why Article 21(3) asks about the quality of a supplier's own cybersecurity practices rather than just the product they sell.

What the implementing regulation requires of them

Commission Implementing Regulation (EU) 2024/2690 applies to managed service providers and managed security service providers among other digital entity types. It sets technical and methodological requirements across the Article 21(2) measures — policies, risk management, incident handling, business continuity, supply chain security, access control, cryptography, human resources and testing — and specifies when an incident is considered significant for those entities.

For MSPs this is the most concrete compliance target available: it converts the directive's ten headings into an implementable control set. For MSP customers, it is a useful benchmark to assess against, even where the MSP argues it is out of the regulation's scope.

What to ask an MSP

Beyond the standard supplier questionnaire, MSP-specific questions:

  1. Which of your staff can access our environment, from where, and how is that list maintained?
  2. Is administrative access to our tenant separated from access to other customers? Demonstrate the isolation.
  3. Do you use dedicated, named privileged accounts per technician, or shared credentials?
  4. Is MFA enforced on every path into our environment, including RMM, jump hosts and break-glass accounts?
  5. Are your administrative actions in our environment logged, and can we receive those logs directly?
  6. How is your own RMM and management infrastructure secured, segmented and monitored?
  7. What happens to our access paths when one of your technicians leaves — what is the revocation SLA?
  8. Have you been compromised, or had a customer compromised through your access, in the last 24 months?
  9. Are you yourself in scope of NIS2? In which member state, in which category, and are you registered?
  10. Which of your subcontractors — including offshore support — can reach our environment?

Question 5 is the highest-value one. An MSP that cannot give you logs of what it did in your environment cannot support your own incident reporting obligations.

Contract terms specific to MSPs

Layer these on top of the core clause set:

  • Access inventory and review. A maintained list of individuals with access, reviewed at agreed intervals, with your right to require removal.
  • Log provision. Administrative action logs delivered to you or available on demand, with a defined retention period.
  • Incident notification, tightened. Include incidents affecting the MSP's own infrastructure and tooling, not only incidents in your environment — that is how supply chain compromise reaches you.
  • Change of subcontractor and offshoring notice, with a right to object.
  • Cooperation with your regulatory reporting, including provision of facts within your 24-hour and 72-hour windows.
  • Exit. Credential and access revocation timelines, return of configuration and documentation, and transition assistance. Nothing is worse than discovering at termination that only the MSP holds the keys.

If you are an MSP

The commercial reality is that customer due diligence will arrive before your supervisor does. Practical priorities:

  • Establish your own scope position — member state, category, registration status — and be able to state it in one paragraph. Customers now ask this in procurement.
  • Build the evidence pack once. Certification with a scope statement that actually covers the managed service, penetration test summaries, incident response evidence, access control attestations. Reusing one pack across hundreds of questionnaires is the difference between a sales advantage and a sales tax.
  • Fix the access story first. Per-technician named accounts, MFA everywhere, per-customer isolation, and customer-visible logging answer most of the hard questions in the list above.
  • Run your own supply chain programme. Your tooling vendors are your Article 21(2)(d) suppliers, and your customers will ask about them.
  • Get notification windows right. Committing to 24 hours across a customer base is an operational commitment, not a legal one. Make sure the on-call process can meet it.

MSPs that treat NIS2 readiness as a product feature, with evidence available on request, consistently spend less time in procurement than those that treat each questionnaire as a bespoke exercise.

Frequently asked questions

Are managed service providers in scope of NIS2?
Yes. ICT service management is an Annex I sector covering managed service providers and managed security service providers. Medium-sized MSPs are important entities and large ones are essential entities, subject to the usual size and exception rules.
Why does NIS2 single out MSPs?
Because they hold privileged access across many customers at once. A single compromised MSP can propagate into every client environment it administers, which makes it a concentration risk the directive addresses both directly and through customers’ supply chain duties.
Does using an MSP transfer NIS2 responsibility?
No. Outsourcing operations does not outsource the obligation. The in-scope entity remains accountable for its Article 21 measures and for the security of the relationship with the MSP under Article 21(2)(d).