In force since 15 August 2026 Only mandatory once designated Nine and ten months

Custom Wwke software development for critical entities

The Wwke works differently from most obligations: it doesn't apply to you automatically. A ministry designates you as a critical entity, and only from that moment do the clocks start running. Nine months for the risk assessment, ten for the measures. That sounds generous, but it isn't, because physical measures for buildings, sites and staff have lead times that pay no attention to your deadline.

Why the designation is the decisive moment

The Critical Entities Resilience Act (Wwke) came into force on 15 August 2026, together with the Cybersecurity Act. It implements the European CER Directive and is about something other than cyber: resilience against sabotage, terrorism, natural disasters, outages and other major disruptions. Around five hundred organisations are expected to be designated, in sectors such as energy, drinking water, transport, healthcare, banking and government.

The difference from the Cybersecurity Act lies in how you come to fall under it. Under the Cbw, you assess that yourself and register. Under the Wwke, the responsible ministry designates you, and only then do the obligations arise. From that designation, you generally have nine months for a risk assessment and ten months to put technical, organisational and physical measures in place.

That is the pitfall. If you wait for the designation, you start with ten months for work that takes longer: camera layouts, access control, background checks on staff, changes to sites and continuity agreements with suppliers. The organisations that get this right map their resilience now, so that the designation becomes an administrative event rather than a starting signal.

How we build this

Here, the critical process is the unit, not the department. Once you know which process cannot be allowed to fail and what it depends on, the rest follows.

1
Identifying the critical processes

Which service must never fail under any circumstances, and what is needed to deliver it? Buildings, installations, people, suppliers and systems. In most organisations, that overview does not exist in one place.

2
Mapping threats to those processes

Not just cyber, but also power outages, flooding, sabotage, the loss of a key person and the loss of a single supplier. The Act calls for the broad view, and that is the hardest part. If you already have an RI&E with an action plan, we reuse that approach.

3
Planning measures with lead times

Every measure gets an owner and a realistic lead time. Physical measures involve delivery times and permits, and these do not always fit within ten months.

4
Starting the clock in advance

We set up the schedule as if the designation arrives today. What then proves unachievable is exactly what you need to set in motion now.

What the software actually does

The register of critical processes and their dependencies underpins everything. Which components you need depends on your sector and on how many locations you manage.

Critical processes and their dependencies

For each service, which locations, installations, people and suppliers are needed to deliver it. This integration shows where a single failure affects several processes, and that is exactly what the risk assessment has to demonstrate.

Monitoring the nine- and ten-month clock

From the designation, two deadlines run in parallel, each measure with its own lead time. The system shows which measure will miss its deadline while there is still time to speed up.

Measures per location and asset

Physical resilience is site-specific. Access control, camera surveillance, emergency power and perimeter security are recorded per location, along with the condition they are in.

Personnel resilience on record

Background checks, access rights to sensitive locations and the question of which roles are indispensable. If a key person drops out, what counts is whether you had recognised that in advance.

Incidents and disruptions on record

A disruption with significant consequences must reach the competent authority quickly. Recording starts at the moment it happens, with an app on site, and not when the report is being drafted.

Exercises and reassessments retained

When did you exercise, what went wrong and what was done about it. A resilience plan that has never been tested is just a paper plan when the regulator comes calling.

Who we build for

The sectors that will be designated differ greatly in what determines their resilience. Four situations.

Drinking water and energy

Your critical processes depend on physical installations at scattered locations, often unmanned. Here, the resilience question is about access, failure and recovery, and much less about offices.

Transport and logistics

Your service runs through hubs and through parties that are not yours. Dependence on suppliers is the core of the risk assessment here, and the hardest to substantiate.

Healthcare

Continuity here means care carries on while something fails. Alongside the physical side, there is the question of which systems and which people are indispensable, and both belong in the same file. You set up the reporting chain separately; see the incident reporting portal.

Government and public services

You often manage many sites with widely varying functions and security levels. The challenge is not to arrange something per building but to determine which buildings are critical for which service.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

Exactly which organisations will be designated and which requirements apply per sector will be filled in further after the law enters into force. Everything connected to that should be configurable.

Node.js / Python / .NET PostgreSQL Register of critical processes Dependencies on locations, people and suppliers Threats and risk assessment Measures with lead time and owner Deadline monitoring from designation Location and asset management Recording of exercises Incident registration with timeline Reporting to the competent authority Version history on assessments Audit logging Hosting in the EU

Why Appfront

The clock starts at designation, the work earlier

Physical measures have lead times and sometimes require permits. We set up the planning as if the designation falls today, so it becomes visible what you need to start now.

Physical and digital in one file

The Wwke covers sabotage and natural disasters, the Cbw covers cyber. If both apply to you, you want one dependency overview and two accountability reports, not two separate systems.

Connecting to what you already manage

Location data, access systems and maintenance schedules already exist. We connect to them through integrations rather than retyping them.

Honest about what is not yet settled

Exactly who will be designated and which requirements apply per sector is still to be determined. We build the structure and make no statements about the further rules.

Security and privacy

This file describes where your organisation is vulnerable and which locations matter. That is more sensitive than an ordinary security file, because it concerns physical objects that someone could approach. We therefore set access per role and per location, so that a manager of one site does not get the picture of the whole, and we log every access.

The people side requires extra care. Data on background checks and on which roles are indispensable affects the privacy of your employees, and ordinary privacy legislation applies to it. We keep the minimum: the outcome and the validity date, not the investigation itself. How we handle security ourselves is described in our information security policy; reports from outside go through our CVD policy.

Frequently asked questions about the Wwke

The Senate adopted the bill on 7 July 2026 and the act entered into force on 15 August 2026, at the same time as the Cybersecurity Act. It transposes the European CER Directive. Unlike with the Cbw, the obligations do not arise for everyone immediately, but only after designation.

The ministry responsible for your sector designates critical entities; this is expected to involve a few hundred organisations. You cannot determine this yourself, and you do not need to register. If you provide a service whose failure would be socially disruptive, the chance is real. Preparing before you know is the wisest approach with this instrument.

In principle nine months for the risk assessment and ten months to put the technical, organisational and physical measures in place. These deadlines run in parallel, not one after the other. For physical measures with lead times or permits, ten months is tight, which is the reason not to postpone the inventory.

The Cbw (Cyberbeveiligingswet) is about digital resilience, applies to well over eight thousand organisations and works through self-registration. The Wwke (Wet weerbaarheid kritieke entiteiten) is about physical resilience, applies to a few hundred organisations and works through designation. If you fall under both, you have two separate files with their own deadlines, but largely the same underlying dependencies.

You report an incident that causes a significant disruption to your service to the competent authority within twenty-four hours. What counts as significant depends on your sector and on the further rules. In practice, it means the incident must be recorded during the disruption rather than afterwards, because reconstructing events later takes more time than you have.

It is a good start and saves a lot of work. On top of that, the law asks you to make dependencies explicit for each critical process, to link measures to identified threats, and to be able to show that you have run exercises. A plan that sits in a drawer and has never been tested does not meet those requirements.

The obligation is yours, but your resilience depends on parties outside your organisation. The risk assessment must make that dependency visible, which in practice means putting continuity agreements in place with suppliers you currently contract on trust. This is usually the longest-running part.

That depends on the number of locations, how much is already documented and whether integrations with existing systems are needed. The register of critical processes with dependencies can usually be put to use quickly and gives you immediate insight; location management and integrations cost more. We give a substantiated estimate after the discovery phase.

Preparing for designation?

Take one service that cannot be allowed to fail and try to write down what it depends on: which locations, which people, which suppliers. Where that list gets vague, that is where your risk assessment lies. We build this both as a standalone application and as part of a broader custom software project.

Edit content