Security Component Customization via Segmented Key Cryptograms
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing methods for customizing security components in ticketing systems are lengthy, costly, and inflexible due to the need for secure initialization of personalized secrets, which requires secure premises and trusted personnel, limiting scalability and flexibility in deployment.
Innovation Solution
A method involving inserting a first secret into the security component by the manufacturer, generating an application secret, and creating a personalization cryptogram by encrypting it with the first secret, allowing customization in an unprotected environment while maintaining confidentiality through secure domain operations and limited access to the encryption component.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If personalized secrets are introduced in secure premises, then security is improved, but deployment time and cost increase
Solution Approach 1:
The patent segments the secret key management into two parts: a first secret key K0 inserted during manufacturing in secure conditions, and a second secret key K generated later by the acquirer. This segmentation allows the time-consuming secure customization to be replaced by a simple cryptographic operation, dramatically reducing deployment time while maintaining security.
Solution Approach 2:
The patent performs preliminary action by inserting the first secret key K0 into the security component during manufacturing in secure premises. This preliminary secure operation eliminates the need for repeated secure customized operations during deployment, allowing future personalization to be done in unprotected environments.
2Reliability
If personalized secrets are introduced in secure premises, then security is improved, but deployment flexibility decreases
Solution Approach 1:
By segmenting the secret key into a manufacturer-inserted first secret K0 and an acquirer-generated second secret K, the patent enables deployment in unprotected environments, significantly improving flexibility and adaptability while maintaining security through the initial secure insertion of K0.
Solution Approach 2:
The patent uses cryptographic operations as an intermediary mechanism. The acquirer uses the first secret K0 (inserted securely during manufacturing) to generate the second secret K through cryptographic operations, allowing secure personalization without requiring secure premises during deployment.
3Ease of operation
If the encryption component is made accessible for personalization, then ease of operation is improved, but security risks increase
Solution Approach 1:
The patent extracts the sensitive first secret K0 from the encryption component after it has been used to generate the personalization cryptogram. The encryption component is delivered to the acquirer without the first secret K0, eliminating security risks associated with continuous access while maintaining ease of operation for personalization.
Solution Approach 2:
The patent performs the sensitive operation of inserting the first secret K0 into the encryption component during manufacturing in secure premises. This preliminary secure operation allows the encryption component to be subsequently used in unprotected environments without exposing the first secret, balancing ease of operation with security.
Data Source
Figure 1
AI summary
The invention relates to a method of customizing a security component in an unprotected environment. The method according to the invention comprises: a step of inserting a first secret K0 in said security component, said step being implemented in a secure domain under the responsibility of the manufacturer of the security component; a step of generating an application secret K and a step of generating a customization cryptogram [K]K0 obtained by encoding the application secret K by the first secret K0, said steps being implemented in a secure application domain under the responsibility of the holder of the security component; a step of customizing the security component by inserting into said security component the customization cryptogram [K]K0, said customization step being implemented in an application domain. In particular, the invention applies to secure access module components.