Secure Object Construction via Deployment Server Mediator

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for building and distributing secure objects in computer systems require the build machine to know the target machine's system key, which is undesirable and limits flexibility, as all target machines must share the same system key or receive different versions of software.

Innovation Solution

A method that uses a Deployment Server on the target machine to securely construct and encrypt secure objects without the build machine needing the target machine's system key, employing cryptographic protection and public key cryptography to ensure secure communication and installation, allowing the target machine to complete the construction process independently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the build machine stores the target machine's system key to enable secure object construction, then the secure object can be decrypted and executed on the target machine, but the security of the system key is compromised and all target machines must share the same system key

Engineering Contradiction:

Improvesecure object executionVSAvoidsystem key exposure

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a deployment server as an intermediary component that acts as a mediator between the build machine and the target machine. The deployment server receives encrypted secure objects from the build machine, decrypts them using its own private key, and redistributes them to target machines. This intermediary approach eliminates the need for the build machine to store target machine system keys while maintaining secure execution capability.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the key management function by separating the build machine's encryption capability from the target machine's decryption capability. Instead of the build machine holding all target machine keys, the system divides responsibilities: the build machine encrypts using target machine public keys, and the deployment server or target machines use their own private keys for decryption. This segmentation eliminates key exposure risks.

Inventive Principle:

Principle #1Segmentation

2Reliability

If the build machine sends different versions of secure object software to each target machine with unique system keys, then each target machine can execute secure objects securely, but the device complexity and distribution overhead increase

Engineering Contradiction:

Improvesecure execution on each targetVSAvoidsoftware version management

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements universality by enabling a single build machine to construct secure objects for multiple target machines with different system keys. The build machine uses the target machine's public key to encrypt the secure object, allowing one build process to serve multiple targets. The deployment server also serves multiple functions: receiving encrypted objects, decrypting them, and distributing to various target machines.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Object-affected harmful factors

If the build machine does not know the target machine's system key, then the system key remains secure and not exposed, but the build machine cannot directly construct and encrypt the secure object for the target machine

Engineering Contradiction:

Improvesystem key securityVSAvoidsecure object construction process

Core Design Contradiction:

Object-affected harmful factorsVSEase of manufacture

Solution Approach 1:

The deployment server serves as an intermediary that bridges the gap between the build machine and target machine. It receives encrypted secure objects from the build machine, decrypts them using its own private key (which it obtained during system initialization), and redistributes them to target machines. This allows the build machine to remain key-agnostic while still enabling secure object construction.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary action by having the deployment server obtain and store its own private key during the system initialization phase, before actual secure object construction occurs. This pre-prepared key enables the deployment server to later decrypt and redistribute secure objects without requiring the build machine to know target machine keys.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS10007793B2Secure object having protected region, integrity tree, and unprotected region

Publication Date: 2018.06.26 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A method and structure for a secure object, as tangibly embodied in a computer-readable storage medium. The secure object includes a cryptographically protected region containing at least one of code and data, an initial integrity tree that protects an integrity of contents of the cryptographically protected region; and an unprotected region that includes a loader, an esm (enter secure mode) instruction, and one or more communication buffers.