Post-Quantum Cryptography Key Provisioning via Seed Derivation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing Trust Provisioning systems are vulnerable to quantum computing attacks, as quantum computers can recover RSA/ECC secret keys, and post-quantum cryptography (PQC) key updates face challenges due to larger key sizes, space constraints, and ongoing algorithm standardization, making it difficult to securely transition devices to PQC algorithms.
Innovation Solution
A system and method for provisioning cryptographic devices with post-quantum cryptography (PQC) keys using a key generation seed, PQC private and public keys, and an updater, which adapts to various PQC algorithms by reserving sufficient memory and using a hardware security module (HSM) to securely generate and store PQC keys, enabling flexible updates and secure operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If PQC keys are provisioned with larger key sizes to withstand quantum attacks, then security against quantum computing attacks is improved, but device memory space requirements increase
Solution Approach 1:
The system pre-provisions a key generation seed in the device memory before the actual PQC key deployment. This seed is used later to generate the full PQC key pair through a key derivation function, avoiding the need to store the entire large PQC key in memory during provisioning. The seed acts as a preliminary action that enables future key generation without immediate space consumption.
Solution Approach 2:
The system extracts only the essential seed material (smaller than full PQC keys) for storage in the device, while the full PQC key is generated on-demand using the seed and a key derivation function. This extraction approach retains the security benefits of large PQC keys while minimizing the memory footprint by storing only the condensed seed version.
2Reliability
If PQC algorithms are updated in deployed devices to maintain security, then future security resilience is improved, but device complexity and update management difficulty increase
Solution Approach 1:
The system implements a universal key generation seed that can be used across multiple different PQC algorithms. The same seed can generate keys for different PQC schemes through configurable key derivation functions, allowing a single provisioning mechanism to support multiple algorithms and simplifying future updates when new algorithms are standardized.
Solution Approach 2:
The system uses a dynamic key derivation function that can be configured to generate different PQC key types based on algorithm requirements. This dynamic approach allows the same provisioning infrastructure to adapt to different PQC algorithms without requiring separate provisioning mechanisms for each algorithm, reducing update management complexity.
3Adaptability or versatility
If multiple PQC algorithms are supported for flexibility, then adaptability to future standardization is improved, but memory provisioning requirements increase
Solution Approach 1:
The system pre-provisions a key generation seed that serves as a universal foundation for multiple PQC algorithms. This preliminary seed storage enables the device to support multiple algorithms without requiring separate memory allocations for each algorithm's key material, as all keys can be derived from the single seed using algorithm-specific key derivation functions.
Data Source
AI summary
Various embodiments relate to a system for provisioning a cryptographic device, including: a memory; a processor coupled to the memory, wherein the processor is further configured to: determine the maximum key generation seed size, maximum PQC private key size, maximum PQC public key size, and maximum PQC updater size of a plurality of post quantum cryptography algorithms; provision memory in the cryptographic device to store a key generation seed, PQC private key, PQC public key, and PQC updater based upon the determined maximum key generation seed size, maximum PQC private key size, maximum PQC public key size, and maximum PQC updater size; and provision the cryptographic device with a non-PQC secret key, a non-PQC public key, and non-PQC algorithm code configured to carry out non-PQC cryptographic algorithms.