- Products are default, important (Class I or Class II, Annex III) or critical (Annex IV). The category decides the conformity assessment route under Article 32
- Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents through the single reporting platform, under two separate sets of deadlines
- The support period must be at least five years unless the product is expected to be in use for less time (Article 13(8))
This page covers the detailed CRA obligations: product categories and conformity assessment, the essential requirements, SBOMs, support periods, reporting, open source, products already on the market and the evidence to keep. For scope, roles, the timeline and fines, see our Cyber Resilience Act guide.
Product categories and conformity assessment
The essential requirements are the same for every product. What changes with the category is how conformity must be demonstrated (Article 32). Important products are listed in Annex III, split into Class I and Class II. Critical products are listed in Annex IV. Annex I is not a list of products: it holds the essential requirements themselves.
| Category | Where it is listed | Examples from the annexes | Conformity assessment route |
|---|---|---|---|
| Default | Not listed in Annex III or IV | Most products, for example many business applications and consumer devices without a listed core function | Internal control (module A) is allowed. The manufacturer may also use a third-party route |
| Important, Class I | Annex III, Class I | Identity management systems, standalone browsers, password managers, anti-malware software, VPN products, SIEM, operating systems, routers and modems, smart home security products | Internal control only if harmonised standards, common specifications or a European cybersecurity certification scheme are applied in full. Otherwise EU-type examination (modules B and C) or full quality assurance (module H) |
| Important, Class II | Annex III, Class II | Hypervisors and container runtime systems, firewalls, intrusion detection and prevention systems, tamper-resistant microprocessors and microcontrollers | EU-type examination (modules B and C), full quality assurance (module H), or a European cybersecurity certification scheme at assurance level at least "substantial" |
| Critical | Annex IV | Hardware devices with security boxes, smart meter gateways, smartcards and secure elements | European cybersecurity certification where the Commission requires it by delegated act. Until then, the Class II routes apply |
Classification depends on the product's core functionality, not its trade name or the sector you sell into. A product that merely integrates a listed component, such as a smart fridge with a browser built in, is not an important product for that reason alone. A product whose core function is a listed one, such as a standalone password manager, is. The Commission's implementing regulation on the technical descriptions of Annex III and IV categories sets out where each category starts and ends, and it is worth reading before you settle on a class.
The essential cybersecurity requirements
Annex I has two parts. Part I covers the properties of the product. Part II covers the vulnerability handling the manufacturer must run for as long as the product is supported.
Part I: product properties
- Products are designed, developed and produced to ensure a level of cybersecurity appropriate to the risks, based on a documented cybersecurity risk assessment (Article 13(2)).
- They are made available without known exploitable vulnerabilities.
- They ship with a secure by default configuration, with the option to reset to the original state.
- Vulnerabilities can be addressed through security updates, including automatic updates where applicable, with an opt-out.
- They protect the confidentiality, integrity and availability of data, process only the data needed for the intended purpose, limit attack surfaces and reduce the impact of incidents.
- They record and monitor relevant internal activity, and let users remove their data and settings securely.
Part II: vulnerability handling
- Identify and document vulnerabilities and components, including an SBOM.
- Address and remediate vulnerabilities without delay, and provide security updates, where technically feasible separately from functionality updates.
- Test and review the product's security regularly.
- Publish information about fixed vulnerabilities once an update is available, with limited exceptions.
- Put in place and enforce a coordinated vulnerability disclosure policy and a contact address for reporting vulnerabilities.
- Distribute security updates securely and without delay, free of charge unless agreed otherwise for a tailor-made product.
Software bill of materials (SBOM)
Annex I Part II requires manufacturers to draw up an SBOM "in a commonly used and machine-readable format covering at the very least the top-level dependencies of the product". The Act does not name a format. SPDX and CycloneDX are widely used and meet the description, but the regulation does not require either one.
The SBOM forms part of the technical documentation. You do not have to publish it, but market surveillance authorities can ask for it. It lists components and versions. It is not a vulnerability report: vulnerability status comes from your monitoring process, which uses the SBOM as its inventory.
Many manufacturers will need software composition analysis tooling and a release process that regenerates the SBOM for each build. If you cannot yet say which open source libraries ship in each product version, building that inventory is a sensible first step.
Support period
Manufacturers must determine a support period for each product. Under Article 13(8) it reflects the time the product is expected to be in use and is at least five years, unless the product is expected to be in use for less than five years, in which case it matches that shorter period. The shorter period has to follow from how the product is expected to be used, not from the lifecycle the manufacturer would prefer commercially. The manufacturer takes into account user expectations, the nature of the product and relevant EU law when setting it.
During the support period, the manufacturer handles vulnerabilities in line with Annex I Part II. Each security update must remain available for at least ten years after it is issued, or for the rest of the support period if that is longer (Article 13(9)). The end date of the support period, at least month and year, must be shown clearly at the time of purchase and, where possible, on the product or its interface (Article 13(19)).
Reporting obligations since September 2026
Article 14 has applied since 11 September 2026. It applies to every product with digital elements on the EU market, including products placed on the market before December 2027. It contains two separate duties, each with its own deadlines.
| Stage | Actively exploited vulnerability | Severe incident affecting the security of the product |
|---|---|---|
| Early warning | Without undue delay and within 24 hours of becoming aware | Without undue delay and within 24 hours of becoming aware |
| Notification | Without undue delay and within 72 hours, with general information on the product, the exploit and corrective or mitigating measures | Without undue delay and within 72 hours, with information on the nature of the incident, an initial assessment and measures taken |
| Final report | No later than 14 days after a corrective or mitigating measure is available | Within one month after the 72-hour incident notification |
The clock starts when the manufacturer becomes aware of the facts that make something an actively exploited vulnerability or a severe incident. Do not wait for a CVE to be assigned or for the technical investigation to finish. If your support team receives evidence on Monday that customers are being attacked through a firmware flaw, the early warning is due on Tuesday, even if the CVE is published weeks later.
Both are submitted through the single reporting platform run by ENISA (Article 16). A notification goes to the CSIRT designated as coordinator in the member state of your main establishment and to ENISA at the same time. ENISA opened the platform on 11 September 2026. You file once and the coordinating CSIRT shares the notification with other member states where the product is sold. The manufacturer must also inform affected users about the vulnerability or incident and any mitigating measures they can take, where necessary in a structured, machine-readable format.
A severe incident under the CRA is not the same thing as a personal data breach. A CRA incident concerns the security of the product. It may or may not involve personal data. If it does, you assess the GDPR notification separately and report it to the data protection authority. One event can trigger both duties, with different recipients and deadlines.
Open source software
Free and open source software that is not made available in the course of a commercial activity is outside the CRA. Whether an activity is commercial needs a case-by-case analysis. Charging for the software, or monetising it through a related service or platform, points to a commercial activity. Contributing code to a project you do not control does not by itself make you a manufacturer, and a volunteer maintainer publishing software outside a commercial activity is not a manufacturer either.
The Act creates a separate role for open-source software stewards: legal persons, such as some foundations, that systematically provide sustained support for the development of free and open source software intended for commercial activities. Stewards must have a documented cybersecurity policy, cooperate with market surveillance authorities and report actively exploited vulnerabilities and severe incidents to the extent they are involved in development (Articles 3(14) and 24). Their obligations are lighter than a manufacturer's, and they are not subject to administrative fines (Article 64(10)).
If you are a manufacturer that ships open source components inside your own product, you remain responsible for those components. Annex I applies to the whole product, and you report vulnerabilities you find in a component to whoever maintains it.
Products already on the market
Article 69 sets the transitional rules. A product placed on the EU market before 11 December 2027 is subject to the CRA only if it undergoes a substantial modification from that date. The reporting duties in Article 14 are the exception: they apply to all products with digital elements placed on the market, including those placed before 11 December 2027. This is not a blanket exemption: continuing to sell a version already on the market and placing new versions on the market have to be assessed against the transitional rules and the legal meaning of placing on the market. Do not assume that every product developed before December 2027 is exempt. EU-type examination certificates and approval decisions already issued for the cybersecurity requirements of other EU harmonisation legislation remain valid until 11 June 2028, unless they expire sooner.
What counts as a substantial modification is addressed in the Commission's July 2026 guidance. A security update that does not change the intended purpose is generally not one. A software update that adds functions or changes the risk profile may be.
Evidence to have ready
Market surveillance authorities will ask for documents, not intentions. This matrix lists what we would expect a manufacturer to be able to produce.
| Area | Requirement | Evidence |
|---|---|---|
| Scope and classification | Articles 2, 6 and 7, Annexes III and IV | Product inventory with role, core functionality, category and the reasoning behind it |
| Cybersecurity risk assessment | Article 13(2) and (3) | Documented risk assessment per product, updated during the support period |
| Security by design | Annex I Part I | Secure development policy, default configuration records, test results |
| Vulnerability handling | Annex I Part II | Coordinated vulnerability disclosure policy, contact point, triage and remediation records |
| SBOM | Annex I Part II(1) | Machine-readable SBOM per release, covering at least top-level dependencies |
| Support period | Article 13(8), (9) and (19) | Support period decision and rationale, end date shown at purchase, update availability records |
| Conformity assessment | Article 32, Annex VII | Technical documentation, EU declaration of conformity, notified body certificate where needed, CE marking |
| Incident reporting | Article 14 | Registration on the single reporting platform, named reporters, escalation procedure, records of each report and user notification |