CyFun Maturity

Score every CyberFundamentals requirement for how well it is written down and how well it is actually practised, read the CCB self-assessment verdict for your target level, and work down the list of requirements that fall short.

This is the maturity workbench for CyFun (the CyberFundamentals Framework — the Belgian baseline cybersecurity framework published by the Centre for Cybersecurity Belgium, the CCB). Every CyFun control carries two scores: a documentation score for how well it is written up, and an implementation score for how well it is actually run. Maturity (how reliably and repeatably something is done, scored 1 to 5) is measured against the pass thresholds the CCB sets for your organisation’s CyFun assurance level, and the page collects every requirement below them. Aegis can suggest scores from what you have linked; a person reviews and applies them.

Open the COMPLIANCE group in the left navigation and select CyFun Maturity; the route is /compliance/cyfun/maturity. CyFun is licensed per framework — without it, the route shows a “framework not available” placeholder, and if the framework is licensed but switched off in Settings it shows a “switched off” card instead.

Who uses it

Opening the page requires Contributor or above. A Viewer never sees CyFun Maturity in the left navigation, and is sent to /unauthorized when opening the route directly. Reading and scoring are separate rights:

View-only access is stated on the page

A Contributor sees a notice above the tabs: You have view-only access to the CyFun maturity assessment. Scores stay visible, but changing them requires the Update Compliance permission. If you need to score, ask an administrator for a Manager or Admin role.

Each saved score is written to the audit log against the person who set it.

What’s on this screen

The header shows a teal shield, the title CyFun Maturity Assessment, and beneath it the target level in amber followed by the CCB pass threshold for that level — in the captured screen, Target level: Essential (CCB pass threshold: total average ≥ 3.5 on a 1–5 scale). Buttons sit to the right: AI Maturity Narrative (outlined, sparkle icon), Calculate Auto Score (indigo, calculator icon — shown to Managers and Admins only, so it is absent from the Contributor capture) and Quick-Start Assessment (teal, with an arrow marking that it opens another page).

Four summary cards follow: Avg. Documentation Maturity and Avg. Implementation Maturity, each with its target underneath; Assessment Completion, with the count of assessed controls; and Controls Below Target, with the line Requirement score below and the threshold. The captured screen reads 3.2 and 3.1 against a target of 3.5, 85% completion across 186/218 controls, and 132 below target. A line under the cards says these averages cover every CyFun requirement and are informational; the verdict that counts is the panel below.

The CCB self-assessment conformity panel states that verdict. A badge at its top right reads Meets or Does not meet … yet with the level name, and a sentence explains how the CCB scores: each requirement is the mean of its documentation and implementation maturity, then requirements are averaged per subcategory, subcategories per category, and categories into the total. Four figures follow, each green when its rule passes and red when it fails:

Under the figures, an amber line counts requirements that still need both scores (in the captured screen, 32 requirements still need both a documentation and an implementation score.). When you have recorded more exclusions than allowed, or recorded N/A where the CCB does not allow it, red lines say so and name the requirements. With no requirement in scope for the level, the panel is replaced by a note that there is no self-assessment verdict yet.

Then, for a Contributor, the view-only notice; then a tab strip: Overview, By Function, By Control, Key Measures and Gaps with the gap count in brackets. Overview puts a Maturity by Function radar chart on the left and a Function Summary table on the right. Below whichever tab you have open — not only Overview — sit a saved AI insights panel and an action-items list.

  1. In the left navigation, select the COMPLIANCE group. It expands; select CyFun Maturity and this dashboard opens.
  2. Select AI Maturity Narrative to open the briefing dialog described under The AI assist below. The dashboard stays behind it until you close the dialog.
  3. Check Key measures below threshold first. A key measure below its threshold fails the level on its own, whatever the total average says.
  4. Read Total average vs threshold. It shows your total and the level’s threshold side by side, so you can see how far there is to go.
  5. Read the amber line under the figures. Until every requirement in scope has both scores, the verdict rests on a partial picture.
  6. Read the grey notice above the tabs, if it is shown. It means your role can read everything on the page but not change a score; the score buttons on every tab stay greyed out.
CyFun Maturity Assessment — /compliance/cyfun/maturity.
CyFun Maturity Assessment — /compliance/cyfun/maturity.

Read your standing at a glance

Both averages are means across every control against the same target, so the distance between them tells you whether the weakness is in the paperwork or in the practice. Assessment Completion is the share of controls carrying any score; below 100%, the averages come from a partial picture. The averages include not-applicable and out-of-level requirements, which is why they are informational: the conformity panel applies the CCB rules for your level and gives the pass or fail.

Look at maturity function by function

The radar chart plots the six CyFun functions — Govern, Identify, Protect, Detect, Respond and Recover. A blue shape is documentation maturity, a green shape implementation maturity, and a dashed amber ring marks the target at its exact value, including fractional thresholds such as 3.5; anything inside the ring is short. The Function Summary table repeats this as numbers: a coloured dot per function, badges such as 3/5 under Doc. and Impl., and an assessed-versus-total count such as 30/40. A badge is green when the target is met and red with a warning triangle when below; a function with nothing assessed shows Not assessed rather than a zero. In the captured screen, Govern reads 3/5 and 3.1/5, both red against the Essential threshold.

The By Function tab shows the same six functions as a Detailed Function Breakdown: one block per function with an assessed count, a blue documentation bar and a green implementation bar, each with an amber marker at the target position.

Score a control by hand

The By Control tab, headed All Controls, lists every CyFun requirement with columns Control, Function, Doc. Score, Impl. Score, Assurance Levels and Key Measure. Under a requirement’s title, a badge reading Reviewed at every certification audit marks a requirement the CCB links to the management aspects, and an N/A badge marks one recorded as not applicable — the self-assessment counts it at the level’s fixed N/A score instead of its maturity scores. You need Manager or Admin to score; for a Contributor the score buttons are greyed out.

  1. Select the By Control tab. The table replaces the chart, under a line such as Showing 218 of 218 controls with maturity scores. for your totals.
  2. Type a reference, category or title into the Search controls... box. The table filters as you type and the count follows; with no matches you get No controls match your search.
  3. In Doc. Score, select one of the five numbered buttons. It turns green if it meets the target or amber if below, and a small spinner runs while the change saves.
  4. Set Impl. Score the same way. Each score saves on its own the moment you select it — there is no save button — and once the save is confirmed the summary cards, the conformity panel and the gap count refresh in place, keeping your tab and search.
  5. Select the teal control reference to open that control in the main compliance register, where you link the policies, procedures and evidence behind it.

If a save fails, a message says why — for example Could not reach the server. The score was not saved — check your connection and try again. or You do not have permission to change maturity scores. — and the buttons become selectable again.

Work through the key measures first

Some requirements are flagged as key measures — those the CCB designates as priorities at a given assurance level. Every key measure in scope must reach its own threshold for the level to be met, and a key measure can never be marked N/A. The Key Measures tab shows only those, with its own Search key measures... box, a KM Level column, and the same inline scoring; the score colours here compare against the key-measure threshold rather than the total threshold. If your time is limited, score these first.

Close the gaps

The Gaps tab, headed Controls Below Target, is the focused worklist. Its subtitle states what it collects: requirements whose score (the mean of documentation and implementation) is below your level’s threshold, key measures below their own threshold, and N/A decisions the CCB does not allow. Each row carries badges for a key measure, its assurance levels, the management aspect and, where relevant, N/A not allowed: key measure or N/A not allowed at Essential. A Score column shows the requirement score against the threshold, such as 2.5 / 3.5, in red when failing, with Key measure below and the threshold underneath when a key measure blocks the level. Doc. Gap and Impl. Gap read OK in green when met, or a red figure such as -0.5 when short.

  1. Select the Gaps tab. Its count matches the Controls Below Target card, so you know the size of the list before opening it.
  2. Select a row anywhere except the score buttons. The chevron rotates and the control’s requirements appear underneath, each with a status mark — open circle for not started, half circle marked WIP, filled circle marked Done. A control with no requirements says so.
  3. Set the scores inline. The Score and gap columns recalculate immediately: reach the target and the gap cell changes to OK. Once the save is confirmed the list refreshes, and a requirement that now meets the threshold drops out of it.

With nothing below target, the table is replaced by a green tick and All controls meet the target maturity level.

The AI assist

AI Maturity Narrative. The button opens a dialog titled CyFun Maturity Narrative, subtitled Your maturity, read by function, with next steps, which lists what it will cover before you run it. Select Run Maturity Narrative and Aegis works through four visible stages, from reading the scores to drafting the next steps, then returns a plain-language account of where you stand plus three to five next steps. It narrates figures already computed; it never recomputes, rescores or invents a score. Keep it with the dialog’s save-as-record action: saved narratives appear in the insights panel below and can become tracked Action items. Each run counts against your tenant’s monthly AI allowance, and is refused if an administrator has switched AI assistance off.

Calculate Auto Score. Shown to Manager and Admin only. This proposes scores from what each control already has linked. Documentation follows the linked policy: nothing linked scores 1, rising to 5 for an approved policy reviewed within its cycle. Implementation follows procedures, evidence and control monitors on the same scale, with 5 reserved for an approved procedure backed by valid evidence and healthy monitors. Nothing is written until you confirm.

  1. Select Calculate Auto Score. The button shows a spinner while Aegis reads your linked artefacts, then a dialog opens titled Automatic Score Suggestions.
  2. Read the summary line — how many controls were analysed, how many have a suggested change — then check the table beneath, which shows current → suggested values for up to fifty changed controls.
  3. Choose Apply Unset Only to fill controls with no score yet, or Apply All (Overwrite) (amber) to replace existing scores too. Cancel closes the dialog unchanged.
  4. A message confirms how many scores were updated and how many skipped, and the dashboard refreshes with the new figures.
Overwriting replaces human judgement — take care

Apply All (Overwrite) replaces scores people set by hand, including ones argued over and agreed. Use Apply Unset Only unless you mean to reset the whole assessment to what the linked artefacts show.

A suggestion is a starting point, not a verdict

Auto-score reflects what is linked in Aegis, not an inspection of how the control runs. Leave the final judgement with the control’s owner.

The GRC Coach: a guided route to CyFun Basic

When an administrator offers it (Offer the GRC Coach view in the runtime settings), anyone can switch to the Coach view with the Coach view button in the top bar and back with Full view. The coach is meant for people without compliance experience. It adds no data of its own: every answer lands in the same records this chapter shows, and only a person's click writes anything.

Tips and limits

The thresholds follow your CyFun assurance level, as the CCB self-assessment sets them:

Level Total average Each key measure Each category N/A exclusions allowed A valid N/A counts as
Basic 2.5 2.5 no rule 1 2.5
Important 3 3 no rule 3 3
Essential 3.5 3 3 5 3

Where this connects

Auto-score reads work you do elsewhere, so the more you link, the more useful it is: write controls up in Policies and Procedures, attach proof in Evidence, and keep checks running in Control monitoring. See where CyFun sits among the other standards, and record its assurance level, in Compliance frameworks, and use Audit readiness before an external assessment.