Webpage Security Script for Extension Content Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Browser extensions can abuse their power to modify webpages by injecting secondary content that may not originate from the webpage, potentially replacing original content and compromising user security, leading to malicious activities such as phishing or unwanted advertisements.

Innovation Solution

A security script and validation rules are sent with the webpage to the web browser, which monitors content changes and prevents unauthorized secondary content from being displayed by checking against authorized lists, and an observation program restores the document object model to its original state if unauthorized changes are detected.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If browser extensions are allowed to modify webpage content, then functionality and user interface enhancement are improved, but security and content integrity deteriorate

Engineering Contradiction:
Improvefunctionality enhancementVSAvoidcontent integrity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a security script as an intermediary between the browser extension and the webpage content. This script acts as a mediator that monitors and controls what modifications extensions can make to webpage content, allowing legitimate functionality while blocking malicious changes. The security script validates extension requests against a whitelist of authorized content, enabling safe content modification without compromising integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If browser extensions can inject secondary content, then user interface customization is improved, but security against malware deteriorates

Engineering Contradiction:
Improveinterface customizationVSAvoidmalware risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent implements preliminary action by pre-establishing a security script and validation rules before any extension content injection occurs. The system proactively defines what content is authorized (whitelist approach) and sets up monitoring mechanisms in advance. When an extension attempts to inject content, the pre-configured security script evaluates it against the established rules, preventing malicious content from being injected while allowing legitimate customization.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If extensions replace original webpage content, then advertising revenue is improved, but user trust and security deteriorate

Engineering Contradiction:
Improveadvertising revenueVSAvoiduser trust
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies local quality by allowing different treatment for different content regions on the webpage. The security script evaluates each content injection request individually against the validation rules, permitting authorized content (such as legitimate advertisements) in specific locations while blocking unauthorized replacements. This selective approach enables controlled content modification for revenue generation while maintaining user trust through consistent security enforcement.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS9954894B2Webpage security
Publication Date: 2018.04.24 MICROSOFT TECHNOLOGY LICENSING LLC
  • US9954894B2 patent drawing
  • US9954894B2 patent drawing
  • US9954894B2 patent drawing

AI summary

Aspects of the technology described herein allow webpages to maintain control over content displayed as part of the webpage when viewed on a browser. The technology described herein can send a security script and validation rules along with a webpage to a web browser. The web browser then runs the security script, which monitors content on the webpage. In one aspect, when an add-in attempts to display secondary content, the security script checks identification information associated with the secondary content against the validation rules, which lists authorized content. If the secondary content does not satisfy a validation rule, then the security script can prevent the browser from displaying the secondary content.