Third-Party Script Security via Domain Reputation Risk Scoring
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The integration of third-party scripts in webpages poses security risks due to the potential for malicious scripts to be hacked or compromised, compromising user data and security.
Innovation Solution
A method involving a computing device that detects attempts to load scripts from third-party domains, compiles a list of domains, identifies reputation scores, generates a risk score, and performs security actions to secure the network device from malicious scripts, including sandboxing or preventing execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If a webpage embeds a reference to a separate script controlled by a third-party, then the webpage can be smaller in size and the script can be cached by the browser for future use, but the webpage may inadvertently execute a malicious script once the webpage is loaded in a browser
Solution Approach 1:
The system performs preliminary actions by compiling a list of domains that host webpages embedding references to the script, identifying reputation scores for these domains, and generating a risk score for the script before the webpage is loaded in the browser. This advance assessment allows the system to determine whether the script is malicious prior to execution, preventing the harmful effect while maintaining the benefit of external script hosting.
Solution Approach 2:
The system introduces an intermediary security assessment mechanism between the webpage and the external script. By acting as a mediator that evaluates domain reputation and generates risk scores, the system filters out malicious scripts before they can execute in the browser, while still allowing legitimate scripts to be loaded. This intermediary layer resolves the contradiction by enabling external script hosting without directly exposing the browser to malicious content.
2Adaptability or versatility
If a separate script is controlled by a third-party, then the separate script can be updated and improved over time in a single location without requiring updates to any particular webpage, but there is always a possibility that the separate script may be hacked or otherwise compromised
Solution Approach 1:
The system implements feedback by continuously monitoring domain reputation scores and updating risk assessments for external scripts. When a third-party script is updated or compromised, the system detects changes in domain reputation and adjusts risk scores accordingly. This feedback mechanism maintains reliability by ensuring that updated scripts are重新evaluated for security risks while preserving the adaptability benefit of centralized script updates.
3Ease of operation
If the benefits of embedding a reference in a webpage to a separate script controlled by a third-party are weighed against the security risks, then the benefits may be outweighed by the security risks inherent in the use of the separate script
Solution Approach 1:
The system changes the parameter of risk assessment by introducing dynamic risk scoring based on domain reputation. Instead of treating all external scripts uniformly, the system evaluates each script's risk level by analyzing domain reputation scores and adjusts security measures accordingly. This parameter change allows the system to maintain ease of operation for low-risk scripts while applying stricter security controls to high-risk scripts, resolving the contradiction between convenience and security.
Data Source
AI summary
Securing a network device from a malicious embedded script hosted on a third-party domain. In one embodiment, a method may include detecting an attempt by a browser executing on a network device to load a webpage that embeds a reference to a script hosted on a third-party domain, compiling a list of domains that host webpages that embed references to the script hosted on the third-party domain, identifying reputation scores for the domains in the list of domains, generating a risk score for the script based on the identified reputation scores, determining that the script is malicious based on the generated risk score being above a threshold risk score, and, in response to determining that the script is malicious, performing a security action on the network device that secures the network device from the malicious script.