Upcoming Cybersecurity Obligations in Belgium: NIS 2 Act Takes Effect
Category: IP/IT/Data
The NIS 2 Directive has been transposed into Belgian law by the Act of 26 April 2024, which imposes a number of cybersecurity obligations on entities within its scope. Compared to the NIS 1 Directive, the NIS 2 Directive now covers a wider range of sectors and entities. The NIS 2 Act shall apply as of 18 October 2024.
I. Background
Directive (EU) 2016/1148 of 6 July 2016 concerning measures for a high common level of security of network and information systems, transposed into Belgian legal order by the Law of 7 April 2019 (NIS Directive), was one of the most important cybersecurity legislation, and imposed a number of cybersecurity obligations on a limited number of entities.
On 16 January 2023, Directive (EU) 2022/2555 of 14 December 2022 on measures for a high common level of cybersecurity (NIS 2 Directive) came into force and shall replace the NIS Directive as of 18 October 2024.
The NIS 2 Directive has a broader scope of application than the NIS 1 Directive.
The NIS 1 Directive covered 7 sectors, including energy, transport, banking, financial market infrastructures, healthcare, and water supply. However, the NIS 2 Directive significantly broadens the scope, expanding it to 18 sectors by including 12 additional sectors such as government services, food production, chemical industries, postal services, waste management, space, manufacturing of medical devices, and digital providers.
The NIS 2 Directive has been transposed into Belgian law by the Act of 26 April 2024 establishing a framework for the cybersecurity of networks and information systems of general interest for public security (the NIS 2 Act), which imposes a number of cybersecurity obligations on entities within its scope.
The NIS 2 Act comes into force as of 18 October 2024.
II.ENTITIEs in scope of NIS 2
II.1.Type of services provided and size
The NIS 2 Act applies if the organisation provides a service listed in Annex I or II and meets specific size criteria.
The relevant services are the following:
According to Article 3, §1,1° and 2° of the NIS 2 Act, all entities listed in Annexes I or II which either qualify as medium-sized enterprises or exceed the thresholds for medium-sized enterprises1 shall fall within the scope of that Act.
Accordingly, an entity shall fall under the scope of the NIS 2 Act if operates in a sector listed in Annexe I or Annexe II and:
has up to 250 employees, a turnover of up to EUR 50 million and/or a balance sheet total of up to EUR 43 million; or
exceeds these thresholds.
II.2. Other criteria
Regardless of its size, an organisation may also fall within the scope of the NIS 2 Act if:
it provides one of the following services: public electronic communications networks or services; trust services; or operates as a top-level domain registry or domain name system service provider; or
it is identified as an essential or important entity under the NIS 2 Act; or
it is a public administration entity which is (i) dependent on the federal state, (ii) dependent on federated entities, (iii) an emergency zone as defined by applicable law; or
it operates critical infrastructure within the meaning of the Act of 1 July 2011 on the security and protection of critical infrastructures2; or
it provides domain name registration services.
(see Article 3, §3 NIS 2 Act).
It should be noted that the list of sectors and/or subsectors falling within the scope of the NIS 2 Act may be extended by Royal Decree. The above criteria may therefore be subject to changes in the future and a periodical evaluation from time to time in this regard is therefore recommended.
iii. Essential or important entities
Under Articles 9, 10, and 11 of the NIS 2 Act, an entity may be classified as an essential or important entity, as outlined in the table below:
Type of Entity/Services | Essential? | Important? |
Annex I (Highly Critical Sectors) | Yes if it exceeds medium-sized thresholds or is identified as such by the CBB | yes if identified as such by the CBB |
Annex II (Other Critical Sectors) | Yes if identified as such by the CBB | Yes if identified as such by the CBB |
Trust Service Providers | Yes | No |
Top-level Domain Registries/DNS Providers | Yes | No |
Providers of public electronic communications networks or publicly available electronic communications services | Yes if medium-sized or larger | yes if identified as such by the CBB |
Public Administration (Federal) | Yes | No |
Public Administration (Federated Entities) | Yes if identified as such by the CBB | Yes if identified as such by the CBB |
Critical Infrastructure Operators | Yes | No |
Other Entities | Yes if identified as such by the CBB | Yes if identified as such by the CBB |
Essential entities face stricter requirements and shall be monitored more regularly and more strictly than important entities.
IV.Obligations under the NIS 2 Act
The main obligations under the NIS 2 Act include the following:
IV.1.Cybersecurity risk-management measures
Essential and important entities must take appropriate and proportionate technical, operational and organisational measures to manage the risks posed to the security of network and information systems which those entities use for their operations or for the provision of their services, and to prevent or minimise the impact of incidents on recipients of their services and on other services3.
These shall be based on an all-hazards approach that aims to protect network and information systems and the physical environment of those systems from incidents, and shall include at least the measures listed in Article 30 NIS 2 Act, i.e.:
policies on risk analysis and information system security;
incident handling;
business continuity, such as backup management and disaster recovery, and crisis management;
supply chain security, including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers;
security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure;
policies and procedures to assess the effectiveness of cybersecurity risk-management measures;
basic cyber hygiene practices and cybersecurity training;
policies and procedures regarding the use of cryptography and, where appropriate, encryption;
human resources security, access control policies and asset management;
the use of multi-factor authentication or continuous authentication solutions, secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate;
a coordinated vulnerability disclosure policy.
In that respect, the Centre for Cybersecurity Belgium (CBB) has developed a reference framework, “CyberFundamentals” including these measures which can be used for conformity assessment. More information can be found on the CyberFundamentals webpage, available via the following link: https://atwork.safeonweb.be/tools-resources/cyberfundamentals-framework.
IV.2.Reporting obligations
Essential and important entities must notify without undue delay to the CCB any incident that has a significant impact on the provision of their services (Article 34 NIS 2 Act).
Moreover, where appropriate, entities concerned shall notify, without undue delay, the recipients of their services of significant incidents that are likely to adversely affect the provision of those services.
The notification of significant incidents shall take place in several stages4.
In practice, notification is made through the procedure set out on the CCB website (https://ccb.belgium.be/en).
IV.3.Registration obligation
Entities in scope of the NIS 2 Act must register with the CCB within a specific deadline.
The deadline for registration depends on the type of entity (5 months in principle with some exceptions - e.g. data centres must complete the registration must by 18 December 2024 at the latest (see Articles 13- 14 NIS 2 Act)).
In practice, entities must fill in a registration form on the website https://atwork.safeonweb.be/.
IV.4.Training obligations
The management bodies of essential and important entities must approve cybersecurity risk management measures and oversee their implementation. If the entity breaches its obligations with regard to risk management measures, the management body shall be liable.
Moreover, members of the management bodies are required to undergo training to ensure they have sufficient knowledge and skills to assess cybersecurity risks and evaluate risk management practices, as well as their impact on the services provided by the entity (see Article 31 NIS 2 Act).
V. Sanctions
In case of non-compliance with the NIS 2 Act, administrative measures may be imposed (e.g. warnings, orders to make certain aspects of violations of the NIS 2 Act public, orders to cease and desist from engaging in conduct that violates the Act, etc.) as well as administrative fines ranging from 500 EUR to 10,000,000 EUR or 2% of the annual global turnover, whichever is higher (see Article 58-60 of the NIS 2 Act).
Should you have any questions in this regard, do not hesitate to reach out to one of the members of the IP/IT/Data protection team of Liedekerke on their individual e-mail address or via ip/it-team@liedekerke.com.
1 Under Article 2 of the Annex to Recommendation 2003/361/EC of 6 May 2003 concerning the definition of micro, small and medium-sized enterprises.
2 Meaning that the structure is an installation, system or part thereof, of Federal interest, which is essential to the maintenance of the vital functions of society, the health, safety, security or economic or social well-being of citizens, and the disruption or destruction of which would have a significant impact as a result of the failure of those functions.
3 Recital (81) of the NIS 2 Directive (to which the preparatory works for the NIS 2 Act refer) indicates in that respect that “in order to avoid imposing a disproportionate financial and administrative burden on essential and important entities, the cybersecurity risk-management measures should be proportionate to the risks posed to the network and information system concerned, taking into account the state-of-the-art of such measures, and, where applicable, relevant European and international standards, as well as the cost for their implementation.”
4For instance: within 24 hours of becoming aware of the significant incident, the entity shall submit an early warning; within 72 hours (24 hours for trust service providers) of becoming aware of the significant incident the entity shall submit an incident notification; a final report must be submitted no later than one month after the submission of the incident notification; etc.