Incident to report to a regulator?Incident to report? Intake Line

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

NIS2 BelgiumEssential 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
Requirements per topic and verdict
Topic Basic Security ControlsNIS2 Belgium Verdict
Governance
Management accountability Basic Security Controls: – NIS2 Belgium: 1 Only NIS2 Belgiumno specific requirement on the other side in the acts covered
Security policy Basic Security Controls: – NIS2 Belgium: 3 NIS2 Belgium asks morenational law departs from the Directive
Risk management
Risk assessment Basic Security Controls: – NIS2 Belgium: 3 NIS2 Belgium asks morenational law departs from the Directive
Review, audit and improvement Basic Security Controls: – NIS2 Belgium: 5 NIS2 Belgium asks morenational law departs from the Directive
Protection
Vulnerability handling Basic Security Controls: – NIS2 Belgium: 2 NIS2 Belgium asks morenational law departs from the Directive
Detection and response
Reporting to authorities Basic Security Controls: – NIS2 Belgium: 5 Only NIS2 Belgiumno specific requirement on the other side in the acts covered
Supervision and enforcement
Registration with authorities Basic Security Controls: – NIS2 Belgium: 2 Only NIS2 Belgiumno specific requirement on the other side in the acts covered
Penalties and liability Basic Security Controls: – NIS2 Belgium: 3 NIS2 Belgium asks morenational 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

Status

Reviewed against the official texts.

Included

  • NIS2 Directive (EU) 2022/2555 Articles 3, 20, 21, 23, 27, 29, 34 · 31 requirements
  • NIS2 Implementing Regulation 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 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 CSIRTComputer Security Incident Response Team (CCBCentre pour la Cybersécurité Belgique (Centre for Cybersecurity Belgium)); essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important 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 serviceAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2. providers, for incidents affecting their trust servicesAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2.)

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 entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only)

External assessment or certification

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Essential: periodic assessment against CyberFundamentalsCyberFundamentals Framework or ISO/IEC 27001Information Security, Cybersecurity and Privacy Protection: Information Security Management Systems: Requirements, or a CCBCentre pour la Cybersécurité Belgique (Centre for Cybersecurity Belgium) inspection. Important: voluntary (Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only (important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance. may opt in))

Review of the risk framework

Basic Security Controls: Not in the acts covered

NIS2 Belgium: Risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. and treatment plan at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. 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 entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important 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 entityAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance. has the power to ensure it complies with the law and is liable for failing to. If an essential entityAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. 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

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) · 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 incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 1.1 · 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 securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. policy covering at least the measures of paragraph 3.

    NIS2 Belgium, Article 30, paragraph 5

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) · 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 incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.1 · 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 securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. policy covering at least the measures of paragraph 3.

    NIS2 Belgium, Article 30, paragraph 5

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 cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures work.

    NIS2, Article 21(2)(f) · 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) · 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 securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. at planned intervals and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.3 · applies as in the Directive

  • Periodic conformity assessment Adds

    Applies to: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only (important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance. may opt in)

    Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. undergo a periodic conformity assessmentConformity Assessment Under Belgian NIS2, either by a conformity assessment bodyConformity Assessment Body Under Belgian NIS2 approved by the CCBCentre pour la Cybersécurité Belgique (Centre for Cybersecurity Belgium) against CyberFundamentalsCyberFundamentals Framework or ISO/IEC 27001Information Security, Cybersecurity and Privacy Protection: Information Security Management Systems: Requirements, or by a CCBCentre pour la Cybersécurité Belgique (Centre for Cybersecurity Belgium) inspection. Important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance. 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

  • Verification at 18 months, certification at 30 Adds

    Applies to: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. only

    Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important 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 CCBCentre pour la Cybersécurité Belgique (Centre for Cybersecurity Belgium) (or, for ISO/IEC 27001Information Security, Cybersecurity and Privacy Protection: Information Security Management Systems: Requirements, send the scope and statement of applicabilityAn ISO/IEC 27001 document recording the information security controls an organisation needs, why it needs them and whether they have been implemented. Controls are safeguards such as access restrictions or backup arrangements. The document also explains why any controls in the standard's Annex A reference list are unnecessary. It connects the organisation's security risks and treatment decisions with the safeguards selected for its information security management system.), and the certification within 30 months.

    NIS2 Belgium, Royal Decree of 9 June 2024, Article 22

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 vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. handling and disclosure.

    NIS2, Article 21(2)(e) · applies as in the Directive

  • Coordinated vulnerability disclosure policy Adds

    Adopt a coordinated vulnerability disclosureA process in which someone who discovers a security weakness reports it to the system owner or product supplier and works with them to address it. The parties coordinate investigation, a fix and the timing and content of any public disclosure, reducing the chance of exposing users before protection is available. A national cybersecurity centre may help coordinate when several parties are involved or contact fails. policy, as an eleventh minimum measure next to the ten of NIS2Directive on Measures for a High Common Level of Cybersecurity Across the Union.

    NIS2 Belgium, Article 30, paragraph 3, 11°

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 incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. to the national CSIRTComputer Security Incident Response Team (the CCBCentre pour la Cybersécurité Belgique (Centre for Cybersecurity Belgium)). The CSIRTComputer Security Incident Response Team forwards them to any sectoral authority, and forwards essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities.' notifications to the National Crisis Centre.

    NIS2 Belgium, Articles 34 and 35

  • 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) · 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) · applies as in the Directive

  • Intermediate report

    An intermediate report on status updates, when the CSIRTComputer Security Incident Response Team or authority asks for one.

    NIS2, Article 23(4)(c) · 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) · 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 CCBCentre pour la Cybersécurité Belgique (Centre for Cybersecurity Belgium) 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

  • Registry of digital providers

    DNSDomain Name System, TLDTop-Level Domain, 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 ENISAEuropean Union Agency for Cybersecurity 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 · 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 entityAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance. has the power to ensure it complies with the law and is liable for failing to. If an essential entityAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities. 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

  • Fines from EUR 500, doubled for repeats Stricter

    Fines start at EUR 500 and reach the NIS2Directive on Measures for a High Common Level of Cybersecurity Across the Union 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

  • 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

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.

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…