Book demo

Cyber Resilience Act

Cyber Resilience Act: Requirements, Deadlines and Obligations at a Glance

Cyber Resilience Act

Connected devices and software must not only work, they must also be adequately protected against cyberattacks. This is where the Cyber Resilience Act (CRA) comes in: the CRA EU regulation sets cybersecurity requirements for products with digital elements that are made available on the European market. Manufacturers, importers and distributors may be affected, with different obligations depending on the product and their role. This article explains which products are covered, what the CRA requirements involve, what must be reported and when and how plano WFM complies with the CRA. 

Content

What Is the Cyber Resilience Act? (Definition)

The Cyber Resilience Act, or CRA, is Regulation (EU) 2024/2847. It sets mandatory cybersecurity requirements for certain hardware and software products placed on the EU market. The goal is to take security risks into account from the development stage and to address vulnerabilities appropriately throughout a product’s lifecycle. 

What Does “Product with Digital Elements” Mean? 

The CRA applies to products with digital elements. These generally include software and hardware products whose intended or reasonably foreseeable use involves a direct or indirect connection to another device or network. Software and hardware components placed on the market separately may also fall within the scope. Examples include connected devices, operating systems, apps, certain business software and components integrated into other products. Whether a product is “digital” is not the only factor: what matters is whether it meets the criteria set out in the regulation.

Who Is Affected by the Cyber Resilience Act?

The CRA primarily applies to economic operators that make products with digital elements available on the EU market. The obligations depend on the company’s role and the product concerned. 

Economic operator  Typical role  Responsibilities at a glance 
Manufacturer  Develops a product (or has it developed) and markets it under its own name  Has the most extensive obligations. Must meet the applicable requirements, assess conformity and establish vulnerability-handling processes. 
Importer  Places a product from a non-EU country on the EU market  Must, among other things, check that the required conformity and product information is available. 
Distributor  Makes a product available in the supply chain  Must act with due care and respond appropriately to known issues. 
Open-source software steward  Provides ongoing support for certain open-source projects as part of commercial activities  Is subject to a separate, limited regulatory framework and should not simply be treated as a manufacturer. 

Which Products Are Covered by the CRA and Which Are Not?

The CRA covers a broad range of hardware and software, provided the products meet the definition of a product with digital elements and are made available on the EU market. The specific classification depends on the product’s technical characteristics, function and applicable legal framework.

Hardware, Software and Digital Components 

Products that may be covered include connected devices, certain operating systems, apps, software products and digital components. An individual part or software component may also be covered if it is placed on the market separately and meets the legal criteria. 

The Cyber Resilience Act and SaaS 

Whether the Cyber Resilience Act applies to a SaaS offering cannot be answered in general terms. A standalone cloud service is not automatically a product with digital elements simply because it is accessed over the internet. However, the CRA may also cover certain remote data processing solutions if a manufacturer develops them for a product and that product cannot perform one of its functions without the solution. Locally installed software, apps or client components may fall within the scope independently of the cloud service.

CRA Exemptions and Other EU Rules 

Some product groups are exempt, for example where other EU legislation already provides equivalent cybersecurity requirements. Under certain conditions, this includes products in regulated areas such as medical devices, vehicles and aviation. Other rules may also apply at the same time. The CRA does not automatically replace requirements under the NIS2 Directive or DORA. 

Cyber Resilience Act Requirements for Products and Manufacturers

The Cyber Resilience Act requirements go beyond protecting a product at the time it is placed on the market. The CRA requires cybersecurity to be considered throughout development, provision and support. The specific measures depend on the product and the risks associated with it. 

Security by Design and Secure Default Settings 

Security should be built into a product’s development and design from the outset. This may include appropriate access controls, data protection and secure default settings. Products should also be designed to avoid or reduce known security risks as far as possible. 

Risk Assessment Throughout the Product Lifecycle 

A CRA risk assessment helps identify potential threats to a product and their possible impact in a systematic way. It can inform security measures, product design and technical documentation. Components, dependencies and the intended use should also be taken into account. 

Risks can change over time, for example when new vulnerabilities are discovered or the operating environment changes. The assessment should therefore not be treated as a one-off task at the start of a project. 

Vulnerability Management, Updates and the CRA Support Period 

Manufacturers must establish processes to identify, fix and coordinate the disclosure of vulnerabilities. These include security updates and appropriate communication channels. 

The support period should reflect the product’s expected period of use. The CRA generally provides for a minimum support period of five years, unless the expected period of use is shorter. Users must be informed when the support period ends. The exact period must therefore be determined for each product and considered in light of its use and type. 

CRA SBOM Requirements and Technical Documentation 

A Software Bill of Materials (SBOM) provides transparency about the software components included in a product. It helps manufacturers track dependencies and potential vulnerabilities. The CRA does not generally require a complete SBOM to be made publicly available. 

Technical documentation provides evidence of how a manufacturer has taken the relevant requirements into account and assessed conformity. It must contain the information required for the product in question and the applicable conformity assessment procedure. 

CRA Effective Date: Deadlines and Entry into Force

For the CRA, it is important to distinguish between when the regulation entered into force and when its provisions become applicable. 

Date  Significance 
10 December 2024  The regulation entered into force. 
11 June 2026  The provisions on conformity assessment bodies apply. 
11 September 2026  The reporting obligations under Article 14 apply. 
11 December 2027  The CRA becomes generally applicable. 

The regulation contains transitional rules for products placed on the market before 11 December 2027. In general, those products become subject to the remaining requirements if they are substantially modified after that date. Separate transitional provisions apply to the reporting obligations. 

CRA Vulnerability Reporting: What Must Be Reported and When?

The CRA reporting obligations apply from 11 September 2026. From that date, manufacturers must report certain actively exploited vulnerabilities and serious security incidents that affect the security of a product with digital elements. The deadlines start when the manufacturer becomes aware of the relevant matter. 

Cause  Initial report  Follow-up report  Final report 
Actively exploited vulnerability  Early warning within 24 hours  Detailed report, generally within 72 hours  No later than 14 days after a corrective or mitigating measure becomes available 
Serious security incident affecting a product  Early warning within 24 hours  Detailed report, generally within 72 hours  Generally within one month of the 72-hour report 

A central EU platform is planned for these reports. 

CRA Conformity Assessment

Before placing a product on the market, manufacturers must assess and document its conformity using the applicable procedure. If the product conforms, an EU Declaration of Conformity and CE marking are among the relevant evidence and markings. CRA certification is not automatically required for every product. Whether an independent assessment body must be involved depends, among other things, on the product category and the applicable conformity assessment procedure. 

For important products with digital elements, the CRA distinguishes, among other things, between Class I and Class II. These product classes are subject to specific conformity assessment rules. For Class I products, an internal assessment may be possible if certain conditions are met. Class II products generally require an assessment involving an independent body or an equivalent European cybersecurity certification. 

CRA harmonised standards may provide a presumption of conformity if they have been published in the Official Journal of the EU and apply to the relevant requirements. In other words, applying a relevant standard can make it easier to demonstrate that certain requirements have been met. Mapping Cyber Resilience Act requirements to standards can therefore help manufacturers plan their compliance work. 

CRA Checklist: How Companies Can Prepare

This CRA checklist provides an initial framework for companies that may be affected. It does not replace an assessment of the specific products and obligations involved: 

  • Identify products, software and digital components made available in the EU. 
  • Clarify the company’s role (manufacturer, importer or distributor) for each product. 
  • Check the scope, possible CRA exemptions and relevant product classes. 
  • Document risks, dependencies and security measures. 
  • Establish processes for vulnerability handling and security updates. 
  • Set the support period and decide how to communicate it to users. 
  • Prepare reporting channels and responsibilities for the obligations that apply from September 2026. 
  • Plan the technical documentation and conformity assessment. 
  • Check the current harmonised standards and the applicable legal position. 

How Does plano WFM Comply with the Cyber Resilience Act?

As part of Allegion, we use a leading cybersecurity platform for cloud and AI environments. plano WFM also has a Product Security Incident Response Team (PSIRT), which handles Cyber Resilience Act matters relating to all plano products. Cybersecurity is also a high priority in product development. We use modern technologies and analyse and assess currently known vulnerabilities every day, drawing on official sources. This helps us stay up to date with relevant developments. 

If an incident occurs, we follow the CRA requirements and provide information proactively. Customers do not have to ask first: plano WFM meets its applicable information obligations.

Cyber Resilience Act Summary: Keep the CRA in Mind Early

The Cyber Resilience Act sets EU-wide cybersecurity requirements for certain products with digital elements. Manufacturers must consider security throughout the product lifecycle, establish processes for handling vulnerabilities and, where required, demonstrate conformity. plano’s workforce management software fully meets the CRA requirements. To support compliance, we use a leading cybersecurity platform for cloud and AI environments and regularly analyse and assess known vulnerabilities. 

Would you like to learn more about plano WFM’s smart staff planning solution? Book a no-obligation demo! 

Book Demo

We’re Here for You

Have questions about our products?
We’re here to help.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*
Please enter your business email address.
Number of Employees*
How did you find the Lead?

Please fill in all fields marked with * before submitting the form.

Frau macht ein Herz mit ihren Händen

Contact

 Let's get in touch and discuss your ideas.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*
E-Mail*

Please fill in all fields marked with * before submitting the form.

Great to have you here

Work with us to find the best solution for your company too.
Make an appointment now for a free, no-obligation product demo.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*
Please enter your business email address.
Number of Employees*
How did you find the Lead?

Please fill in all fields marked with * before submitting the form.

Great that you want to meet us

Register now for our roadshow in your area.

Great that you want to meet us

Register now for the plano Campus. Please register each participant individually and with their own email address!

Great to have you here

Work with us to find the best solution for your company too.
Make an appointment now for a free, no-obligation product demo.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*
E-Mail*

Please fill in all fields marked with * before submitting the form.