Browser Plug-in Phishing Detection via SSL and Address Lists
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing anti-phishing methods are ineffective against innovative phishing techniques, costly for large-scale deployment, or unable to cope with rapidly increasing fraudulent websites, particularly failing to authenticate secure data submissions in web browsers.
Innovation Solution
A web browser plug-in that detects data entry fields, verifies the authenticity of web addresses by checking against user-approved, embedded, or web-based lists, and ensures secure sites use SSL protocol, intercepting and allowing data transmission only if authentication is confirmed, with user query options for unauthenticated sites.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If website bookmark-based anti-phishing methods are used, then users are protected against known phishing sites, but they are ineffective against fraudulent web links on fake emails or embedded fraudulent login pages
Solution Approach 1:
The solution segments the anti-phishing protection into multiple independent verification layers: data entry field detection, SSL certificate verification, and multiple approved address list sources (user-approved, embedded, web-based). This segmentation allows each layer to address specific phishing vectors independently, making the system effective against diverse phishing techniques without relying on a single method
Solution Approach 2:
The browser plug-in serves multiple functions: it detects data entry fields, verifies SSL certificates, checks addresses against multiple approved lists, and provides user alerts. This multi-functional approach allows a single system to protect against various phishing techniques (fake emails, embedded pages, look-alike sites) simultaneously, resolving the contradiction between reliability and adaptability
2Ease of manufacture
If blacklists are used for anti-phishing, then implementation is simple, but they are unable to cope with the rapidly increasing fraudulent websites
Solution Approach 1:
The system performs preliminary verification by checking SSL certificates and cross-referencing with multiple approved address lists before allowing data submission. This preliminary action ensures that even newly created fraudulent sites without blacklist entries are blocked through SSL verification and multi-source address validation, maintaining both simplicity and effectiveness
Solution Approach 2:
The invention introduces SSL certificate verification and multiple approved address lists as intermediary verification layers between the user and the website. These intermediaries provide an additional layer of trust that doesn't rely solely on blacklists, enabling the system to handle rapidly increasing fraudulent sites while maintaining implementation simplicity through automated verification
3Reliability
If hardware token-based authentication is used, then security is enhanced, but it is very costly for mass distribution
Solution Approach 1:
The system replaces physical hardware tokens with a software-based browser plug-in that replicates the authentication function. This copying approach maintains the security functionality of token-based authentication while eliminating the costs associated with hardware manufacturing, distribution, and maintenance, enabling mass deployment without sacrificing security
Solution Approach 2:
The invention substitutes the mechanical hardware token system with a software-based solution running in the web browser. This substitution replaces physical authentication devices with digital verification mechanisms (SSL certificates, address list matching), achieving the same security enhancement at minimal cost for mass distribution
4Reliability
If SSL certificate verification is performed, then secure sites are authenticated, but additional verification steps may slow down data submission
Solution Approach 1:
The browser plug-in performs SSL certificate verification and address list matching in the background before the user attempts to submit data. This preliminary action ensures that when the user reaches the submission stage, authentication is already complete, minimizing perceived delay while maintaining high authentication accuracy
Data Source
AI summary
Redirection of user entered data to an unauthenticated website (“phishing”) is checked by, at redirection, detecting the presence of data entry fields in a user web page and, if any are present, authenticating the redirection address against lists of approved websites or the redirection web site certificate. If the new address is not authenticated, the user may still opt to be redirected.


