NIS 2 Compliance Management
NIS 2 Compliance Management
Manage NIS 2 obligations, cybersecurity risks, controls, incidents and supply-chain security across international operations in one structured GRC environment.
Request a demoWhat is NIS 2?
The NIS 2 Directive (EU) 2022/2555 establishes a common framework for a high level of cybersecurity across the European Union. It expands the scope of the original NIS Directive and introduces stronger requirements for cybersecurity risk management, incident reporting, business continuity, supply-chain security and management accountability.
NIS 2 is an EU directive that must be implemented through national legislation. Its requirements therefore operate through the relevant national laws and supervisory authorities of EU Member States. Although it is not a worldwide cybersecurity law, its impact can extend well beyond Europe through international operations, service relationships and global supply chains.
For multinational organisations, NIS 2 is an important part of a broader cybersecurity and regulatory compliance programme. Organisations need to understand where the directive applies, which national rules are relevant and how common security controls can be governed across different jurisdictions.
NIS 2: European regulation with international impact
NIS 2 primarily applies to organisations that meet the Directive's sector, service and size criteria and fall within the relevant jurisdictional rules. The location of an organisation, its establishments, the services it provides and its role in a critical supply chain all matter.
EU-based organisations
Entities established in EU Member States may be directly subject to the applicable national NIS 2 implementation law when they meet the relevant criteria.
International organisations
Non-EU organisations may be directly affected in specific circumstances, particularly for services subject to the Directive's jurisdictional rules and EU establishment or representative requirements.
Global suppliers and partners
Suppliers outside the EU may face cybersecurity requirements through contracts, supplier assessments and the supply-chain risk-management obligations of in-scope customers.
Direct legal applicability and indirect commercial impact are different. A supplier does not automatically become an entity directly regulated by NIS 2 simply because it serves an in-scope organisation.
Sectors covered by NIS 2
The Directive identifies 18 sectors across two broad groups: sectors of high criticality and other critical sectors.
Sectors of high criticality
- Energy
- Transport
- Banking
- Financial market infrastructure
- Healthcare
- Drinking water
- Wastewater
- Digital infrastructure
- ICT service management
- Public administration
- Space
Other critical sectors
- Postal and courier services
- Waste management
- Chemicals
- Food production and distribution
- Manufacturing
- Digital providers
- Research organisations
The precise scope depends on the service or activity provided, the relevant size thresholds, exceptions and national implementation rules. The sector list alone does not determine whether an organisation is in scope.
Essential and important entities
NIS 2 distinguishes between essential entities and important entities. Both categories have cybersecurity risk-management and incident-reporting obligations, but supervisory arrangements and enforcement differ.
Essential entities
Generally include organisations in designated highly critical sectors and other categories identified by the Directive and national legislation. They are subject to more intensive supervisory arrangements.
Important entities
Include other organisations meeting the applicable sector and size criteria. They are subject to NIS 2 obligations and supervisory oversight, including supervision following evidence or indications of non-compliance.
Classification should be assessed separately for the relevant legal entity, services and jurisdiction. Multinational groups should not assume that one classification automatically determines the position of every subsidiary or business unit.
Core NIS 2 cybersecurity requirements
Article 21 requires appropriate and proportionate technical, operational and organisational measures to manage risks to network and information systems. The measures should take account of the organisation's exposure to risks, size, likelihood and severity of incidents, and potential societal and economic impact.
1. Risk analysis and security policies
Establish documented risk analysis processes, information security policies, risk ownership and a systematic approach to managing cybersecurity risks.
2. Incident handling
Define processes for detecting, recording, assessing, responding to and learning from cybersecurity incidents.
3. Business continuity
Prepare for disruption through backup management, disaster recovery, crisis management and tested continuity arrangements.
4. Supply-chain security
Assess cybersecurity risks arising from suppliers and service providers, including the security of relevant contractual and operational relationships.
5. Secure systems and vulnerability management
Address security throughout the acquisition, development, operation and maintenance of systems, including vulnerability handling and disclosure.
6. Effectiveness of security measures
Establish policies and procedures to assess whether cybersecurity risk-management measures are implemented and effective.
7. Cyber hygiene and training
Implement appropriate cyber hygiene practices and cybersecurity awareness and training for relevant personnel.
8. Cryptography and encryption
Establish appropriate policies and procedures for the use of cryptography and, where appropriate, encryption.
9. Access and asset management
Manage assets, access rights and human resources security to reduce the risk of unauthorised access and misuse.
10. Multi-factor authentication
Use multi-factor authentication or continuous authentication solutions, secure communications and emergency communication systems where appropriate.
Management accountability and governance
NIS 2 makes cybersecurity a management responsibility. Management bodies must approve the cybersecurity risk-management measures and oversee their implementation. They must also undertake appropriate training and promote relevant training for employees.
For international groups, this means establishing clear accountability between group management, local legal entities, regional security functions and operational teams. Decisions, oversight activities, risk acceptance and remediation should be documented in a way that supports the applicable local obligations.
Incident reporting and response
NIS 2 introduces a staged reporting process for significant incidents. Organisations need clear escalation paths, defined responsibilities and the ability to assess whether an incident meets the applicable reporting criteria.
Early warning
Early warning after becoming aware of a significant incident.
Incident notification
A more detailed notification, including an initial assessment of severity and impact.
Final report
A final report, generally within one month after the incident notification.
The Directive also provides for an intermediate report where requested by the relevant CSIRT or competent authority. The applicable national reporting channel and any sector-specific rules must be checked before operational use.
International operations and jurisdiction
NIS 2 contains specific jurisdiction rules. As a general principle, an in-scope entity falls under the jurisdiction of the Member State in which it is established. The Directive also provides special rules for certain digital and ICT service providers, public electronic communications providers and public administration entities.
Certain digital providers, including cloud computing service providers, data centre service providers, content delivery network providers, managed service providers and managed security service providers, are generally subject to the jurisdiction of the Member State in which they have their main establishment in the EU. Where a relevant provider is not established in the EU but offers services in the EU within the applicable categories, the Directive provides for a legal representative in the Union.
- Assess the legal entity and service footprint in each relevant jurisdiction.
- Identify which national implementation laws and competent authorities apply.
- Determine whether special jurisdiction or representative rules apply to the service.
- Coordinate group-wide security controls while preserving local reporting and accountability requirements.
Global supply-chain security
One of the most important international dimensions of NIS 2 is supply-chain security. In-scope entities must address cybersecurity risks arising from their direct suppliers and service providers. This can influence organisations located outside the EU when they provide products or services to regulated customers.
Relevant considerations include supplier cybersecurity practices, secure development processes, service resilience, subcontracting arrangements, incident notification, vulnerability management, audit rights and the ability to manage dependencies.
Supplier assessment
Evaluate supplier security maturity, certifications, risk exposure and ability to meet security requirements.
Contractual requirements
Define security obligations, incident notification, audit rights, subcontracting and vulnerability handling.
Ongoing monitoring
Monitor supplier risks, service changes, security incidents, remediation and continuity arrangements.
How Cetbix GRC supports NIS 2 management
NIS 2 compliance requires more than policies and isolated technical controls. Organisations need to connect obligations to risks, controls, accountable owners, evidence, incidents and improvement activities.
Requirements management
Maintain a structured register of NIS 2 and relevant national requirements, with links to internal policies, processes and controls.
Risk management
Identify, assess and prioritise cybersecurity risks across entities, locations, systems and business services.
Control management
Document technical and organisational controls, responsible teams, implementation status and review cycles.
Evidence management
Connect policies, records, test results, approvals and other evidence to the requirements and controls they support.
Third-party risk
Structure supplier assessments, security requirements, remediation activities and ongoing reviews across the supply chain.
Management reporting
Provide visibility into risk exposure, control status, open findings and compliance progress across the organisation.
NIS 2 and international frameworks
NIS 2 can be managed alongside established international standards and cybersecurity frameworks. These frameworks can provide useful methods, control structures and evidence models, but none automatically establishes compliance with NIS 2 or every national implementation law.
ISO/IEC 27001
Provides an information security management system framework for managing information security risks, controls, responsibilities and continual improvement.
ISO/IEC 27002
Provides guidance on information security controls that can support the design and operation of NIS 2-related measures.
ISO 22301
Supports business continuity management, including preparedness, response, recovery and resilience.
ISO 31000
Offers principles and guidance for integrating risk management into organisational governance and decision-making.
NIST Cybersecurity Framework
Provides a widely used framework for understanding, assessing, prioritising and communicating cybersecurity risks.
CIS Critical Security Controls
Offers prioritised technical and organisational safeguards that can support practical cybersecurity improvement.
COBIT
Supports the governance and management of enterprise information and technology, including accountability and performance oversight.
DORA
Establishes digital operational resilience requirements for financial entities in the EU. Its relationship with NIS 2 should be assessed under the relevant sector-specific legal provisions.
Example: Mapping NIS 2 requirements to GRC controls
A structured mapping helps organisations demonstrate how legal requirements are translated into operational measures and verifiable evidence.
| NIS 2 topic | Example control | Evidence | GRC record |
|---|---|---|---|
| Risk analysis | Documented cybersecurity risk assessment | Risk register, assessment results, approvals | Risk and requirement |
| Incident handling | Incident response and escalation process | Incident records, exercise results, response plans | Process and evidence |
| Business continuity | Backup and recovery arrangements | Backup logs, recovery tests, continuity plans | Control and test |
| Supply-chain security | Security assessment of relevant suppliers | Supplier assessments, contracts, review records | Third-party risk |
| Access control | Role-based access and periodic access reviews | Access lists, review approvals, access logs | Control and evidence |
| Training | Cybersecurity awareness programme | Training records, attendance, awareness tests | Control and activity |
Practical example: Cybersecurity incident at a global IT supplier
An international organisation relies on an external IT service provider for a business-critical application. The provider experiences a cyber incident that disrupts service availability and may affect the confidentiality or integrity of data used by an EU-based regulated entity.
How a global GRC process can support the response
- Identify the dependency: Record the supplier, service, relevant legal entities, locations, business owners and affected systems.
- Assess the risk: Evaluate the impact on availability, integrity and confidentiality, including potential business consequences.
- Activate response processes: Assign incident ownership, follow escalation procedures and coordinate with internal and external stakeholders.
- Assess reporting obligations: Determine which regulated entities and national reporting regimes may be affected, and apply the relevant reporting timelines.
- Collect evidence: Link incident records, communications, supplier information, decisions and recovery test results.
- Track remediation: Assign corrective actions, owners and deadlines, and verify that agreed improvements are implemented.
A GRC platform can provide traceability between supplier risk, affected requirements, relevant controls, incident records and remediation activities across organisational boundaries.
A structured NIS 2 compliance workflow
Determine scope
Assess entities, services, sectors and jurisdictions to determine where NIS 2 applies.
Identify gaps
Compare existing processes and controls with applicable EU and national obligations.
Assess risks
Evaluate threats, vulnerabilities, dependencies and potential business impact.
Implement controls
Define measures, responsibilities, implementation plans and review cycles.
Monitor and evidence
Maintain evidence, test effectiveness and monitor outstanding actions.
Review and improve
Report to management, address findings and improve the security programme.
NIS 2 within the global regulatory landscape
Organisations operating internationally often need to manage multiple cybersecurity, privacy, operational resilience and sector-specific obligations at the same time. NIS 2 can form one part of a broader regulatory compliance architecture.
| Framework or regulation | Geographic or sector focus | Primary focus |
|---|---|---|
| NIS 2 | European Union | Cybersecurity and resilience of essential and important entities |
| DORA | European Union, financial sector | Digital operational resilience in financial services |
| GDPR | European Union, with certain extraterritorial reach | Personal data protection and privacy |
| NIST Cybersecurity Framework | Internationally used framework | Cybersecurity risk management and organisational resilience |
| ISO/IEC 27001 | International standard | Information security management systems |
| Sector-specific cybersecurity rules | Varies by country and industry | Additional requirements for regulated sectors and services |
These frameworks and regulations have different scopes and legal effects. A shared control environment can support coordinated management, but legal applicability and compliance must be assessed separately.
Frequently asked questions
Does NIS 2 apply worldwide?
No. NIS 2 is an EU directive implemented through national legislation. However, certain non-EU organisations may fall within its jurisdictional rules, and international suppliers may be indirectly affected through the supply-chain requirements of regulated customers.
Can a company outside the EU be directly affected?
Yes, in certain circumstances. For example, some digital service providers established outside the EU but offering relevant services within the EU may be subject to specific jurisdiction and legal representative requirements. The precise position depends on the service and applicable provisions.
Does NIS 2 apply to suppliers outside the EU?
A supplier outside the EU is not automatically directly regulated by NIS 2 simply because it supplies an in-scope entity. However, the regulated customer must manage relevant supply-chain risks, which can lead to contractual security obligations, assessments, audit rights and incident notification requirements for the supplier.
Do all EU Member States implement NIS 2 in exactly the same way?
No. The Directive establishes a common EU framework, but national legislation, competent authorities, registration procedures and certain implementation details can differ. Organisations operating across multiple Member States should assess the applicable national requirements.
Does ISO 27001 certification mean that an organisation is NIS 2 compliant?
No. ISO/IEC 27001 can provide a strong management-system foundation, but certification does not automatically demonstrate compliance with every NIS 2 or national implementation obligation. A requirement-by-requirement assessment is still necessary.
What is the relationship between NIS 2 and DORA?
DORA is a sector-specific EU regulation for financial entities. NIS 2 contains provisions addressing the relationship with sector-specific Union legal acts. Organisations in the financial sector should assess the relevant legal provisions rather than assume that one framework simply replaces the other.
Can GRC software guarantee NIS 2 compliance?
No software can guarantee legal compliance. A GRC platform can help structure requirements, risks, controls, responsibilities and evidence, but the organisation remains responsible for determining its obligations and implementing effective measures.
Manage NIS 2 across your organisation
Connect cybersecurity requirements, risks, controls, suppliers and evidence in a structured GRC environment. Support consistent governance across international operations and regulatory jurisdictions.
Contact usDisclaimer: This page provides general information about the NIS 2 Directive and its international implications. It does not constitute legal advice or a determination that a particular organisation is in scope. Applicability, classification, jurisdiction, reporting obligations and required measures must be assessed against the current applicable EU and national legislation and competent-authority guidance.