← CRA Glossary
Technical Security

Firmware Update & OTA Security

A firmware update delivers new software to a device's embedded systems - microcontrollers, bootloaders, and operating environments - to fix vulnerabilities, add features, or address hardware behaviour. Over-the-air (OTA) updates deliver firmware remotely. The CRA requires manufacturers to implement and maintain a secure update mechanism throughout a product's support period.

A firmware update delivers new software to a device's embedded systems - microcontrollers, bootloaders, and operating environments - to fix vulnerabilities, add features, or address hardware behaviour. Over-the-air (OTA) updates deliver firmware remotely. The CRA requires manufacturers to implement and maintain a secure update mechanism throughout a product's support period.

Technical Security

Last updated 19 July 2026

What Are Firmware Updates and OTA Security?

Firmware is the low-level software that controls a device's hardware - it runs on microcontrollers, manages peripherals, and often implements core protocol stacks. A firmware update replaces or patches this software to address vulnerabilities, fix bugs, or add functionality. Over-the-air (OTA) update mechanisms allow firmware to be delivered and installed remotely without physical access to the device. OTA update security refers to the controls that ensure only authentic, integrity-verified firmware is accepted by a device: cryptographic signatures on update packages, TLS-secured delivery channels, rollback prevention, and integrity checks performed by a trusted bootloader before executing new code.

CRA reference:, Article 13(3)

Why Firmware Update Security Is a CRA Requirement

of the CRA requires manufacturers to ensure that their products include the ability to receive security updates - and that the update mechanism is itself secure. Article 13(3) reinforces that manufacturers must make security updates available promptly and ensure they are easy to install. An insecure update mechanism is a high-value attack target: if an attacker can inject malicious firmware through the update channel, they gain persistent, privileged access to the device. A secure update mechanism is therefore not merely a feature - it is a prerequisite for the manufacturer's ability to fulfil its ongoing security obligations throughout the product support period.

CRA reference:, Article 13(3)

How Manufacturers Implement Secure OTA Updates

A secure OTA update implementation requires controls at every stage of the update lifecycle. During build: firmware images must be signed with a private key held in a Hardware Security Module (HSM); version metadata and changelogs must be generated. During delivery: firmware must be transmitted over a TLS-authenticated channel; update servers must require device authentication before serving packages. On device: the bootloader or update agent must verify the cryptographic signature before staging; downgrade attacks must be prevented via a version counter; and a validated rollback-to-last-good mechanism should exist to recover from failed updates. Update delivery and installation outcomes should be logged for audit purposes.

CRA reference:,

Common Mistakes

A common firmware update error is signing update packages but not verifying the signature on device - the signature exists in the build pipeline but is never checked before execution. Another error is delivering updates over unencrypted HTTP, making the package susceptible to man-in-the-middle substitution. Manufacturers also frequently implement update mechanisms that lack downgrade protection, allowing an attacker who can intercept the update channel to force installation of an older, vulnerable firmware version. Finally, some manufacturers ship products where the update mechanism depends on a cloud service with no defined availability or continuity commitment, rendering the device unable to receive security updates if the service is discontinued.

CRA reference:

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Must manufacturers provide firmware updates for the entire support period under the CRA?+

Yes. The CRA requires manufacturers to address vulnerabilities and make security updates available without undue delay for the duration of the product's support period. The minimum support period for most products is five years from market placement, or the expected product lifetime if shorter. Manufacturers must maintain the infrastructure and processes to develop and deliver firmware updates for this entire period - they cannot simply cease providing updates when it becomes commercially inconvenient.

Is it sufficient to make firmware updates available for manual download?+

For many consumer products, making updates available for download without active OTA delivery may not satisfy the CRA's intent that updates are 'easy to install'. The Annex I requirement that security updates can be received and installed is most straightforwardly met by an OTA mechanism. For industrial and enterprise products where manual update processes are standard and change-controlled, manual delivery with clear notification mechanisms may be acceptable, but the manufacturer must ensure the update pathway does not become a practical barrier to timely patching.

What happens to firmware update obligations when a product reaches end of life?+

At end of life, the manufacturer's obligation to provide security updates ends - but this must be managed transparently. The CRA requires manufacturers to clearly communicate the end-of-support date to users in advance, giving users time to plan replacement or mitigation. Manufacturers must not simply stop providing updates without notice. After the support period ends, the product remains on the market as a known risk, and market surveillance authorities may take action if the product's unpatched vulnerabilities pose a significant risk to users or third parties.

Sector checklists covering Firmware Update & OTA Security

Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Smart Home DevicesSmart home devices, such as thermostats, smart speakers, lighting controllers and home security cameras, are among the most common products with digital elements in scope for the CRA. Thermostats and lighting controllers are default class, and Module A internal control is open to them (Article 32(1)). A smart speaker with a general purpose virtual assistant is Important Class I (Annex III, point 16). A home security camera, smart lock, baby monitor or alarm system is Important Class I (Annex III, point 17). So is a hub or software that centrally controls these security products.IoT Sensors & Connected DevicesIoT sensors - temperature, humidity, pressure, flow, and motion sensors - are the backbone of industrial and building automation. Most fall into the Default CRA class, but their constrained hardware often makes meeting Annex I security requirements challenging. Manufacturers must plan for secure update mechanisms even on resource-constrained devices.EV Charging Equipment & EVSECompliance tips for EV chargers and Electric Vehicle Supply Equipment (EVSE) manufacturers under the EU Cyber Resilience Act. EV charging stations, Level 2 chargers, and DC fast chargers sit at the intersection of energy infrastructure, payment systems, and connected electric vehicles (EV). Residential and public chargers are default class, because Annex III lists no EV charging category (Article 7(1)). Grid integration and public use do not change the class. They raise the risk that the Article 13(2) cybersecurity risk assessment must address. Secure communication protocols (OCPP 2.0.1, ISO 15118) and vulnerability management are required compliance elements.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Firmware Update & OTA Security fits into your complete CRA compliance programme.

View checklists →