Express + expert help

View pricing →
Skip to main content
guideCRA5 min read

CRA readiness countdown — scope, reporting, assessment and release checkpoints

Planning checkpoints before CRA main product obligations apply on 11 December 2027, with reporting already in force, class-specific routes and release evidence.

By Vladimír VicianUpdated

Fact-checked against the law as of Reviewed by Vladimír Vician on How we check

Article 71 of the Cyber Resilience Act (Regulation (EU) 2024/2847) sets the application dates:

ProvisionApplication dateStatus on 21 November 2026
Chapter IV (Articles 35 to 51), notification of conformity assessment bodies11 June 2026In application
Article 14, manufacturer reporting11 September 2026In application
All other provisions, including the product and manufacturer obligations11 December 2027Not yet in application; check scope, conformity and the Article 69 transition

Article 69(2) concerns products placed on the market before 11 December 2027 and later substantial modifications. Article 69(3) expressly brings in-scope legacy products into Article 14 reporting. Manufacturing stock before the date is not the same as placing individual units on the market.

Already in force — Article 14 reporting

Reporting is not a future milestone. If the process is not in place, set it up now: access to the Single Reporting Platform, the people authorised to submit, escalation outside working hours and record keeping. The CRA reporting checklist walks through the steps.

Both reporting paths have a 24-hour early warning and a 72-hour notification, counted from becoming aware. For actively exploited vulnerabilities, Article 14(2)(c) sets the final report at 14 days after a corrective or mitigating measure is available. For severe incidents, Article 14(4)(c) sets it at one month after the 72-hour notification.

About twelve months before application — December 2026

Establish scope per product. Check the connection condition, intended purpose, associated remote processing and Article 2 exclusions. An MDR medical device is excluded from CRA scope; digital functionality alone does not make every product subject to CRA.

Classify by core functionality. Article 7(1) of the Cyber Resilience Act makes a product "important" when it has the core functionality of an Annex III category. Compare the actual product with Annex III, Annex IV and the technical descriptions in Implementing Regulation (EU) 2025/2392. A component or marketing name does not decide the final product’s class. Record the reasoning and unresolved questions.

Assess modifications. Use the test in Article 3(30) and the Commission guidance on the application of the Cyber Resilience Act (C/2026/6013), section 4. A new interface or SoC needs an impact assessment; it is not automatically a substantial modification merely because that feature changed. Preserve the product, firmware and placement evidence for the decision.

Assign economic-operator roles. Article 18 permits appointment of an authorised representative by written mandate. It does not impose a universal representative requirement. Identify manufacturer and importer duties, any applicable responsible-operator requirement and the actual mandate tasks. See the representative overview.

Plan engineering and assessment capacity. If the chosen route needs a notified body, ask the bodies you are considering for their current lead times. Assessment duration and capacity vary by product and body, so this page gives no standard figure.

About six months before application — June 2027

Make the SBOM and handling process reproducible. Annex I Part II requires a commonly used, machine-readable SBOM covering at least top-level dependencies. Neither automatic generation on every development build nor a named CycloneDX/SPDX format is universally prescribed by that wording. Build a workflow that produces the required release evidence and documents remaining coverage gaps. See embedded tooling.

Verify controls and risk evidence. Connect the Article 13(2) assessment with actual implementation and tests. Establish the support period, update arrangements and vulnerability-handling process. A proposed control is not a completed test.

About three months before application — September 2027

Verify the route against Article 32 of the Cyber Resilience Act. The European Commission's conformity assessment page gives an overview.

  • Products outside the important and critical categories: Article 32(1) offers every route, including internal control (module A). Applying a harmonised standard is not a precondition for module A here.
  • Important Class I: internal control is available only where harmonised standards, common specifications or a European cybersecurity certification scheme at assurance level at least 'substantial' are applied (Article 32(2)); otherwise B+C or H. Check whether a standard has actually been cited: see CRA harmonised standards.
  • Important Class II: B+C, H or, where available and applicable, a European cybersecurity certification scheme at assurance level at least 'substantial' (Article 32(3)). Qualifying free and open-source products can use the Article 32(1) routes if their technical documentation is public (Article 32(5)).
  • Critical products: a European cybersecurity certificate is required only where a delegated act under Article 8(1) says so; otherwise the Class II routes apply (Article 32(4)). On 21 November 2026 EUR-Lex listed two delegated regulations supplementing the Cyber Resilience Act, (EU) 2025/1535 and (EU) 2026/881, and neither was adopted under Article 8(1).

Document the route, scope, actual applied specifications and completed assessment evidence. For radio products, perform the separate RED assessment; an EN 18031 citation is not automatic CRA coverage.

Release check — 11 December 2027

For units and obligations affected by main application, verify the technical documentation against Annex VII, the declaration against Article 28 and Annex V, marking, instructions, support information and the actual assessment result. Preserve the release configuration, evidence and issuance record.

Do not cite future assessments as completed, or treat a certificate preserved by Article 69(1) as a blanket replacement for all CRA requirements. Resolve the product-specific transition and certificate scope first.

Explore Cenitia’s compliance workflow

Review the supported scope and workflow

FAQ

Frequently asked questions

  • Which CRA obligations already apply?

    As of 21 November 2026, two parts of the Cyber Resilience Act (Regulation (EU) 2024/2847) apply: Chapter IV on the notification of conformity assessment bodies, since 11 June 2026, and Article 14 manufacturer reporting, since 11 September 2026. The product and manufacturer obligations apply from 11 December 2027, subject to scope and the Article 69 transition.

  • Is a CRA authorised representative mandatory for every non-EU manufacturer?

    No. CRA Article 18 permits appointment by written mandate. Assess any separate responsible-economic-operator rule and sector-specific duty, and distinguish the importer’s tasks from representative tasks.

  • Can every Class I product use internal control?

    No. Under Article 32(2) of the Cyber Resilience Act a Class I product can use internal control (module A) only where harmonised standards, common specifications or a European cybersecurity certification scheme at assurance level at least 'substantial' are applied. Where they are not applied, are applied only in part or do not exist, Class I needs modules B+C or H. Class II needs B+C, H or, where available and applicable, such a certification scheme (Article 32(3)). Qualifying free and open-source important products can use module A if their technical documentation is public (Article 32(5)).

  • What are the final reporting deadlines?

    Both reporting paths have a 24-hour early warning and 72-hour notification from awareness. The vulnerability final report is due within 14 days after a corrective or mitigating measure becomes available. The severe-incident final report is due within one month after the 72-hour notification. Do not combine those triggers.

  • Are the preparation checkpoints legal deadlines?

    No. The December, June and September planning checkpoints are suggested project milestones. Set them using the actual product, engineering effort, evidence gaps and assessment-body availability. The application dates and statutory reporting deadlines remain legally distinct.

Continue reading

Related guides

Put this into practice

Free tools & references

New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.