Client-Side Domain Verification for Forged Website Detection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for identifying and preventing website forgery are ineffective in detecting initial attacks, allowing significant damage to occur before identification, as they rely on patterns of authorized accesses and can be easily defeated by copying entire target pages, including images, which eliminates log file evidence of requests from forged sites.
Innovation Solution
Embedding client-side executable domain identification code in the primary website's pages that determines the hosting domain and transmits unauthorized domain information to an authorized server, enabling the execution of countermeasures such as altering the page's appearance or functionality to prevent credential entry and providing fake credentials to thwart the site forger.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If web beacon images are used to identify forged sites by monitoring image requests in log files, then forged sites can be detected, but the method is easily defeated by copying the entire target page including all image files on the forger's own server, which eliminates log file evidence of requests from forged sites
Solution Approach 1:
The patent extracts the detection functionality from server-side log file monitoring to client-side executable code. By embedding domain identification code directly in the web page that executes on the user's browser, the detection capability is removed from the vulnerable server-side log analysis approach and placed in the client environment where it can autonomously verify domain authenticity without relying on image request patterns.
Solution Approach 2:
The patent introduces an intermediary domain identification code that acts as a mediator between the target website and the user's browser. This code serves as a trusted intermediary that verifies the actual hosting domain against the expected domain, bridging the gap between the user and the website authenticity verification without relying on indirect methods like image request monitoring.
2Reliability
If server-side log file monitoring is used to detect website forgery patterns, then some forged sites can be identified, but significant damage occurs before identification since the method cannot detect first-time attacks
Solution Approach 1:
The patent implements preliminary action by embedding domain identification code in the web page itself, which executes automatically when the page is loaded. This pre-positioned code performs domain verification at the moment of page access, eliminating the time delay inherent in server-side log analysis that occurs after the fact. The detection happens proactively before any damage can occur from credential theft.
Solution Approach 2:
The patent enables self-service detection where the client-side executable code autonomously performs domain verification without requiring server-side log analysis or external intervention. The code independently determines whether it is being executed from an authorized or unauthorized domain and takes appropriate action, making the detection system self-sufficient and immediately responsive to forgery attempts.
3Reliability
If client-side executable domain identification code is embedded in web pages to detect unauthorized domains, then forged sites can be identified in real-time, but the system complexity increases due to embedding and executing code in client devices
Solution Approach 1:
The patent applies universality by designing domain identification code that can be embedded in any web page and executed in any standard web browser. The code serves multiple functions: it automatically executes when the page loads, determines the actual hosting domain, compares it against authorized domains, and triggers appropriate responses. This multi-functional approach consolidates detection, verification, and response capabilities into a single universal code component.
Solution Approach 2:
The patent uses a lightweight executable code object that is embedded in the web page and executes temporarily in the client's browser memory. This disposable code performs its verification function and then terminates, leaving no permanent installation on the client device. The code is essentially discarded after execution, making the approach low-cost and avoiding complex persistent client-side software installations.
Data Source
AI summary
A system, a method, and computer program product identify a website that is a forgery of a primary website. Client side executable code is included in a page of the primary website, which page is copied in the forged website. The client side code, when executed by a client device, determines whether the domain from which the page is served is an authorized domain. Where the serving domain is not authorized, the client device is configured to alter the execute countermeasures against the forged website, such as altering operation of the forged page.