Belgium CyberFundamentals: every control, and what you already have

44 controls 35 frameworks share controls with it Belgium verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

Belgium CyberFundamentals Framework Evidence & Implementation Kit

44 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

If you run	Shared controls
NIST Cybersecurity Framework 2.0	44	measure it →
AWWA Cybersecurity Guidance for the Water Sector (American Water Works Association)	14	measure it →
API 1164	13	measure it →
ISO/IEC 27400:2022	11	measure it →
ASD Strategies to Mitigate Cyber Security Incidents	10	measure it →
ISO/IEC 27011:2024	9	measure it →
ISO/IEC 27010:2015	8	measure it →
APPI	7	measure it →
IEC 62351	7	measure it →
ASIS SPC.1-2009	6	measure it →
Barbados Data Protection Act 2019	6	measure it →
AML/CTF Act 2006 (Australia)	4	measure it →

Every control

Code	Control	Also in
`BE-CF-01`	Account management and provisioning	7
`BE-CF-02`	Access enforcement and least privilege	10
`BE-CF-03`	Multi-factor authentication requirements	9
`BE-CF-04`	Remote access controls	1
`BE-CF-05`	Wireless access restrictions	1
`BE-CF-06`	Identity proofing and verification	7
`BE-CF-07`	Boundary protection and segmentation	1
`BE-CF-08`	Cryptographic protection of data	12
`BE-CF-09`	Denial-of-service protection	1
`BE-CF-10`	Transmission confidentiality and integrity	1
`BE-CF-11`	Session management controls	1
`BE-CF-12`	Network monitoring and defense	1
`BE-CF-13`	Risk assessment procedures	15
`BE-CF-14`	Vulnerability scanning and management	5
`BE-CF-15`	Security categorization	13
`BE-CF-16`	Threat intelligence integration	3
`BE-CF-17`	Continuous monitoring strategy	15
`BE-CF-18`	Incident response planning and testing	1
`BE-CF-19`	Incident handling and containment	1
`BE-CF-20`	Incident reporting and notification	9
`BE-CF-21`	Forensic analysis capabilities	9
`BE-CF-22`	Lessons learned and improvement	9
`BE-CF-23`	Baseline configuration establishment	6
`BE-CF-24`	Configuration change control	2
`BE-CF-25`	Security impact analysis	6
`BE-CF-26`	System component inventory	6
`BE-CF-27`	Software usage restrictions	1
`BE-CF-28`	Audit event logging and storage	4
`BE-CF-29`	Audit record review and analysis	4
`BE-CF-30`	Time synchronization	1
`BE-CF-31`	Audit log protection and retention	4
`BE-CF-32`	Accountability and non-repudiation	2
`BE-CF-33`	Asset management and data flow mapping	2
`BE-CF-34`	Business environment	1
`BE-CF-35`	Cybersecurity governance and policy	1
`BE-CF-36`	Supply chain risk management	1
`BE-CF-37`	Awareness and training	2
`BE-CF-38`	System maintenance	1
`BE-CF-39`	Data security lifecycle management	1
`BE-CF-40`	Recovery planning	1
`BE-CF-41`	Recovery improvements	1
`BE-CF-42`	Recovery communications	1
`BE-CF-43`	Assurance level selection and scoping	1
`BE-CF-44`	NIS2 alignment	1

Tell me when Belgium CyberFundamentals files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What an auditor will ask you to produce

The artefacts named on the failure modes this framework speaks to.

Incident response plan and playbooks
Tabletop exercise reports
Incident ticket history with timelines
Forensic toolkit and chain-of-custody log
Post-incident review minutes
escalation matrix
Access control policy and standard
Joiner/mover/leaver workflow records
Role and entitlement matrix
Quarterly access review attestations

How programmes fail on this

Failure modes named by this framework and others. Each opens the full record.

Unclear escalation thresholds named by 5 frameworks
Lessons learned never closed out named by 4 frameworks
Shared or generic accounts retained named by 4 frameworks
Forensic readiness lacking outside core systems named by 4 frameworks
Stale or dormant accounts not deprovisioned named by 4 frameworks
Playbooks untested for major scenarios named by 4 frameworks

What this page is

A control-level reference for Belgium CyberFundamentals, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition