AURIX™ Security Solutions

Infineon’s AURIX™ 32-bit microcontroller family, with its embedded Hardware Security Module (HSM), is a perfect fit for automotive applications, where specific security functionalities are required. Typical examples of such applications are tuning protection,  immobilizer , secure on-board communication etc. Infineon not only offers a scalable portfolio of compatible AURIX™ devices, with integrated HSM, but also the necessary SW packages as well as support services. This provides our customers with everything they need to fulfill the security requirements of their applications 

Click & check below the complete AURIX™ portfolio of Infineon:

Highly flexible and programmable  solution based on:

• Secure Platform:

HSM provides a secure platform, separated from the rest of the microcontroller by a firewall, thereby creating a trusted execution environment.

• Security Standard Compliance:

AURIX™ HSM fulfills SHE HIS and Evita Medium standards as well as provide some additional functionalities.

• Backward Compatibility:

AURIX™ security solutions are backward compatible to security SHE HIS implementations in previous TriCore based microcontroller families.

• Security Differentiation:

Customized secure OEM or Tier1 crypto apps can be processed within trusted HSM execution environment and therefore allow independent HSM specific SW code review in reference to the huge application host SW from multiple parties. This helps to harden the security level by reliably avoiding potential security backdoors.

• Secure Failure Analysis:

For the purpose of preventing unpermitted debug access, AURIX™ HSM offers 256 bit password for debugger access protection. It is possible to create car specific debugger password, which can be stored in OEM/TIER1 data base or generated by secret algorithm. Destructive Debugger Entry functionality opens debugger access but initiates a persistent destructive action - device gets inoperable in native ECU car environment.

• Secure Process:

Infineon can provide a secure personalization flow. 1st personalization step usually happens at the Tier1, where initial HSM SW and optional transportation key(s) are injected to the ECU. 2nd personalization step happens at the OEM, where a car specific Individual key(s) are injected.  AURIX™™ HSM offers device specific, individual random read-only key. Read-only key can be used for injected keys and make them invisible for the application SW layer.

• Convergence of security and safety:

AURIX™ microcontrollers address both functional safety as well as IT-security requirements, making sure those are properly integrated and not conflicting with one another

The SHE+ driver controls the hardware security peripheral in the HSM domain and interacts to the TriCore host core. SHE+ offers the AUTOSAR CRY interface to integrate the HSM security features into an automotive application including interface to AUTOSAR, communication from TriCore to HSM

SHE+ can be added to existing MCAL Driver packages and is configured with the Tresos Studio. This is an Eclipse-based tool for the configuration of AUTOSAR software modules.and vice versa, key storage functionality and security peripheral drivers.

SHE+ can offer the following functionality:

Please check the youtube channel Infineon4Engineers for more videos.