Cyber Resilience Act Obligations for Manufacturers: Checklist
The Cyber Resilience Act obliges manufacturers of products with digital elements on three levels: the product must meet the cybersecurity requirements of Annex I Part I, the manufacturer must handle vulnerabilities in accordance with Annex I Part II throughout the support period, and it must demonstrate both through a cybersecurity risk assessment, technical documentation, conformity assessment and CE marking (Art. 13). The reporting obligations under Art. 14 have applied since 11 September 2026, all other obligations apply from 11 December 2027.
This article lists the obligations one by one and includes a checklist. Deadlines, scope and product classes at a glance can be found on the page Cyber Resilience Act consulting.
Level 1: Security of the product (Annex I Part I)
Principle: a product must be designed, developed and produced in such a way that it ensures an appropriate level of cybersecurity based on the risks. On the basis of the cybersecurity risk assessment, it must in particular:
| Requirement | What this means in practice |
|---|---|
| be made available on the market without known exploitable vulnerabilities | vulnerability check of your own software and all components before every delivery |
| have a secure by default configuration | no default passwords, unnecessary services disabled, possibility to reset the product to its original secure state |
| ensure that vulnerabilities can be addressed through security updates | update mechanism, automatic updates with an opt-out where appropriate, notification of users about available updates |
| ensure protection from unauthorised access | authentication, identity and access management, reporting of possible unauthorised access |
| protect the confidentiality of data | encryption of stored and transmitted data using state-of-the-art mechanisms |
| protect the integrity of data, programs and configuration | protection against manipulation, detection and reporting of corruptions |
| minimise data | process only the data that is necessary for the purpose |
| protect the availability of essential functions | resilience, including against denial-of-service attacks, functioning after an incident |
| minimise the negative impact on other devices and networks | the product must not become a risk to the services of others |
| limit attack surfaces | only necessary interfaces, ports and functions open |
| reduce the impact of an incident | exploitation mitigation mechanisms that make it harder to exploit vulnerabilities |
| record and monitor security-relevant activity | recording of relevant access and modifications, with an opt-out for users |
| allow users to securely remove and transfer data | users can permanently remove data and settings and, where feasible, transfer them |
These requirements apply to all products within scope, regardless of the product class. The class only determines the conformity assessment procedure (see CRA product categories and conformity assessment). Which requirements apply to a specific product, and to what extent, follows from the cybersecurity risk assessment and must be justified.
Level 2: Vulnerability handling (Annex I Part II)
These obligations are process obligations. They apply for the entire duration of the support period:
- Identify and document vulnerabilities and components, including by drawing up a software bill of materials (SBOM) in a commonly used and machine-readable format, covering at the very least the top-level dependencies. More on this in the article SBOM under the CRA.
- Address and remediate vulnerabilities without delay, preferably through security updates that are provided separately from functionality updates, where technically feasible.
- Apply regular tests and reviews of the security of the product.
- Publicly disclose fixed vulnerabilities once a security update has been made available: description, affected products, impact, severity and information on remediation.
- Put in place and enforce a policy on coordinated vulnerability disclosure.
- Facilitate the sharing of information from outside, in particular by providing a contact address for reporting vulnerabilities.
- Distribute updates securely, automatically where applicable.
- Disseminate security updates without delay and free of charge, accompanied by advisory messages for users.
In addition, since 11 September 2026 the reporting obligation has applied to actively exploited vulnerabilities and severe incidents, including for products that are already on the market. Deadlines and procedure are described in the article CRA reporting obligations.
Level 3: Manufacturer obligations and evidence (Art. 13)
| Obligation | Content |
|---|---|
| Cybersecurity risk assessment | documented assessment that is taken into account in the planning, design, development, production, delivery and maintenance phases and is updated during the support period |
| Determine the support period | in line with the expected time of use, as a rule at least five years (Art. 13(8)); indicate the end date clearly at the time of purchase |
| Availability of updates | each security update remains available after it has been issued for a minimum of ten years or for the remainder of the support period, whichever is longer (Art. 13(9)) |
| Technical documentation | in accordance with Annex VII, including a description of the product, its design and development, the cybersecurity risk assessment, the support period, applied standards and test reports |
| Conformity assessment | procedure depending on the product class, from internal control to a notified body |
| EU declaration of conformity and CE marking | for software, affixed to the declaration of conformity or the accompanying website, where it must be easily accessible to consumers |
| Retention | technical documentation and declaration of conformity for ten years or for the support period, if that is longer |
| Identification and contact | type, batch or serial number, name and address of the manufacturer, single point of contact for reporting vulnerabilities |
| Information for users | security information and instructions in accordance with Annex II, for example on secure commissioning, updates and the end of support |
| Corrective measures | in the event of non-conformity, bring the product into conformity, withdraw or recall it, and cooperate with the authorities |
Infringements of the essential cybersecurity requirements or of the manufacturer obligations can lead to fines of up to EUR 15 million or 2.5 % of worldwide annual turnover, whichever is higher.
Third-party components and open source
Hardly any product consists only of in-house code. The CRA therefore requires manufacturers to exercise due diligence when integrating components sourced from third parties, including open-source software, so that these do not compromise the cybersecurity of the product. If a manufacturer identifies a vulnerability in a component, it must report it to the person or entity maintaining the component.
In practice this means:
- assess components before use: maintenance status, known vulnerabilities, licence, origin
- monitor dependencies continuously via the SBOM
- agree contractually with suppliers that they provide security updates and SBOM data throughout your support period
- plan replacement strategies for components that are no longer maintained
Anyone who is covered by NIS2 themselves has to manage the security of their supply chain anyway. Both can be built together, see NIS2 and the supply chain.
Obligations of importers and distributors
Anyone who does not manufacture products themselves has graduated obligations:
Importers
Importers may only place on the market products for which the manufacturer has carried out the conformity assessment, drawn up the technical documentation and affixed the CE marking. They indicate their own contact details and inform the manufacturer of vulnerabilities they become aware of.
Distributors
Before making a product available on the market, distributors verify that the CE marking and the manufacturer and importer details are present.
Caution: own brand
Anyone who places a product on the market under their own name or trademark, or substantially modifies it, becomes the manufacturer themselves and bears all the obligations listed here.
Checklist for manufacturers
Organisation
- product portfolio recorded, role determined for each product (manufacturer, importer, distributor)
- product class determined and justified for each product
- persons responsible for product security and vulnerability handling appointed
- reporting process under Art. 14 set up, staffed and rehearsed (mandatory since 11.09.2026)
Product
- cybersecurity risk assessment documented for each product
- gap analysis against Annex I Part I carried out
- secure default configuration and reset function implemented
- signed, traceable update mechanism in place
- support period determined, justified and clearly indicated to buyers
Process
- SBOM generated automatically in the build
- vulnerabilities continuously monitored, assessed and remediated
- coordinated vulnerability disclosure policy published, contact address set up
- security updates provided free of charge and separately from functionality updates, where possible
- supplier contracts secure updates and SBOM data throughout the support period
Evidence
- technical documentation in accordance with Annex VII created for each product family
- conformity assessment procedure clarified, appointment with a notified body requested (if necessary)
- user information in accordance with Annex II drawn up
- EU declaration of conformity and CE marking prepared by 11.12.2027
- retention for at least ten years organised
How SDG supports you
We advise you on the CRA obligations and support implementation in terms of methodology and organisation. Technical implementation in the product remains with your development team.
- Gap analysis against Annex I for each product line, with a prioritised action plan
- Setting up the processes for vulnerability handling, SBOM, coordinated vulnerability disclosure and reporting under Art. 14
- Structuring the technical documentation and preparing for the conformity assessment
- Supplier management, aligned with an existing ISMS based on ISO 27001 or a NIS2 programme
- Training for product management, development and management: training
An overview of all our services can be found on the page Cyber Resilience Act consulting.
Frequently asked questions about CRA obligations for manufacturers
What obligations does a manufacturer have under the Cyber Resilience Act?
It must ensure that the product meets the cybersecurity requirements of Annex I Part I, handle vulnerabilities in accordance with Annex I Part II throughout the support period, carry out a cybersecurity risk assessment and draw up technical documentation, assess conformity, affix the CE marking, and report actively exploited vulnerabilities and severe incidents.
What does secure by default mean under the CRA?
The product must be delivered with a secure default configuration, for example without default passwords and with unnecessary services disabled. It must also be possible to reset it to this original secure state.
For how long must a manufacturer provide security updates?
During the support period, which is based on the expected time of use and is, as a rule, at least five years. The end date must be clearly indicated to buyers. In addition, updates that have been issued must remain available for a longer period.
Do security updates have to be free of charge under the CRA?
Yes. Security updates must in principle be provided free of charge and without delay, accompanied by advisory messages for users. Where technically feasible, they should be offered separately from functionality updates.
Am I responsible for open-source components in my product?
Yes. Manufacturers must exercise due diligence when integrating components sourced from third parties, including open source, and ensure the cybersecurity of the product as a whole. They must report vulnerabilities in components to the maintainers of the component.
What obligations do importers and distributors have?
Importers may only place on the market compliant products with CE marking and technical documentation, and they indicate their contact details. Distributors check the CE marking and the manufacturer details. Anyone who sells under their own brand is considered the manufacturer.
Legal sources: Regulation (EU) 2024/2847 (Cyber Resilience Act), in particular Art. 13, 14, Annexes I, II and VII, BSI: CRA implementation act
Note: This article provides general information and does not replace legal advice in individual cases.