Restricted Internet Application Execution via Containment Zone and Broker
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Applications interacting with the Internet face security risks due to malware and unauthorized access to system resources, which can compromise system performance and user data.
Innovation Solution
Executing applications in a restricted process with reduced privileges, using a containment zone for trusted data and a broker mechanism to manage access to sensitive areas, and employing a shim mechanism for third-party extensions to maintain compatibility and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If applications are executed with full privileges to access system resources, then functionality and user experience are improved, but security risks and system vulnerability increase
Solution Approach 1:
The patent segments the file system into restricted areas (containing sensitive system files and user data) and unrestricted areas. Applications running in restricted mode are granted access only to specific unrestricted areas, effectively dividing access permissions to balance functionality and security.
Solution Approach 2:
The patent introduces a broker mechanism as an intermediary between restricted applications and the file system. The broker mediates access requests, allowing applications to obtain necessary resources while preventing direct access to sensitive areas, thus maintaining both functionality and security.
2Reliability
If applications are restricted from accessing sensitive areas, then security is improved, but application functionality and user experience deteriorate
Solution Approach 1:
The broker acts as an intermediary that transparently handles access requests from restricted applications. Users experience no degradation in functionality because the broker automatically retrieves necessary resources from restricted areas on behalf of applications, maintaining ease of operation while preserving security.
Solution Approach 2:
The broker mechanism enables restricted applications to self-service by automatically obtaining necessary resources from restricted areas without requiring user intervention or compromising security. This maintains full application functionality while preserving the restricted execution model.
3Reliability
If a broker mechanism is introduced to manage access, then security control is improved, but system complexity increases
Solution Approach 1:
The broker mechanism is designed as a universal component that handles multiple types of access requests (file reads, writes, executions) through a single interface. This multi-functional design consolidates security control logic, managing access complexity rather than increasing it.
Solution Approach 2:
The broker automatically manages access control decisions without requiring complex configuration or user intervention. The system self-regulates access based on pre-defined policies, maintaining security control while minimizing the operational complexity burden on users and developers.
4Object-affected harmful factors
If restricted mode is enforced, then malware prevention is improved, but automated processes and scripting capability are reduced
Solution Approach 1:
The broker serves as an intermediary that automatically processes access requests from automated processes and scripts running in restricted mode. This maintains automation capability by allowing scripts to request necessary resources through the broker, while the broker's security checks prevent malicious automated actions.
Solution Approach 2:
Automated processes in restricted mode can self-service by submitting access requests to the broker, which automatically grants or denies access based on security policies. This maintains scripting and automation capabilities while enforcing malware protection through the broker's security enforcement.
Data Source
AI summary
In various embodiments, applications that are configured to interact with the Internet in some way are executed in a restricted process with a reduced privilege level that can prohibit the application from accessing portions of an associated computing device. For example, in some embodiments, the restricted process can prohibit applications from read and write access to portions of a system's computer-readable media, such as the hard disk, that contains administrative data and settings information and user data and settings. In these embodiments, a special portion of the disk, termed a “containment zone”, is designated and used by applications in this restricted process.