Cyber Resilience Act · Regulation (EU) 2024/2847

The Cyber Resilience Act: reporting is live, the rest follows in 2027.

If you make software or connected hardware sold in the EU, the Cyber Resilience Act already requires you to report actively exploited vulnerabilities and severe incidents within 24 hours, and from December 2027 every product must meet its security requirements to carry the CE mark. We set up the reporting process now and build the product security programme behind it.

  • Founder-led
  • ISACA CISM
  • US & EU
  • Reply within one business day
Who needs it

Usually, one of these is true.

This is advisory support, not legal advice. We are not a notified body and do not issue conformity assessments: we prepare you for self-assessment or for the notified body your product category requires.

  • You make software, apps, firmware or connected devices that are sold or made available in the EU.
  • You are a US manufacturer whose EU importers or distributors are asking about the CRA and the CE mark.
  • You have no written vulnerability handling process, software bill of materials or security support period.
  • You need to know whether your product falls into a category that needs a stricter, third-party assessment.
The essentials

The CRA at a glance

TopicWhat to know
Who it coversManufacturers of products with digital elements made available in the EU, plus their importers and distributors, wherever the manufacturer is based.
Reporting, since 11 September 2026For actively exploited vulnerabilities and severe incidents: an early warning within 24 hours, a notification within 72 hours, and a final report within 14 days of a fix for a vulnerability or within a month for an incident, through the EU single reporting platform.
Full applicationFrom 11 December 2027: essential security requirements, vulnerability handling, conformity assessment and the CE mark for products placed on the EU market.
Product dutiesSecure by design and by default, a software bill of materials, a vulnerability disclosure policy, and free security updates for a support period that normally lasts at least five years.
PenaltiesUp to EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher, for breaching the essential requirements.
How we work

From reporting process to CE mark.

  1. Product inventory and classification

    Which products are in scope, and whether any fall into the important or critical categories that need a stricter assessment.

  2. Reporting playbook

    How you spot active exploitation, who decides, and how the 24-hour, 72-hour and final reports are filed, rehearsed now that the duty applies.

  3. Gap assessment

    Each product measured against the essential requirements and vulnerability handling rules, with gaps ranked by effort.

  4. Secure development and SBOM

    A secure development lifecycle, a software bill of materials and a vulnerability disclosure policy that engineering can sustain.

  5. Conformity and documentation

    Technical documentation, support periods and the conformity route for each product, ready for December 2027.

What you get

Deliverables you can hand to an auditor.

Scoped on the free call and agreed as a fixed fee. Start with an Assess project, then Build and Manage as you need them.

  • Product inventory and CRA classification
  • Vulnerability and incident reporting playbook
  • Gap assessment against the essential requirements
  • Vulnerability disclosure policy and handling process
  • SBOM and secure development plan
  • Conformity assessment roadmap and documentation outline
Good to know

Questions about Cyber Resilience Act.

Does the CRA apply to SaaS?

Software delivered purely as a service is generally covered by other EU rules, such as NIS2, rather than the CRA. Remote data processing that a product needs to work, such as a device’s cloud back end, can fall within it. We check your products one by one.

We are a US company. Why does this matter now?

The reporting duty already applies to products on the EU market, including ones sold before the law takes full effect. Your EU importers and distributors have duties too, and they will ask you for evidence.

What is an actively exploited vulnerability?

One with reliable evidence that someone has exploited it in a system without the owner’s permission. The clock starts when you become aware of that evidence.

Does open-source software count?

Open source developed outside a commercial activity is largely outside the CRA. Commercial products that include open-source components are in scope, and their makers answer for those components.

Related: Vulnerability management · NIS2 for US and EU groups

Next step

Start with a free conversation about Cyber Resilience Act.

A free 30-minute conversation to agree what matters most and what to do first. If you would like to prepare, answer the short questionnaire beforehand.

  • Founder-led
  • ISACA CISM
  • US & EU
  • Reply within one business day