NIS2 covers more sectors than before and divides activities into two main categories: highly critical and Other critical sectors. These are listed in the Annexes to the Directive (Annexes I and II) and form the basis for which organisations are subject to the requirements.
Even if your organization is not classified as “critical” per se, you can still be affected. Many organisations covered by NIS2 will need to set clearer requirements its suppliers and partners, particularly with regard to cybersecurity and supply chain risk management.
NIS2 divides organizations into two categories:
The basic safety requirements are essentially the same for both categories, but the degree of Supervision, follow-up and sanctions differ.
The category of an organization is determined, among other things, by nature and size of the business;. Factors such as number of employees, turnover and balance sheet — according to EU SME definitions — often play a decisive role in the assessment.
The NIS2 Directive defines a total 18 sectors which may be subject to cybersecurity and incident reporting requirements. These are divided into two categories (Annex I and Annex II) and include, among others, essential services, digital infrastructure, public administration and IT-related services.
These sectors are central to social and economic functioning, and are directly affected by NIS2.
In addition to the above, NIS2 also covers additional sectors considered important to the broader societal and economic infrastructure:
NIS2 sharpens the expectation that you will have a structured cybersecurity work. In practice, this is often about.
Risk Management & Safeguards
Policies, risk analyses, protections, procedures and controls commensurate with the level of risk.
Incident management & reporting
Ability to detect, manage and report incidents according to clear processes.
Management Responsibility & Governance
A clearer responsibility in the organisation to ensure that the safety work is actually carried out and followed up.
Continuity & Recovery
Plans to keep operations running and restore in case of serious incidents (backup/DR, crisis management, procedures).
— in 4 easy steps
1) Assess scope
Find out if you (or your customers) are covered — and what parts concern you.
2) Map the current situation
Identify risks, critical assets, dependencies and the biggest gaps.
3) Introducing measures and working methods
Build processes for risk management, incident management, access, continuity, and vendor governance.
4) Follow up and improve on an ongoing basis
Measure, test, revise and strengthen security over time — so that it becomes part of everyday life.
We help MSPs and IT organizations translate requirements to practical implementation: from the current situation and structure to the choice of tools, implementation and working methods that last over time — focusing on creating impact in operations, support and control.