Your digital compliance
Secure products: Cybersecurity Act and Cyber Resilience Act
Bring hardware and software to the EU market that meet the Cyber Resilience Act, and use EU cybersecurity certification where it counts.
The Cyber Resilience Act covers hardware and software with digital elements sold on the EU market. Manufacturers must report actively exploited vulnerabilities from 11 September 2026, and most other duties, including CE marking, apply from 11 December 2027. Pitch helps you check whether your product is in scope and what that requires.
Your digital compliance
Explore the nine themes of your digital compliance.
Scroll on, or turn the needle yourself, and see what clients ask us along the way. Anything that catches your eye? Click that part of the circle to dive in.
- GDPR and privacy Personal data, handled lawfully: your record of processing, cookies, data subject requests, and what to do after a breach.
- AI Act Find out which AI Act duties apply to you as a provider or user of AI, and when.
- Data Act and data sharing Share or license your data on your terms, and meet the access and switching rules of the Data Act.
- NIS2: does it apply to your company? NIS2 applies to medium-sized and large companies in the sectors of its two annexes. If you are in scope, you register with the CCB, take security measures, report incidents in stages and answer for it at board level. Pitch tells you where you stand.
- Operational resilience: NIS2 and DORA NIS2 and, in financial services, DORA: keep your services running, manage your suppliers and report incidents on time.
- Secure products: Cybersecurity Act and Cyber Resilience Act You are here Bring hardware and software to the EU market that meet the Cyber Resilience Act, and use EU cybersecurity certification where it counts.
- Online platforms: Digital Services Act Host user content or run a marketplace? Set up notice and action, transparent terms and trader checks under the DSA and the P2B Regulation.
- Consumer law and e-commerce Selling online to consumers comes with a long checklist. Information duties, withdrawal and guarantees, pricing and reviews, green claims, accessibility.
- Sanctions and anti-money laundering Screen customers and partners, and know what the sanctions and anti-money laundering rules expect of you.
GDPR and privacy
AI Act
Data Act and data sharing
NIS2: does it apply to your company?
Operational resilience: NIS2 and DORA
Secure products: Cybersecurity Act and Cyber Resilience Act
Online platforms: Digital Services Act
Consumer law and e-commerce
Sanctions and anti-money laundering
What clients ask us
Does the Cyber Resilience Act apply to our product?
The Cyber Resilience Act (Regulation (EU) 2024/2847) covers products with digital elements made available on the EU market: hardware and software that connect, directly or indirectly, to a device or a network. That includes apps, firmware and software sold separately, and the remote data processing a product needs to work. Pure SaaS falls outside it, and so do products with their own regime, such as medical devices and vehicles. It applies to manufacturers, importers and distributors, including those outside the EU.
When do the Cyber Resilience Act obligations start?
The regulation entered into force on 10 December 2024 and applies in steps. From 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents, also for products already on the market. Most other obligations, including the essential requirements and CE marking, apply from 11 December 2027. Products placed on the market before then are generally only caught after a substantial modification. Use the time to build the vulnerability handling process, because that takes longest.
What must we do as a manufacturer?
Design and ship the product without known exploitable vulnerabilities, secure by default, and keep it secure with updates for a support period that reflects its expected use, as a rule at least five years. Run a vulnerability handling process with a software bill of materials and a coordinated disclosure policy. Before you sell, carry out the conformity assessment, draw up the technical documentation and the EU declaration of conformity, and affix the CE marking. Reports go through ENISA's single reporting platform: an early warning within 24 hours, a notification within 72 hours and a final report afterwards.
Can we assess our product ourselves, or do we need a notified body?
For most products a self-assessment is enough. Important products, listed in Annex III, need more: for class I, such as password managers, VPNs and routers, you can self-assess only if you apply harmonised standards or a certification scheme; for class II, such as firewalls and hypervisors, a notified body must be involved. For critical products, such as smart cards and hardware security modules, the Commission can require a European cybersecurity certificate. Classify your product early, because it decides your timeline and budget.
What is the Cybersecurity Act, and do we need a certificate?
The Cybersecurity Act (Regulation (EU) 2019/881) gave ENISA a permanent mandate and set up an EU framework for cybersecurity certification of ICT products, services and processes. The first scheme, EUCC, based on the Common Criteria, applies since 27 February 2025, and an amendment of 2025 extends the framework to managed security services. Certification is voluntary unless EU or national law requires it. Customers and public tenders increasingly ask for it, though, and under the Cyber Resilience Act it can be the way to show conformity.
We use and publish open-source software. Where do we stand?
As a manufacturer you are responsible for the whole product, including the open-source components you integrate, so check them with due diligence and track them in your software bill of materials. Free open-source software developed or supplied outside a commercial activity is outside the Cyber Resilience Act. Organisations that support open source for commercial use as open-source software stewards have lighter duties, such as a cybersecurity policy and cooperation with authorities. Your licence choice and your contracts should match your role.
- AcademyCan I Protect My Software? →
- SolutionsPatent and Technology Licensing →
What do we risk, and how do we share the burden with our suppliers?
Breaching the essential requirements can lead to fines of up to EUR 15 million or 2.5% of worldwide annual turnover, and market surveillance authorities can order a withdrawal or recall. Most of the work sits upstream, with chip, module and software suppliers. Agree on security requirements, vulnerability notification within your own reporting deadlines, update support for the full support period, documentation and cooperation in conformity assessments. Pitch drafts and reviews these clauses.
- SolutionsCommercial Contracts & Transactions →
- TechnologyContract Review →
- TechnologyDocument Studio →
How we help
-
Commercial Contracts & Transactions
Supply, distribution, services, SaaS and procurement contracts, and the deals around them, drafted and reviewed with the IP, data and tax angles in view.
-
Data Act Compliance
The EU Data Act gives users of connected products a right to their data, sets rules against unfair data terms between businesses and makes cloud switching easier. We work out what it means for your products, your contracts and your cloud services.
-
NIS2 Cybersecurity Compliance
Are you an essential or important entity under the Belgian NIS2 law, and what does that ask of your board, your suppliers and your incident handling? We answer the legal side and keep the evidence in order.
Read more
-
Can I Protect My Software?
Software is protected by copyright, sometimes by patent, and by trade secret law. This article explains what each protects, who owns the code, and how the rights combine.
-
SaaS Agreements
Subscriptions, service levels, data ownership, liability and exit in SaaS contracts, with the GDPR, the Data Act and national contract rules.
-
The NIS2 Directive
Who falls under NIS2, what the directive requires, how the 24-hour, 72-hour and one-month incident reports work and how they relate to GDPR breach notification.
-
AI, Software and the New Product Liability Directive
Directive (EU) 2024/2853 treats software and AI systems as products. It applies to products placed on the market after 9 December 2026. Who is liable, for what damage, how the burden of proof shifts and what to put in your contracts.
-
Cyber Resilience Act I: which products are caught, and in which class
How to tell whether hardware or software you sell falls under Regulation (EU) 2024/2847, whether it is a default, important (class I or II) or critical product, and which conformity route follows from that, with the dates up to 11 December 2027.
-
Cyber Resilience Act II: vulnerability handling and reporting since 11-09-2026
What manufacturers must report under Article 14 of Regulation (EU) 2024/2847 since 11 September 2026, within 24 hours, 72 hours, 14 days and one month, and the vulnerability handling duties of Annex I, Part II, that follow from 11 December 2027.
-
Cyber Resilience Act III: importers, distributors, open source and contracts
The duties of importers, distributors and authorised representatives under Articles 18 to 23 of Regulation (EU) 2024/2847, when a reseller becomes a manufacturer, how free and open-source software and its stewards are treated, and the clauses that follow.
-
Open source after the EU Open Source Strategy
What the EU Open Source Strategy of June 2026 announces, which binding rules already apply to open source (the Cyber Resilience Act, the Interoperable Europe Act) or are proposed (the Cloud and AI Development Act), and what companies that build on, publish or steward open source should do about licences, security and public tenders.
Let’s talk
Tell us what you’re working on. We’ll get the right person on it and reply within one business day. The first chat is free.