Supervisory Script Mitigating Malicious Client-Side Scripts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Client-side scripts in client-server architectures are vulnerable to malicious attacks, making it challenging to maintain a high-performance, highly available, and secure environment as they can be compromised to gather sensitive user information without detection.
Innovation Solution
Implementing a supervisory script that loads before other scripts, which collects and analyzes information about script interactions, identifies potential malicious activities, and overrides architected APIs to mitigate threats by blocking unauthorized data access and network requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If client-side scripts are used to reduce processing load and improve responsiveness, then system performance and user experience are improved, but security vulnerability increases as scripts can be compromised by attackers
Solution Approach 1:
The patent introduces a supervisory script as an intermediary layer between the client environment and other scripts. This supervisory script monitors and controls the execution of client-side scripts, allowing performance benefits to be maintained while security risks are mitigated through centralized oversight and intervention capabilities.
Solution Approach 2:
The supervisory script is loaded and executed before other client-side scripts to establish security controls in advance. By performing preliminary actions such as setting up monitoring hooks and defining execution policies before malicious scripts can execute, the system prevents security breaches while maintaining script functionality.
2Reliability
If supervisory scripts are implemented to detect and mitigate malicious activities, then security is improved, but system complexity increases
Solution Approach 1:
The supervisory script is designed to perform multiple functions within a single component: monitoring script execution, detecting malicious activities, enforcing security policies, and controlling script behavior. This multi-functionality reduces the need for separate security mechanisms and simplifies the overall system architecture while maintaining comprehensive security.
3Reliability
If supervisory scripts override architected APIs to block unauthorized access, then security is improved, but ease of operation deteriorates due to modified API behavior
Solution Approach 1:
The supervisory script applies security controls selectively to specific API calls and script operations rather than uniformly overriding all API behavior. By implementing local quality control where security interventions are applied only when suspicious activities are detected, the system maintains security while preserving normal API functionality and ease of operation for legitimate scripts.
Data Source
AI summary
Technology related to detecting and/or mitigating malicious client-side scripts is disclosed. In one example, a method includes sending a request for a page of a client application. In response to the request for the page, the page and a supervisory script of the page are received. The supervisory script of the page of the client application can be executed within a client environment. The supervisory script can override an operation associated with an architected application programming interface (API) of the client environment. During rendering of the page, a call to the architected API of the client environment can be serviced by performing a modified operation that is different than the architected operation associated with the architected API.