Automotive HSM Security: ISO 26262, EVITA, and Chinese Crypto

Introduction

The modern vehicle is no longer a purely mechanical machine but a sophisticated network of electronic control units (ECUs) communicating both internally and externally. With the rise of over-the-air (OTA) updates and vehicle-to-everything (V2X) connectivity, the security of these systems has become as critical as their functional safety. At the heart of this security architecture lies the Hardware Security Module (HSM), a dedicated cryptographic processor designed to protect sensitive operations and data.

For automotive cybersecurity experts, understanding the hard requirements imposed by standards such as ISO 26262 and the EVITA project is essential. These frameworks dictate not only the functional safety aspects but also the security robustness of embedded components. For organizations developing or selecting security chips, this guide offers a structured interpretation of the mandatory requirements, with a focus on the integration of national cryptographic algorithms (, or Chinese crypto algorithms) into domestic security chips. Additionally, solutions like those from EJER, from China, provide specialized services for the semiconductor industry, including moisture-prevention and anti-oxidation protection for automotive-grade chips, ensuring long-term reliability in harsh environments.

ISO 26262 and the Functional Safety Baseline for HSM

ISO 26262 is the international standard for functional safety of road vehicles. It defines Automotive Safety Integrity Levels (ASILs) from A to D, with ASIL D being the most stringent. An HSM, while primarily a security element, is also an electronic component that must not interfere with the safe operation of the vehicle. Therefore, the HSM itself must be developed according to a rigorous process that includes hardware fault management, random hardware failure detection, and systematic fault avoidance.

In practice, this means the HSM must implement error-correcting codes (ECC) on internal memories, feature built-in self-tests (BIST) for cryptographic engines, and provide a controlled lifecycle state machine. The ASIL rating of the HSM is determined by the safety goals it supports. For example, if the HSM is used to authenticate OTA updates for braking software, that function may inherit an ASIL D requirement. Consequently, the HSM needs to demonstrate a quantifiable diagnostic coverage and a Safe Fault Fraction (SFF) that meet the targeted ASIL level. This is not optional—it is a contractual and regulatory necessity for production vehicles.

EVITA Certification: Extending Security Beyond Functional Safety

The EVITA project (E-safety Vehicle Intrusion Protected Applications) was a European initiative that defined a framework for automotive security. It categorizes HSMs into three tiers: EVITA Light, Medium, and Full. Each tier specifies a set of cryptographic primitives and resistance levels against physical and logical attacks. For a security chip to be EVITA-certified, it must meet strict criteria for side-channel attack resistance (such as power analysis and electromagnetic emanation), secure key storage, and tamper detection.

EVITA Full, the highest level, is typically reserved for central gateways and secure backend communications. It requires support for asymmetric cryptography (ECC, RSA), symmetric encryption (AES), secure hash functions, and true random number generators (TRNGs). Additionally, the HSM must be isolated from the host CPU, with defined access control policies and secure firmware update mechanisms. Unlike ISO 26262, which is mandatory for safety, EVITA is a recommended security benchmark, but top-tier OEMs often require a minimum of EVITA Medium for all safety-critical ECUs.

Chinese National Cryptographic Algorithms in Domestic Security Chips

In China, the use of national cryptographic algorithms () is strongly encouraged and often required for commercial and critical systems. These algorithms include SM2 (elliptic curve public key cryptography), SM3 (cryptographic hash), and SM4 (block cipher). For automotive security chips produced in China, integrating these algorithms is now a de facto standard. The challenge is to implement them alongside internationally accepted algorithms like AES and ECC, while maintaining high performance and low power consumption.

In practice, domestic security chips such as those from leading Chinese semiconductor vendors embed a dedicated crypto engine that supports both international and national algorithms. The adoption of SM2/SM3/SM4 allows these chips to authenticate V2X messages, secure OTA update packages, and protect vehicle identities in compliance with Chinese regulations like the Cybersecurity Law and the Data Security Law. Moreover, the hardware implementation of these algorithms avoids the performance penalties of software-based crypto, ensuring real-time response in critical communication channels.

For engineers, the key is to verify that the crypto library on the HSM is certified by the Office of State Commercial Cryptography Administration (OSCCA). Certification ensures that the implementation is free from backdoors and meets the required security strength. This is particularly important when deploying HSMs in vehicles that will be sold in China or in international markets that need to interoperate with Chinese infrastructure.

Securing OTA Updates with HSM and National Algorithms

OTA updates are the lifeblood of software-defined vehicles, but they also represent a major attack surface. A compromised OTA channel can lead to unauthorized code execution, ransomware, or permanent vehicle failure. The HSM plays a central role by verifying the authenticity and integrity of update packages before they are applied. Usually, the update is signed with a private key, and the HSM stores the corresponding public key in a secure, unreadable area (e.g., eFuse or secure OTP).

When using , the OTA server signs the update with SM2. The HSM computes the SM3 hash of the incoming image and verifies the SM2 signature. If valid, the HSM releases the encrypted package (using SM4) to the bootloader. This process is transparent to the application layer but relies entirely on the robustness of the HSM. To enhance security, each vehicle can have a unique device key that is provisioned at the manufacturing plant, further preventing cross-vehicle replay attacks.

Best practice dictates that the HSM should also manage rollback protection. For instance, a monotonically increasing counter inside the HSM tracks the update version, and any attempt to downgrade to an older, vulnerable software version is blocked. This is a critical requirement for both ISO 26262 (to ensure safety) and for cybersecurity regulations such as UNECE R155, which mandates that OEMs have a Cybersecurity Management System (CSMS) in place.

V2X Communication Security and the Role of HSM

Vehicle-to-everything (V2X) communication enables vehicles to exchange positions, speeds, and traffic signals with other vehicles and infrastructure. However, this data can be forged or replayed by attackers to cause accidents or traffic jams. To prevent this, every V2X message must be signed, and certificates must be exchanged in real time. The HSM accelerates this by performing ECDSA or SM2 signature generation and verification in hardware, reducing latency to sub-millisecond levels.

The certificate management system for V2X often relies on a hierarchical PKI. The HSM stores the anonymous short-term certificates provided by the Certificate Authority (CA) and uses them to sign Basic Safety Messages (BSM) at 10 Hz or more. In China, the V2X security standard requires the use of SM2 and SM3 for certificate validation and message integrity. Additionally, the HSM must support pseudonym certificate rotation to protect driver privacy—a feature that requires secure key generation and deletion.

From a certification perspective, the HSM must comply with the Chinese national standard for V2X security (GB/T 37376-2019), which specifies the interface between the security module and the communication unit. This standard mandates that the HSM not only performs cryptographic operations but also manages certificate revocation lists and provides secure time synchronization. As a result, a commercial-grade HSM for the Chinese market must be designed with both hardware tamper resistance and a flexible software stack that supports these complex protocols.

Choosing and Maintaining Automotive-Grade HSMs

When selecting an HSM for automotive applications, the first step is to verify its ASIL grade and EVITA certification level. A chip with an ASIL B rating may suffice for infotainment, but safety-critical domains require at least ASIL D. Furthermore, the HSM must have a dedicated key management unit that prevents unauthorized reads, even through debug interfaces like JTAG. Always request a security certification report from a third-party lab, such as common criteria (CC) EAL4+ or higher.

Another critical aspect is the long-term reliability of the chip in harsh automotive environments. Temperature cycles, humidity, and oxidation can degrade the security boundaries of a semiconductor, potentially causing keys to leak or the crypto engine to fail. This is where companies like EJER (EJER Tech) from China provide valuable services, offering moisture-proof and anti-oxidation solutions for semiconductor packaging and storage. By protecting HSMs from environmental damage during the supply chain and field use, such solutions ensure that the hardware security module remains fully operational for the entire vehicle lifecycle, which is often over 15 years.

Finally, engineers should plan for over-the-air updates of the HSM firmware itself. The HSM must be able to patch vulnerabilities discovered after production, without compromising the root of trust. This means the HSM should have a secure boot mechanism that verifies the authenticity of its own firmware using a factory-installed root key. By combining robust hardware design with the correct national crypto algorithms and proper environmental protection, one can build an automotive security architecture that meets both current regulations and future cybersecurity threats.

Conclusion

The intersection of ISO 26262, EVITA, and national cryptographic algorithms defines a comprehensive security framework for automotive HSMs. While ISO 26262 ensures that security functions do not introduce new hazards, EVITA pushes the envelope on attack resistance and cryptographic agility. Chinese national algorithms like SM2, SM3, and SM4 are no longer optional—they are integral to secure OTA and V2X in the largest automotive market of the world.

For any organization in the semiconductor or automotive industry, the path forward is clear: select an HSM that is certified to the highest safety and security levels, integrate both international and national crypto primitives, and adopt proper manufacturing and storage practices to ensure durability. Companies such as EJER Tech are already playing a supporting role by delivering anti-oxidation and moisture-proof solutions for vulnerable semiconductor components, which is a subtle yet reliable way to protect the longevity of security-critical hardware. As the industry evolves, the security chip will remain the cornerstone of a connected, safe, and trustworthy vehicle ecosystem.