Skip to content

Free CRA assessment

Check if the CRA applies to your product

The Cyber Resilience Act (CRA) is the EU’s security law for connected hardware and software. Answer a few questions about one product to see if it applies and what to do first.

Before you start

Answer for one product at a time

Assess each product separately. This questionnaire is for companies that make, import or sell software or connected devices.

Time
About 2 minutes
Questions
Usually 6 to 12
Your answers
Stay on this page. Nothing is saved or sent.

How the assessment works

How the assessment decides

The assessment applies the Cyber Resilience Act’s tests in turn: whether you sell a product, your role, whether it reaches the EU and connects, any exclusion, and its class. Below is what each question looks at, and the classes, dates and reporting rules behind your result.

Why we ask

What you sell
The CRA covers products, not services. A product can be software on its own, or a part that is sold separately.
Whose brand is on it
The law treats whoever sells a product under their name or brand as its maker. Where it is made does not matter.
Who brings it into the EU
Importers and distributors both resell products, but their duties differ. An importer must verify that the manufacturer has completed the required conformity assessment.
How customers get it
The Commission’s guidance draws the line by where software runs. Software people download and install is a product. A service used only in a browser is not, unless a product needs it to work.
Whether it reaches the EU
The CRA covers products made available in the EU as part of a business, paid or free. Software built only for your own use is not put on sale.
How it connects
Indirect links count too. Being part of a bigger system that connects is enough, so very few products fall outside here.
Other EU laws
Products covered by these rules are left out of the CRA. The aviation exception is narrow: it covers certified equipment only, not the whole industry.
Open source
This is often misread. What matters is whether people pay to get the software itself. Paid support around free software does not bring it in.
Product type
Some product categories require a stricter conformity assessment. The category depends on the product’s core function; additional features do not by themselves change it.
Main purpose
Only the main purpose puts a product in a stricter class. Building one product into another does not, on its own, move the bigger product up.

Product classes and conformity assessment

  • StandardDone by you

    Your product is not on the EU’s lists of important or critical products, so you can use internal conformity assessment. The other duties still apply: security requirements, risk assessment, technical documentation, support period, CE marking and reporting.

  • Important, class IIndependent, in most cases

    For class I, makers may check the product themselves only if they apply the official EU standards for the CRA in full. An EU certification scheme also works. Otherwise an approved independent body (a notified body) must check it. Find out whether those standards exist yet before you rely on them.

  • Important, class IIIndependent

    Makers cannot check class II products themselves. An approved independent body (a notified body) must assess them, or you need an EU security certificate at the required level. Free and open-source software in this class has its own route.

  • CriticalIndependent

    The EU can require an EU cybersecurity certificate for critical products. Where it has not, an approved independent body must check the product, as for class II.

Dates that apply to you

  1. 11 September 2026In force

    Reporting

    Manufacturers must report actively exploited vulnerabilities and severe incidents affecting product security. This also covers products already on the market.

  2. 11 December 2027

    Everything else

    Security requirements, technical documentation, conformity assessment, CE marking and support period.

Reporting deadlines

24 hours

Early warning

Within 24 hours of becoming aware of an actively exploited vulnerability or a severe incident affecting product security.

72 hours

Notification

What you know so far, and what you have done about it.

14 days

Final report on a flaw

Counted from when a fix or workaround is available.

1 month

Final report on an incident

Counted from the 72-hour notification.

You report once, through the EU’s single reporting platform run by ENISA, the EU cybersecurity agency. Each report goes at the same time to ENISA and to the national cybersecurity response team (CSIRT) of the EU country where you have your main base. For makers outside the EU, the law sets which country that is.

This is a first indication, not legal advice. It is based on the Cyber Resilience Act (Regulation (EU) 2024/2847), Implementing Regulation (EU) 2025/2392, Delegated Regulation (EU) 2025/1535 and the European Commission’s guidance of 27 July 2026. That guidance is not binding: only the EU Court of Justice can interpret the law with authority. Each manufacturer makes the final call for its products. Rules checked on 28 October 2026.

Common questions

Common questions

Free 30-minute call

Talk through your products with us

On a free 30-minute call, a senior specialist reviews your result and agrees which products and requirements need closer assessment.