Summary
- CEN and CENELEC have published EN 40000-1-1 and EN 40000-1-2 under the Cyber Resilience Act standardisation programme.
- The standards cover cybersecurity terminology, risk management and security processes throughout a product's lifecycle.
- Manufacturers already face qualifying vulnerability and incident reporting obligations, with the CRA's principal product requirements applying from 11 December 2027.
Europe has published its first two standards supporting the Cyber Resilience Act, giving manufacturers an initial technical framework for managing the security of connected hardware and software throughout their working lives. The publications establish common terminology and lifecycle risk management principles as companies prepare for the regulation’s main requirements, which become applicable in December 2027.
European standards bodies CEN and CENELEC confirmed on 19 November that EN 40000-1-1 and EN 40000-1-2 are now available. The first addresses cybersecurity terminology, while the second establishes principles covering product risk management and activities extending through design, development, production, maintenance, support and retirement.
The standards were developed in response to the European Commission’s standardisation request M/606, which forms part of the work needed to turn the Act’s legal requirements into practical technical specifications. More standards are being prepared to address additional cybersecurity controls and the needs of particular product categories.
The legislation applies broadly to products with digital elements made available on the EU market, including connected devices, network equipment, operating systems and other software. Certain remote data processing services supporting product functions can also fall within scope, reflecting the dependence of modern products on software and infrastructure operating beyond the physical device.
Cybersecurity becomes a lifecycle responsibility
Many connected products remain in service long after their original development teams have completed the initial engineering work. During that period, researchers may discover vulnerabilities, software components may become obsolete and changes to connected systems can introduce risks that did not exist when the product was first released.
The Cyber Resilience Act addresses those conditions by establishing requirements for manufacturers to consider cybersecurity throughout a product’s lifecycle. A product that satisfies its immediate functional requirements may still present unacceptable risks if vulnerabilities cannot be identified, assessed and corrected during the period in which it is supported.
EN 40000-1-2 provides a common framework for organising those responsibilities, while EN 40000-1-1 addresses the terminology needed to communicate them consistently. Shared definitions can appear less consequential than technical controls, but they influence how suppliers, engineers, conformity assessment bodies and regulators understand the same requirements.
For example, organisations developing a connected industrial controller may need to identify the software components used, understand foreseeable threats and establish procedures for delivering updates. Those activities involve engineering, supplier management and operational support rather than a single security test undertaken immediately before release.
Manufacturers of software face comparable obligations. Applications can incorporate external libraries, software development frameworks and other components whose vulnerabilities may affect the finished product. Managing those dependencies requires a reliable understanding of what has been included and how security issues can be addressed when components change.
The standards help establish a common language for such work, but they do not remove the need for product-specific risk assessment. A consumer application, medical device and industrial network component can present different threats and support requirements, even when they are subject to common legislative principles.
Reporting obligations are already in force
Although the principal Cyber Resilience Act requirements apply from 11 December 2027, important reporting provisions have been applicable since 11 September 2026. Manufacturers must notify qualifying actively exploited vulnerabilities and severe incidents affecting the security of products with digital elements.
The reporting framework requires an early warning within 24 hours of becoming aware of a qualifying issue, followed by a more substantial notification within 72 hours. Further reporting obligations apply according to the nature of the vulnerability or incident.
These requirements create immediate operational responsibilities. Manufacturers need procedures for identifying relevant information, determining whether an incident meets the reporting threshold and coordinating responses across technical, legal and management teams.
They may also need information from suppliers whose components form part of the affected product. A manufacturer cannot necessarily determine the consequences of a vulnerability without understanding which software or hardware dependencies are involved.
Reporting responsibilities should therefore be considered alongside product development and maintenance processes. Creating a technical contact address is insufficient if a company cannot establish which products are affected or obtain the evidence needed to make a reliable notification.
Standards will influence conformity assessments
The publication of European standards is not equivalent to automatic conformity with the Cyber Resilience Act. Harmonised standards can support a presumption of conformity with specified requirements when the relevant legal conditions are met, including appropriate recognition through the EU’s formal process.
Manufacturers therefore need to distinguish between the availability of a technical standard and its precise regulatory status. A published document may provide valuable guidance without, by itself, establishing that every applicable legislative obligation has been satisfied.
The distinction becomes important when companies plan testing, technical documentation and conformity assessment activities. They must determine which requirements apply to their products and which specifications can be used to demonstrate compliance.
Further horizontal and product-specific standards remain under development. These are expected to provide more detailed guidance on technical security requirements, vulnerability management and particular classes of products.
The breadth of the programme reflects the varied technologies covered by the legislation. CEN and CENELEC say more than 450 committee members from 28 national standardisation organisations and 17 liaison organisations contributed to developing the initial publications.
Manufacturers face a demanding implementation timetable
For organisations producing several families of hardware and software, the legislation may require changes across development processes, technical documentation, supplier relationships and arrangements for supporting products after release.
Companies with older product lines must consider whether their existing processes can provide the evidence and security maintenance arrangements required when applicable CRA obligations take effect. Newer products may be easier to design around updated procedures, although they can still contain components whose security depends on external suppliers.
International manufacturers also need to understand how European obligations interact with engineering and product support arrangements operating across different jurisdictions. A common development programme may serve multiple markets, while different legal reporting or conformity requirements apply to individual territories.
Early implementation work can reduce the risk of discovering major documentation or maintenance gaps close to a regulatory deadline. Nevertheless, businesses should avoid assuming that a single organisational policy or technical checklist will address the requirements of every product they supply.
The first standards provide a foundation for that preparation, but the full compliance picture will depend on the remaining specifications and their eventual legal status. Manufacturers now have a clearer common framework for terminology and lifecycle processes while awaiting the more detailed standards needed to support conformity assessments across the European market.












