Obfuscated Container Image Deployment for Secure Analytics

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional techniques fail to securely deploy obfuscated executable modules in external systems, lacking the ability to obfuscate executables before deployment and customize the build environment, which leads to inefficiencies and increased complexity for external users.

Innovation Solution

A method and system for securely deploying obfuscated executable modules involve selecting modules from a repository, transforming them into a container image using a custom base image that includes environment modules, and publishing the container image with obfuscation actions to an external system, enabling secure, customizable, and efficient deployment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional deployment methods are used, then external systems can manually initiate executables, but security is compromised and the process is inefficient

Engineering Contradiction:
ImprovesecurityVSAvoiddeployment efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system performs obfuscation actions on executable modules before deployment to external systems. The build system transforms modules into obfuscated container images in advance, so that when deployed, the external system receives already-secured artifacts without needing to handle sensitive executable content, thus improving both security and deployment efficiency

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a build system as an intermediary between the internal system and external system. This build system acts as a secure gateway that performs obfuscation and transformation of executable modules before they reach external systems, eliminating the need for external systems to directly access or handle sensitive executable content

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If executables are made accessible by external systems, then external users can run them, but the external system becomes overwhelmed with testing and management complexity

Engineering Contradiction:
Improveexternal system operationVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the complex obfuscation and transformation processes from the external system and concentrates them in a dedicated build system. The external system only needs to interact with simplified container image artifacts rather than managing complex executable modules, thus reducing external system complexity while maintaining ease of operation

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The build system transforms executable modules into container images with different structural parameters and formats. This parameter transformation changes the deployable artifact from a complex executable module requiring extensive testing to a standardized container image that is easier to manage and deploy, reducing external system complexity

Inventive Principle:
Principle #35Parameter changes

3Loss of time

If manual executable deployment is used, then external users can initiate tasks, but build time is excessive and security is compromised

Engineering Contradiction:
Improvebuild timeVSAvoidsecurity
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system performs obfuscation actions on executable modules before deployment to external systems. The build system transforms modules into obfuscated container images in advance, so that when deployed, the external system receives already-secured artifacts without needing to handle sensitive executable content, thus improving both security and deployment efficiency

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces manual executable deployment mechanisms with an automated build system that uses containerization technology. This substitution automates the obfuscation and deployment process, reducing build time while maintaining security through systematic transformation of modules into secure container images

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20240103921A1Systems and methods for secured and integrated analytics deployment accelerator
Publication Date: 2024.03.28 HONEYWELL INTERNATIONAL INC
  • US20240103921A1 patent drawing
  • US20240103921A1 patent drawing
  • US20240103921A1 patent drawing

AI summary

Disclosed are methods and systems for securely deploying obfuscated modules in an external system. For instance, a method may include selecting one or more modules from a module repository, the one or more modules associated with completing a task, receiving a custom base image, the custom base image including one or more environment modules configured to provide a specific execution environment for the one or more modules, transforming based on the custom base image, the one or more modules into a container image, the transforming including performing at least one obfuscation action on the one or more modules, and publishing the container image and a container image identifier to the external system, the external system configured to execute a cluster instance corresponding to the task, the cluster instance comprising at least one of: the container image identifier, one or more environmental parameters, and one or more entry point parameters.