Start with the common criteria in Article 3
Article 3 sets cross-provider significance conditions, including certain direct financial losses, suspected exfiltration of trade secrets, deaths or considerable damage to health, and successful malicious unauthorised access capable of causing severe operational disruption. Some triggers depend on consequences or credible grounds for suspicion, not only a measured outage duration. The incident team should gather financial, technical and operational evidence while facts remain incomplete.
Identify the correct provider-specific provision
Articles 5 to 14 add conditions for DNS providers, TLD registries, cloud services, data centres, CDNs, managed and managed security services, online marketplaces, search engines, social networking platforms and trust services. Provider definitions matter because a cloud platform and a managed service operator do not necessarily share the same availability tests. A business delivering more than one named service should assess each relevant provider function.
Avoid a universal 30-minute rule
Certain provider-specific provisions include a duration threshold, while others use user impact or other consequences without the same time minimum. For example, Article 10 includes complete unavailability of a managed service or managed security service for more than 30 minutes. It would be incorrect to apply that threshold automatically to every online platform or trust service. Store the actual legal condition alongside each alerting rule.
Consider recurring incidents under Article 4
Article 4 addresses recurring incidents with the same apparent root cause when its cumulative conditions are met. Incident aggregation therefore requires a way to relate separate events, preserve their impact and identify likely shared causes. A series of apparently minor events should not be dismissed before checking the repeated-incident provision. Equally, repeated events alone do not remove the need to apply its specific conditions.
Connect significance assessment to notification
Determining significance is different from completing the incident reporting workflow under NIS2 Article 23 and applicable national implementation. Assign ownership for early assessment, collect time-stamped evidence and record changes in the assessment as facts develop. Maintain provider-specific response playbooks and relevant competent-authority contacts. Retest procedures after exercises or real incidents.
Points of clarification
Is the implementing regulation the same as the NIS2 Directive?
No. It provides more detailed measures and significance tests for the provider categories named in its Article 1.
Do all regulated providers use identical incident thresholds?
No. The regulation includes common and provider-specific conditions.
Where can the applicable thresholds be checked?
Consult Articles 3 to 14 of Regulation (EU) 2024/2690 in the official EUR-Lex text.