JS Proxy Layer for Realtime DOM Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional web browsers have limited APIs and controls over JavaScript (JS) access to the document object model (DOM) and browser APIs, compromising user data security and privacy, especially in online environments where malicious scripts can execute unchecked.
Innovation Solution
A system is implemented that integrates a proxy layer and cache management to manage browser execution, providing real-time permission and access control, employing JS level proxies/hooks to validate and restrict third-party script execution, and employing a caching layer to optimize performance and secure data access.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If JavaScript is allowed unrestricted access to DOM and browser APIs, then web functionality and compatibility are improved, but data security and privacy deteriorate
Solution Approach 1:
The patent introduces a proxy layer as an intermediary between JavaScript code and the DOM/browser APIs. This proxy layer intercepts all API calls, validates them against security policies, and selectively permits or blocks access. The proxy acts as a mediator that maintains the functional benefits of JS access while filtering out harmful operations, thus resolving the contradiction between functionality and security.
Solution Approach 2:
The patent segments the browser execution environment into distinct layers: a secure execution environment, a proxy layer for access control, and the original JavaScript code. This segmentation allows independent control of security policies without affecting the overall web functionality. The proxy layer can be configured to permit specific operations while blocking others, maintaining versatility where needed and security where required.
2Object-affected harmful factors
If a proxy layer is added to control JS access, then data security is improved, but system complexity increases
Solution Approach 1:
The proxy layer is designed to handle multiple functions through a single unified structure: it intercepts API calls, validates them against policies, logs access patterns, and controls execution permissions. By consolidating these functions into one multi-functional layer, the patent reduces the need for multiple separate security mechanisms, thereby limiting the increase in system complexity while maintaining comprehensive security.
3Object-affected harmful factors
If real-time access control is implemented, then data privacy is improved, but execution speed decreases
Solution Approach 1:
The system performs preliminary validation of JavaScript code and API access requests before execution occurs. Security policies are established in advance, and the proxy layer is pre-configured with allowed and blocked operations. This preliminary action eliminates the need for continuous real-time analysis during execution, reducing overhead while maintaining strong privacy protection through advance authorization.
4Adaptability or versatility
If third-party scripts are allowed to execute freely, then website functionality is improved, but vulnerability to malicious code increases
Solution Approach 1:
The patent implements a feedback mechanism where the proxy layer continuously monitors third-party script execution and reports access patterns to a control system. Based on this feedback, the system dynamically adjusts execution permissions, blocking suspicious operations while allowing legitimate functionality. This feedback loop enables the system to maintain reliability by identifying and preventing malicious code execution while preserving website functionality through adaptive control.
Data Source
AI summary
The system can be configured to execute a subset of “hooks” or “proxies,” to manage IS, DOM, or API execution. The subset of hooks or proxies are associated with known data access operations, known functions, etc., that target system accesses representing vulnerability or data accesses for sensitive information. For example, the subset leverage options available in conventional browsers to secure control as the system cannot recompile the end-user's browser in a real-time site scenario, nor force an extension installation. In such on-line environments, the system is configured to employ IS level proxies/hooks, that can be delivered, for example, by a IS tag, inline code, or a server-side templating solution. Based on execution of the real-time permission and access control, for example, via the IS level proxies/hooks, various embodiments are configured to provide real time alerts and restrictions on third party IS code, DOM requests, and APIs.


