SSL Certificate Validation via Local Remote Cache Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users are vulnerable to malicious redirects and fraudulent SSL certificates due to existing security protocols failing to detect DNS compromises and phishing attacks, which can lead to unauthorized access and credential theft.
Innovation Solution
A method that intercepts SSL certificates, compares certificate information with locally and remotely stored data, and takes protective action if the certificate is not verified, ensuring the authenticity of the SSL certificate by querying trusted sources and updating local caches for verification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If SSL certificate validation is performed using only browser-stored certificate authorities, then the validation process is simple and fast, but malicious redirects and fraudulent certificates are not detected
Solution Approach 1:
The system performs preliminary certificate validation by comparing the SSL certificate against previously stored certificate information from the same domain, before allowing the connection to proceed. This advance check detects malicious redirects and fraudulent certificates that would otherwise bypass browser security.
Solution Approach 2:
The patent introduces an intermediary validation layer that compares SSL certificates against historical certificate data stored locally and remotely. This intermediary system acts as an additional security checkpoint between the browser's basic validation and the actual connection, detecting phishing attempts without requiring complete system redesign.
2Measurement precision
If certificate information is verified against remote trusted sources, then detection accuracy improves, but validation time and network dependency increase
Solution Approach 1:
Certificate information from trusted remote sources is pre-fetched and stored in a local cache during legitimate connections. When a connection is established, the system first compares the SSL certificate against this pre-stored local cache data, providing fast verification without requiring real-time network access for every check.
Solution Approach 2:
The system implements a hierarchical verification approach where the most frequently accessed certificate validation data is stored locally with high availability, while remote sources serve as backup for less common cases. This localizes the verification process for common scenarios, reducing network dependency and validation time.
3Productivity
If local cache of certificate information is maintained, then verification speed improves, but cache updates and synchronization complexity increase
Solution Approach 1:
The local certificate cache is updated periodically during legitimate SSL connections to the same domain. When a connection is established, the system automatically refreshes the cached certificate information, ensuring the local store remains current without requiring manual intervention or complex synchronization protocols.
Solution Approach 2:
The certificate cache automatically updates itself during normal SSL handshakes. When the browser establishes a legitimate connection, the system captures and stores the certificate information locally, making the cache self-maintaining. This eliminates the need for separate update mechanisms or complex synchronization with remote sources.
Data Source
AI summary
Certificate information associated with a received certificate, such as a Secure Sockets Layer (SSL) certificate is stored in a trusted local cache and/or in one or more remote trusted sources, such as a single remote trusted source and/or a trusted peer network. When a site certificate is received on a host computer system, certificate information associated with the received site certificate is obtained and compared with the stored certificate information to determine whether or not the site certificate indicates malicious activity, such as a malicious DNS redirection or a fraudulent local certificate. When a site certificate is not found indicative of malicious activity, the site certificate is released. Alternatively, when a site certificates is found indicative of malicious activity protective action is taken. In some embodiments, a user's log-in credentials are automatically obtained from a trusted local cache and automatically submitted to a web site.