When exactly does this apply?
The regulation entered into force on 10 December 2024. The reporting obligation for actively exploited vulnerabilities and serious incidents applies from 11 September 2026; most of the other obligations, including the essential requirements and CE marking, apply from 11 December 2027. The reporting obligation is therefore the first one to affect you, and it relies on work that cannot be put in place in a few weeks: you can only report within 24 hours if you know within 24 hours whether something affects you.
Does our software fall under this?
Probably. It covers products with digital elements offered on the European market, which is broad: standard software, firmware, devices that connect, and also individual software components placed on the market independently. There are exceptions, including for products already covered by specific sector legislation and for open source that isn't offered commercially. Custom software that you build for a single client is more nuanced; we check that case by case.
We only sell within the Netherlands. Does it still apply?
Yes. The regulation applies to products made available on the European Union market, and the Netherlands is part of that. There is no lower threshold based on turnover or company size. There is some relief for small and micro enterprises on parts of the documentation obligation, and the Commission is working on simplified formats. That changes nothing about the reporting obligation itself.
What exactly does the five years of support involve?
You must fix vulnerabilities and make security updates available throughout the support period. That period is at least five years, unless the product's expected lifetime is shorter; if it is longer, support follows the lifetime. Importantly, this concerns security updates, not new functionality. In practice it mainly affects your versioning policy: you must still be able to build and ship an old release.
How does this relate to the Cybersecurity Act?
They apply to different things. The Cyberbeveiligingswet, the Dutch implementation of NIS2, targets your organisation and your services; the CRA targets the product you place on the market. If you are covered by both, the underlying processes overlap – risk management, incident handling, supply chain security – but the evidence required differs. We set up those processes so that you maintain them once and can use them in both places.
Do we have to make an SBOM public?
No. The obligation is to have one and to be able to provide it to the market surveillance authority on request, in a common machine-readable format and at least for the top level of dependencies. What you share with customers is up to you. In practice, we see that customers do ask for it and that including it is an advantage in procurement processes, because it shows that the overview exists.
What happens if we fail to report?
Enforcement runs through the national market surveillance authority, and the maximum fines in the regulation are substantial: for breaches of the essential requirements, up to fifteen million euros or two and a half per cent of worldwide annual turnover, whichever is higher. In practice, what weighs more heavily in most conversations is that a product can be withdrawn from the market and that customers ask about this in their procurement process.
We use a lot of open source. What does that mean?
It means you include those components in your inventory and that the vulnerabilities in them become your responsibility as soon as you place the product on the market. The maker of the open-source component does not carry that duty, unless it is offered commercially. There is a separate, lighter role for open-source stewards, such as the foundations behind large projects. For you as a manufacturer, little changes: you are responsible for what you ship.
Do we need an external body for this?
That depends on the category your product falls into. For most products, a self-assessment with technical documentation and an EU declaration of conformity is enough. For important and critical categories – think password managers, firewalls or operating systems – heavier routes apply, sometimes involving a notified body. We determine that category during scoping, because it shapes the rest of the process.
What is realistic if we start today?
The component inventory and the signal sources are the quickest to arrange and deliver the most, because the reporting deadline depends on them. The reporting process itself is mainly a matter of making agreements and running one exercise. Delivering updates over a long horizon is the longest-running part, especially if devices are in the field. We fix that order in the gap analysis, so that whatever becomes mandatory first is also ready first.
Do you also carry out the conformity assessment yourselves?
No. We are not a notified body and do not issue CE marking. What we deliver is the work that underlies it: the engineering, process and documentation you take into the assessment, whether that is a self-assessment or runs through an external party. In projects where a notified body is involved, we work with the party you choose and supply whatever they request.