SoC Secure Provisioning via Embedded Public Key
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
System on a Chip (SoC) devices are vulnerable to malicious attacks during provisioning, leading to potential malfunctions in critical systems like autonomous driving, financial processing, and air traffic control, as they are susceptible to malware and unauthorized provisioning before being deployed in secure environments.
Innovation Solution
The secure initial provisioning of SoCs involves generating public/private key pairs and secret shared keys, embedding these keys in Resistor Transistor Logic (RTL) during manufacturing, and using them to encrypt and decrypt provisioning data, ensuring that only authorized entities can provision the SoCs, thereby preventing unauthorized access and malware loading.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If SoCs are provisioned after installation in systems, then ease of operation is improved, but security is worsened due to susceptibility to malicious attacks during provisioning
Solution Approach 1:
The patent applies preliminary action by embedding cryptographic keys directly into the SoC hardware during the manufacturing process, before the device is deployed or provisioned. This pre-provisioning with security credentials ensures that the SoC is secure from the moment it is manufactured, eliminating the vulnerability window that exists when provisioning is deferred until installation. The public key is hardwired into the hardware, creating an inherent security foundation that prevents malware injection during subsequent provisioning operations.
2Reliability
If cryptographic keys are embedded in RTL during manufacture, then security is improved, but device complexity increases due to key management requirements
Solution Approach 1:
The patent applies the extraction principle by removing the private key from the SoC hardware entirely and storing it only in the external secure element. This separation means the SoC itself does not need to implement complex key management mechanisms - it only needs to use the publicly embedded key for cryptographic operations. The complexity of secure key storage and management is extracted and isolated in the dedicated secure element, simplifying the overall system architecture while maintaining strong security.
Solution Approach 2:
The patent introduces a secure element as an intermediary component that handles all sensitive key management operations. This secure element acts as a mediator between the SoC and the private key, providing secure storage and cryptographic processing without requiring the SoC to implement its own key management infrastructure. The intermediary absorbs the complexity of key protection while presenting a simple interface to the rest of the system.
3Reliability
If public key is embedded in RTL, then provisioning security is improved, but manufacturing precision requirements increase due to hardware key embedding
Solution Approach 1:
The patent applies the copying principle by using standard cryptographic key generation and embedding processes that can be replicated across many devices. The public key embedded in the RTL is a cryptographic value that can be generated and programmed using conventional semiconductor manufacturing techniques. This approach allows mass production of secure devices without requiring exotic or highly precise manufacturing capabilities, as the cryptographic keys are embedded as standard digital data in the hardware logic.
4Reliability
If private key is stored externally, then security is improved, but loss of information risk increases due to external storage vulnerability
Solution Approach 1:
The patent applies beforehand cushioning by implementing redundant secure storage mechanisms and backup procedures for the private key in the external secure element. The system is designed with fail-safes that protect against loss or corruption of the private key, such as secure backup copies stored in protected memory or the ability to recover keys through authenticated processes. This pre-prepared protection ensures that the private key remains available and secure even if the external storage medium experiences failures or is subjected to physical damage.
Data Source
AI summary
Securely provisioning a System on a Chip (SoC) includes generating a public/private key pair having a public key and a private key, securely storing the private key external to the SoC, embedding the public key in Resistor Transistor Logic (RTL) of the SoC during manufacture of the SoC, encrypting provisioning data using the private key to create encrypted provisioning data, and programming the SoC using the encrypted provisioning data. The secure provisioning may further include generating a secret shared key, embedding the secret shared key in the RTL of the SoC during manufacture of the SoC, and encrypting the provisioning data using the secret shared key. The RTL may be the boot Read Only Memory (ROM) of the SoC. The secure provisioning technique may also be used for subsequent provisioning after the SoC is deployed.