Identify a managed service rather than generic IT advice
The NIS2 definition of managed service provider covers an entity that supplies services related to installation, management, operation or maintenance of ICT products, networks, infrastructure, applications or other network and information systems through assistance or active administration, on premises or remotely. A one-off consulting engagement does not automatically satisfy the definition. Assess the contracted services and actual operational responsibilities, including whether the provider can change or administer customer systems.
Treat customer access as a central risk
Managed service providers may hold privileged access to many customer environments. Compromise of a remote management platform, support identity or software deployment workflow can spread consequences across several organisations. The Annex's measures on access control, secure development, vulnerability handling and supplier security should be implemented in ways that reflect this concentration of trust. Use least privilege, accountable changes, secure credentials and monitoring suitable for the service architecture.
Coordinate incident response with customers
Provider incidents can have consequences for services it operates and for the customers relying on them. Contractual notice duties, regulatory reporting and technical containment can differ. Prepare procedures that identify who assesses an incident against legal significance criteria, who contacts customers, and which team controls remediation in shared environments. Time-stamped evidence should distinguish an internal MSP system outage from an incident that disrupts customer services.
Apply Article 10 incident criteria
Article 10 of Implementing Regulation 2024/2690 contains significant-incident criteria for managed service and managed security service providers. Examine those alongside Article 3 common criteria and Article 4 recurring incidents where applicable. Record the providers' own service impact, affected customers, incident duration and material consequences. Do not replace the regulation's tests with an unsupported rule that any single customer alert is necessarily a reportable NIS2 incident.
Show effective management oversight
Create a control inventory mapped to the Annex and demonstrate that remote access, supplier dependencies, continuity and security monitoring are tested. Track serious findings to named remediation owners. Identify the relevant Member State jurisdiction and national reporting channels. Present the management body with service-based risk, material exceptions and evidence of improvement, rather than a list of security tools purchased.
Points of clarification
Are these requirements relevant to all NIS2 entities?
No. Regulation 2024/2690 applies to the specified categories of providers in its Article 1.
Are there provider-specific incident criteria?
Yes. Article 10 supplies provider-specific significance conditions alongside other applicable provisions.
Where should the official text be checked?
Consult the operative articles and Annex of Regulation 2024/2690 on EUR-Lex.