1. What the Cyber Resilience Act is and who it applies to
The Cyber Resilience Act (CRA) is the European regulation that sets cybersecurity requirements for products with digital elements placed on the Union market. It covers hardware and software, including components that connect to a network: routers, IP cameras, industrial controllers, applications and firmware. The aim is simple: a product sold in Europe must arrive with a baseline of security and must receive updates for a declared period, so that users are not left exposed to known defects.
Many SMEs think the regulation only concerns those who make technology. In reality the CRA also involves those who develop software under their own brand, those who import devices from outside the EU and those who resell them. Those who buy and use these products also have a direct interest, because compliance shows up in what they receive: documentation, support and updates. The line between product and service, particularly in the cloud, is a point to clarify with your legal adviser case by case.
2. Security by design: what it means in practice
Security by design means that security is built into the project from the outset, rather than being added at the end as a patch. Under the CRA, the manufacturer must design the product so that it has a secure default configuration, limits access to data and functions to those who genuinely need it, and protects communications. Factory default credentials are also a critical point: identical passwords across all devices, or administrative accounts that are always active, are precisely the defects the regulation aims to eliminate.
For a buying company, this translates into very concrete questions. Does the product force a password change at first start-up? Does it support multi-factor authentication where needed? Does it log events so that what happened can be reconstructed? Can unnecessary functions be disabled? You do not need to be an engineer to ask these questions: they belong in a request for quotation and in a supplier's technical sheet. A vague or missing answer is already useful information about the product's maturity.
3. Roles and obligations along the supply chain
The CRA distinguishes the roles of economic operators, and the role determines who must do what. A company can hold several roles at once, for example when it integrates a third-party software module into its own solution and resells it under its own name: in that case it is the manufacturer of that product and is fully responsible for it. It is worth mapping your position before discussing compliance tasks, because a mistake in classification means working on the wrong obligations, with time and money wasted.
The table summarises the general logic. For the details of each role and for borderline cases, refer to the official text of the regulation and to a legal assessment. If your company develops a product that you sell to customers, the weight of the obligations is very different from that of a company that only uses internal tools. Company size is not the criterion either: role and product matter, not the number of employees.
| Role | What it does | What to check |
|---|---|---|
| Manufacturer (develops the product or has it developed under its own brand) | Designs, documents, handles vulnerabilities and updates | Conformity assessment, technical documentation, duration of security support |
| Importer (places on the EU market products of a manufacturer outside the EU) | Places the product on the European market | That the manufacturer has carried out the assessment and that the documentation is available |
| Distributor (makes the product available without modifying it) | Sells or makes the product available | CE marking and instructions in the required language |
| Business user (installs and uses the product) | Manages the product within its organisation | End of security support, update procedure, clauses in the supplier contract |
4. Vulnerabilities, updates and reporting
The CRA requires the manufacturer to handle vulnerabilities for the whole of the declared support period. This means having a channel to receive reports, a process to analyse them, the ability to release fixes and to communicate them to users in an understandable way. An update that exists but does not reach customers, or that requires complex manual intervention on dozens of devices, is not enough: the requirement concerns whether the fix is actually distributed, not only whether it exists.
For vulnerabilities that are actively exploited, the regulation requires notification to the authorities within very tight deadlines, set out in the text of the norm. The practical point is this: before that moment you need to know who handles reports, who decides and who communicates. If your supplier has no designated person or process, the risk of delay grows precisely at the worst moment. Ask in writing how this flow is managed, who the point of contact is and through which channels communications reach users.
5. Third-party software and the bill of materials
Almost every digital product contains third-party components, including free software. The CRA pushes towards transparency about these components, which is why people talk about the software bill of materials, or SBOM: a structured list of the libraries and modules that make up the product. It is not a marketing document. It is the tool that tells you, when a vulnerability emerges in a library, whether your system is affected and in which version.
A common mistake is thinking that open-source software carries no obligations. Free code can be used, but whoever integrates it into a commercial product is responsible for it like anyone else, and must know which versions are in use and how they are updated. A serious supplier should be able to name its main components, explain how it receives alerts about the ones it uses and say who decides whether and when to release a fix.
6. Getting started: a checklist for the first steps
You do not need to wait for the detail of every deadline before acting. The work is simpler if it starts from what you already have: supplier contracts, product technical sheets and existing update procedures. The first goal is to know which digital products you use or sell, what role you hold for each and who is responsible for security on each.
The next step is to build these requirements into supply contracts and future purchases. Writing down the support period, the timescales for handling vulnerabilities and the obligation to provide the component list turns compliance into something verifiable, rather than a general promise. A company that does this before the deadlines has fewer surprises when the requirements become mandatory.
- List the digital products you develop, sell, import or use, distinguishing hardware, software and cloud services.
- For each, note the role you hold in the supply chain and the reference manufacturer or supplier.
- Ask suppliers for the security support period and the process by which they handle vulnerabilities.
- Check that purchased products carry CE marking, a declaration of conformity and instructions in your language.
- Assign a person responsible for product security and a deputy.
- Have a lawyer or consultant review borderline cases, especially where the product blurs into a service.
Frequently Asked Questions
Does the CRA apply to small businesses that only use software?
It depends on your role. If you use third-party software or devices in your business, without modifying them and without selling them under your own brand, your obligations are generally limited, but you need to know the security support you are guaranteed. If you develop a digital product that you sell or distribute to customers, even under your own name, you fall within scope as a manufacturer and the obligations become much broader.
What does the CE marking mean under the CRA?
The CE marking indicates that the product has been assessed and declared to conform to the applicable European requirements. For products with digital elements, the manufacturer issues an EU declaration of conformity and keeps the technical documentation available to the authorities. As a buyer, ask the supplier for the declaration and the user instructions. If they are missing, that is a warning sign to investigate before purchase.
What is an SBOM and is it really necessary?
SBOM stands for software bill of materials, a structured inventory of the software components of a product, including third-party libraries. It helps you quickly establish whether a newly published vulnerability affects your systems. Your small business does not necessarily have to produce one, but you should ask your supplier whether it provides one and how often it is updated.
How long must a manufacturer guarantee security support?
The regulation requires the manufacturer to declare a support period and to honour it. The duration is not the same for every product: it depends on the type of product, its intended use and its expected useful life. Do not assume a period. Ask for it in writing, compare it with the life you expect the system to have, and check what happens at expiry, for example whether the product remains usable but without fixes.
Does the CRA conflict with the GDPR?
No, they are different rules that complement each other. The GDPR concerns the processing of personal data; the CRA concerns the security of digital products. A product can comply with one and not the other. When choosing a supplier it is worth checking both aspects, because a vulnerability in a device can turn into a personal data breach, which must also be assessed for notification purposes.