The EU’s Cyber Resilience Act (CRA) sets security rules for products with digital elements sold in the EU: hardware and software that connect to other devices or networks. Its first supporting European standards were published this week.
What’s changing
The European Commission says the first European standard supporting the CRA was published on 18 November 2026. CEN and CENELEC, two of Europe’s three official standards bodies, announced it on 19 November as two parts:
- EN 40000-1-1, Vocabulary. The common terms and definitions for the whole EN 40000 series.
- EN 40000-1-2, Principles, product risk management, and lifecycle activities. A common way to identify, assess and manage cyber security risk across a product’s life.
The Commission says the standard sets “generic cybersecurity principles applicable to a wide range of products with digital elements”. It covers design and development through production, maintenance, end of support and decommissioning.
Its examples include connected door locks controlled through smartphone apps, routers, and microprocessors and microcontrollers. Software is covered too, such as operating systems, browsers and password managers. So are remote data processing services that support a product, such as cloud-based smart lock management.
The standards were written by a joint CEN and CENELEC committee (CEN-CLC/JTC 13/WG 9). It has more than 450 members from 28 national standards bodies. The work answers a request the Commission made to CEN, CENELEC and ETSI in February 2025 (M/606).
More will follow. The Commission says “over 30 standards” are in the making. CEN and CENELEC say a standard on vulnerability handling (FprEN 40000-1-3) and the first product-specific standards are coming soon.
The standards can be bought through national standards bodies, on their own publication schedules.
Neither announcement says whether these standards will be cited in the EU’s Official Journal. Only cited standards give a presumption that a product meets the CRA’s requirements. One tracker of CRA standards, Blue Panther, reported in October that none had yet been cited.
The CRA’s dates
The CRA entered into force on 10 December 2024. Its reporting obligations for manufacturers have applied since 11 September 2026. The main obligations apply from 11 December 2027.
What it means for you
If you make products with digital elements, EN 40000-1-2 shows how Europe expects product security risk to be managed across a product’s life. It’s the base later, more detailed standards will build on. It’s worth reading now, with just over a year until the main obligations apply.
If you buy them, the CRA is a way to ask your suppliers better questions. Ask how they’re preparing, and how they’ll handle and tell you about vulnerabilities.
These Blueprint requirements cover the same ground:
- RW-LAW-19 Coming changes in the law tracked (Advanced). Watch for new laws “and plan the work needed to meet them before they take effect”.
- RW-DEV-17 A secure way of building software (Established). Follow a written secure development process for software you build.
- RW-DEV-19 Software tested before release (Established). Test for security weaknesses before each significant release.
- RW-DEV-20 Third-party code kept free of known flaws (Established). Check third-party components for known vulnerabilities, and update or replace them.
- RW-DEV-23 A way for outsiders to report security concerns (Established). Publish a way for others to report weaknesses, “and respond to every report”.
How RiskWitness helps
“Does the CRA apply to us?” Assets and Suppliers. Record the products you make and the software and devices you buy, with owners. Link each product to the suppliers whose components it relies on.
“How far along are we?” Frameworks. RiskWitness includes the RiskWitness Blueprint, with starter controls mapped to it. If you’re licensed to use EN 40000-1-2, add it as one of your own frameworks by pasting in its requirements from your copy. Map your controls and policies to each one. RiskWitness shows how well each requirement is met. Own frameworks need the Team plan or above.
“What could go wrong before December 2027?” Risks. Record the risk of not being ready, with an owner. Score it before and after controls, and choose a treatment.
“Who’s doing what, by when?” Actions and Reports. Turn the work into actions with owners and due dates, such as a vulnerability reporting route. Then produce a PDF report or slide deck for leadership.
Every step is kept in a history that shows who did what, when, and the old and new values. Nobody can edit or delete it. When leadership, an auditor, a customer or a regulator asks how you prepared, the answer is already written down.
Sources
- First European standard published to support the Cyber Resilience Act, European Commission, 19 November 2026
- CRA Milestone Unlocked: First European standards supporting CRA are now available!, CEN-CENELEC, 19 November 2026
- Cyber Resilience Act, European Commission, updated 7 September 2026
- Cyber Resilience Act implementation, European Commission, updated 27 July 2026
- CRA Harmonised Standards: Status October 2026, Blue Panther, 26 October 2026
