NIS2 compliance: what software and AI companies need to know

    NIS2, Directive (EU) 2022/2555, sets cybersecurity requirements for in-scope entities. NIS2 compliance depends on the national law that applies to your organisation, its services, size and sector, not simply whether it writes software.

    Keldyn Trust Centre sharing security frameworks and evidence with customers
    At a glance
    Directive
    Directive (EU) 2022/2555.
    Key date
    Member state transposition deadline was 17 October 2024. National laws vary in timing and detail.
    Applies to
    Essential and important entities, including some digital infrastructure and ICT service providers. Suppliers feel it through supply chain requirements.
    Incident reporting
    Early warning within 24 hours and notification within 72 hours for significant incidents.
    Keldyn's role
    Keeps security requirements and evidence close to engineering work. National law determines your obligations.
    On this page

    National laws and the transposition deadline

    The member state transposition deadline was 17 October 2024. National laws vary in timing and detail. Check the law and regulator in each relevant jurisdiction before deciding your obligations.

    Reporting a significant incident

    1. Within 24 hours
      Early warning

      Of becoming aware of the incident

    2. Within 72 hours
      Incident notification
    3. Within one month
      Final report

      Of the incident notification

    Check the applicable national procedure. Not legal advice.

    Essential and important entities

    NIS2 distinguishes essential and important entities. Classification depends on factors including sector, size and specific designations. Both categories have cybersecurity risk-management and incident-reporting duties, with different supervisory approaches.

    Digital infrastructure and ICT service management can be directly in scope. Cloud computing and managed service providers are examples; a software company should assess the services it actually provides rather than assume it is only a supplier.

    Supply chain security reaches software suppliers

    In-scope customers must consider supply chain security, including their direct suppliers and service providers. They may request evidence of secure development, access control, vulnerability handling and incident processes even when a supplier is not directly in scope.

    Cybersecurity risk-management measures

    • Risk analysis and information system security policies.
    • Incident handling, business continuity, backup and crisis management.
    • Supply chain security and secure acquisition, development and maintenance, including vulnerability handling.
    • Assessment of security measures, cyber hygiene and training.
    • Access control, asset management, cryptography and appropriate authentication.

    Incident reporting: 24 hours, 72 hours and one month

    For significant incidents, NIS2 sets an early warning within 24 hours of becoming aware, followed by an incident notification within 72 hours. A final report is due within one month of the incident notification. Assess significance, recipients and applicable national procedures before an incident happens.

    This guide is not legal advice. Confirm scope and reporting duties under the applicable national law with a qualified adviser.

    How Keldyn helps

    01

    Check the design

    Your coding agent maps your architecture. Keldyn builds a threat model and checks it against your frameworks before the build.

    Security by design and threat modelling →
    02

    Review changes

    Check AI-written code against your security and compliance requirements before it merges.

    AI code review and secure coding →
    03

    Prepare your evidence

    Evidence from your tools and your checks, ready for your auditor. Review the scope, risks and evidence with your team.

    Evidence and audit →

    Keldyn helps keep security requirements and evidence close to engineering work. National law determines your NIS2 obligations.

    Frequently asked questions

    Does NIS2 apply to software companies?

    It can. Digital infrastructure and ICT service management providers, including cloud and managed service providers, can be directly in scope. Other software suppliers may face customer requirements through supply chain security. Check services, sector, size and national law.

    What is the difference between essential and important entities?

    The categories depend on sector, size and specific designations. Both have risk-management and reporting duties, but supervisory approaches differ. Confirm your classification under national law.

    What are the NIS2 incident reporting timelines?

    For significant incidents, the directive sets an early warning within 24 hours of awareness and an incident notification within 72 hours. Confirm the applicable national procedures and reporting authority.

    Has NIS2 taken effect everywhere in the EU?

    The transposition deadline was 17 October 2024, but national laws vary in timing and detail. Check the relevant member state’s law rather than assuming a uniform implementation date.

    “You should be building to compliance rather than fixing to it.”
    Tim BrownTim Brown
    Co-Founder, Kyance
    Read the Kyance story →
    Trusted by teams at
    BoardlyKyanceVerinityHybrid AIMX3
    Qualified lead auditors on our team

    See how Keldyn fits your team.