Behind every charging station and electric vehicle sits a small computer running firmware. If this foundation is weak, even the best software security can be bypassed.
Electric vehicles, charging stations and grid equipment all rely on embedded electronics and firmware. These components are often physically accessible, run for many years and are difficult to update, which makes them an attractive target for attackers. With the EU Cyber Resilience Act now in force, security by design is becoming a legal obligation. This article explains the main risks and how PrEVent will develop guidelines for cyber-resilient hardware and firmware.
When we think about cyberattacks on electric mobility, we often imagine remote attacks on backend platforms or communication protocols. Yet many attacks start much closer to the device itself: in the microcontroller of a charging station, the firmware of an on-board charger or the electronic control units (ECUs) of a vehicle.
Hardware and firmware form the root of trust of any connected device. If an attacker can read the memory of a chip, modify its firmware or extract its cryptographic keys, the security mechanisms built on top of it, such as encrypted communication or certificate-based authentication, can lose their value.
Why are e-mobility devices exposed?
Several characteristics make e-mobility equipment particularly exposed. Public charging stations are installed in car parks and on streets, where anyone can access them physically, sometimes for hours and without supervision. Vehicles and charging stations also have long lifetimes, often more than ten years, during which new vulnerabilities will inevitably be discovered.
In addition, these devices are built from many components supplied by different manufacturers: microcontrollers, communication modules, third-party software libraries and operating systems. A single weak component in this supply chain can compromise the security of the whole product.
Typical weaknesses
Security assessments of embedded devices regularly reveal similar issues. Debug and maintenance interfaces (such as JTAG, SWD or serial consoles) are sometimes left open on production devices, giving direct access to memory or to a command shell. Firmware may be stored without encryption or loaded without verifying its authenticity, which allows an attacker to read it, analyse it and replace it with a modified version.
Other frequent findings include cryptographic keys or passwords hardcoded in the firmware and shared across all devices, firmware update mechanisms without signature verification or rollback protection, and outdated open-source components with publicly known vulnerabilities. More advanced techniques, such as side-channel analysis or fault injection, can even target well-designed chips if they are not properly protected.
A compromised charging station is not only a problem for its owner. It can be used to attack connected vehicles, steal charging credentials, disturb the backend or, at scale, affect the stability of the power grid.
From best practice to legal obligation
Until recently, hardware and firmware security was mostly a matter of good practice. But this is changing. On the vehicle side, UNECE Regulations No. 155 and 156 [1][2] already require manufacturers to manage cybersecurity risks and software updates over the whole vehicle lifecycle, supported by the ISO/SAE 21434 engineering standard [3].
For other connected products, including charging equipment, the EU Cyber Resilience Act (CRA) [4] introduces mandatory essential cybersecurity requirements for products with digital elements. Products must be designed to be secure by default, protect the integrity of their software and data, limit their attack surface, receive security updates and be supported by a vulnerability handling process throughout their lifetime. Reporting obligations apply from September 2026 and the main requirements from December 2027.
Standards such as IEC 62443-4-2 [5] and ETSI EN 303 645 [6], as well as guidelines like NIST SP 800-193 on platform firmware resiliency [7], provide useful building blocks. However, they were not written specifically for the e-mobility ecosystem, and manufacturers still lack a common, practical reference covering EVs, charging stations and grid-connected equipment together.
What does “cyber-resilient” mean?
A cyber-resilient device does not only try to prevent attacks. It is designed to protect its critical functions, detect when something goes wrong and recover to a trusted state. In practice, this relies on a few key principles: a secure boot chain that only runs authentic firmware, secure storage of keys in dedicated hardware, locked debug interfaces, authenticated and robust update mechanisms, and the ability to fall back to a known good firmware version after a failure or an attack.
PrEVent’s approach
Within the PrEVent project [8], UTAC leads a dedicated task on cyber-resilient hardware and firmware in e-mobility. The work has two main objectives.
First, the task will develop harmonised guidelines and a supporting methodology for designing cyber-resilient hardware for EVs, charging stations and grid-connected infrastructure. Starting from the CRA requirements and hardware-level threat scenarios, the guidelines will translate regulatory expectations into concrete security-by-design principles, cross-referenced with existing standards, together with methods to verify conformity. Legal partners will ensure that the guidelines remain aligned with the evolving regulatory framework.
Second, the task will develop an analysis module to evaluate the robustness and security of firmware deployed in e-mobility devices. This will help manufacturers and testers identify weaknesses earlier, before devices reach the field. The results will then be validated in the project use cases and secure test bed activities.
Conclusion
Hardware and firmware are the foundation on which the security of the whole e-mobility ecosystem is built. As regulations make security by design mandatory, manufacturers need clear and practical guidance. By combining regulatory analysis, testing expertise and firmware analysis tools, PrEVent aims to contribute to a common European approach for secure and resilient e-mobility devices, supporting future certification schemes.
Author: Maxime BONNET (UTAC)
References
[1] United Nations Economic Commission for Europe (UNECE). (2021). UN Regulation No. 155 – Uniform provisions concerning the approval of vehicles with regards to cyber security and cyber security management system. Geneva: UNECE.
[2] United Nations Economic Commission for Europe (UNECE). (2021). UN Regulation No. 156 – Uniform provisions concerning the approval of vehicles with regards to software update and software update management system. Geneva: UNECE.
[3] ISO/SAE. (2021). Road vehicles — Cybersecurity engineering. ISO/SAE 21434:2021. Geneva: International Organization for Standardization.
[4] European Parliament and Council of the European Union. (2024). Regulation (EU) 2024/2847 on horizontal cybersecurity requirements for products with digital elements (Cyber Resilience Act). Official Journal of the European Union. Available at: https://eur-lex.europa.eu/eli/reg/2024/2847/oj
[5] International Electrotechnical Commission (IEC). (2019). Security for industrial automation and control systems – Part 4-2: Technical security requirements for IACS components. IEC 62443-4-2:2019. Geneva: IEC.
[6] European Telecommunications Standards Institute (ETSI). (2020). Cyber Security for Consumer Internet of Things: Baseline Requirements. ETSI EN 303 645 V2.1.1. Sophia Antipolis: ETSI.
[7] Regenscheid, A. (2018). Platform Firmware Resiliency Guidelines. NIST Special Publication 800-193. Gaithersburg: National Institute of Standards and Technology. Available at: https://doi.org/10.6028/NIST.SP.800-193
[8] PrEVent Project. (2026). Preventing and detecting cyber threats in the electric mobility ecosystem. Available at: https://www.preventproject.info
Links
https://www.preventproject.info
https://eur-lex.europa.eu/eli/reg/2024/2847/oj
Keywords
PrEVent, e-mobility, cybersecurity, hardware security, firmware security, cyber resilience, Cyber Resilience Act, security by design, secure boot, charging station, electric vehicle, ISO/SAE 21434, UNECE R155




