Decoding the world of cybersecurity

EU publishes first Cyber Resilience Act standards

Europe’s first Cyber Resilience Act standards establish common cybersecurity terminology and product risk management principles. Manufacturers can use them to structure compliance preparations ahead of the legislation’s main December 2027…

EU publishes first Cyber Resilience Act standards
Summary
  • CEN and CENELEC have published EN 40000-1-1 and EN 40000-1-2, the first two European standards supporting the Cyber Resilience Act.
  • The publications address shared terminology and cybersecurity risk management throughout the product life cycle.
  • Further standards and the relevant legal conformity arrangements are still developing, while the CRA's main requirements take effect in December 2027.

European manufacturers have received their first two cybersecurity standards supporting the EU's Cyber Resilience Act, establishing common terminology and an approach to managing security risks throughout the life cycle of products containing digital components.

The standards, EN 40000-1-1 and EN 40000-1-2, were published on 18 November 2026 through the European standardisation organisations CEN and CENELEC. The European Commission confirmed the development the following day.

The first publication establishes terminology, while the second addresses cybersecurity principles, product risk management and activities extending from initial design through production, maintenance and the end of a product's support period.

Both form part of a much wider standardisation programme intended to help manufacturers meet requirements introduced by the Cyber Resilience Act (CRA).

Product security becomes a continuing obligation

The CRA introduces cybersecurity requirements for a broad range of hardware and software products made available on the EU market.

Its scope includes products such as operating systems, connected devices, networking equipment and software components, alongside remote data processing functions necessary for some products to operate.

Manufacturers must account for cybersecurity during product development and maintain appropriate arrangements for managing vulnerabilities and updates during the applicable support period.

Those responsibilities extend beyond the initial release of a product. Security weaknesses can emerge after deployment, including through changes to supporting software, connected services or third-party components.

A connected industrial controller, for example, may depend on embedded software, network interfaces and external maintenance tools. A vulnerability in any of those components could affect the security of the wider product even if the device's physical hardware remains unchanged.

EN 40000-1-2 establishes a framework for considering such dependencies throughout the product life cycle. Its coverage includes risk identification, assessment and management, allowing manufacturers to organise cybersecurity activities as part of an ongoing product development and support process.

The standard does not replace the technical requirements of the legislation or establish a single set of security controls suitable for every category of product.

Its role is to provide common principles that can support more detailed standards and implementation arrangements.

Shared terminology supports consistent assessment

EN 40000-1-1 addresses a separate but closely connected problem: the need for manufacturers, suppliers, conformity assessment bodies and regulators to apply cybersecurity terminology consistently.

Product security involves several disciplines, including software development, hardware engineering, vulnerability management and regulatory compliance. Terms used in one discipline can carry different assumptions in another.

Inconsistent definitions can create uncertainty when organisations document product risks, assign responsibilities or assess whether particular measures satisfy a technical requirement.

A shared vocabulary therefore supports communication between companies developing products and the organisations responsible for assessing or regulating them.

It also provides a foundation for the further EN 40000 standards now in development, which will address more specific cybersecurity requirements and categories of connected products.

CEN and CENELEC say the standards were developed through a working group involving specialists from across Europe. More than 450 committee members participated through national standardisation organisations and liaison bodies.

Publication does not automatically establish conformity

The new standards arrive during the CRA's phased implementation.

The legislation entered into force on 10 December 2024. Requirements for manufacturers to report actively exploited vulnerabilities and severe incidents affecting product security began applying on 11 September 2026, supported by ENISA's Single Reporting Platform.

The CRA's main product security obligations are scheduled to apply from 11 December 2027.

Manufacturers developing products for that market therefore face a period in which they must align design, development and support processes with requirements that are already established in law while the accompanying standards programme continues to develop.

European harmonised standards can support a presumption of conformity with corresponding legislative requirements when the relevant legal conditions are satisfied, including publication of their references in the Official Journal of the European Union.

Publication of a European standard through a standards organisation is not, by itself, proof that it already carries that legal status or establishes conformity with every applicable CRA requirement.

Manufacturers also need to determine whether their products fall within categories requiring particular conformity assessment arrangements.

Those decisions depend on the product and the applicable legislation, rather than simply the availability of the first general standards.

Supply chain records become part of preparation

The lifecycle framework is particularly relevant to manufacturers incorporating software or components supplied by other companies.

A product developer may control its final design but depend on external libraries, embedded firmware, cloud services and specialist hardware supplied through several contractual relationships.

Vulnerability management can therefore require information and cooperation from organisations outside the manufacturer's direct control.

Effective records of components, security responsibilities, support arrangements and available updates can help establish how a newly discovered weakness affects products already deployed.

That information may also be necessary when deciding whether a vulnerability creates reporting obligations under the CRA.

The first standards provide a common framework for organising those activities, but detailed standards covering vulnerability handling, technical requirements and specific product categories remain under development.

With the December 2027 application date approaching, manufacturers can begin using the published terminology and risk management principles while monitoring the remaining standards and conformity assessment arrangements.

×