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 Requirements for Managed Security Service Providers
Implementing Regulation 2024 2690 / 2026-10-11

NIS2 Requirements for Managed Security Service Providers

Managed security service providers (MSSPs) are expressly covered by Commission Implementing Regulation (EU) 2024/2690. They must address the Annex's technical and methodological measures and assess significant incidents under Article 10 and the regulation's common criteria. The provider's privileged access, monitoring obligations and customer-facing response functions make contractual and operational boundaries especially important.

Identify the managed security service

Under NIS2, an MSSP provides or assists with activities relating to cybersecurity risk management. Services may include managed detection, incident response, security operations or specialist monitoring, but the precise contractual activities determine the role. A company buying managed security services is not the MSSP merely because it receives alerts. Identify the regulated legal provider, the systems it operates, the customers served and where responsibility transfers between provider and customer.

Apply the Annex to privileged operations

The Annex addresses risk assessment, access control, incident handling, business continuity, personnel practices, supplier relationships and the effectiveness of security measures. For an MSSP, administrator credentials, monitoring platforms and case-management systems may provide access across many customer environments. Protect these assets with appropriate authentication, segmentation, controlled changes and response procedures. Document who can use emergency access and how its use is reviewed.

Build clear customer incident coordination

An incident in the MSSP's own environment may affect its ability to monitor or defend many clients. A customer incident identified by the MSSP is not automatically a significant incident of the MSSP itself. Establish procedures distinguishing provider-service impact from events in customer systems, while meeting contractual escalation promises. Records should capture detection, affected services, customer communications and the evidence needed for each party to assess its own legal duties.

Use Article 10's actual thresholds

Article 10 covers both managed service providers and MSSPs. It treats complete unavailability of a managed security service for more than 30 minutes as one significant-incident case. Other conditions include limited availability affecting more than five percent of EU users or more than one million EU users, whichever is smaller, for more than one hour, and specified data integrity, confidentiality or authenticity compromises. Evaluate Article 3's common criteria and Article 4 recurring-incident rule as well, rather than treating one outage measure as the entire test.

Connect assurance to management oversight

Map each applicable Annex measure to an accountable control owner and evidence such as access reviews, detection exercises and recovery tests. Senior management should receive material risks involving shared security platforms, critical suppliers and unresolved incidents. Keep national notification channels and cross-border jurisdiction details accurate. Revisit the control mapping when adding new managed security services or changing how customer access works.

Points of clarification

Is every cybersecurity consultant an MSSP?

Not automatically. Assess whether the entity supplies or assists with cybersecurity risk-management services within the applicable NIS2 definition.

Does a customer incident always trigger an MSSP notification?

No. Determine the legal obligations and significance of the event for each entity, including the provider's own affected service.

Which provision gives MSSP-specific incident criteria?

Article 10 of Regulation 2024/2690 addresses both managed service and managed security service providers.

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.