Service · Software development

Complying with the Cyber Resilience Act.

The Cyber Resilience Act places the obligation on the product, not on your organisation: anyone who puts software or a connected device on the European market must be able to show how it was built, provide updates for years and report within 24 hours. We set that up as a process and build the software that makes it sustainable.

24/72-hour reporting obligationFive years of updatesSBOMTechnical documentation

What the regulation asks of you, and where we contribute.

The Cyber Resilience Act (Regulation (EU) 2024/2847) entered into force on 10 December 2024. The reporting obligation for actively exploited vulnerabilities and serious incidents applies from 11 September 2026; the remaining obligations apply from 11 December 2027. It affects anyone who places a product with digital elements on the European market, including software, firmware and connected devices, and therefore many more companies than just hardware manufacturers.

What makes the regulation distinctive is where it applies. Policy alone is not enough: something must demonstrably be in place in and around the product itself. The second peculiarity is the timescale. Providing at least five years of security updates for something you release today means that in five years you must still be able to build, test and deliver for this version. That is a design question about how you split up your software and how you keep versions apart.

We are not a notified body and we do not carry out conformity assessments; for that you go to a notified body or do the self-assessment. What we do is the work that underpins it: an SBOM that is generated automatically, a vulnerability process that meets the reporting deadlines, and a delivery chain that can still get an update to your customer in five years' time. For organisations that also fall under the Cybersecurity Act, we set up those processes so that they feed into each other.

We take this on as a standalone project and as part of custom software development. If your product also touches on AI obligations, see AI Act compliance software; if you are working towards certification, see ISO 27001-compliant development. Reports from outside the company go through our CVD policy.

Three kinds of CRA work we take on.

Which option delivers the most for you depends on what you make and where you stand now. In the first conversation, we will tell you where the gap is biggest.

First engagement · fixed sprint budget

Component overview and vulnerability process

The CRA requires an SBOM covering at least the top layer of dependencies, and a process for handling vulnerabilities. We build the generation of that overview into your build pipeline, so it cannot go out of date, and connect the signal sources to it. Then we set up the assessment: which finding affects which released version, who decides, and within what timeframe it is fixed. That is the foundation the reporting obligation rests on.

SBOM in the build pipelineSignal sourcesImpact assessmentRemediation deadlines
Mid-sized project · fixed sprint budget

Reporting process within 24 and 72 hours

Three deadlines, and the clock starts when you become aware of the issue. We define who sends the early warning, where the information comes from and what the message looks like, and we rehearse it once with a realistic scenario. That rehearsal is the part most often skipped and the one that reveals the most: usually it is not the reporting but the assessment that turns out to be the step that slows things down.

Early warningReporting templatesDivision of rolesTabletop exercise
Larger project · fixed sprint budget

Update delivery with a five-year horizon

A channel through which you can get a security update to your customer, even for a version that has been running for years. Signed packages, a versioning policy that keeps old releases supportable, a rollback option, and visibility of which customer is on which version. For devices in the field, this includes over-the-air updates, with the assurance that a partially failed update does not render the device unusable.

Signed packagesVersioning policyRollbackVisibility of the field

What you have at the end of an engagement.

Working technology plus the records you need when a customer or a regulator asks for them.

  • An up-to-date component overview per versionGenerated automatically with every build, with name, version, origin and licence, so that for every released version you can trace what it contained.
  • A reporting process that meets the deadlinesRoles, templates and a decision tree for the early warning within 24 hours, the report within 72 hours and the final report, with one rehearsal included.
  • A delivery chain for updatesSigned packages, a channel that also reaches old versions, and insight into which customer or device is running which release.
  • A vulnerability disclosure policyA public point of contact and a handling route for researchers who find something, in line with what is customary in the Netherlands around coordinated disclosure.
  • Technical documentation that grows with the productDesign choices, risk assessment, test results and the justification for the support period, maintained where the work happens instead of reconstructed afterwards.
  • Handover to your teamWorking sessions with the people who will run it, so the process keeps going when attention moves on to something else.

When you need to act now.

Four situations where the gap between what you have in place and what the regulation requires turns out to be widest in practice.

Product in the field

Your software runs on customers' devices

For software you run yourself, an update is a single action. For software installed on customers' devices, it is a chain you need to have set up before you need it. That is almost always the longest-running part of a CRA project.

No overview

You don't know what is in your product

A notice comes in about a component, and someone has to establish whether your product uses it, in which version, and whether the vulnerable function is actually called. With an up-to-date overview that takes minutes; without one it becomes a round of phone calls that won't fit into 24 hours.

Long lifespan

Your product outlasts your release cycle

You release a new version every year and support the previous one for six months. Providing five years of updates then means revisiting your versioning policy, not patching harder.

Customers are asking for it

It is already in your procurement processes

Even before the obligation applies in full, customers are asking in their terms for a component overview and for agreements on updates. If you only start preparing that when the first request arrives, you lose days and come across as unprepared.

How a CRA project works with us.

1

Introduction and scoping

First, the question of which of your products fall under the regulation and which category they end up in, because that determines whether a self-assessment is enough. We also look at whether you are a manufacturer, importer or distributor; each role has different duties, and that distinction determines half of the scope.

2

Gap analysis on the product

We go through the essential requirements against what exists today: which components are in the product, how vulnerabilities are currently spotted, how an update reaches the customer, and what is documented. The result is a list of gaps, sorted by how long they take to close rather than by how bad they sound.

3

Building in sprints

We work in sprints and start with the component overview, because everything else relies on it. Then the signal sources and the assessment, then the reporting process, then delivery. Your own developers take part; this is process work, and it cannot stand apart from the organisation.

4

Practising with a scenario

A tabletop exercise with a realistic report: a vulnerability in a component you use, actively exploited, reported on a Friday afternoon. We measure how long it takes before a well-founded assessment is ready, and where things got stuck. That is more valuable than any process description.

5

Documentation and handover

We organise the technical documentation so that it is kept up to date where the work happens. Then a handover to your team and, if you wish, a period in which we keep an eye on the first real reports.

Frequently asked questions about the Cyber Resilience Act.

What product owners, CTOs and compliance officers ask us before a project like this begins.

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.

Talk to us about the Cyber Resilience Act.

A no-obligation introductory call of half an hour. Tell us what you build and who you supply it to, and we will tell you where the gap probably lies and what needs doing first – even if we end up not working together.

Edit content