The EU Cyber Resilience Act (CRA), Regulation (EU) 2024/2847, sets cybersecurity rules for every product with digital elements sold in the EU. Its reporting obligations have applied since 11 September 2026, and the rest of the regulation applies from 11 December 2027. These are the questions instrument makers ask us most, answered plainly.
Not sure whether the CRA applies to your products? Take the two-minute CRA self-check
Want the requirements as a working checklist? Download our free CRA Annex I checklist.
Guidance only, not legal advice. Check your obligations against the regulation and with your legal advisers.
Scope: which products the CRA covers
What is the EU Cyber Resilience Act?
The Cyber Resilience Act is an EU regulation that sets mandatory cybersecurity requirements for products with digital elements: hardware and software that can connect to a device or a network. It entered into force on 10 December 2024. Manufacturers must report actively exploited vulnerabilities and severe incidents from 11 September 2026, and every product placed on the EU market from 11 December 2027 must meet its essential requirements and carry CE marking for it.
Does the Cyber Resilience Act apply to laboratory instruments?
In most cases, yes. The CRA covers products with a direct or indirect logical or physical data connection to a device or network. An instrument with firmware, a USB link to a PC, an Ethernet port or a companion analysis application is a product with digital elements. It does not need to reach the internet to be in scope.
Does the CRA apply to research use only (RUO) instruments?
Yes. Research use only instruments and general laboratory equipment are not covered by the medical device rules, so the CRA applies to them. If you sell one platform as both an IVD and an RUO instrument, assume the RUO version is in scope and assess it on its own.
Are medical devices and in vitro diagnostics covered?
No. Products regulated under the Medical Device Regulation (EU) 2017/745 or the In Vitro Diagnostic Regulation (EU) 2017/746 are excluded from the CRA, because those regulations carry their own cybersecurity requirements.
Does standalone analysis software count, or only instruments?
Software counts on its own. Desktop analysis software that you sell or supply separately from the instrument is a product with digital elements. Pure software as a service is generally outside the CRA unless it is a remote data processing solution the product needs to perform one of its functions.
A partner wrote our instrument software. Who is responsible?
The manufacturer is whoever places the product on the market under its own name or trademark. If your name is on the instrument or the software, the CRA obligations are yours, even if a partner such as TotalLab built the code. Your contracts with software partners should cover SBOMs, vulnerability handling and security updates for that reason.
Products you already sell
Does the CRA apply to instruments we already sell?
Partly. Units placed on the market before 11 December 2027 do not have to meet the essential requirements unless they are later substantially modified. The reporting obligations are different: they have applied to every in-scope product since 11 September 2026, whenever it was sold.
Can we keep selling our current model unchanged after December 2027?
Only if it complies. The rule applies to each individual unit, not to the product model. A unit you place on the EU market in January 2028 must meet the CRA in full, even if it is identical to units you sold in 2026. Units already shipped to distributors before the deadline can still be sold on.
What counts as a substantial modification?
A change after the product is on the market that affects how it meets the essential requirements, or that changes its intended purpose. A security update that only reduces risk is generally not a substantial modification. New features or a major software version usually need assessing.
Reporting from 11 September 2026
What do we have to report, and how fast?
You must report any actively exploited vulnerability in your product, and any severe incident affecting its security, once you become aware of it. The deadlines are an early warning within 24 hours, a notification within 72 hours, and a final report within 14 days of a corrective measure being available for a vulnerability, or within one month for a severe incident.
Where do CRA reports go?
Reports are filed through ENISA's Single Reporting Platform and go to the coordinating CSIRT of the EU member state where you have your main establishment. You also need to inform affected users and tell them what they can do to reduce the risk.
The vulnerability is in an open-source library we use. Is that our problem?
Yes. You are responsible for the components inside your product, including open-source and third-party libraries. If an actively exploited vulnerability in one of those components affects your product, the reporting duty applies. This is why an up-to-date SBOM matters: you cannot report a vulnerability in a component you do not know you ship.
SBOMs, updates and support periods
What is an SBOM, and how detailed does it need to be?
A software bill of materials lists the components in your software. The CRA requires one in a commonly used, machine-readable format, covering at least the top-level dependencies. SPDX and CycloneDX are the two formats most manufacturers use. You keep it in your technical documentation; you do not have to publish it.
How long do we have to provide security updates?
For the support period you declare, which should reflect how long the product is expected to be used and is normally at least five years. You must state the end date of the support period, month and year, at the point of sale. Each security update must then stay available for at least 10 years after it is issued, or for the rest of the support period if that is longer.
Our software has no update mechanism. Is that a problem?
Yes. The CRA expects you to be able to fix vulnerabilities through security updates, delivered securely and, where possible, separately from feature updates. Updates that only reach customers when a field engineer visits with a USB stick will struggle to meet that, especially for an installed base across several countries.
Conformity assessment, CE marking and fines
Do we need a notified body?
Most products can self-assess, using the internal control procedure. The exceptions are products whose core function puts them on the CRA's lists of important or critical products. Important class I products can self-assess only if they apply harmonized standards or a certification scheme; class II and critical products need a third party. Most laboratory instruments are not on those lists, but check each product's core function.
How does CRA CE marking relate to the CE marking we already apply?
From 11 December 2027, the CE marking on an in-scope product also signals conformity with the CRA. Your EU declaration of conformity and technical documentation will need to cover the CRA alongside the other legislation that already applies to the instrument.
What are the penalties for non-compliance?
Breaching the essential requirements or the main manufacturer obligations can lead to fines of up to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher. Other breaches carry lower caps. Market surveillance authorities can also require a non-compliant product to be withdrawn from the EU market, which for most OEMs is the bigger risk.
How does the CRA relate to 21 CFR Part 11 and EU Annex 11?
They cover different things. 21 CFR Part 11 and Annex 11 govern the integrity of electronic records and signatures in regulated use. The CRA governs the cybersecurity of the product itself. The disciplines overlap: access control, audit trails, documented development and validation all help with both.
Where to start
Where should we start?
List every product you sell into the EU and check which are in scope. Then get SBOMs and a vulnerability reporting process in place, because those obligations already apply. After that, decide product by product whether to remediate the software, redevelop it, or retire the product from the EU market before December 2027.
Two ways to take the first step:
Related reading
- How TotalLab makes legacy instrument software CRA compliant
- The Cyber Resilience Act and your legacy software: a survival guide
Sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Official Journal of the European Union.
- Cyber Resilience Act summary, European Commission.
- Legacy products are in scope for CRA reporting from 11 September 2026, cyberresilienceact.eu.
- Three dangerous misconceptions about the Cyber Resilience Act, congatec.
- Cyber Resilience Act: what you need to know and what you need to be doing, DLA Piper, February 2026.
Prefer to talk it through? Book a free CRA readiness audit
Find out where your products stand
Answer nine questions and see straight away whether the CRA applies to your product and where your biggest gaps are. No call, no commitment.
