Native Component Network Interface Security via User Space Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed computing architectures, integrating components across different domains while maintaining security is challenging due to restricted access to resources, as components often need to communicate with multiple domains and resources, but security measures restrict access to known users, limiting the functionality and access of browser-based components.

Innovation Solution

A native component is configured to present a network-based interface, allowing access only from the same device and user space by using TCP or UDP interfaces, and determining session identifiers to authenticate requests, ensuring secure communication through SSL and trusted certificates, and supporting REST, SOAP, or HTTP protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If access to resources within a domain is restricted to known or authenticated users, then security is improved, but integration capability and communication between distributed resources deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidintegration capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a browser-based component as an intermediary that operates within the trusted domain of the requesting application. This intermediary component facilitates communication with native components in other domains by leveraging the existing authentication context of the requesting application, thereby enabling integration without requiring direct authentication to restricted resources. The intermediary acts as a mediator that translates requests and maintains security boundaries while enabling cross-domain communication.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If browser-based components are restricted due to security concerns, then security is improved, but functionality and access to resources deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidfunctionality access
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent makes the browser-based component universal by enabling it to access native components across multiple domains and resources. Instead of being limited to a single domain, the component can invoke native components in various domains while maintaining security through the intermediary approach. This multi-functionality allows the same browser-based component to interact with different native components without requiring separate authentication mechanisms for each domain.

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

Solution Approach 2:

The browser-based component serves as an intermediary that bridges the gap between untrusted external resources and trusted internal native components. By operating within the authenticated context of the requesting application, it can safely access native components while maintaining security boundaries, thereby expanding functionality without compromising security.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If components need to communicate with multiple domains and resources, then adaptability is improved, but security management complexity deteriorates

Engineering Contradiction:
Improvecommunication capabilityVSAvoidsecurity management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The browser-based intermediary component simplifies security management by centralizing the authentication and authorization logic within the requesting application's existing security framework. Instead of managing separate authentication mechanisms for each domain, the system leverages the existing security context of the requesting application to access multiple domains, thereby reducing security management complexity while maintaining communication capability across multiple domains.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12001540B2Systems and methods for integrating with a native component using a network interface
Publication Date: 2024.06.04 ROCKET SOFTWARE CANADA INC (SUCCESSOR BY AMALGAMATION WITH AMC CONNECTIVITY SOFTWARE (CANADA) ULC
  • US12001540B2 patent drawing
  • US12001540B2 patent drawing
  • US12001540B2 patent drawing

AI summary

Embodiments as disclosed herein may provide systems and methods for component integration and security. In particular, in one embodiment, a native component that presents a network based interface may be on a device, where that native component may expose a network based interface for access by other components. This native component can then be accessed through the network based interface. To address security concerns and other issues, the native component may be configured to determine if a received request is associated with the same user space and only respond to requests originating from the same user space.