Skip to content
14/19RegulationSupported in WardBee

EU Cyber Resilience Act (CRA) explained

EU law making manufacturers responsible for the cybersecurity of any product with digital elements they sell.

See current catalog counts, technical check coverage, and remaining gaps

This reference explains the framework. Product coverage depends on the bundled catalog, connected evidence, and assessment scope; a technical mapping is not full compliance.

Automation coverage

4 of 35 controls have an automated technical check (11.4% automated). 31 require human evidence and are excluded from automated claims.

What we automate, and what we don't — from the bundled EU Cyber Resilience Act control mapping. This is coverage of the framework, not a compliance score.

What it is

Regulation (EU) 2024/2847 sets mandatory cybersecurity requirements for products with digital elements placed on the EU market — hardware and software alike. Manufacturers must ship products free of known exploitable vulnerabilities, maintain a component inventory and a coordinated disclosure process, provide security updates across a defined support period, report actively exploited vulnerabilities and severe incidents to ENISA and national CSIRTs, and hold technical documentation backing the CE marking.

Latest EU Cyber Resilience Act updates

Framework Watch →

Certifiable?

Not a certification — it is law. Conformity is declared (and for higher-risk classes, assessed) and shown by CE marking.

Where it's used

Anywhere in the EU market: manufacturers, importers, and distributors of connected hardware, software products, and the remote data processing sold with them.

Effort level

Heavy and ongoing: it covers the whole product lifetime, with a 24-hour reporting clock once you are aware of active exploitation.

Typical trigger

You sell or distribute a product with digital elements in the EU. Scope follows the market, not your headquarters.

Related frameworks

Sits beside ISO 27001 and SOC 2 rather than replacing them — those cover your organization, the CRA covers your product.

Why it matters

The CRA moves product security from a selling point to a condition of market access. From December 2027, a product with digital elements cannot carry CE marking — and therefore cannot be sold in the EU — unless its security requirements, vulnerability handling, and technical documentation are in place. The reporting duties bite a year earlier, and they run on hours, not weeks.

When is it needed?

As soon as you place a product with digital elements on the EU market, or plan to. Teams usually start when a distributor asks how the product will be CE marked under the CRA, or when a customer asks for an SBOM. Article 14 reporting obligations have applied since 11 September 2026.

Use cases

  • Connected hardware and IoT devices sold into the EU
  • Commercial software products and on-premise applications
  • SaaS with remote data processing sold as part of a product
  • Component and library vendors supplying other manufacturers
  • Importers and distributors verifying manufacturer conformity

Who asks for it?

  • Market surveillance authorities in EU member states
  • National CSIRTs and ENISA for reportable vulnerabilities and incidents
  • Notified bodies assessing important and critical product classes
  • Distributors and importers before taking a product to market
  • Enterprise customers asking for an SBOM and a support commitment

Benefits

  • Market access: CE marking under the CRA is the entry ticket to the EU
  • One product register that answers customer SBOM and support questions
  • Reporting deadlines tracked from the moment awareness is recorded
  • Evidence assembled continuously instead of rebuilt before every audit
  • Clear split between what is proven and what still needs human sign-off
  • Groundwork that also serves ISO 27001, SOC 2, and IEC 62443 programs

Legal requirements

Yes. Regulation (EU) 2024/2847 entered into force on 10 December 2024. Reporting obligations under Article 14 apply from 11 September 2026 and the regulation applies in full from 11 December 2027. Non-compliance carries administrative fines and can remove a product from the EU market. This is a summary, not legal advice.

Key control areas

Secure-by-default configuration and no known exploitable vulnerabilities at release
Product risk assessment carried through design and development
Component inventory (SBOM) maintained per release
Coordinated vulnerability disclosure policy and contact point
Security updates for the declared support period
Early warning within 24 hours of awareness of active exploitation
Notification within 72 hours, followed by a final report
Technical documentation, conformity assessment, and EU declaration of conformity
User information and instructions covering secure use
Product classification: default, important class I or II, or critical

Want to see how WardBee maps your environment to EU Cyber Resilience Act?

What's new · v1.0.0

ScanComb and WardBee 1.0: compliance checks, TISAX and SOC 2 readiness, and a new public site

This is the first release of ScanComb and WardBee. WardBee brings automated compliance checks, framework workspaces, reports and task tracking for engineering, security and compliance teams. scancomb.com adds free checks and a TISAX readiness check, plus guides and news.

Highlights

  • TISAX readiness check Answer a public questionnaire and get a free readiness score by email. A paid report adds findings, an action plan for each chapter, a roadmap and a PDF. You can import the gaps into a WardBee workspace as tasks.
  • Dedicated TISAX section in WardBee Manage TISAX in one place. Set the scope, keep a self-assessment register, follow an action plan with tasks, track audits and labels, and manage suppliers and exports.
  • SOC 2 readiness Work through a readiness questionnaire, criterion guidance, a policy pack and reviews. Criteria are explained in plain words and questions can be answered in the side drawer. You can download a SOC 2 readiness report as a PDF.
  • Sovereignty Profile free check Run the free Sovereignty Profile check and get a report. The scores are explained in plain words.
  • Projects with a shared scan pool Run several projects or clients in separate workspaces that share one pool of scans. A For consultants page explains the setup.

Improvements

  • Resource inventory See an inventory of your resources with filters, saved views and notifications.
  • EU Cyber Resilience Act support Prepare for the EU Cyber Resilience Act with product classification and a continuous technical file.
  • NIS2 Supplier Check Assess suppliers against NIS2 with the NIS2 Supplier Check.
  • Free AI security check and AI Shield playbooks Take a free AI security check and read practical playbooks on AI agent permissions, prompt injection, shadow AI and more.
  • Manual control verification Verify controls that cannot be checked automatically, using a clearer drawer for manual controls.
  • Clearer controls and findings Findings and resource names are easier to read, you can filter to checks-only scans, and you can compare one scan with the previous one.
  • Faster control and dashboard pages Controls, the dashboard and risks load faster. App pages show a loading state right away.
  • Better start for new workspaces New workspaces start with ISO 27001 and SOC 2, with an explanation of what scans do. If no frameworks are chosen, a Choose frameworks step guides you.
  • Support tickets, announcements and notification bell Open support tickets inside WardBee and get email updates. Announcements appear in a header bell.
  • New site design, menu and guides scancomb.com has a new look and a grouped menu with News, Free checks and Guides. WardBee uses the same visual style, and the in-app docs are task-focused guides.
  • What's New and Framework Watch A What's New dialog shows release notes on scancomb.com. A weekly Framework Watch news issue is also published.
  • Team invitations and two-factor sign-in Invite teammates by email with consistent role names. Two-factor setup includes a QR code.

Fixes

  • Security improvements to sign-up and sign-in Sign-up and sign-in are now better protected.
  • More accurate AWS multi-factor authentication checks All MFA device types are now recognized, and users who only use programmatic access are no longer flagged.
  • Confirmed failures are shown correctly A confirmed failure now outranks an error in a control's status.
  • One critical-control email per scan You now get a single critical-control email per control for each scan.
  • Smoother onboarding and failed checks Workspaces without frameworks are sent to setup. Checks that fail are refunded, and queued checks show as Queued.
  • Correct access errors Signed-out or unauthorized requests now get a proper access error instead of a server error.