Compliance

Does NIS2 apply to my company? A plain-language guide for Belgian businesses

Who falls under Belgium's NIS2 law, what it requires, which deadlines matter in 2027 and 2028, and why it affects you even if you're not in scope.

Belgium was one of the first EU countries to turn the NIS2 directive into national law, and it has been in force since 18 October 2024. Two years in, many business owners still aren't sure whether it applies to them, and those that are out of scope are discovering it affects them anyway. This guide explains the essentials in plain language.

What is NIS2?

NIS2 is the EU's updated cybersecurity directive. In Belgium it is implemented by the Act of 26 April 2024 and a Royal Decree of 9 June 2024. The supervisor is the Centre for Cybersecurity Belgium (CCB), which also acts as the national incident response team.

The goal is simple: organisations that society depends on must manage cyber risk properly, report serious incidents quickly, and have their management take responsibility for it.

Does it apply to you? Three questions

Your organisation is in scope when all three of these are true:

  1. You operate in one of the 18 listed sectors. Eleven are "high criticality" (for example energy, transport, banking, health, drinking water, digital infrastructure, ICT service management, public administration and space). Seven are "other critical" (for example postal and courier services, waste management, chemicals, food production and distribution, manufacturing of medical devices, electronics, machinery and vehicles, digital providers and research).
  2. You are established in Belgium.
  3. You are at least a medium-sized enterprise: 50 or more employees, or annual turnover and balance sheet above €10 million. Partner and linked companies count towards these thresholds, so a small subsidiary of a larger group can be in scope.

A handful of organisations fall under NIS2 regardless of size, such as DNS service providers, top-level domain registries, qualified trust service providers, providers of public electronic communications networks, and entities designated as critical.

The CCB offers a free NIS2 scope test on Safeonweb@Work that walks you through these questions.

Essential or important?

In-scope organisations are classified into two categories:

Essential entity Important entity
Who Large companies in high-criticality sectors (plus some designated entities) Medium companies in high-criticality sectors, and in-scope companies in the other critical sectors
Supervision Proactive: mandatory conformity assessments and inspections Reactive: the CCB acts when there are indications of non-compliance
Maximum fine €10 million or 2% of worldwide turnover €7 million or 1.4% of worldwide turnover

What does NIS2 require?

1. Register

In-scope organisations had to register on Safeonweb@Work by 18 March 2025 (digital infrastructure providers even earlier). If you've only now realised you're in scope, register as soon as possible. Late registration is better than none.

2. Take appropriate security measures

Article 21 of the directive lists the minimum measures. In practice, they boil down to:

  • A risk analysis and information security policies
  • Incident handling, business continuity, backups and crisis management
  • Supply-chain security: knowing and managing the risks of your IT suppliers
  • Secure development, maintenance and vulnerability handling (patching)
  • Regularly testing whether your measures actually work
  • Basic cyber hygiene and security awareness training
  • Encryption, access control and asset management
  • Multi-factor authentication and secured communications

None of this is exotic. It is what a well-run IT environment should already have, but NIS2 requires you to be able to prove it.

3. Report significant incidents

If a significant incident hits, you must notify the CCB on a tight timeline:

  • Within 24 hours: an early warning
  • Within 72 hours: an incident notification with an initial assessment
  • Within one month: a final report

That 24-hour window is short. Without logging, monitoring and a clear escalation path set up in advance, it is almost impossible to meet.

4. Involve management

The management body must approve the security measures, oversee their implementation and follow cybersecurity training. Directors can be held personally liable for non-compliance. NIS2 is explicitly not something to delegate entirely to the IT department.

The deadlines that matter now

Belgium lets organisations demonstrate compliance through the CyberFundamentals (CyFun®) framework developed by the CCB, through ISO/IEC 27001 certification, or through an inspection by the CCB. CyFun comes in three assurance levels: Basic, Important and Essential.

For essential entities:

  • By 18 April 2026 they needed at least a CyFun Basic or Important verification, or a contract with an accredited assessment body. ISO-route entities had to submit their scope, Statement of Applicability and latest internal audit.
  • By 18 April 2027, essential entities whose risk assessment calls for the CyFun "Essential" level must demonstrate it. Entities that can justify a lower level through their risk analysis don't need to reach "Essential". Following a recent CCB communication, entities that can't yet do so may instead submit a remediation plan showing they meet the "Important" level, with a plan to reach "Essential" by 18 April 2028.

Important entities have no mandatory periodic assessment, but a voluntary CyFun verification or ISO/IEC 27001 certification gives them a presumption of conformity if the CCB ever comes knocking.

On the horizon: in January 2026 the European Commission proposed targeted amendments to NIS2, including a new "small mid-cap" category. These are proposals, not law. The current Belgian rules apply until anything is formally adopted and transposed.

Out of scope? You're probably still affected

This is the part many SMBs miss. NIS2 obliges covered organisations to manage the security risks of their direct suppliers and service providers. If you deliver products or services to a company that falls under NIS2, expect:

  • Security questionnaires during procurement and contract renewal
  • Contract clauses about incident notification, MFA, backups and patching
  • Requests for evidence, such as a CyFun Basic self-assessment or an ISO 27001 certificate

Being able to answer those questions confidently is quickly becoming a commercial advantage, and failing them can cost you a customer.

Where to start

  1. Run the scope test on Safeonweb@Work, and check your group structure against the size thresholds.
  2. Do a gap assessment against CyberFundamentals. The Basic level is a practical starting point even if you're not in scope.
  3. Fix the high-impact basics first: MFA everywhere, tested backups, patching, logging, and an incident response plan with named contacts. Patching is often the quickest win: see how Go-Flow cut the time to fix critical vulnerabilities from 41 days to 3.
  4. Brief your management on their responsibilities and schedule their training.
  5. Document everything. Under NIS2, a measure you can't evidence might as well not exist.

The takeaway

NIS2 asks for what good security practice already looks like, and it expects you to be able to prove it. Whether you're directly in scope or a supplier to a company that is, the organisations that start with an honest gap assessment now will find the deadlines, and the questionnaires, far less stressful.

This article is general information, not legal advice. Check the CCB's NIS2 pages for the latest official guidance.

← All articles

Not sure where you stand?

Find your gaps before an attacker does

A free, no-obligation assessment maps your risks and gives you a prioritised plan, whether or not you work with us.