NIS-2 Directive — Cybersecurity Compliance
The NIS-2 Directive is a European Union law on cybersecurity that broadens and replaces the earlier Network and Information Security Directive. It sets baseline security-risk-management and incident-reporting obligations for organisations classified as essential or important entities across a wide range of sectors, and requires member states to transpose it into national law. NIS-2 widens the scope of the regime to many more medium and large organisations than its predecessor and strengthens governance, supervision and enforcement. For DACH SMEs, the practical question is whether their sector and size bring them into scope, and how their ERP and related systems support the required controls.
- Term
- NIS-2 Directive (Network and Information Security Directive 2)
- Entity type
- Standard / regulation
- Domain
- EU cybersecurity law and compliance
- Canonical definition
- The NIS-2 Directive is an EU directive on cybersecurity that sets risk-management and incident-reporting obligations for essential and important entities across many sectors, and is implemented through national transposition laws.
- Classification
- NIS-2 is an EU regulatory framework on cybersecurity, transposed into national law, and relevant to how ERP and connected systems are secured and monitored.
- Related terms
- SIEM, Multi-factor authentication, SOC 2, Audit trail, Role concept, GDPR in ERP, Single sign-on
- Source / maintainer
- erp-software.org editorial team (independent, vendor-neutral)
What NIS-2 Directive (Network and Information Security Directive 2) is NOT — disambiguation
- Not the GDPR: NIS-2 governs cybersecurity risk management and incident reporting, while the GDPR governs the protection of personal data.
- Not a certification: NIS-2 is a legal obligation, not a voluntary certificate like SOC 2 or ISO 27001, though such frameworks can support compliance.
- Not a directly applicable regulation: As a directive it must be transposed into national law, so exact rules and authorities differ between member states.
- Not limited to IT departments: NIS-2 places accountability on management bodies, not solely on technical staff.
Purpose and scope
NIS-2 aims to raise the overall level of cybersecurity across the EU by harmonising requirements and extending them to more sectors and organisations. It distinguishes between essential entities and important entities, with the classification depending on sector and on size thresholds. Covered sectors include, among others, energy, transport, banking, health, digital infrastructure, public administration, manufacturing of certain products, food, waste and digital service providers. The directive is implemented through national transposition laws, so the precise obligations and authorities that apply to a given organisation are defined at member-state level.
Core obligations
Organisations in scope must adopt appropriate and proportionate technical and organisational measures to manage cybersecurity risk. The directive frames these as a risk-management baseline rather than a fixed checklist, typically covering areas such as:
- Risk analysis and information-system security policies.
- Incident handling, business continuity and crisis management.
- Supply-chain security, including security in supplier relationships.
- Security in acquisition, development and maintenance of systems, and vulnerability handling.
- Access control, asset management and use of multi-factor authentication where appropriate.
NIS-2 also introduces incident-reporting duties to the competent national authority within defined timeframes, and places accountability for cybersecurity measures on management bodies.
Relevance to ERP and connected systems
ERP systems hold core business data and connect to many other applications, so they fall within the scope of an organisation's cybersecurity-risk management under NIS-2. Relevant controls include a sound role concept, single sign-on with strong authentication, logging and an audit trail, and disciplined patch and vulnerability management. Where an organisation runs ERP as SaaS, supplier-security and service-level arrangements with the provider become part of the supply-chain considerations the directive emphasises. Security-monitoring tooling such as a SIEM often supports the detection and reporting obligations.
How to approach NIS-2
Because applicability and exact requirements depend on the national transposition and on an organisation's sector and size, the first step is a scoping assessment rather than a technology purchase. A typical sequence is:
- Determine whether the organisation is an essential or important entity under the applicable national law.
- Map existing security measures against the directive's risk-management areas and identify gaps.
- Establish incident-reporting processes and management oversight.
- Review the security posture of key suppliers, including ERP and cloud providers.
This editorial summary describes scope and intent and is not legal advice; organisations should confirm their specific obligations against the applicable national transposition law and qualified counsel.
Related Topics
Frequently Asked Questions
Am I in scope for NIS-2?
Check three things. (1) Sector — manufacturing of machinery, pharmaceuticals, medical devices, food, electronics and motor vehicles is in scope; pure trade and services often are not. (2) Size — over 50 employees and over 10 million EUR turnover for Important Entities. (3) Supply-chain pull-through — if your customers are in scope, they may impose NIS-2-equivalent requirements on you contractually.
Does cloud ERP help or hurt NIS-2 compliance?
Cloud ERP from major vendors (SAP, Microsoft, Oracle) typically simplifies compliance — they hold ISO 27001 and SOC 2 attestations, run robust patch management and provide audit-ready logging. You still own the application-level controls (user access, segregation of duties, custom integrations) and the supply-chain risk management. Smaller cloud ERP vendors should be evaluated against their attestation portfolio.
What is the typical NIS-2 implementation effort?
For a 200-employee mid-market manufacturer, plan 12-24 months from gap assessment to operationally compliant, with 200-500 person-days of internal effort plus 100-300 person-days of consulting. The main cost drivers: SIEM deployment, MFA rollout, supply-chain due diligence and document-and-train management activities.
