Cyber Resilience Act: what hardware and software manufacturers must do by 2027

Key takeaways

  • The CRA is a regulation, not a directive. It applies directly in every EU Member State, so there is no national law to wait for.
  • It covers almost every connected hardware and software product sold in the EU, from routers and IoT devices to mobile and desktop applications.
  • Reporting obligations have applied since 11 September 2026: an early warning within 24 hours and a notification within 72 hours, through ENISA's single platform, which forwards them to the coordinating CSIRT of your Member State.
  • From 11 December 2027, new products must meet the essential requirements of Annex I and carry the CE marking, and the manufacturer must handle vulnerabilities for the whole support period.
  • Annex I explicitly requires products to be placed on the market without known exploitable vulnerabilities and their security to be tested effectively and regularly. A penetration test is the most direct evidence.
  • Fines reach up to €15 million or 2.5% of worldwide annual turnover.

“The CRA won’t matter to us until December 2027.” We hear this from software and device manufacturers more and more often. It is only half true.

The Cyber Resilience Act (Regulation (EU) 2024/2847) does not apply in full until 11 December 2027, but its first hard obligation has applied since 11 September 2026. Since that date, a manufacturer must report every actively exploited vulnerability in its product within 24 hours, including in products it sold years ago.

This article covers who the CRA applies to, which deadlines are already running, what your product must meet and where penetration testing fits in.

What the Cyber Resilience Act is and who it applies to

The CRA introduces uniform cybersecurity requirements for what it calls products with digital elements: hardware and software whose intended or reasonably foreseeable use includes a data connection to a device or a network. It works much like product safety law: a product that does not meet the requirements does not get the CE marking and cannot be sold in the EU.

Three types of economic operator carry obligations:

  • The manufacturer develops or manufactures the product and places it on the market under its own name or trademark. It carries most of the obligations.
  • The importer checks that a product from a manufacturer outside the EU meets the requirements and comes with documentation.
  • The distributor checks the CE marking and does not sell a product it knows to be non-compliant.

Watch out for one trap: if you substantially modify someone else’s product or sell it under your own brand, the CRA treats you as the manufacturer, with every obligation that comes with it.

Typically in scope: smart home devices and cameras, routers and network equipment, industrial control systems, mobile apps, desktop and on-premise software, firmware, operating systems, and libraries and components sold separately.

Out of scope:

  • medical devices, motor vehicles, civil aviation and marine equipment, which have their own legislation,
  • pure SaaS with no delivered product, which falls under NIS2,
  • non-commercial open source. Open-source projects that companies systematically support fall under the lighter regime for so-called open-source software stewards.

There is an important exception for SaaS. If your cloud backend is necessary for the product to perform one of its functions, most often with an app or device controlled through the cloud, the CRA treats it as part of the product.

Timeline: the dates that are already running

The CRA is phased in. There are only 15 months between the first hard obligation and full application.

DateWhat happens
10 December 2024The CRA entered into force
11 June 2026The rules on notification of conformity assessment bodies started to apply
11 September 2026Reporting obligations under Article 14; ENISA's reporting platform launched
11 December 2027Full application: essential requirements, conformity assessment, CE marking

The harmonised standards you will use to demonstrate conformity are still being finalised, and the Commission has already proposed pushing back their delivery deadlines. Until a standard is cited in the Official Journal of the EU, it does not give a presumption of conformity. So do not wait for the standards: you will need vulnerability handling, an SBOM, risk assessment and testing in any case.

Reporting since 11 September 2026: 24 hours, 72 hours, 14 days

The manufacturer must report two types of event: actively exploited vulnerabilities and severe incidents that affect the security of the product. The deadlines run from the moment you become aware of the event.

StageActively exploited vulnerabilitySevere incident
Early warningwithin 24 hourswithin 24 hours, including whether the incident is suspected of being caused by unlawful or malicious acts
Notificationwithin 72 hourswithin 72 hours
Final reportno later than 14 days after a corrective measure is availablewithin 1 month of the notification

What to watch out for:

  • It covers old products too. The reporting obligation also applies to products placed on the market before 11 December 2027. Your installed base is in play right now.
  • Not every bug is reported. You only report a vulnerability for which you have reliable evidence that someone has exploited it. A vulnerability that you or your pentester find is fixed through your normal vulnerability handling process.
  • Reports go through ENISA’s Single Reporting Platform (SRP), which delivers them to ENISA and the coordinating CSIRT at the same time. Which CSIRT that is depends on the manufacturer’s main establishment, meaning the Member State where decisions on the cybersecurity of its products are predominantly taken. ENISA publishes the list of coordinating CSIRTs.
  • Inform your users as well. You must tell the affected users about the exploited vulnerability or incident and about any measures they can take.
  • Keep your own clock. In its first version, the platform’s 72-hour counter does not run from the moment you became aware of the event but from the submission of your early warning. The statutory deadline is what counts, so record the moment of awareness in your incident log.
  • Set up access in advance. Platform accounts are personal, through EU Login with multi-factor authentication. Create them now, not in the middle of an incident.

If you are also an essential or important entity under NIS2, incidents affecting your own operations are reported separately under your national NIS2 law, to your national CSIRT or competent authority.

What a product must meet from December 2027

From 11 December 2027, every new product must meet the essential requirements of Annex I. They come in two parts: the properties of the product itself and the process the manufacturer uses to handle vulnerabilities.

Part I: product security

  • placed on the market without known exploitable vulnerabilities,
  • secure by default configuration, with the option to reset the product to its original state,
  • security updates, where applicable automatic by default with an option to turn them off,
  • protection from unauthorised access: authentication, identity and access management,
  • confidentiality of data (encryption at rest and in transit) and integrity of data, commands, programs and configuration,
  • minimisation of the data processed,
  • availability of essential functions, also after an incident, including resilience against DoS attacks,
  • minimal negative impact on the availability of services provided by other devices and networks,
  • the smallest possible attack surface, including external interfaces,
  • mechanisms that reduce the impact of an incident,
  • logging of security-relevant events,
  • secure and easy deletion of all data and settings.

Part II: vulnerability handling

  • a software bill of materials (SBOM) in a machine-readable format, covering at least the top-level dependencies,
  • fixing vulnerabilities without delay and, where technically feasible, shipping security updates separately from feature updates,
  • effective and regular security tests and reviews,
  • publishing information about fixed vulnerabilities,
  • a coordinated vulnerability disclosure (CVD) policy and a contact address for reports,
  • secure distribution of updates, free of charge and with an accompanying advisory.

On top of this come a cybersecurity risk assessment, technical documentation and the EU declaration of conformity. The manufacturer sets the support period according to how long the product is expected to be in use, generally at least five years.

Product categories and conformity assessment

How you demonstrate conformity depends on the product category. Most products fall into the default category and can be self-assessed.

CategoryExamplesConformity assessment
Defaulteveryday apps, consumer electronics, most IoT devicesself-assessment by the manufacturer
Important, class I (Annex III)browsers, password managers, VPNs, SIEM, operating systems, routers and switches, IAM and PAM, smart locks, security camerasself-assessment only if harmonised standards are applied in full, otherwise a notified body
Important, class II (Annex III)hypervisors and container runtimes, firewalls, IDS and IPS, tamper-resistant microprocessors and microcontrollersalways third party: a notified body or European certification
Critical (Annex IV)hardware security modules, smart meter gateways, smartcardsEuropean cybersecurity certification where a delegated act requires it, otherwise the class II procedures

If your product falls into class I or class II, book a notified body as early as you can. Capacity will be tight before December 2027.

Fines: a GDPR-style model

The CRA borrows its three-tier fine structure from the GDPR. The higher of the two amounts always applies.

InfringementMaximum fine
Essential requirements (Annex I) and manufacturer obligations, including reporting (Articles 13 and 14)€15 million or 2.5% of worldwide annual turnover
Other obligations, for example of importers, distributors or in conformity assessment€10 million or 2%
Incorrect, incomplete or misleading information to authorities€5 million or 1%

Micro and small enterprises cannot be fined for missing the 24-hour early-warning deadline. The duty to report and the other deadlines still apply to them in full. Beyond fines, the market surveillance authority can order corrective action, restrict the product’s sale or withdraw it from the market.

CRA, NIS2 and ISO 27001: what covers what

The CRA regulates the product, NIS2 regulates how an organisation runs its operations, and ISO 27001 is a voluntary management system. Many companies will deal with all three at once.

CRANIS2ISO/IEC 27001
Subjectproducts with digital elementsthe organisation's services, networks and systemsinformation security management system
FormEU regulation, directly applicabledirective, transposed into national lawvoluntary standard with certification
Applies tomanufacturers, importers, distributorsessential and important entitiesanyone who chooses it
ReportingENISA and CSIRT via the SRP, 24 h and 72 hnational CSIRT or competent authority, 24 h, 72 h and 1 monthno obligation towards an authority
Consequence of non-compliancesales ban, fine up to €15 million or 2.5%fines and management liabilityloss of the certificate

The CRA does not directly affect a pure SaaS company; NIS2 does, if the company meets its criteria. But if you ship an app, an agent or a device with your service, you may fall under both regimes. ISO 27001 controls 8.8 (management of technical vulnerabilities) and 8.29 (security testing in development and acceptance) are a good foundation for the CRA.

In its Digital Omnibus package, the Commission proposes a single entry point for reporting incidents under NIS2, the GDPR and DORA, built on the CRA platform. The proposal is still going through the legislative process, so for now you report to each recipient separately.

Where penetration testing fits in

The CRA never uses the words “penetration test”, but without one, Annex I is hard to meet. Two requirements are unambiguous: the product must not go on the market with known exploitable vulnerabilities, and the manufacturer must test its security effectively and regularly.

A simple rule applies: a vulnerability we find does not have to be reported within 24 hours. One an attacker finds does.

CRA requirementHow a test demonstrates it
No known exploitable vulnerabilitiesa penetration test before each release, a dependency check against the SBOM
Protection from unauthorised accesstests of authentication, authorisation, session management and APIs (e.g. IDOR, BOLA)
Confidentiality and integrityverification of encryption in transit and at rest, and of firmware and configuration signing
Minimal attack surfacemapping open ports, unused services and debug interfaces such as UART or JTAG
Secure distribution of updatestesting the OTA mechanism: signature verification, downgrade, man-in-the-middle
Effective and regular testinga repeat test for every major release, plus retests of fixes

And the product means the whole chain: the device and its firmware, the mobile app, the API and the cloud backend. An attacker picks the weakest link, so the test has to cover all of them. The test report, with its risk ratings and remediation steps, also feeds the risk assessment in your technical documentation. We cover what auditors expect from technical evidence in Penetration test: the key to a successful cybersecurity audit.

A practical plan: what to do before December 2027

The first two steps concern obligations that already apply, so do not leave them until the end.

  1. Map your portfolio. Which products are in scope, which role you play (manufacturer, importer, distributor) and which category each product falls into.
  2. Get ready to report today. Identify your coordinating CSIRT, create accounts on the ENISA platform, decide who determines that a vulnerability is “actively exploited”, and rehearse the 24-hour scenario.
  3. Put a coordinated vulnerability disclosure policy in place. A public contact, such as security.txt or a security@ address, and a clear process for researchers.
  4. Build an SBOM and monitor your dependencies. A vulnerability in a third-party library is your vulnerability.
  5. Run a gap analysis against Annex I and a cybersecurity risk assessment for each product.
  6. Test the product end to end with a penetration test, and build testing into your release cycle.
  7. Vet your component suppliers. Manufacturers must exercise due diligence when integrating third-party components.
  8. Prepare the documentation and conformity assessment. Technical documentation, the support period, the EU declaration of conformity and, for class I or class II, a notified body booked in time.

How Haxoris can help

Over more than 10 years and 400+ penetration tests, we have seen where products fail most often. For the CRA, we can deliver:

  • Penetration testing of the whole product: web and mobile applications, APIs, IoT devices and firmware and the cloud backend in AWS, Azure or GCP. You can use the reports, with their risk ratings and concrete remediation steps, directly in your technical documentation.
  • A security audit against Annex I: where you stand today, what is missing and in what order to tackle it.
  • Regular testing and retests tied to your release cycle, so you can demonstrate effective and regular testing.
  • Red teaming: we check whether your team detects a real attack and handles it within the deadlines the CRA and NIS2 require.
  • One test, several frameworks: results you can use for the CRA, NIS2 and ISO 27001.

Related articles: What is penetration testing? · Penetration test: the key to a successful cybersecurity audit · CVE-2026-24061: the telnetd bug that turns “secure” networks into root access

Want to know where your product is weak before an attacker finds out? Book a free consultation.

Cyber Resilience Act – frequently asked questions

01

When does the Cyber Resilience Act apply?

Regulation (EU) 2024/2847 entered into force on 10 December 2024 and applies in stages. The rules on notified bodies have applied since 11 June 2026, manufacturers' reporting obligations since 11 September 2026, and the essential requirements, conformity assessment and CE marking apply from 11 December 2027.

02

Does the CRA cover software we give away for free?

Yes, if you make it available in the course of a commercial activity, for example a free app that comes with a paid service. Only non-commercial open source is out of scope.

03

We are a SaaS company. Does the CRA apply to us?

Pure SaaS does not; that is NIS2 territory, if you meet its criteria. But if you ship an app, an agent or a device with the service, or your cloud is necessary for a product delivered that way to work, the CRA applies to you.

04

Do we have to report a vulnerability our pentester finds?

No. Only actively exploited vulnerabilities are reported. You fix a vulnerability found in testing through your vulnerability handling process and publish information about it once the fix is released.

05

Who do we report an actively exploited vulnerability to?

Through ENISA's Single Reporting Platform, which delivers the notification simultaneously to ENISA and to the CSIRT designated as coordinator in the Member State of your main establishment, meaning where decisions on the cybersecurity of your products are predominantly taken. ENISA publishes the list of coordinating CSIRTs. The early warning is due within 24 hours of becoming aware.

06

What about products we sold before December 2027?

The reporting obligations have applied to them since 11 September 2026. The Annex I requirements only apply to them if you substantially modify them after 11 December 2027.

07

Should we wait for the harmonised standards?

No. The standards are still being finalised and their deadlines keep moving, but vulnerability handling, the SBOM, risk assessment and testing do not depend on them. You need these steps whichever route you take to demonstrate conformity.

We find the vulnerabilities in your product before you have to report them.

Free Consultation