Secure Object Construction Without Target System Key Exposure
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for constructing secure objects in computer systems require the build machine to know the target machine's system key, leading to security vulnerabilities and the need for all target machines to share the same system key or send different versions of software.
Innovation Solution
A method where a Deployment Server on the target machine generates and encrypts secure objects using its own system key, ensuring that the build machine does not need to know the target machine's system key, and using public key cryptography to encrypt and decrypt handles, allowing secure object construction without access to the target machine's system key.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If the build machine stores the target machine's system key to construct secure objects, then secure object construction is enabled, but security is compromised and system key exposure occurs
Solution Approach 1:
The system key is extracted from the build machine environment entirely. Instead of storing the target machine's system key on the build machine, the patent uses the build machine's own system key to encrypt handles that will later be decrypted by the target machine using its own system key. This separation eliminates the security vulnerability of key exposure while maintaining construction capability.
Solution Approach 2:
An intermediary encryption layer is introduced where the build machine's system key acts as a temporary mediator. The build machine encrypts handles with its own key, and the target machine decrypts them with its own key. This intermediary approach allows secure object construction without direct access to the target machine's system key, resolving the contradiction between construction ease and security.
2Ease of manufacture
If all target machines share the same system key for secure object execution, then construction is simplified, but security isolation between machines is lost
Solution Approach 1:
Each target machine is assigned its own unique system key, creating local quality in the security configuration. The build machine's system key is used temporarily during construction, but the final secure objects are bound to each target machine's specific key. This allows simplified construction processes while maintaining machine-specific security isolation and adaptability.
3Reliability
If the build machine sends different versions of secure object software to each target machine, then security is maintained, but distribution complexity increases
Solution Approach 1:
The patent changes the parameter of handle encryption from target-machine-specific keys to build-machine-universal keys. The build machine encrypts all handles with its own system key, creating a universal format that any target machine can decrypt using its own system key. This parameter change maintains security (each machine uses its unique key) while simplifying distribution (one version fits all machines).
Data Source
AI summary
A method and structure for enhancing protection for at least one of software and data being executed on a computer. A file to comprise a secure object is constructed, using a processor on a build machine, the secure object to be executed on a target machine different from the build machine. The secure object comprises at least one of code and data that is to be encrypted when the secure object is stored on the target machine. The encrypted stored secure object is decrypted by the target machine when executed by the target machine after retrieval from a memory on the target machine. The decryption uses a system key of the target machine. The secure object is stored, upon completion of construction, in an encrypted state as a completed secure object, and the secure object is completed without the build machine having the system key of the target machine.