---
title: "NIS2 registration with the CCB | Pitch, European law firm"
description: "Whoever falls under the Belgian NIS2 law must register with the Centre for Cybersecurity Belgium and report changes within two weeks."
url: https://pitch.law/academy/nis2-registration-with-the-ccb
---

[pitch](https://pitch.law/)[Academy](https://pitch.law/academy)[Data](https://pitch.law/academy/guides/topics/information-technology)

# NIS2 registration with the CCB

Whoever falls under the Belgian NIS2 law must register with the Centre for Cybersecurity Belgium and report changes within two weeks. Who, when, which details to give and what comes next.

Pitch prepares your NIS2 registration with the Centre for Cybersecurity Belgium. Every essential or important entity registers within five months of the law entering into force or of an identification, giving its name, enterprise number, contact details, IP ranges and sector. Changes are reported within two weeks (Article 13).

- - By [Bart Lieben](https://pitch.law/team/bart-lieben), Attorney-at-Law
  - 21 November 2026

- Updated

  21-11-2026

Part of your goal: [NIS2: does it apply to your company?](https://pitch.law/goals/nis2)

## The legal framework

Registering is the first concrete duty under the Belgian [NIS2 law of 26 April 2024](https://www.ejustice.just.fgov.be/eli/wet/2024/04/26/2024202344/justel). It follows from [Article 3 of Directive (EU) 2022/2555](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32022L2555#art_3), which has Member States draw up a list of essential and important entities. In Belgium the Centre for Cybersecurity Belgium (CCB) is the national cybersecurity authority and registration runs through the CCB's platform, [Safeonweb@Work](https://atwork.safeonweb.be). If you are not sure you have to register, start with [Does NIS2 apply to my company?](https://pitch.law/academy/does-nis2-apply-to-my-company).

### Who has to register

Essential entities, important entities and entities that provide domain name registration services register with the CCB, following the practical rules the CCB sets (Article 13(1) of the law). For an entity in scope, registering is therefore not optional. If you already give part of this information to a sectoral authority under a legal obligation, you complete it with that authority (Article 13(2)).

### When

Within five months of the law entering into force, or of the CCB identifying you as a special entity (Article 13(1); Article 11). The law entered into force on 18 October 2024, so for entities already in scope then, the period ran until 18 March 2025. For a company that comes into scope later, for example through growth, Article 13 does not expressly say by when it must register. Do not wait: register straight away, because the law puts the duty on every entity that falls under it.

### Which details

You give at least (Article 13(1)):

- your name and your registration number in the Crossroads Bank for Enterprises (or an equivalent registration in the European Union);
- your address and current contact details, with e-mail address, IP ranges and telephone number;
- where applicable, your sector and subsector from Annex I or II;
- where applicable, the Member States in which you provide services that fall under the law.

The King can add to that list. You keep the details up to date: report any change without delay and in any case within two weeks of the change (Article 13(3)). Think of a new IP range, another telephone number or a new contact person.

### Extra details for digital providers

DNS service providers, top-level domain registries, entities providing domain name registration services, providers of cloud computing, data centres, content delivery networks, managed services and managed security services, and providers of online marketplaces, search engines and social networks give additional details (Article 14(1)). These include the address of the main establishment and other establishments in the Union, or the representative if the provider is established outside the Union, and the IP ranges. You report changes to these without delay and in any case within three months (Article 14(2)).

### What comes next

Registering is the start. The following then apply, among others:

- **The cybersecurity measures of Article 30**, based on a risk analysis and an information security policy.
- **The duty to report significant incidents** (Articles 34 and 35): an early warning within 24 hours, an incident notification within 72 hours and a final report no later than one month after that notification. The report goes to the national CSIRT.
- **The assessment of your compliance**: required for essential entities, voluntary for important ones (Articles 39 and 41). See [CyberFundamentals and NIS2](https://pitch.law/academy/cyberfundamentals-cyfun-and-nis2).
- **Training and responsibility of the management body** (Article 31).

## In practice

A medium-sized transport company in Mechelen falls under Annex I. It appoints one person to follow the registration, gathers the details (enterprise number, address, e-mail address, IP ranges, telephone number, sector) and registers through the CCB's platform. It sets a calendar reminder for the two-week period for changes.

A cloud provider with its head office in Ghent also gives the Article 14 details. If it moves a data centre and gets new IP ranges, it reports that change within three months.

A company that sees its size pass the medium-sized ceilings registers as soon as it knows it falls under the law, not after the next annual accounts.

An internal register holds the details, the contact person and the date of the last change. If you have questions on scope, a group structure or a joint registration, we help with a short [scope analysis and a registration plan](https://pitch.law/solutions/nis2-cybersecurity-compliance).

## Frequently asked questions

### Does each entity register separately, or the group together?

The duty rests on each entity that falls under the law. The CCB sets the practical rules for registration. With several entities, check with the CCB how to register them, and record who is responsible for each.

### Does registration prove that we comply with NIS2?

No. Registering is a duty to report who you are. Whether you take the measures of Article 30 is a separate question, assessed under Article 39 or 41.

### What if I do not register?

Registering is a legal duty (Article 13). For breaches of the law the CCB can impose administrative measures, such as warnings and binding instructions (Article 58). The other sanctions the law provides are in [NIS2 fines and director liability](https://pitch.law/academy/nis2-fines-and-director-liability). So register at once, and record how you reached your conclusion if you doubted that the law applied to you.

### What if my details change?

Report every change without delay and in any case within two weeks (Article 13(3)). For the extra details of digital providers it is within three months (Article 14(2)).

## How this connects

The step after registration is the [assessment of your compliance with CyberFundamentals or ISO/IEC 27001](https://pitch.law/academy/cyberfundamentals-cyfun-and-nis2). For incidents the [data breach workflow](https://pitch.law/technologies/breach-response-workflow) helps, and your [processing register](https://pitch.law/technologies/privacy-register) shows which personal data sits in the affected systems. See also the [NIS2 page under goals](https://pitch.law/goals/nis2). Want a quick first indication? Try our [free NIS2 check](https://pitch.law/checks/nis2).

## In short

- Registration is a duty of every entity in scope
- Within five months of the law entering into force or of an identification
- Changes are reported within two weeks
- Digital providers give extra details

## Related solutions

- [Solutions](https://pitch.law/solutions/nis2-cybersecurity-compliance)
  ### [NIS2 Cybersecurity Compliance](https://pitch.law/solutions/nis2-cybersecurity-compliance)
  [Are you an essential or important entity under the Belgian NIS2 law, and what does that ask of your board, your suppliers and your incident handling? We answer the legal side and keep the evidence in order.](https://pitch.law/solutions/nis2-cybersecurity-compliance)

## Our proprietary Legal Tech

- [Technology](https://pitch.law/technologies/breach-response-workflow)
  ### [Data Breach Handling](https://pitch.law/technologies/breach-response-workflow)
  [A GDPR Article 33 and 34 workflow with a 72-hour countdown, a reference per breach and a structured notification to the supervisory authority, approved by a lawyer.](https://pitch.law/technologies/breach-response-workflow)
- [Technology](https://pitch.law/technologies/privacy-register)
  ### [Records of Processing and Compliance Registers](https://pitch.law/technologies/privacy-register)
  [One register engine for the GDPR record of processing activities and for the AI Act, NIS2 and DORA registers, with article references, evidence and attorney or DPO approval.](https://pitch.law/technologies/privacy-register)

## More in Data

- ### [Children Online: the EU KIDS Act Proposal and Age Verification](https://pitch.law/academy/children-online-kids-act-and-age-verification)
  [What the Digital Services Act already requires to protect minors, what the EU KIDS Act proposal of 17 September 2026 would add for social networks, video platforms, games, app stores and chatbots, and how the EU age verification framework fits in.](https://pitch.law/academy/children-online-kids-act-and-age-verification)
- ### [The Cloud and AI Development Act: sovereignty rules for cloud and AI procurement](https://pitch.law/academy/cloud-and-ai-development-act)
  [What the Commission's proposal for a Cloud and AI Development Act would require of cloud providers that sell to the public sector, of contracting authorities, and of bidders for cloud and AI contracts, and how it sits next to the Data Act and the procurement Directive.](https://pitch.law/academy/cloud-and-ai-development-act)
- ### [Cyber Resilience Act III: importers, distributors, open source and contracts](https://pitch.law/academy/cyber-resilience-act-importers-distributors-open-source)
  [The duties of importers, distributors and authorised representatives under Articles 18 to 23 of Regulation (EU) 2024/2847, when a reseller becomes a manufacturer, how free and open-source software and its stewards are treated, and the clauses that follow.](https://pitch.law/academy/cyber-resilience-act-importers-distributors-open-source)
- ### [Cyber Resilience Act I: which products are caught, and in which class](https://pitch.law/academy/cyber-resilience-act-products-and-classes)
  [How to tell whether hardware or software you sell falls under Regulation (EU) 2024/2847, whether it is a default, important (class I or II) or critical product, and which conformity route follows from that, with the dates up to 11 December 2027.](https://pitch.law/academy/cyber-resilience-act-products-and-classes)
- ### [Cyber Resilience Act II: vulnerability handling and reporting since 11-09-2026](https://pitch.law/academy/cyber-resilience-act-vulnerability-handling-and-reporting)
  [What manufacturers must report under Article 14 of Regulation (EU) 2024/2847 since 11 September 2026, within 24 hours, 72 hours, 14 days and one month, and the vulnerability handling duties of Annex I, Part II, that follow from 11 December 2027.](https://pitch.law/academy/cyber-resilience-act-vulnerability-handling-and-reporting)
- ### [Cyber incidents across borders: the Cyber Solidarity Act](https://pitch.law/academy/cyber-solidarity-act)
  [What Regulation (EU) 2025/38 sets up, the European Cybersecurity Alert System, the Cybersecurity Emergency Mechanism with the EU Cybersecurity Reserve and the incident review mechanism, how a company hit by a major incident can benefit, and what it means for managed security service providers.](https://pitch.law/academy/cyber-solidarity-act)

## Let’s talk

Tell us what you’re working on. We’ll get the right person on it and reply within one business day. The first chat is free.

[Schedule a meeting](https://pitch.law/schedule)
