Reed Smith Client Alerts

Key takeaways

  • Organisations need to assess if they fall within scope of NIS2 (see criteria below)
  • If so, they must take measures to comply with related cybersecurity requirements and reporting obligations by October 2024
  • Importantly, they must then notify the relevant EU member state regulator that they fall within scope of NIS2 by April 2025

Among the plethora of new EU cybersecurity laws, some require positive action to self-identify to EU member state regulators. There may be a common belief that under NIS2 (Directive EU 2022/2555 on Network Information Security) EU member states will identify organisations as being in scope. Under the preceding directive, NIS1, the approach towards identifying organisations that fell within its scope varied between EU member states and certain member states designated organisations that fell within its scope. While NIS2 appears to emphasise that EU member states must identify organisations in scope, it requires organisations themselves to determine whether they fall within its scope and self-identify with a relevant EU member state regulator.

What is the action required?

If your organisation falls within the scope of NIS2 (see the criteria below), it must assess its current cybersecurity measures against the requirements of NIS2 and fix any gaps, if necessary, to comply with NIS2 by October 2024 when NIS2 becomes law in EU member states. Your organisation will also need to notify the relevant EU member state regulator that it is within the scope of NIS2 before 17 April 2025. For example, the German bill on NIS2 implementation names the Federal Office of Information Technology, Systems and Telecommunication for this purpose. Digital infrastructure organisations caught by NIS2 (see B(viii) below) will need to notify the relevant EU member state regulator by 17 January 2025.