> Basic Security Controls vs NIS2 Belgium side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# Basic Security Controls vs NIS2 Belgium

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

[Basic Security Controls](https://grc.plus/regulation/basic-security-controls-government/)

[NIS2 Belgium](https://grc.plus/regulation/nis2/belgium/)Essential and important entities

## At a Glance

They differ on 8 of 8 topics. Each verdict names what it rests on; read the wording before relying on it.

- **Basic Security Controls** Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- **NIS2 Belgium** Asks more on 5 topics Alone on 3 topics More detailed on 0 topics

| Topic | Basic Security Controls | NIS2 Belgium | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Management accountability | Basic Security Controls: – | NIS2 Belgium: 1 | **Only NIS2 Belgium**no specific requirement on the other side in the acts covered |
| Security policy | Basic Security Controls: – | NIS2 Belgium: 3 | **NIS2 Belgium asks more**national law departs from the Directive |
| Risk management |  |  |  |
| Risk assessment | Basic Security Controls: – | NIS2 Belgium: 3 | **NIS2 Belgium asks more**national law departs from the Directive |
| Review, audit and improvement | Basic Security Controls: – | NIS2 Belgium: 5 | **NIS2 Belgium asks more**national law departs from the Directive |
| Protection |  |  |  |
| Vulnerability handling | Basic Security Controls: – | NIS2 Belgium: 2 | **NIS2 Belgium asks more**national law departs from the Directive |
| Detection and response |  |  |  |
| Reporting to authorities | Basic Security Controls: – | NIS2 Belgium: 5 | **Only NIS2 Belgium**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Registration with authorities | Basic Security Controls: – | NIS2 Belgium: 2 | **Only NIS2 Belgium**no specific requirement on the other side in the acts covered |
| Penalties and liability | Basic Security Controls: – | NIS2 Belgium: 3 | **NIS2 Belgium asks more**national law departs from the Directive |

## What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

- [Basic Security Controls](https://grc.plus/regulation/basic-security-controls-government/) GS_G2_Basic_Security_Controls, version 1.0 4 requirements

Status

Reviewed against the official texts.

Included

- [NIS2](https://grc.plus/regulation/nis2/) Directive (EU) 2022/2555 Articles 3, 20, 21, 23, 27, 29, 34 · 31 requirements
- [NIS2 Implementing Regulation](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/) Commission Implementing Regulation (EU) 2024/2690 Articles 3 to 14 · Annex · 17 requirements Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

National requirements

- [NIS2-wet](https://grc.plus/regulation/nis2/belgium/) Articles 13, 30, 34, 35, 39 to 42, 59 to 62
- Royal Decree of 9 June 2024

9 national requirements recorded, as departures from the Directive or additions to it. Everything else applies as the Directive has it.

Status

Reviewed against the official texts.

## Key Numbers

### Incident reports go to

Basic Security Controls: Not in the acts covered

NIS2 Belgium: National CSIRT (CCB); essential entities' reports also reach the National Crisis Centre

### First notice of an incident

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Without undue delay and in any event within 24 hours of becoming aware

### Incident notification

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust service providers, for incidents affecting their trust services)

### Intermediate report

Basic Security Controls: Not in the acts covered

NIS2 Belgium: On request

### Final report

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Within one month of the incident notification

### Deadline to have the measures in place

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Verified within 18 months and certified within 30 months of entry into force or identification (Essential entities only)

### External assessment or certification

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Essential: periodic assessment against CyberFundamentals or ISO/IEC 27001, or a CCB inspection. Important: voluntary (Essential entities only (important entities may opt in))

### Review of the risk framework

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Risk assessment and treatment plan at planned intervals, at least annually, and after significant incidents or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

### Register of third-party arrangements

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Directory of direct suppliers and service providers (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

### Registration with the authority

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Within five months of entry into force or identification (two months for digital providers); changes within two weeks

### Management body training

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Required

### Management body liability

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Responsible for ensuring compliance with the whole law; temporary ban for managers of essential entities

### Maximum fines

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Essential: EUR 500 to 10 million or 2%. Important: EUR 500 to 7 million or 1.4%. Doubled for a repeat within three years.

## Governance

### Management accountability

**Only NIS2 Belgium** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4

Nothing in the acts covered.

- Personal responsibility of managers Differs
  Anyone responsible for or legally representing an essential or important entity has the power to ensure it complies with the law and is liable for failing to. If an essential entity does not take the required measures in time, a manager at managing director or legal representative level can be temporarily barred from management duties.
  [NIS2 Belgium, Articles 60 and 61](https://grc.plus/regulation/nis2/belgium/#requirements)

### Security policy

**NIS2 Belgium asks more** national law departs from the Directive

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

Nothing in the acts covered.

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Network and information system security policy
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A security policy approved by the management body, reviewed at least annually and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 1.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive
- Risk analysis and information security policy Adds
  Carry out an all-hazards risk analysis and, based on it, draw up an information security policy covering at least the measures of paragraph 3.
  [NIS2 Belgium, Article 30, paragraph 5](https://grc.plus/regulation/nis2/belgium/#requirements)

## Risk management

### Risk assessment

**NIS2 Belgium asks more** national law departs from the Directive

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

Nothing in the acts covered.

- Risk analysis and security policies
  Policies on risk analysis and on information system security.
  [NIS2, Article 21(2)(a)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Risk management framework
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.1](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive
- Risk analysis and information security policy Adds
  Carry out an all-hazards risk analysis and, based on it, draw up an information security policy covering at least the measures of paragraph 3.
  [NIS2 Belgium, Article 30, paragraph 5](https://grc.plus/regulation/nis2/belgium/#requirements)

### Review, audit and improvement

**NIS2 Belgium asks more** national law departs from the Directive

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

Nothing in the acts covered.

- Assessing effectiveness
  Policies and procedures to assess whether the cybersecurity risk-management measures work.
  [NIS2, Article 21(2)(f)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Corrective measures
  An entity that finds it does not comply with the measures takes the necessary corrective measures without undue delay.
  [NIS2, Article 21(4)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Independent review
  Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers
  Independent reviews of network and information security at planned intervals and after significant incidents or changes.
  [NIS2 Implementing Regulation, Annex, point 2.3](https://grc.plus/regulation/nis2-implementing-regulation-2024-2690/#requirements) · applies as in the Directive
- Periodic conformity assessment Adds
  Applies to: Essential entities only (important entities may opt in)
  Essential entities undergo a periodic conformity assessment, either by a conformity assessment body approved by the CCB against CyberFundamentals or ISO/IEC 27001, or by a CCB inspection. Important entities may opt in to assessment by a body. Entities assessed by a body are presumed, until proven otherwise, to meet the Article 30 measures.
  [NIS2 Belgium, Articles 39 to 42; Royal Decree of 9 June 2024](https://grc.plus/regulation/nis2/belgium/#requirements)
- Verification at 18 months, certification at 30 Adds
  Applies to: Essential entities only
  Essential entities that choose assessment by a body obtain, within 18 months of entry into force or identification, a verification at basic or important level, based on their risk analysis, by a body approved by the CCB (or, for ISO/IEC 27001, send the scope and statement of applicability), and the certification within 30 months.
  [NIS2 Belgium, Royal Decree of 9 June 2024, Article 22](https://grc.plus/regulation/nis2/belgium/#requirements)

## Protection

### Vulnerability handling

**NIS2 Belgium asks more** national law departs from the Directive

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8

Nothing in the acts covered.

- Secure acquisition, development and maintenance
  Security in the acquisition, development and maintenance of network and information systems, including vulnerability handling and disclosure.
  [NIS2, Article 21(2)(e)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Coordinated vulnerability disclosure policy Adds
  Adopt a coordinated vulnerability disclosure policy, as an eleventh minimum measure next to the ten of NIS2.
  [NIS2 Belgium, Article 30, paragraph 3, 11°](https://grc.plus/regulation/nis2/belgium/#requirements)

## Detection and response

### Reporting to authorities

**Only NIS2 Belgium** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

Nothing in the acts covered.

- Notify the national CSIRT of significant incidents Differs
  Notify significant incidents to the national CSIRT (the CCB). The CSIRT forwards them to any sectoral authority, and forwards essential entities' notifications to the National Crisis Centre.
  [NIS2 Belgium, Articles 34 and 35](https://grc.plus/regulation/nis2/belgium/#requirements)
- Early warning
  An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.
  [NIS2, Article 23(4)(a)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Incident notification
  An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.
  [NIS2, Article 23(4)(b)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Intermediate report
  An intermediate report on status updates, when the CSIRT or authority asks for one.
  [NIS2, Article 23(4)(c)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive
- Final report
  A final report with a detailed description, the likely type of threat or root cause, the applied and ongoing mitigation and any cross-border impact. For an ongoing incident, a progress report at that time and the final report within one month of handling it.
  [NIS2, Article 23(4)(d) and (e)](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

## Supervision and enforcement

### Registration with authorities

**Only NIS2 Belgium** no specific requirement on the other side in the acts covered

Nothing in the acts covered.

- Register within five months Differs
  Register with the CCB within five months of entry into force or identification, giving the company number, address, contacts including IP ranges, sector and Member States served. Report changes within two weeks. Digital providers register within two months (Article 14).
  [NIS2 Belgium, Article 13](https://grc.plus/regulation/nis2/belgium/#requirements)
- Registry of digital providers
  DNS, TLD, domain name registration, cloud, data centre, content delivery, managed (security) service providers, marketplaces, search engines and social networks submit their details to the competent authority by 17 January 2025 for the ENISA registry, and report changes without delay and within three months. The authority is that of their main establishment or EU representative (Article 26).
  [NIS2, Article 27](https://grc.plus/regulation/nis2/#requirements) · applies as in the Directive

### Penalties and liability

**NIS2 Belgium asks more** national law departs from the Directive

Nothing in the acts covered.

- Personal responsibility of managers Differs
  Anyone responsible for or legally representing an essential or important entity has the power to ensure it complies with the law and is liable for failing to. If an essential entity does not take the required measures in time, a manager at managing director or legal representative level can be temporarily barred from management duties.
  [NIS2 Belgium, Articles 60 and 61](https://grc.plus/regulation/nis2/belgium/#requirements)
- Fines from EUR 500, doubled for repeats Stricter
  Fines start at EUR 500 and reach the NIS2 maximums, are doubled for a repeat of the same facts within three years, and have separate bands for information and supervision breaches.
  [NIS2 Belgium, Article 59](https://grc.plus/regulation/nis2/belgium/#requirements)
- No fines for public administration Narrower scope
  The fines and the temporary suspension or management ban do not apply to public administration entities. Other measures, such as warnings and binding instructions, still apply.
  [NIS2 Belgium, Article 62](https://grc.plus/regulation/nis2/belgium/#requirements)

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022. 23 topics where all apply the Directive as it is are not shown.

## More Comparisons

- [Compare Basic Security Controls](https://grc.plus/compare/basic-security-controls/)
- [Compare NIS2 Belgium](https://grc.plus/compare/nis2-belgium/)

Source: https://grc.plus/compare/basic-security-controls-vs-nis2-belgium/
