What Is CyberFundamentals (CyFun) for Belgian IT Teams? — Integrations & APIs article by Rui Codex

CyberFundamentals (CyFun) is the cybersecurity framework from the Centre for Cybersecurity Belgium (CCB) that helps organisations put NIS2-style security measures into practice. It is built on the NIST Cybersecurity Framework and offers Basic, Important and Essential levels, so IT teams can scope controls to their actual risk.

Key takeaways

  • CyFun turns the security expectations of Belgium's NIS2 law into a structured set of controls that IT teams can assess and document.
  • The assurance level you target should follow your organisation's NIS2 classification and risk profile, not the level a supplier prefers.
  • A CyFun assessment is only as useful as the asset inventory behind it, so start with systems, not policies.
  • Integrations, legacy platforms and third-party access are where most gaps appear in practice.
  • Technical implementation support can close gaps, but it does not replace legal, compliance or audit advice.

What is CyberFundamentals (CyFun) and why does NIS2 reference it?

CyFun is a practical cybersecurity framework developed by the Centre for Cybersecurity Belgium, which is the national cybersecurity authority. It takes the structure of the NIST Cybersecurity Framework and translates it into concrete, numbered security measures that a Belgian organisation can check against its own environment.

The NIS2 Directive requires essential and important entities to take appropriate and proportionate technical, operational and organisational measures to manage cybersecurity risk. The directive is the binding text, and it does not list individual controls. You can read the obligations in the official text of Directive (EU) 2022/2555 on EUR-Lex. CyFun fills the gap between that principle and daily engineering work by describing what good practice looks like in measurable terms.

For IT teams, the value of the framework is its vocabulary. Instead of debating whether a control is 'in scope', you can map each measure to an asset, an owner and evidence. Official guidance and the framework documents are published by the Centre for Cybersecurity Belgium, and those documents should be the reference for your interpretation.

Tip: Download the current framework version from the CCB directly and record its version number in your assessment file. Controls get revised, and an assessment against an outdated version is hard to defend.

Which CyFun level fits your organisation?

The level you target determines how many measures apply and how the result is verified. The framework distinguishes Basic, Important and Essential levels. Choose the level that matches your NIS2 classification and your realistic threat exposure, and confirm the choice with your regulator-facing advisers.

Each level is a trade-off. A higher level gives stronger assurance and a more credible story for customers and authorities, but it also means more evidence, more monitoring and more ongoing maintenance. A lower level is cheaper to reach but can leave gaps in exactly the systems that matter most to your operations.

CriterionBasic-oriented approachEssential-oriented approach
Evidence effortLighter, focused on core controlsHeavier, covers more controls and documentation
Ongoing maintenancePeriodic reviewContinuous monitoring and regular re-assessment
Fits best whenLimited scope and low exposureCritical services and high dependency on digital systems
Tip: Do not pick a level based on what a vendor certifies. Pick it based on the services your organisation actually delivers and the systems those services depend on.

How do IT teams run a CyFun assessment?

IT teams run a CyFun assessment in four stages: scope, inventory, measure and evidence. Each stage depends on the one before it, so skipping the inventory is the most common reason assessments produce an inaccurate picture.

  1. Define the scope by listing the services, business units and sites covered by NIS2.
  2. Build an asset inventory of servers, cloud tenants, endpoints, identity providers and external connections that support those services.
  3. Assess each applicable measure against the inventory, recording a status and a named owner.
  4. Collect evidence such as configuration exports, access reviews, backup restore tests and incident procedures.

The evidence stage is where teams underestimate the effort. A policy document shows intent, but an assessor or auditor needs proof that the control runs. Automate evidence collection where you can, for example by exporting identity-provider logs on a schedule, rather than gathering screenshots the week before a review.

Common trade-offs appear here. Manual assessments are cheap to start but drift out of date within months. Tool-driven assessments stay current but need integration work and someone to maintain them. For most teams the practical answer is a spreadsheet for scope and ownership, with automated feeds for the technical evidence.

Where do integrations and legacy systems create gaps?

Integration points and legacy systems are the usual weak spots in a CyFun assessment because they sit between owners. A finance system that calls an API into a warehouse may have a clear owner on each side, yet nobody owns the credential that connects them.

Watch for these failure modes:

  • Service accounts with broad permissions that were created for a one-off migration and never removed.
  • Integrations that send data over unencrypted or undocumented channels.
  • Legacy platforms that no longer receive security patches but still hold regulated data.
  • Third-party vendors with remote access that is not logged or reviewed.

When these gaps are found, the fix is usually engineering rather than policy. Rotate credentials, document data flows and replace or isolate the legacy component. Rui Codex works on this kind of technical implementation, including system integration projects where the data flows must be made visible before they can be secured. The governance decisions remain with your organisation and its advisers.

Hypothetical examples of CyFun scoping

Here are two hypothetical scenarios:

Scenario one: A regional logistics company discovers during its inventory that its route-planning software is hosted by a vendor whose remote support access is not logged. The team records the gap, makes vendor access time-limited and requests logs as a contractual step. The control moves from unassessed to in progress, with a named owner.

Scenario two: A software team preparing for assessment finds that a reporting database still runs on an operating system no longer receiving security updates. Rather than patch it in place, the team plans a migration and isolates the database behind a restricted network segment in the meantime. The risk is documented, time-bound and visible to management.

Neither scenario describes a real organisation. Both show that the honest output of an assessment is often a list of documented gaps with owners and dates, not a clean score.

What should a CyFun roadmap contain?

A CyFun roadmap should list each open gap, its owner, the technical change required and a realistic date. It should separate quick fixes, such as removing stale accounts, from structural work, such as replacing a legacy system. Mixing the two hides the real effort.

Tip: Review the roadmap every quarter with the people who own the systems, not only the security function. Gaps close when engineers, operations and management agree on the sequence.

Good roadmaps also state what evidence will prove each closure. That turns the plan into something an assessor can verify. If you need help turning the findings into a delivery plan, you can request a project consultation at the Rui Codex contact page, or read how the team approaches security and compliance engineering in earlier articles.

Frequently Asked Questions

Is CyberFundamentals (CyFun) mandatory in Belgium?

CyFun itself is a framework that organisations can use to meet NIS2 security expectations. Whether a specific obligation applies to your entity depends on the Belgian NIS2 implementation and your classification, so check the official sources and your legal advisers before deciding. Using the framework is a practical way to structure that work.

What is the difference between CyFun and NIST CSF?

CyFun builds on the NIST Cybersecurity Framework but adapts it into concrete measures tailored to the Belgian context and NIS2. NIST CSF is a general structure for managing cybersecurity risk. CyFun adds the detailed measures and assurance levels that Belgian organisations use for their assessments.

Can a small IT team complete a CyFun assessment alone?

A small team can complete an assessment, but it needs clear ownership and time from the people who run the systems. The biggest risk is that one person holds all the knowledge. Splitting the work by system and documenting evidence as you go keeps the effort manageable.

Does Rui Codex certify CyFun compliance?

No. Rui Codex offers technical implementation support, such as integration work, secure system design and engineering changes. It does not provide legal, compliance or audit advice, and it does not issue certifications. Your assessor or auditor makes the formal determination.

Where should an IT team start with CyFun?

Start with an inventory of the systems that support in-scope services, including integrations and third-party access. That inventory makes every later step, from measure assessment to evidence collection, faster and more accurate. Email info@ruicodex.com if you want to discuss how to structure that work.

Sources

Tags: CyberFundamentals CyFun NIS2 Belgium cybersecurity IT security Compliance engineering Security assessment Integration security

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request