Browser Container Isolation for Secure Client-Side Data Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current information security measures focus on securing enterprise web applications and host servers, but there is a need for enhanced client-side security, particularly in ensuring the secure transfer of user data across various environments, including public and private cloud servers, while maintaining isolation and efficiency.

Innovation Solution

The solution involves running client-side applications in browser containers, allowing secure data transfer between a website server and the browser, with session-specific information cached on the client-side, reducing HTTP requests, and utilizing web sockets for data state changes, thereby enhancing isolation and scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of energy

If data is transferred between website server and browser without caching, then data freshness is maintained, but bandwidth consumption and network congestion increase

Engineering Contradiction:
Improvebandwidth consumptionVSAvoiddata freshness
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The patent implements preliminary action by caching session-specific information and tenant data on the client-side before it is needed. The browser container pre-loads and stores data that will be required during application execution, eliminating the need for repeated server requests. This reduces bandwidth consumption while ensuring data is readily available when needed, resolving the contradiction between energy loss and reliability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If client-side applications run without container isolation, then device resources are efficiently utilized, but security and isolation between applications are compromised

Engineering Contradiction:
ImprovesecurityVSAvoidcontainer isolation
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the client-side execution environment into isolated browser containers. Each container provides a separate, secure context for running client-side applications, preventing interference between different applications while maintaining efficient device resource utilization. This segmentation approach enhances security without significantly increasing overall device complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The browser container acts as an intermediary layer between the client-side application and the underlying device resources. This intermediary provides the necessary isolation and security controls while managing resource allocation efficiently, resolving the contradiction between security requirements and device complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If session-specific information is cached on client-side, then network requests are reduced, but security risks of storing sensitive data increase

Engineering Contradiction:
Improverequest efficiencyVSAvoidsecurity risks
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent implements local quality by making the browser container and its cached data user-specific and session-specific. Each container isolates sensitive information to a particular user context, ensuring that cached session information is only accessible within that specific container. This localized approach improves request efficiency while mitigating security risks by preventing unauthorized access to cached data.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12067134B2Secure data transfer via user-specific data containers
Publication Date: 2024.08.20 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12067134B2 patent drawing
  • US12067134B2 patent drawing
  • US12067134B2 patent drawing

AI summary

A processor may identify that one or more client-side applications have been initiated. The processor may identify a browser container. The processor may securely run the one or more client-side applications in the browser container. A website server may collect data that is to be transferred to a browser and sent back from the browser, and the browser container may be associated with the browser. The processor may permit a transfer and sending of the data between the website server and the browser. The transfer and sending of the data may include session specific information that is to be cached on a client-side.