Compute Instance Identity Verification via Non-Transferable Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Virtualized computing services face challenges in providing secure identity verification mechanisms for compute instances, as manual approaches are error-prone and susceptible to intruders, and existing systems lack robust mechanisms for managing multiple cryptographically verifiable identities within provider networks.
Innovation Solution
Implementing a mechanism for non-transferable cryptographic keys stored in secure key stores, allowing compute instances to use programmatic interfaces to generate identity-related artifacts without revealing the private key, and assigning multiple cryptographically verifiable identities (CVIs) within respective namespaces to enhance security and identity validation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual identity verification approaches are used for compute instances, then administrative flexibility is maintained, but security reliability deteriorates due to error-proneness and susceptibility to intruders
Solution Approach 1:
The compute instance automatically performs identity verification by presenting its cryptographic identity (public key or certificate) to service providers without requiring manual administrative intervention. The instance autonomously proves its identity through cryptographic challenges, eliminating human error while maintaining operational simplicity through automated key management.
Solution Approach 2:
Manual administrative verification processes are replaced with cryptographic mechanisms. Instead of human administrators manually verifying identities, the system uses public-key cryptography where the compute instance automatically proves its identity through mathematical proofs (digital signatures or key exchange), providing both security and automation.
2Adaptability or versatility
If multiple cryptographically verifiable identities are assigned to compute instances, then identity validation capability is improved, but device complexity increases due to key management requirements
Solution Approach 1:
A single cryptographic key pair serves multiple identity validation purposes. The compute instance's public key can be used across different services and applications within the provider network, eliminating the need for separate key pairs for each service while maintaining the ability to verify identity in various contexts.
Solution Approach 2:
The virtualization layer acts as an intermediary that manages cryptographic keys on behalf of compute instances. The virtualization layer generates, stores, and manages the private keys securely while presenting public keys to service providers, abstracting away the complexity of key management from both the compute instances and the service providers.
3Reliability
If private keys are stored securely to prevent intrusion, then security is improved, but accessibility for identity verification deteriorates
Solution Approach 1:
The cryptographic identity system separates the private key (kept secure in the virtualization layer) from the public key (used for verification). This segmentation allows the private key to remain protected while the public key is freely shared with service providers for identity verification, resolving the contradiction between security and accessibility.
Solution Approach 2:
Instead of transferring or exposing the private key, the system uses the public key (a safe copy or derivative of the private key) for all verification purposes. The public key contains all necessary information for identity verification but cannot be used to derive the private key, maintaining security while enabling widespread verification.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A compute instance of a virtual computing service (VCS) is assigned first and second cryptographically verifiable identities (CVIs) within respective namespaces. A cryptographic key pair associated with the first CVI includes a non-transferable private key managed by a secure key store which does not permit the private key to be copied. The VCS enables the instance to use the private key for asserting the CVIs. In response to a first identity query, the instance indicates the first CVI. In response to a second identity query, the instance indicates the second CVI.