The EU Cyber Resilience Act - A Gamechanger in the IoT Market

Quick links:

CONTACT OUR EXPERTS

Standards vs Regulations: What is the difference?

Within the private sector, the industry is structuring itself with cybersecurity standards based on an international consensus from experts from industry, academia and government with the aim to manage new forms of risks and to complement future regulations. Standards are usually introduced by working groups and sponsored by public or non-profit organisations like ETSI, NIST, ANSI, IETF, OWASP and so on, or private standards bodies, such as the internationally recognized standard ISO and the European recognised EN standard. Compliance with a standard is usually voluntary enabling businesses to ensure their products comply with specific market or other contractual requirements.

Within the industry in general there are a lot of cybersecurity standards, take ETSI EN 303 645 as an example. It is designed to prevent large-scale, prevalent attacks against smart devices by establishing a security baseline and building security into products by design. This globally applicable standard targets consumer IoT devices like connected children’s toys and baby monitors, smoke detectors, door locks and other connected safety devices, TVs and speakers, smart wearables, connected appliances, and smart home assistants. Of the 13 recommendations, the top three are: no default passwords, implement a vulnerability disclosure policy, and keep software updated.

Like EN 303 645, the ISA/IEC 66243 standards give guidance on ensuring the safety, integrity, and security of products throughout their lifecycle but for automation and control systems. By defining common terms, concepts and models, asset owners can determine the level of security required to meet their own business and risk needs. It helps establish a cybersecurity lifetime methodology for product developers, including a mechanism to certify products, and risk assessment and vendor development processes.

Regulations, on the other hand, are implemented by the public sector to enforce measures that improve the cybersecurity of the nations. In essence, they are mandatory rules made by a government or other governmental authorities made to control the way things are done or the way people behave to mitigate cybersecurity risks. In the context of the EU Cyber Resilience Act, it is applied in its entirety across all EU member states. Conversely, a directive sets out goals and lets each country devise its own laws.

There is some interplay between standards and regulations. Standards are used as guidelines for organisations that are regulated. They can provide some methodology, organisational measures, technical requirements that can help a company to prove its conformance to regulations. In addition, already existing standards can influence the content of upcoming regulations by setting foundations and expressing a consensus on a subject. Indeed, for the EU Cyber Resilience Act, it may hint at certain existing cybersecurity standards or perhaps replicate them entirely.

Examples of EU regulations that exist today include the most well-known one GDPR, the General Data Protection Regulation, which has been in place since 2018. By itself it is not a cybersecurity regulation but there is the obligation to protect the personal data that has been collected. The NIS2 Directive, or Network Information and Systems Directive, is the first EU-wide cybersecurity regulation applied to digital service providers and operators of essential services. The regulation imposes concrete requirements for cybersecurity to prevent security incidents and makes their reporting mandatory.

On the other hand, there is the Radio Equipment Directive (RED) that was initially just a regulatory framework to ensure that there was no interference between radio emissions of radio equipment placed on the EU market. More recently, in 2019, high-level cybersecurity requirements were added to RED. What’s interesting is that this is the first cybersecurity directive that targets products and not services.

Cyber Resilience Act in practice

The CRA in practice

The proposed regulation of the EU Cyber Resilience Act targets all products with a digital element, covering both software and hardware. It, therefore, has a broader scope compared to RED and it is probable that it will have stronger cybersecurity requirements.

Overview of the EU Cyber Resilience Act

The Cyber Resilience Act is a legal framework that describes the cybersecurity requirements of both hardware and software products with digital elements that shall be placed on the EU market without any known exploitable vulnerabilities and must ensure security for the whole of the product’s lifecycle.

One of the main impacts of the Cyber Resilience Act is that manufacturers are now legally obliged to document everything about the product, including a definition and explanation about the software and hardware bill of materials (BoM). They must also document a detailed list of all the harmonised EU cybersecurity standards that the product meets and perform thorough risk assessments for the OEM and the end-user to better understand the product. In addition, they need to explain which software they are using (open versus closed source) and ensure that they provide the market with ongoing security breach awareness throughout the lifetime of the product.

The other building block that has a significant impact on manufacturers is the over-the-airway (OTA) upgrade mechanism. This capability is a must for two reasons: firstly, the OEM needs to ensure the product’s security for its entire lifecycle. They also need to improve the security features on their product during its lifecycle. Obviously, the OTA upgrade mechanism needs to be secure with the OEM protecting the integrity and confidentiality of the firmware.

The other building blocks of the Cyber Resilience Act are device authentication, device identity management, device access management, data integrity, and data confidentiality - all the mechanisms to achieve the requirements that exist today. None of them are new technologies, it is just following good practices when it comes to a secure design.

Solution

Device Provisioning Service

Avnet Silica has developed a highly secure solution for provisioning electronic components to cover the security in supply chain and distribution parts of electronic device manufacturers and OEMs.

Machine checking security protocols

Article Series

The IoT Security Series

Read our series of IoT security articles, put together by our in-house IoT, Connectivity and Wireless experts. Find articles and resources on device provisioning, network architecture, device authentication, lifecycle management and much more.

Man looking at laptop as part of IoT Security set up

How to comply with the Cyber Resilience Act

Cyber Resilience Act Requirements

Cyber Resilience Act Requirements

One of the biggest challenges for OEMs will be the risk assessments. Fortunately, 90% of all products will fall under the default category where it is a self-assessment. Typical examples include photo editing, smart speakers, games and hard drives. However, this does not remove the need for data integrity, confidentiality and the provision of security keys and certificates, as well as finding vulnerabilities and alerting the market to them, and improving the product’s security features via OTA updates.

The remaining 10% of products fall under the Critical Class I and Critical Class II categories, which both require a risk assessment against criteria such as functionality and intended use. For Class I products like password managers, network interfaces and microcontrollers, the OEMs must apply a cybersecurity standard or carry out a third-party assessment. For the Class II category, which includes operating systems, CPUs and secure elements, a third-party risk assessment is required.

What is the impact of conforming to the Cyber Resilience Act?

Once the Cyber Resilience Act proposal is formally adopted and enters in the transition phase by the end of 2024, OEMs will have two years to comply with it and there is an application planned for the end of 2026 to early 2027.

Put simply, failure to comply with the requirements would likely be punishable by a fine of up to €15 million or up to 2.5% of the OEM’s annual turnover in the preceding business year, which will be imposed by a body yet to be determined by EU member states.

For OEMs, compliance will incur increased product development costs because performing risk assessments takes time as well as preparing the additional required documentation. If an OEM can confirm that its product is compliant then this can be used to differentiate it, from a marketing point of view, from a product made outside the EU, which can have a knock-on effect – both positive and negative - for each of the product’s brand and future sales.

The Cyber Resilience Act is closely aligned with the requirements of the Delegated Regulation adopted under the RED 2014/53/EU standard. Obviously, the RED has some EMC and health & safety considerations for radio equipment but there are also cybersecurity requirements that are closely linked with the Cyber Resilience Act.

Avnet Silica’s Supplier and Partner Solutions for Compliance - Secure Your Digital Future with Confidence

Avnet Silica offers a range of supplier solutions, which provide developers with the tools and technologies needed to enhance cybersecurity and trust in their embedded systems and IoT devices. These solutions help mitigate security risks, protect sensitive data, and ensure the integrity and reliability of connected devices in today’s interconnected world.

Romain Tesniere talks through the available CRA solutions from Avnet Silica at Embedded World 2024

STMicroelectronics' Cyber Resilience Act Solutions

STM32Trust is a comprehensive set of security solutions for the STM32 MCU family based in Arm® Trustzone-M technology, which ensure separation between the secure and non-secure sides of the architecture. For the STM32 MPU family the security mechanism is based on the Arm® Trustzone-A technology for application processors. This suite includes hardware-based security features such as secure elements and trusted platform modules (TPMs) under STSAFE, which satisfies the need for high-level resistance to physical and side-channel attacks, for example.

On the factory programming side, STM32Trust offers secure firmware installation (SFI) for the STM32 MCUs to protect the confidentiality of the firmware when it is needed, and it is also linked to its update mechanism to support the device in the field. The secure secret provisioning (SSP) for MPUs inject the secrets in a secure way for establishing the root of trust features. The secure elements are also available with generic or custom profiles.

Focusing on the STM32H573 device, which is based on the powerful Arm® Cortex M33 with cryptographic accelerators and hardware-based secure storage, in terms of software, STMicroelectronics provides and maintains a pre-baked secure manager root of trust as a non-modifiable binary, which is SESIP Level 3 compliant. Both the hardware and software are pre-certified, which the device manufacturer maintains, making it much easier for the OEM to comply with the Cyber Resilience Act. If the security software needs to be upgraded STMicroelectronics will provide the binary code to implement the fix or new crypto algorithm. The device is SFI compatible and comes pre-provisioned with x509 certificates and attestation keys.

NXP Semiconductors Cyber Resilience Act Solutions

NXP EdgeLock is a suite of solutions designed to enhance the security of connected devices at the edge. On the hardware side the company offers secure elements (SE05x and A5000), secure MCUs (LPC55Sxx, i.MXRT11xx, MCXN54x and MCXN94x) and secure MPUs (i.MX8ulp, i.MX93 and i.MX91).

In terms of factory programming, the devices are pre-loaded with EdgeLock secure elements and secure enclaves with NXP’s x509 certification. These secure elements and secure enclaves are also remotely manageable via EdgeLock2GO, in the field, on the production line or, thanks to Avnet Silica’s partnership with System General, in one of the Avnet Programming Centers.

NXP Logo

Renesas' Cyber Resilience Act Solutions

Aimed at securing embedded systems and IoT devices, the Renesas Security solutions include hardware-based security features integrated into its microcontrollers – the company does not offer discrete secure elements.

In terms of factory programming, the device lifecycle management (DLM) Server Tool manages shared key injection into the chips. As yet, the company does not offer x509 certification.

 

Renesas

Microchip's Cyber Resilience Act Solutions

The Microchip Trust Platform provides discrete secure elements – the ATECC608 and TA100. The PIC32CM integrates an Arm® Cortex M0 core and ATECC608 into the same package. For certain OEMs, the company is offering early access to the PIC32CK, which integrates the Arm® Cortex M33 core with its hardware secure element.

In terms of programming, this is performed by Microchip, and OEMs can specify their content with the Trust Platform Design Suite (TPDS). In addition, Avnet Silica can offer the Microchip programming services via MCC Direct.

Microchip logo

Witekio’s Cyber Resilience Act Solutions

Dedicated to providing customised security software and services for embedded and connected devices, the company is an on-demand trusted Avnet Silica partner for delivering compliance to the Cyber Resilience Act. Witekio’s packaged services include a cybersecurity workshop to initiate a hardware secure by design methodology.

The fast-track Linux service provides the OEM everything they need to ensure their device is delivered on the market fully secured, and the Linux long-term maintenance service ensures that the device remains secure in the market via regular vulnerability checks and software update deployments.

Witekio Logo

When can secure provisioning be done?

Secure provisioning is important for a robust security architecture, and should be considered in addition to the security countermeasures that will be designed in the devices.

Where can provisioning be done (3PSU)

Display portlet menu
The Avnet Silica Warehouse
The Avnet Silica Warehouse

The Avnet Silica Warehouse offers full control on what and how the secure provisioning is done and locks the device, then the OEM just needs to upload the firmware. This one-stop-shop approach to secure provisioning is practical for certain use cases, however, it requires the customisation content to be ready when shipping components.

Production Line
Production Line

For OEMs wishing to perform secure provisioning on the EMS production line, we offer Plug&Go, which is a small HSM with the appropriate keys and certificates that must be loaded onto the device. This approach gives more flexibility to the OEM on the supply chain scheme with tighter control of production units count but requires the EMS to connect a third-party product to their machines, and may even require connectivity to the internet.

In the Field
In the Field

When there is no personalisation during the manufacturing flow, the late personalisation approach is performed in the field. The piece of software, called an agent, in the IoT device enables it to reach the right PKI cloud service during power-up via NXP’s EdgeLock2GO service platform or other services. This approach requires good internet connectivity, and the products leave the manufacturing facility without the appropriate credentials.

Avnet Silica's Technical Team - Talk to the Experts

Avnet Silica’s technical teams help developers in selecting the appropriate hardware, focusing on services such as confidentiality, integrity, and authentication. These Cyber Resilience Act services are focused on key generation, public key injection, root of trust certification, device certification, and chip ID collects. This blend of hardware and services sets Avnet Silica apart from other component suppliers. Additionally, Avnet Silica supports its customers in monitoring their business and identifying new opportunities.

From initial design to mass production and throughout the product life cycle, Avnet Silica offers comprehensive cybersecurity solutions. We specialise in security and serve as a central hub for all services and tools provided by our suppliers, regardless of the application and supply chain scheme chosen. For example, supporting the need for specific certificates and keys to authenticate to the cloud, such as AWS Connection, Azure Connection and IoTConnect, or protecting the OEM’s IP with integrated confidentiality certificates and keys. There is a need for personalisation and customisation, but chip manufacturers only offer generic information on certification authority and, if you want to comply with Matter, for example, you need to have specific information, which we can provide.

Overall, Avnet Silica’s value proposition is centered around technical expertise, comprehensive product offerings, supply chain solutions, value-added services, and market support.

 

Solutions

Internet of Things

Avnet Silica has the perfect supplier offering to enable you to put your product development into the Internet of Things.

Training & Events

Learning for better, faster projects builds

Connect with the Avnet Silica experts who will guide you to reach further with your projects with on-going seminars, workshops, trade shows and online training.

Customer asking question at seminar.

Avnet Silica

LoRaWAN Security Solutions

The TO136 is Avnet Silica’s exclusive secure element. It is manufactured on a hardware base supplied by Morpho and is loaded with a firmware developed by Trusted Objects and personalized with unique keys and IDs in a secure area.

Contact us

Have a question?

Do you have any questions about Security solutions offered by Avnet Silica? Then please feel free to contact our experts at security-solutions@avnet.eu.