An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesNIS2 for ICT Service Management Providers
High Criticality Sectors / 2026-10-11

NIS2 for ICT Service Management Providers

NIS2 Annex I lists managed service providers and managed security service providers as ICT service management entities operating on a business-to-business basis. The classification concerns services actually delivered to customers and the responsible legal entity. Regulation (EU) 2024/2690 further specifies requirements and incident significance criteria for these categories.

Which entities are included

A managed service provider actively manages or maintains ICT products, networks, infrastructure, applications or other systems for customers. A managed security service provider supplies or assists with cybersecurity risk-management activities. A company may offer both. Mere software resale or occasional advisory work should not be assumed to meet either definition without examining the service and contractual responsibilities.

Scope, classification and legal responsibility

The Annex I sector is expressly business-to-business. Identify the entity performing administration or security management, its clients and its ability to access customer environments. Apply NIS2 Articles 2 and 3 to determine scope and classification, with attention to exceptions and national implementation. The organisation should document which provider category each contracted service falls within.

Cybersecurity measures and operational risks

Remote access tools, privileged identities, deployment pipelines and monitoring platforms can expose multiple customer environments if compromised. Risk management should therefore address authentication, separation of customer access, secure updates, detection, continuity and supplier dependencies. Test how quickly a provider could contain misuse of its central management systems and notify affected customers.

Incident and sector-specific requirements

Implementing Regulation 2024/2690 expressly names managed and managed security service providers. Its Annex contains detailed technical and methodological measures, while Article 10 supplies provider-specific incident-significance conditions. These should be assessed alongside Article 3 common criteria and the NIS2 notification framework. A compromise detected at a customer is not automatically a reportable compromise of the provider's own service.

Governance and supporting evidence

Keep a service register, privilege reviews, operating control evidence, incident escalation responsibilities and customer communication plans. Distinguish contractual notices from regulatory notifications and preserve reliable event timelines. Senior management should oversee systemic supplier and access risks, with remediation owners and follow-up dates.

Points of clarification

Does every organisation in this sector fall under NIS2?

No. Assess the exact service, legal entity, Directive scope rules and relevant national law.

Does Annex I automatically mean essential entity status?

No. Apply Article 3 classification and relevant special rules.

Should scope decisions be documented?

Yes. Record the service category, legal basis, regulator and supporting evidence.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.