Anonymous Containers for Data Isolation and Privacy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The issue of information leaks and unauthorized access to personal data through various mechanisms, including user actions, social engineering, malware, and untrusted network resources, poses a significant challenge in maintaining data security without severely limiting the functionality of computing devices.
Innovation Solution
The implementation of anonymous containers, managed by a container manager, isolates applications from the host operating system, anonymizing configuration and settings data to prevent access to personal information, while allowing applications to function normally by providing spoofed or randomized data, thereby protecting user privacy and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network access is shut down to prevent information leaks, then data security is improved, but device functionality and employee productivity deteriorate
Solution Approach 1:
The patent segments the network access into different containers: trusted containers can access network resources freely, while untrusted containers are isolated and cannot access network resources. This segmentation allows the system to maintain security by preventing information leaks from untrusted applications while preserving productivity by allowing trusted applications to function normally with network access.
Solution Approach 2:
The patent introduces a container manager as an intermediary that mediates between applications and network resources. The container manager assigns network access permissions based on container trust levels, acting as a gatekeeper that allows trusted containers to access network resources while blocking untrusted containers, thus resolving the contradiction between security and productivity.
2Reliability
If limited network access is enabled to prevent access to untrusted resources, then data security is improved, but administration costs and device complexity increase
Solution Approach 1:
The patent implements self-service by allowing applications to automatically be assigned to trusted or untrusted containers based on their behavior and characteristics. The container manager autonomously makes decisions about network access permissions without requiring manual administration, thereby reducing administration costs and complexity while maintaining security.
Solution Approach 2:
The patent changes the parameter of network access permission based on container trust status. Trusted containers receive full network access permission, while untrusted containers receive restricted permission. This parameter change approach simplifies administration by using clear binary permissions rather than complex access control lists, reducing both administration complexity and device management overhead.
3Productivity
If applications are allowed to access network resources, then functionality and productivity are improved, but risk of information leaks and malware attacks increases
Solution Approach 1:
The patent segments applications into trusted and untrusted containers, applying different network access policies to each segment. Trusted containers can access network resources for legitimate business functions, while untrusted containers are isolated, preventing information leaks and malware attacks from spreading to the network, thus resolving the contradiction between functionality and security risk.
Solution Approach 2:
The patent applies preliminary anti-action by pre-classifying applications into trusted or untrusted categories before they access network resources. The container manager proactively assigns appropriate access permissions based on this pre-classification, preventing potential information leaks from untrusted applications before they can occur, while allowing trusted applications to function normally.
Data Source
AI summary
Anonymous containers are discussed herein. An operating system running on a computing device, also referred to herein as a host operating system running on a host device, prevents an application from accessing personal information (e.g., user information or corporate information) by activating an anonymous container that is isolated from the host operating system. In order to create and activate the anonymous container, a container manager anonymizes the configuration and settings data of the host operating system, and injects the anonymous configuration and settings data into the anonymous container. Such anonymous configuration and settings data may include, by way of example and not limitation, application data, machine configuration data, and user settings data. The host operating system then allows the application to run in the anonymous container.