Basics
Cyber Resilience Act: what applies to software from SMEs in Switzerland and Liechtenstein?
By Dominik Natter · Last updated on 3 November 2026 · 10 min read
In short
The Cyber Resilience Act applies to anyone offering software or connected devices on the EU market, including manufacturers based in Switzerland and Liechtenstein. Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents within 24 hours through ENISA's reporting platform. From 11 December 2027, all obligations apply, from security updates and the software bill of materials to CE marking. Web applications that run only in the browser and software built for internal use are generally not covered.
Who does the Cyber Resilience Act apply to?
The Cyber Resilience Act, or CRA, is Regulation (EU) 2024/2847. It covers products with digital elements that are offered on the EU market and connect to a device or network. That means software and hardware, including any remote data processing the manufacturer has built for the product to work.
The CRA distinguishes three roles. The manufacturer develops the product, or has it developed, and sells it under its own name. It carries most of the obligations. The importer brings a product from a manufacturer outside the EU onto the EU market, and the distributor resells it. Both must check that the manufacturer has met its obligations, for example that the CE marking is present.
Typical examples from everyday SME business:
- A machine or measuring device with control software and a network connection.
- An app your customers download from the App Store, for example to operate a device.
- Desktop or server software that you license to customers in the EU.
- A software component that other manufacturers build into their products.
- Deadline for the early warning on exploited vulnerabilities and severe incidents
- 24 hours
- From 11 December 2027, all CRA obligations apply
- December 2027
- Minimum period for security updates, unless the product is used for less time
- 5 years
- Maximum fine, or 2.5 percent of worldwide annual turnover if higher
- EUR 15 million
CRA in Switzerland and Liechtenstein: does it apply to us?
Yes, as soon as you sell into the EU. The CRA is tied to the EU market, not to where the manufacturer is based. A Swiss or Liechtenstein SME that supplies software or devices to customers in the EU must meet the obligations of a manufacturer. If you sell only in Switzerland and Liechtenstein, you are not directly affected today. The EU AI Act follows the same market location principle for AI whose output is used in the EU. Read more in our guide "EU AI Act: what applies to SMEs in Switzerland and Liechtenstein?".
The CRA does not apply domestically. In September 2026, the Federal Council instructed the Federal Department of Defence, Civil Protection and Sport to draft a separate cybersecurity act. It is to set binding requirements for manufacturers, importers and distributors of software and hardware and to be modelled on the CRA.
The consultation draft is planned by June 2027. What exactly will apply is still open.
As an EEA member, Liechtenstein adopts EU single market law through the EEA Agreement. According to EFTA, the CRA is marked as EEA relevant and is under scrutiny for incorporation by Iceland, Liechtenstein and Norway.
As of early November 2026, no EEA Joint Committee decision had been adopted. For deliveries into the EU, this makes no difference: the CRA already applies there.
The CRA does not require you to appoint an authorised representative in the EU. It is voluntary. It can still help. Without an establishment in the EU, the competent reporting authority is determined by where your authorised representative is based, otherwise by your importer, your distributor or the country with the most users. With an authorised representative, that question has a clear answer.
Does custom software fall under the CRA? And SaaS?
It depends on how the software reaches its users. The European Commission clarified this in its guidance of 27 July 2026.
Software that is installed and runs on the user's side is a product under the CRA. This applies to apps and desktop programs and is likely to apply to software installed on the customer's own server as well. According to the guidance, supplying source code to a single customer also counts as placing a product on the market.
A web application that users access exclusively through a browser, on the other hand, is not a product under the CRA. It is only covered if a product needs it to function, for example a portal that a connected device logs into or is controlled through. For pure cloud services, the EU's NIS2 Directive may be relevant instead of the CRA.
What falls under the CRA and what generally does not
Generally not covered
- Web applications and customer portals that run only in the browser and do not operate a product.
- Websites that only provide information.
- Software as a Service that is not part of a product.
- Software a company develops itself for its own operations and does not pass on.
- Pure services such as consulting, operations or support, as long as no product is supplied.
- Free open-source software that is not provided in the course of a commercial activity.
A product under the CRA
- Apps and desktop programs that are installed and run on the user's side.
- Software installed on the customer's own server is likely to be covered as well.
- Source code that you supply to a single customer.
- A portal that a connected device logs into or is controlled through.
- Software built to order for a single business customer.
CRA reporting obligations: what has applied since 11 September 2026
Since 11 September 2026, manufacturers must report two types of events: actively exploited vulnerabilities in their product and severe security incidents affecting the product. Actively exploited means there is reliable evidence that an attacker is already using the flaw.
The obligation also covers products sold before December 2027. Reports are submitted through ENISA's Single Reporting Platform, which has been operational since 11 September 2026. Each report goes to the competent national authority, a so-called CSIRT, and to ENISA at the same time. In addition, you inform affected users about the issue and possible countermeasures.
The deadlines start from the moment you become aware:
Within 24 hours
Early warning
For an actively exploited vulnerability or a severe incident.
Within 72 hours
Notification
With initial details and measures taken.
14 days after a fix
Final report on a vulnerability
No later than 14 days after a fix is available.
1 month after notification
Final report on a severe incident
Within one month of the notification.
What applies from 11 December 2027: an overview of the obligations
From 11 December 2027, manufacturers may only place products on the EU market that meet the CRA's essential requirements. Products placed on the market before that date only need to be brought into line after a substantial modification.
For products not classified as important or critical, a self-assessment of conformity is sufficient. Important and critical products, such as password managers, VPN software, operating systems, routers or firewalls, face stricter procedures, in some cases involving an external conformity assessment body. In practice, the obligations are:
- Risk assessment: you assess the cybersecurity risks of your product and document how you address them.
- Secure delivery: no known exploitable vulnerabilities, secure default settings, protection against unauthorised access and encrypted data.
- Vulnerability management: identify vulnerabilities, fix them without delay, test regularly and provide a contact address for external reports.
- SBOM: a software bill of materials in a commonly used, machine-readable format, covering at least the directly included libraries. You do not have to publish it.
- Security updates throughout the support period, in principle free of charge and, where possible, separate from feature updates. The support period is at least five years, unless the product is expected to be used for a shorter time. You state the end date, with month and year, at the time of purchase.
- Documentation: keep the technical documentation and the EU declaration of conformity for at least ten years, or for the support period if that is longer.
- CE marking for software: standalone software also carries the CE marking, either on the EU declaration of conformity or on a website accompanying the software.
- Reporting process: responsibilities, deputies and templates, so the 24-hour deadline holds at weekends too.
Cyber Resilience Act deadlines
| Item | Deadline | Note |
|---|---|---|
| Entry into force | 10 December 2024 | Regulation (EU) 2024/2847 |
| Conformity assessment bodies | from 11 June 2026 | designated by EU member states |
| Reporting obligations | from 11 September 2026 | also for products already sold |
| Early warning | within 24 hours | actively exploited vulnerability or severe incident |
| Notification | within 72 hours | initial assessment and measures |
| Final report | 14 days or 1 month | 14 days after a fix is available for vulnerabilities, 1 month after the notification for incidents |
| Full application | from 11 December 2027 | requirements, conformity assessment, CE marking |
| Support period | at least 5 years | shorter only if the product is used for less time |
| Retention of documentation | at least 10 years | or the support period, if longer |
| Switzerland | consultation planned by June 2027 | separate cybersecurity act modelled on the CRA |
| Liechtenstein | EEA incorporation pending | as of November 2026 |
What the CRA means for your software supplier and your contracts
If you have a product developed and sell it into the EU under your own name, you are usually the manufacturer. The obligations stay with you, even if a service provider writes the code. Your supplier must, however, provide what you need to meet them.
Plan for updates over the entire lifetime. As a guideline: with project costs of CHF 50,000 and maintenance costs of 15 to 20 percent per year, five years of support add up to CHF 37,500 to 50,000. Read more in our guide "Software maintenance costs: what do maintenance and operations cost per year?".
Clarify in the contract:
- Who is the manufacturer under the CRA, and who takes on which task?
- Security updates: response times for critical vulnerabilities and a term at least as long as the support period you promise your customers.
- Notifications: the supplier informs you immediately when it learns of an exploited vulnerability. Otherwise you will not make the 24 hours.
- The SBOM and technical documentation are delivered with every version and belong to you.
- Third-party components: the supplier continuously checks libraries and open-source components for known vulnerabilities. Check the open source licences as well. Read more in our guide "Who owns the source code of custom software? Rights in Switzerland and Liechtenstein".
- For software built to order: whether and how you deviate from secure defaults or free updates is stated explicitly in the contract.
What fines apply for breaches of the CRA?
EU member states set the fines, and the CRA sets the upper limits. Breaching the essential requirements or the manufacturer and reporting obligations can cost up to EUR 15 million or 2.5 percent of worldwide annual turnover, whichever is higher. For other obligations, the limit is EUR 10 million or 2 percent, and for incorrect or incomplete information given to authorities, EUR 5 million or 1 percent.
Regardless of fines, authorities can require a product to be corrected, withdrawn from the market or recalled.
Checklist: how to prepare for the CRA
Work through these questions in order. For the legal assessment of your specific product, consult a specialist body or a lawyer.
- Do you sell software or connected devices to customers in the EU, directly or through distributors?
- Does your software run on the user's side, or is it only accessed in the browser?
- Are you a manufacturer, importer or distributor? Whose name is on the product?
- Is your product one of the important or critical products with a stricter procedure?
- Is there a reporting process for exploited vulnerabilities, with a deputy?
- Do you know which reporting authority is responsible for you?
- Is there an SBOM for every version delivered?
- Is the support period defined and covered by the maintenance contract with your supplier?
- Is the cost of security updates over the entire lifetime budgeted?
Where this information comes from
Legal basis
The legal basis is Regulation (EU) 2024/2847 on horizontal cybersecurity requirements for products with digital elements, published in the Official Journal of the EU on 20 November 2024. Deadlines, obligations and fine limits are taken from Articles 13, 14, 18, 30, 64 and 71 and Annex I.
Guidance and FAQ
The treatment of web applications, SaaS and source code comes from the European Commission's guidance on the application of the CRA of 27 July 2026, C(2026) 5252. The statements on software built to order and on internal use come from the European Commission's CRA FAQ, version 1.4 of 4 September 2026. Information on the reporting platform and the competent reporting authority comes from ENISA's FAQ on the Single Reporting Platform.
Switzerland and Liechtenstein
The status in Liechtenstein is taken from EFTA's EEA-Lex entry for Regulation 2024/2847. For Switzerland: the Federal Council's press release of 25 September 2026 on the new cybersecurity act and the Federal Office for Cybersecurity's announcement of 20 August 2025.
Not legal advice
This guide is an overview, not legal advice. Whether and how your product is affected should be clarified case by case with a specialist body or a lawyer.
As of: November 2026.
| Entry into force | 10 December 2024 | Regulation (EU) 2024/2847 |
|---|---|---|
| Conformity assessment bodies | from 11 June 2026 | designated by EU member states |
| Reporting obligations | from 11 September 2026 | also for products already sold |
| Early warning | within 24 hours | actively exploited vulnerability or severe incident |
| Notification | within 72 hours | initial assessment and measures |
| Final report | 14 days or 1 month | 14 days after a fix is available for vulnerabilities, 1 month after the notification for incidents |
| Full application | from 11 December 2027 | requirements, conformity assessment, CE marking |
| Support period | at least 5 years | shorter only if the product is used for less time |
| Retention of documentation | at least 10 years | or the support period, if longer |
| Switzerland | consultation planned by June 2027 | separate cybersecurity act modelled on the CRA |
| Liechtenstein | EEA incorporation pending | as of November 2026 |
Frequently asked questions
Does the Cyber Resilience Act apply to custom software?
Yes, if the software is installed on the customer's side and reaches the EU market. Software built to order for a single business customer is not exempt. The CRA only allows two deviations, and only if they are agreed in the contract: secure default settings and free security updates. According to the European Commission's guidance, web applications that run only in the browser and do not operate a product are not products under the CRA.
Do Swiss companies have to comply with the Cyber Resilience Act?
Yes, as soon as they offer software or connected devices in the EU. The CRA applies to the EU market, regardless of where the manufacturer is based. It does not apply within Switzerland itself. However, the Federal Council has commissioned a Swiss cybersecurity act modelled on the CRA, with a consultation draft planned by June 2027.
What do I have to report under the Cyber Resilience Act, and how quickly?
Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe security incidents affecting their products. An early warning is due within 24 hours, a more detailed notification within 72 hours, followed by a final report. Reports go through ENISA's Single Reporting Platform, including for products sold before the rules applied.
Who runs the software after go-live?
We do, if you wish. A maintenance contract covers hosting in the EEA, monitoring, security updates, backups and agreed response times. The usual figure is 15 to 20% of the project cost per year. You can also run the software on your own infrastructure or hand it to your IT partner.
Who holds the rights to the code and the data?
The data is yours. The source code is kept in a repository you have access to, and the usage rights to it pass to you once the work is paid in full. We rely on widely used technologies such as Next.js, C# and PostgreSQL, so that another team can take the software forward if needed.
Matching services:Custom softwareIntegrations
Let us talk about your case.
20 minutes are enough to find out whether a custom solution is worth it for you.