Browser Bookmark Risk Scanning via Server-Side Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for scanning and killing browser bookmarks are inefficient as they rely on outdated lists of risky web addresses, leading to low security and increased storage usage on terminal devices, as the lists are frequently updated and become large.
Innovation Solution
A method and system where a browser background server performs risk scanning and killing on bookmark web addresses, synchronizing with the browser client to ensure the list of risky web addresses is always up-to-date, eliminating the need for the client to store and update the list, thereby improving security and conserving storage space.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the browser client stores and updates the list of risky web addresses locally, then the scanning and killing can be performed offline, but the storage space of the terminal device is increasingly occupied and the list may become outdated
Solution Approach 1:
The patent extracts the list of risky web addresses from the browser client and stores it on the server instead. The browser client only maintains a minimal local cache for offline functionality, while the comprehensive and frequently updated list resides on the server, freeing up terminal device storage space while maintaining security effectiveness.
Solution Approach 2:
The patent introduces a server as an intermediary between the browser client and the list of risky web addresses. The server acts as a centralized storage and update mechanism, allowing multiple clients to access the latest list without each client needing to store and update the complete list locally, thus reducing storage requirements on terminal devices.
2Speed
If the browser client downloads and stores the list of risky web addresses in advance, then the scanning can be performed quickly, but the list becomes outdated and security effectiveness decreases
Solution Approach 1:
The patent implements preliminary action by having the browser client download and cache essential portions of the risky web address list in advance for offline scanning capability. Simultaneously, the system automatically updates the list on the server and synchronizes changes to clients when connected, ensuring both quick local scanning and up-to-date security information.
Solution Approach 2:
The patent implements feedback mechanisms where the server continuously updates the list of risky web addresses and notifies browser clients of changes. The system monitors new risky addresses, updates the central list, and pushes updates to clients, ensuring the scanning capability remains current without requiring complete re-downloads.
3Reliability
If the list of risky web addresses is frequently updated, then the security effectiveness is improved, but the synchronization and update process becomes more complex and consumes more resources
Solution Approach 1:
The server acts as a central intermediary that manages all updates to the list of risky web addresses. Instead of each browser client independently monitoring and updating the list (which would create complexity), the server consolidates update logic, validates new entries, and distributes updates to all clients, simplifying the overall system architecture while enabling frequent updates.
Solution Approach 2:
The server implements a universal update mechanism that serves multiple browser clients simultaneously. The same update process and list management logic handles updates for all connected clients, reducing redundancy and complexity compared to individual client-based update systems. The server performs multiple functions: storing the list, validating new entries, and distributing updates to all clients.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method for performing scanning and killing on browser bookmarks is disclosed. The method comprises: receiving, by a browser background server, a synchronization request including a user account and bookmark web addresses from a browser client; storing, by the browser back ground server, the bookmark web addresses corresponding to the user account; and receiving a cloud scanning and killing instruction including the user account form the browser client, performing risky scanning and killing on the bookmark web addresses corresponding to the user account, determining a risky web address, and feeding back a scanning and killing result including the risky web address to the browser client, by the browser background server. A system for performing scanning and killing on browser bookmarks is also disclosed. The solution can improve security of browser bookmarks, and save storage spaces of a terminal device where the browser client resides.