EUProduct ReadyMARKET-ACCESS PREFLIGHT
EN

CONNECTED PRODUCTS

Cyber Resilience Act preflight for products with digital elements

CRA is phased. Reporting obligations apply from 11 September 2026; most product requirements apply from 11 December 2027.

Interactive preflightSource-backedNo signupNot a certification
Decision boundaryThis is a preflight. “Likely applies” still requires the official source and product facts to confirm legal scope.

QUICK ANSWER

What matters before you rely on a listing or supplier file

CRA is not one single start date. Reporting obligations began earlier than the main product requirements, so a connected-product preflight must keep current and upcoming duties separate.

DATES THAT CHANGE THE ANSWER

The deadline that matters for this workflow

Live obligations and future milestones are deliberately separated. Countdown cards are planning aids; product scope still depends on the actual product and role.

How dates are handled →
UPCOMING2027-12-11

CRA FULL APPLICATION

Main CRA product requirements

Calculating…until this milestone

Most CRA product obligations apply from 11 December 2027; reporting is already a separate current layer.

WHO THIS IS FOR

Use this workflow when this is your decision

Manufacturers and importers of products with digital elements that need to distinguish CRA reporting obligations already in force from the broader 2027 product regime.

DECISION MAP

Resolve the questions in this order

This route is not a keyword shell: each step changes what evidence or market action should come next.

01

Confirm product-with-digital-elements scope

Identify software, network and remote-data functions plus any exclusions or special regimes before treating CRA as applicable.

02

Separate the dates

Reporting obligations and the main product or security requirements do not start on the same date.

03

Build vulnerability handling into product operations

Security support, vulnerability intake, remediation and documentation need owners rather than a one-time launch checklist.

EVIDENCE PACK

What a useful working file should contain

Names and formats vary by product regime. Keep evidence tied to the exact product, role and market rather than collecting disconnected PDFs.

Product/software inventory

Hardware, software components, connectivity, dependencies and versions for the marketed product.

Vulnerability process

Intake, triage, remediation, disclosure or reporting and support-period procedures.

Security risk evidence

Product-specific cybersecurity risk assessment and technical measures appropriate to the scope.

Transition plan

Dated gap plan separating already-live reporting readiness from the main 2027 conformity and documentation work.

WORKED EXAMPLE

Connected consumer hub sold today and supported through 2028

Facts

The team knows CRA exists but has one undated task called be CRA compliant, with no separate reporting owner or dated transition plan.

Practical review plan

First confirm product scope, establish the already-relevant reporting and vulnerability process, then schedule the main 2027 product documentation, security and conformity work with clear owners and product-version linkage.

WHAT TO VERIFY

The scanner focuses on these evidence questions

  • Product with digital elements?
  • Current reporting-process readiness
  • Upcoming secure-by-design layer
  • Do not mark 2027 duties as already fully applicable

INTERACTIVE PREFLIGHT

Build an evidence-gap map for your product

Answer what you know. The engine maps product features, role and sales channel to rule cards and compares them with evidence you say you already have. It does not inspect or authenticate a document.

Rules 2026.10.01-1Verified 2026-10-01
Product features
Evidence you already have optional

Tick only evidence you actually hold. The scanner does not inspect or authenticate it.

CRA timeline

Cyber Resilience Act timeline: the four dates that matter

Regulation (EU) 2024/2847 phases in. Treat each date as a separate obligation, not one single deadline.

DateWhat appliesWho acts
10 December 2024The Regulation entered into force. No product obligations yet.Plan scope and budget
11 June 2026Rules for notifying conformity assessment bodies apply.Notified bodies, authorities
11 September 2026Manufacturers must report actively exploited vulnerabilities and severe incidents (Article 14), including for products already on the market.Manufacturers
11 December 2027Main requirements apply: secure-by-design, vulnerability handling, conformity assessment, CE marking and documentation.Manufacturers, importers, distributors

CRA scope

Is your product in CRA scope?

The CRA covers products with digital elements whose intended or foreseeable use includes a direct or indirect data connection to a device or network.

Usually in scope

  • Smart home devices, cameras, smart plugs, wearables and connected toys
  • Routers, modems, network equipment and IoT gateways
  • Software sold as a product, including apps and firmware placed on the market
  • Components with digital elements sold separately

Usually outside CRA (covered by own rules)

  • Medical and in-vitro diagnostic devices
  • Motor vehicles and their components under type approval
  • Civil aviation and marine equipment
  • Pure SaaS without a product it remotely processes data for
  • Free open-source software not supplied in a commercial activity

Important and critical products (for example routers, password managers, smart home security devices) need stricter conformity assessment routes.

COMMON QUESTIONS

Questions this preflight should help you frame

When do Cyber Resilience Act requirements apply?

CRA reporting obligations started applying on 11 September 2026, while most main product requirements apply from 11 December 2027.

Does CRA apply to every connected product?

No. Scope, exclusions and the product’s role as a product with digital elements require product-specific analysis.