Container Proxy for Secure Application Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network security measures, such as firewalls, fail to identify unauthorized users and secure communications between applications within a network, especially in legacy systems where malware can intercept data, and adding proxies for secure communication increases latency and resource requirements.

Innovation Solution

Implementing a system with containers that include a proxy which uses access information from a controller to encrypt and decrypt messages, ensuring secure communication between applications without modifying existing applications and reducing the need for additional network hops.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If firewalls are employed to control network traffic, then network security is improved, but unauthorized users with stolen credentials or spoofed connections cannot be identified

Engineering Contradiction:
Improvenetwork securityVSAvoidunauthorized user identification
Core Design Contradiction:
ReliabilityVSDifficulty of detecting and measuring

Solution Approach 1:

A proxy is introduced as an intermediary component between applications within the container. The proxy intercepts messages, validates access information, and routes communications securely. This intermediary enables the system to detect and prevent unauthorized access by verifying credentials at the application level rather than relying solely on network-level firewall controls.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If proxies are added for secure communication between applications, then communication security is improved, but latency and resource requirements increase

Engineering Contradiction:
Improvecommunication securityVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The proxy and the application are merged into a single container infrastructure. This co-location eliminates the need for additional network hops between separate physical or virtual machines, reducing latency while maintaining the security benefits of proxy-mediated communication. The container shared memory and network namespace enable efficient inter-process communication.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The proxy within the container serves multiple functions: message interception, access information validation, encryption/decryption, and routing. By consolidating these functions into a single component rather than requiring separate security infrastructure, the system achieves comprehensive security without proportionally increasing latency or resource consumption.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Ease of manufacture

If traditional network security measures are used, then basic traffic control is provided, but secure communication between applications within the network cannot be ensured

Engineering Contradiction:
Improvetraffic controlVSAvoidapplication communication security
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The system segments security enforcement into two layers: network-level firewall controls for basic traffic management, and application-level proxy validation within containers for secure inter-application communication. This segmentation allows each layer to specialize in its function, with the proxy handling fine-grained access control for messages between applications while firewalls manage broader network traffic patterns.

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If access information is dynamically updated for secure communication, then security adaptability is improved, but system complexity increases

Engineering Contradiction:
Improvesecurity adaptabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system implements feedback mechanisms where the proxy continuously receives updated access information from external controllers or configuration sources. This feedback loop enables dynamic adaptation to changing security requirements without manual reconfiguration. The proxy validates incoming messages against current access information, automatically adjusting security enforcement based on updated credentials, authorization rules, or recipient information.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10158610B2Secure application communication system
Publication Date: 2018.12.18 ADP INC
  • US10158610B2 patent drawing
  • US10158610B2 patent drawing
  • US10158610B2 patent drawing

AI summary

A method and apparatus for sending messages. A message is received by a proxy in a container running on a computer system from an application in the container. A recipient for the message is identified by the proxy using access information. The message is encrypted by the proxy using the access information. The message to the recipient is sent by the proxy, wherein the access information is received from a controller.