Information Technology Assessment, Product Testing and Certification

European Commission publishes new practical guidance on the Cyber Resilience Act

18. November 2026

The European Commission has published new practical guidance to help manufacturers, developers, and other economic operators prepare for the Cyber Resilience Act (CRA).

The CRA has been in force since December 2024, but its main obligations will apply from 11 December 2027. Vulnerability and incident reporting obligations have already started to apply from 11 September 2026.

The new guidance does not introduce additional legal requirements. Instead, it provides practical interpretation of several CRA topics that have raised questions among manufacturers and other stakeholders.

Importantly, this is not just another high-level regulatory document. The guidance includes 67 practical examples, supported by use cases, flowcharts and diagrams. It pays particular attention to microenterprises and SMEs, aiming to help companies apply CRA requirements proportionately and without unnecessary administrative burden.

What does the new guidance clarify?

The guidance focuses particularly on:

  • the scope of the CRA and which products are covered;
  • the role of remote data processing solutions (RDPS);
  • treatment of free and open-source software;
  • what constitutes a substantial modification;
  • determination and application of the support period;
  • cybersecurity risk assessment requirements;
  • vulnerability and incident reporting obligations.

The practical examples are particularly useful because many CRA questions are difficult to answer in isolation. Whether a cloud service forms part of a product, whether a software change constitutes a substantial modification, or how long a product should receive security support depends heavily on the actual product and its intended use.

Existing products and substantial modifications

One particularly useful clarification concerns products already placed on the EU market. Products placed on the market before 11 December 2027 do not automatically need to be brought into full CRA conformity simply because the CRA becomes applicable. However, the situation may change if such a product undergoes a substantial modification after that date.

This distinction is important for manufacturers that maintain products over long periods through software updates, hardware revisions or new functionality. A normal bug fix or minor product change does not automatically mean that the product must undergo a new CRA conformity assessment. The relevant question is whether the modification affects the product in a way that qualifies as substantial under the CRA.

Manufacturers should therefore maintain good traceability between product versions, changes, cybersecurity risk assessments and previously collected security evidence.

The product may be more than the physical device

Another important area concerns the scope of a product with digital elements. For many connected products, cybersecurity cannot realistically be assessed by looking only at the physical device.

The complete product may depend on:

  • firmware,
  • a mobile or web application,
  • APIs,
  • backend services,
  • cloud infrastructure,
  • remote data processing solutions,
  • external or third-party services.

Where such remote components are necessary for the product to perform its functions, they need to be considered when establishing the relevant CRA product boundary.

This makes architecture, interfaces, data flows and trust relationships between components increasingly important parts of cybersecurity assessment.

Cybersecurity risk assessment remains central

The new guidance also addresses manufacturers’ obligations concerning cybersecurity risk assessment. This is important because CRA conformity should not be approached simply as a checklist of technical security controls.

The risk assessment provides the basis for determining:

  • relevant assets and threats;
  • applicable cybersecurity requirements;
  • appropriate risk-treatment measures;
  • necessary security verification and testing;
  • residual risks;
  • vulnerability monitoring and security support during the product lifecycle.

Technical testing should therefore be connected to the identified risks and implemented cybersecurity controls.

Support period and vulnerability handling

The support period is another area receiving additional attention. Manufacturers need to consider how long cybersecurity support will be provided and how vulnerabilities, security updates and relevant product information will be managed during that period.

This links the initial conformity assessment with ongoing activities such as:

  • vulnerability monitoring;
  • coordinated vulnerability disclosure;
  • remediation;
  • secure software and firmware updates;
  • maintenance of component and dependency information;
  • communication with users.

CRA therefore extends product cybersecurity beyond a one-time penetration test or security assessment performed before placing the product on the market.

What should manufacturers do now?

The Commission guidance is non-binding, but it provides a useful indication of how manufacturers should prepare for the CRA.

Organizations should already be working on:

  1. defining the complete product boundary, including associated applications and remote services;
  2. establishing and documenting cybersecurity risk assessments;
  3. maintaining traceability between product versions, risks, security requirements and verification evidence;
  4. establishing vulnerability-handling and reporting processes;
  5. defining and justifying support periods;
  6. preparing technical documentation and objective security-testing evidence.

For products already assessed against cybersecurity standards, existing documentation and test reports may provide useful evidence. The key question will be whether those results remain representative of the product being assessed and whether additional CRA-specific evidence is required.

With 67 practical examples and a strong focus on real implementation questions, the new guidance is one of the more useful Commission documents published so far for organizations preparing for the CRA.

Further information:
European Commission: Commission publishes new guidance to support timely Cyber Resilience Act implementation

Back to all news