Plug-in synchronization method and device for remote isolation browser

Abstract

The invention provides a plug-in synchronization method and device for a remote isolation browser, and the method comprises the steps: setting a suspension point on a page of the isolation browser of a client, and enabling the client to send a click event to a server when a user clicks the suspension point, and requesting the remote execution of plug-in operation; the server side receives the request and executes plug-in operation, a plug-in popup window is analyzed into a DOM structure at the server side, and the server side sends the DOM structure to the client side; the client receives the DOM structure and renders the DOM structure to obtain a plug-in operation window, the client sends a click event and a mouse position to the server, and the server executes corresponding operation according to the click event and the mouse position and updates the plug-in state to the client through the DOM technology, so that a user can use the plug-in through an isolation browser, and the user experience is improved. And the safety is ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of remote isolated browsers, and in particular to a plug-in synchronization method and device for a remote isolated browser. Background Art

[0002] In order to improve the security of browsers in the prior art, remote browser isolation (RBI) technology is usually used. This technology isolates the user terminal from malicious web pages by moving the browser's execution environment to a cloud server, thereby improving the security of the browser.

[0003] However, remote browser technology is implemented through DOM reconstruction, which has an obvious shortcoming: it is impossible to synchronize the browser plug-in interaction on the server to the client; because the browser plug-in click button belongs to the outer layer of the browser, the content of this part cannot be directly fed back to the client through DOM reconstruction. Therefore, users cannot use the browser plug-in normally in the remote isolated browser, affecting the comprehensiveness of its functions. Summary of the invention

[0004] The technical problem to be solved by the present invention is to provide a plug-in synchronization method and device for a remote isolated browser, which introduces a two-way synchronous interaction mechanism between a floating point and a plug-in pop-up window on the client, thereby solving the problem that the existing remote isolated browser cannot synchronize plug-ins. Users can fully use the plug-in functions through the remote isolated browser while ensuring the security and interactivity of the system.

[0005] In a first aspect, the present invention provides a plug-in synchronization method for a remote isolated browser, comprising the following steps:

[0006] Step 1: Set a floating point on the page of the isolated browser of the client. When the user clicks the floating point, the client sends a click event to the server to request remote execution of the plug-in operation.

[0007] Step 2: The server receives the request and executes the plug-in operation. The plug-in pop-up window is parsed into a DOM structure on the server, and the server sends the DOM structure to the client.

[0008] Step 3: The client receives the DOM structure and renders it to obtain the plug-in operation window. The client sends the click event and the mouse position to the server. The server performs corresponding operations based on the click event and the mouse position, and updates the plug-in status to the client through DOM technology.

[0009] In a second aspect, the present invention provides a plug-in synchronization device for a remote isolated browser, comprising:

[0010] The plug-in request module sets a floating point on the page of the isolated browser of the client. When the user clicks the floating point, the client sends a click event to the server to request remote execution of the plug-in operation;

[0011] Receiving and processing module: the server receives the request and executes the plug-in operation. The plug-in pop-up window is parsed into a DOM structure on the server, and the server sends the DOM structure to the client;

[0012] Synchronization module, the client receives the DOM structure and renders it to obtain the plug-in operation window. The client sends the click event and the mouse position to the server. The server performs corresponding operations based on the click event and the mouse position, and updates the plug-in status to the client through DOM technology.

[0013] One or more technical solutions provided by the present invention have at least the following technical effects or advantages:

[0014] The present invention constructs a suspension point in the upper right corner of the client browser (the icon of the suspension point corresponds to the plug-in icon). When the user clicks the suspension point, the remote server executes the click operation of the plug-in and renders the pop-up window of the plug-in (as the DOM structure of the web page) below the client suspension point, thereby realizing two-way interaction of the plug-in, which greatly facilitates user use.

[0015] The present invention performs an independent secondary detection on the server side, replaces all URLs in the DOM with safe domain names, completes DOM reconstruction on the server side, confirms that the reconstructed page is risk-free, and then sends it to the client for display. At the same time, a self-developed security protection SDK is deployed on the client side to intercept any JavaScript or XHR request that may be executed on the client side, thereby avoiding security issues that may be caused by existing DOM reconstruction technology and ensuring that the user experience is consistent with the original website.

[0016] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented according to the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the specific implementation methods of the present invention are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The present invention will be further described below in conjunction with embodiments with reference to the accompanying drawings.

[0018] Figure 1 is a flow chart of the method in Embodiment 1 of the present invention;

[0019] Figure 2 It is a schematic diagram of the structure of the device in the second embodiment of the present invention. DETAILED DESCRIPTION

[0020] The embodiment of the present application solves the problem that the existing remote isolated browser cannot synchronize plug-in interaction by providing a plug-in synchronization method and device for a remote isolated browser. The present invention constructs a floating point in the upper right corner of the client browser (the icon of the floating point corresponds to the plug-in icon). When the user clicks the floating point, the remote server executes the click operation of the plug-in and renders the pop-up window of the plug-in (as the DOM structure of the web page) below the client floating point, thereby realizing two-way interaction of the plug-in.

[0021] The overall idea of ​​the technical solution in the embodiments of this application is as follows:

[0022] Server-side implementation steps:

[0023] 1. Capture plug-in events: In the browser of the remote server, when it is detected that the client user clicks the plug-in icon (floating point), the server captures the user operation event through JavaScript.

[0024] 2. Execute plug-in operations: After capturing the user's click event, the server triggers the corresponding action of the plug-in (such as displaying a pop-up window) by simulating the click operation of the browser plug-in.

[0025] 3. Plug-in pop-up window DOM reconstruction: The plug-in pop-up window is parsed into an HTML DOM structure on the server side, and the server transmits the DOM structure to the client through a secure and encrypted communication channel.

[0026] 4. Plug-in status synchronization: During the entire interaction process, the server regularly synchronizes the status of the plug-in (such as opening, closing, data update, etc.) to the client to ensure the real-time nature of the interaction.

[0027] Server-side core sample code:

[0028]

[0029]

[0030] Client implementation steps:

[0031] 1. Create a floating point: Create a floating point in the upper right corner of the client browser. The icon of the floating point corresponds to the icon of the plug-in. Users can click the floating point to trigger the plug-in operation.

[0032] 2. Capture click events: When the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation.

[0033] 3. Receive and render the plug-in pop-up window: The client receives the plug-in pop-up window DOM data from the server and renders it below the floating point to simulate the interaction of the plug-in pop-up window.

[0034] 4. Interactive feedback: When the user performs a plug-in pop-up operation on the client, the operation feedback is sent to the server, and the server updates and synchronizes the plug-in status based on the operation.

[0035] Client core sample code:

[0036] / / 1. Create a floating point

[0037] function createFloatingButton(pluginId,pluginIcon){

[0038] let floatingButton=document.createElement('div');

[0039] floatingButton.id='floating-'+pluginId;

[0040] floatingButton.style.position='fixed';

[0041] floatingButton.style.top='10px';

[0042] floatingButton.style.right='10px';

[0043] floatingButton.style.width='50px';

[0044] floatingButton.style.height='50px';

[0045] floatingButton.style.borderRadius='50%';

[0046] floatingButton.style.backgroundImage=`url(${pluginIcon})`;

[0047] floatingButton.style.cursor='pointer';

[0048] document.body.appendChild(floatingButton);

[0049] / / 2. Add click event

[0050] floatingButton.addEventListener('click',function(){

[0051] / / Send a click request to the server

[0052] sendClickEventToServer(pluginId);

[0053] });

[0054] }

[0055] / / 3. Receive and render the plug-in pop-up window

[0056] function renderPluginPopup(domData){

[0057] let popupContainer=document.createElement('div');

[0058] popupContainer.innerHTML=domData;

[0059] popupContainer.style.position='fixed';

[0060] popupContainer.style.top='60px';

[0061] popupContainer.style.right='10px';

[0062] popupContainer.style.width='300px';

[0063] popupContainer.style.height='400px';

[0064] document.body.appendChild(popupContainer);

[0065] }

[0066] / / 4. Send click event to the server

[0067] function sendClickEventToServer(pluginId){

[0068] / / Send click events via WebRTC or other secure channels

[0069] sendDataToServer({action:'click',pluginId:pluginId});

[0070] }.

[0071] Methods for remote browser isolation to achieve secure remote browsing include:

[0072] 1. Secondary detection and DOM reconstruction on the server

[0073] When a user requests a website, the remote isolated browser first performs a comprehensive inspection of the website through the server, intercepting and cleaning any potential malicious content. During this process, the server replaces all URLs in the DOM with pre-configured safe domain names. After completing these replacements, the server rebuilds the DOM structure, confirms that the reconstructed page is risk-free, and then sends the processed DOM to the client for display. This secondary detection mechanism effectively prevents potential security risks in the traditional DOM reconstruction process; risks include URL leakage and JavaScript code leakage. According to the pre-configured safe domain name, all URLs in the DOM structure are replaced with pre-configured safe domain names; and through DOM technology, JavaScript code can be intercepted; the code in the browser can be used to obtain whether the tag is a script. If it is a script, it is a JavaScript code leak.

[0074] 2. The bottom-line interception mechanism of the self-developed security protection SDK

[0075] The client uses a self-developed security protection SDK, which is a TypeScript SDK to further ensure security. The SDK is responsible for intercepting all JavaScript and XHR requests executed on the client side, preventing any unauthorized code from being executed on the user's device, and ensuring the isolation and security of the browser. The core module functions of the SDK include:

[0076] Monitoring module: used to monitor all JavaScript execution and XHR requests on web pages in real time. This module intercepts and analyzes each step of JavaScript execution and blocks operations that do not comply with security rules.

[0077] Interception module: When suspicious behavior is detected, the interception module will promptly block JavaScript execution or XHR requests and return error logs or warnings to ensure that harmful code is not executed.

[0078] Security log module: records all intercepted operations and detailed log information to help administrators conduct further analysis.

[0079] Custom rule module: Administrators can configure custom security rules to flexibly adjust the interception mechanism in different business scenarios.

[0080] Integration and extensibility: The SDK provides a flexible API that allows enterprise developers to integrate customized security policies and easily expand new functional modules.

[0081] Security protection SDK core code example:

[0082] class SecuritySDK{

[0083] private log: string[] = [];

[0084] constructor(){

[0085] this.init();

[0086] }

[0087] / **

[0088] * Initialize monitoring and interception mechanism

[0089] * /

[0090] private init(){

[0091] this.monitorJavaScriptExecution();

[0092] this.monitorXHRRequests();

[0093] this.monitorFetchRequests();

[0094] this.setupUserFeedback();

[0095] }

[0096] / **

[0097] * Monitor JavaScript execution to prevent unauthorized code from running

[0098] * /

[0099] private monitorJavaScriptExecution(){

[0100] const originalEval=window.eval;

[0101] window.eval = (script: string) => {

[0102] if (this.isUnsafeScript(script)) {

[0103] this.logEvent(`Blocked unsafe JavaScript execution: ${script}`);

[0104] this.showUserWarning('Blocked an unsafe script from executing.');

[0105] return;

[0106]

[0107]

[0108]

[0109]

[0110] * Allows customizing unsafe rules, such as unsafe scripts or domains

[0111] * /

[0112] public setCustomSecurityRules(unsafeScripts: string[], unsafeDomains: string[]) {

[0113] unsafeScripts.forEach(script => {

[0114] if (!this.isUnsafeScript(script)) {

[0115] this.logEvent(`Custom rule added for unsafe script: ${script}`);

[0116] }

[0117] });

[0118] unsafeDomains.forEach(domain => {

[0119] if(!this.isUnsafeURL(domain)){

[0120] this.logEvent(`Custom rule added for unsafe domain:${domain}`);

[0121] }

[0122] });

[0123] }

[0124] }

[0125] / / Start the SDK and apply the security policy

[0126] const sdk=new SecuritySDK();

[0127] sdk.setCustomSecurityRules(['alert("hack")',

[0128] 'console.log(document.cookie)'],['unsafe-domain.com']);

[0129] 3. Secure data transmission

[0130] The data transmission between the server and the client is carried out through an encrypted channel, and all transmitted data is encrypted to prevent it from being intercepted or tampered with during the transmission process. The specific encryption methods used include SSL / TLS protocol and encrypted DOM structure transmission method to ensure that the user's browsing behavior cannot be spied on by the outside world.

[0131] Embodiment 1

[0132] like Figure 1 As shown, this embodiment provides a plug-in synchronization method for a remote isolated browser, comprising the following steps:

[0133] Step 1: Set a floating point on the page of the isolated browser of the client. When the user clicks the floating point, the client sends a click event to the server to request remote execution of the plug-in operation.

[0134] Step 2: The server receives the request and executes the plug-in operation. The plug-in pop-up window is parsed into a DOM structure on the server, and the server sends the DOM structure to the client.

[0135] Step 3: The client receives the DOM structure and renders it to obtain the plug-in operation window. The client sends the click event and the mouse position to the server. The server performs corresponding operations based on the click event and the mouse position, and updates the plug-in status to the client through DOM technology.

[0136] In this embodiment, preferably, step 1 is specifically as follows: a floating point is set at a set position on the isolated browser of the client. When the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation. The icon of the floating point corresponds to the image of the plug-in.

[0137] In this embodiment, preferably, the step 1 is specifically as follows: the server reconstructs the DOM of the website according to the received user request website, obtains the first DOM structure, replaces the URL in the first DOM structure with the pre-configured domain name, and obtains the second DOM structure; the server reconstructs the second DOM structure, detects the reconstructed page, and if there is no risk, adds a suspension point in the second DOM structure and sends it to the client; if there is a risk, the reconstructed page is reconstructed again by DOM to obtain a third DOM structure, replaces the URL in the third DOM structure with the pre-configured domain name, and adds a suspension point in the third DOM structure to obtain a fourth DOM structure, and sends it to the client;

[0138] The client displays the page according to the received DOM structure, the floating point is displayed at the set position on the isolated browser of the client, and the icon of the floating point corresponds to the image of the plug-in; when the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation.

[0139] In this embodiment, preferably, the step 1 is specifically as follows: the server reconstructs the DOM of the website according to the received user request website, obtains the first DOM structure, replaces the URL in the first DOM structure with a pre-configured domain name, and obtains the second DOM structure;

[0140] A security protection SDK is set up; the security protection SDK is used to intercept all JavaScript executions and XHR requests of the client; and compare them with the set security rules. If they meet the requirements, the operation is allowed; if they do not meet the requirements, the operation is rejected;

[0141] The server reconstructs the second DOM structure and detects the reconstructed page. If there is no risk, a suspension point is added to the second DOM structure, and then it is sent to the client together with the security protection SDK. The client runs the security protection SDK and displays the page according to the second DOM structure. If there is a risk, the reconstructed page is reconstructed again to obtain a third DOM structure, and the URL with risk in the third DOM structure is replaced with a pre-configured domain name, and a suspension point is added to the third DOM structure to obtain a fourth DOM structure.

[0142] The fourth DOM structure and the security protection SDK are sent to the client, and the client runs the security protection SDK and displays the page according to the fourth DOM structure;

[0143] The floating point is displayed at a set position on the isolated browser of the client, and the icon of the floating point corresponds to the image of the plug-in; when the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation.

[0144] In this embodiment, preferably, the data transmission between the server and the client is carried out through an encrypted channel, and all data to be transmitted is processed in an encrypted manner before being sent, and the encrypted channel adopts the SSL / TLS protocol.

[0145] Based on the same inventive concept, the present application also provides a device corresponding to the method in Example 1, see Example 2 for details.

[0146] Embodiment 2

[0147] like Figure 2 As shown, in this embodiment, a plug-in synchronization device for a remote isolated browser is provided, including:

[0148] The plug-in request module sets a floating point on the page of the isolated browser of the client. When the user clicks the floating point, the client sends a click event to the server to request remote execution of the plug-in operation;

[0149] Receiving and processing module: the server receives the request and executes the plug-in operation. The plug-in pop-up window is parsed into a DOM structure on the server, and the server sends the DOM structure to the client;

[0150] Synchronization module, the client receives the DOM structure and renders it to obtain the plug-in operation window. The client sends the click event and the mouse position to the server. The server performs corresponding operations based on the click event and the mouse position, and updates the plug-in status to the client through DOM technology.

[0151] In this embodiment, preferably, the plug-in request module is specifically: a floating point is set at a set position on the isolated browser of the client, when the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation, and the icon of the floating point corresponds to the image of the plug-in.

[0152] In this embodiment, preferably, the plug-in request module is specifically as follows: the server reconstructs the DOM of the website according to the received user request website, obtains the first DOM structure, replaces the URL in the first DOM structure with a pre-configured domain name, and obtains the second DOM structure; the server reconstructs the second DOM structure, detects the reconstructed page, and if there is no risk, adds a suspension point in the second DOM structure and sends it to the client; if there is a risk, the reconstructed page is reconstructed again by DOM to obtain a third DOM structure, replaces the URL in the third DOM structure with a pre-configured domain name, and adds a suspension point in the third DOM structure to obtain a fourth DOM structure, and sends it to the client;

[0153] The client displays the page according to the received DOM structure, the floating point is displayed at the set position on the isolated browser of the client, and the icon of the floating point corresponds to the image of the plug-in; when the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation.

[0154] In this embodiment, preferably, the plug-in request module is specifically: the server reconstructs the DOM of the website according to the received user request website, obtains the first DOM structure, replaces the URL in the first DOM structure with a pre-configured domain name, and obtains the second DOM structure;

[0155] A security protection SDK is set up; the security protection SDK is used to intercept all JavaScript executions and XHR requests of the client; and compare them with the set security rules. If they meet the requirements, the operation is allowed; if they do not meet the requirements, the operation is rejected;

[0156] The server reconstructs the second DOM structure and detects the reconstructed page. If there is no risk, a suspension point is added to the second DOM structure, and then it is sent to the client together with the security protection SDK. The client runs the security protection SDK and displays the page according to the second DOM structure. If there is a risk, the reconstructed page is reconstructed again to obtain a third DOM structure, and the URL with risk in the third DOM structure is replaced with a pre-configured domain name, and a suspension point is added to the third DOM structure to obtain a fourth DOM structure.

[0157] The fourth DOM structure and the security protection SDK are sent to the client, and the client runs the security protection SDK and displays the page according to the fourth DOM structure;

[0158] The floating point is displayed at a set position on the isolated browser of the client, and the icon of the floating point corresponds to the image of the plug-in; when the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation.

[0159] In this embodiment, preferably, the data transmission between the server and the client is carried out through an encrypted channel, and all data to be transmitted is processed in an encrypted manner before being sent, and the encrypted channel adopts the SSL / TLS protocol.

[0160] Since the device introduced in the second embodiment of the present invention is a device used to implement the method of the first embodiment of the present invention, those skilled in the art can understand the specific structure and deformation of the device based on the method introduced in the first embodiment of the present invention, so it is not described here in detail. All devices used in the method of the first embodiment of the present invention belong to the scope of protection of the present invention.

[0161] The technical solution provided in the embodiments of the present application has at least the following technical effects or advantages:

[0162] The present invention constructs a suspension point in the upper right corner of the client browser (the icon of the suspension point corresponds to the plug-in icon). When the user clicks the suspension point, the remote server executes the click operation of the plug-in and renders the pop-up window of the plug-in (as the DOM structure of the web page) below the client suspension point, thereby realizing two-way interaction of the plug-in, which greatly facilitates user use.

[0163] The present invention performs an independent secondary detection on the server side, replaces all URLs in the DOM with safe domain names, completes DOM reconstruction on the server side, confirms that the reconstructed page is risk-free, and then sends it to the client for display. At the same time, a self-developed security protection SDK is deployed on the client side to intercept any JavaScript or XHR request that may be executed on the client side, thereby avoiding security issues that may be caused by existing DOM reconstruction technology and ensuring that the user experience is consistent with the original website.

[0164] Although the specific implementation modes of the present invention are described above, those skilled in the art should understand that the specific implementation modes described are only illustrative and are not intended to limit the scope of the present invention. Equivalent modifications and changes made by those skilled in the art in accordance with the spirit of the present invention should be included in the scope of protection of the claims of the present invention.

Claims

1. A plug-in synchronization method for a remote isolated browser, characterized in that: The steps include: Step 1: Set a floating point on the page of the isolated browser of the client. When the user clicks the floating point, the client sends a click event to the server to request remote execution of the plug-in operation. Step 2: The server receives the request and executes the plug-in operation. The plug-in pop-up window is parsed into a DOM structure on the server, and the server sends the DOM structure to the client. Step 3: The client receives the DOM structure and renders it to obtain the plug-in operation window. The client sends the click event and the mouse position to the server. The server performs corresponding operations based on the click event and the mouse position, and updates the plug-in status to the client through DOM technology.

2. A plug-in synchronization method for a remote isolated browser according to claim 1, characterized in that: The step 1 is specifically as follows: a floating point is set at a set position on the isolated browser of the client. When the user clicks the floating point, the client sends a click event to the server to request remote execution of the plug-in operation. The icon of the floating point corresponds to the image of the plug-in.

3. The plug-in synchronization method of a remote isolated browser according to claim 1, characterized in that: The step 1 is specifically as follows: the server performs DOM reconstruction on the website according to the received user request website, obtains a first DOM structure, replaces the URL in the first DOM structure with a pre-configured domain name, and obtains a second DOM structure; the server reconstructs the second DOM structure, detects the reconstructed page, and if there is no risk, adds a suspension point in the second DOM structure and sends it to the client; if there is a risk, the reconstructed page performs DOM reconstruction again to obtain a third DOM structure, replaces the URL in the third DOM structure with a pre-configured domain name, and adds a suspension point in the third DOM structure to obtain a fourth DOM structure, and sends it to the client; The client displays the page according to the received DOM structure, the floating point is displayed at a set position on the isolated browser of the client, and the icon of the floating point corresponds to the image of the plug-in; When the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation.

4. A plug-in synchronization method for a remote isolated browser according to claim 3, characterized in that: The step 1 specifically includes: the server reconstructs the DOM of the website according to the received user request website, obtains the first DOM structure, replaces the URL in the first DOM structure with a pre-configured domain name, and obtains the second DOM structure; A security protection SDK is set up; the security protection SDK is used to intercept all JavaScript executions and XHR requests of the client; and compare them with the set security rules. If they meet the requirements, the operation is allowed; if they do not meet the requirements, the operation is rejected; The server reconstructs the second DOM structure and detects the reconstructed page. If there is no risk, a suspension point is added to the second DOM structure, and then it is sent to the client together with the security protection SDK. The client runs the security protection SDK and displays the page according to the second DOM structure. If there is a risk, the reconstructed page is reconstructed again to obtain a third DOM structure, and the URL with risk in the third DOM structure is replaced with a pre-configured domain name, and a suspension point is added to the third DOM structure to obtain a fourth DOM structure. The fourth DOM structure and the security protection SDK are sent to the client, and the client runs the security protection SDK and displays the page according to the fourth DOM structure; The floating point is displayed at a set position on the isolated browser of the client, and the icon of the floating point corresponds to the image of the plug-in; When the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation.

5. The plug-in synchronization method of a remote isolated browser according to claim 1, characterized in that: The data transmission between the server and the client is carried out through an encrypted channel. All data to be transmitted is processed in an encrypted manner before being sent. The encrypted channel adopts the SSL / TLS protocol.

6. A plug-in synchronization device for a remote isolated browser, characterized in that: include: The plug-in request module sets a floating point on the page of the isolated browser of the client. When the user clicks the floating point, the client sends a click event to the server to request remote execution of the plug-in operation; Receiving and processing module: the server receives the request and executes the plug-in operation. The plug-in pop-up window is parsed into a DOM structure on the server, and the server sends the DOM structure to the client; Synchronization module, the client receives the DOM structure and renders it to obtain the plug-in operation window. The client sends the click event and the mouse position to the server. The server performs corresponding operations based on the click event and the mouse position, and updates the plug-in status to the client through DOM technology.

7. A plug-in synchronization device for a remote isolated browser according to claim 6, characterized in that: The plug-in request module specifically sets a floating point at a set position on the isolated browser of the client. When the user clicks the floating point, the client sends a click event to the server to request remote execution of the plug-in operation. The icon of the floating point corresponds to the image of the plug-in.

8. A plug-in synchronization device for a remote isolated browser according to claim 6, characterized in that: The plug-in request module is specifically as follows: the server performs DOM reconstruction on the website according to the received user request website, obtains the first DOM structure, replaces the URL in the first DOM structure with a pre-configured domain name, and obtains the second DOM structure; the server reconstructs the second DOM structure, detects the reconstructed page, and if there is no risk, adds a suspension point in the second DOM structure and sends it to the client; if there is a risk, the reconstructed page performs DOM reconstruction again to obtain a third DOM structure, replaces the URL in the third DOM structure with a pre-configured domain name, and adds a suspension point in the third DOM structure to obtain a fourth DOM structure, and sends it to the client; The client displays the page according to the received DOM structure, the floating point is displayed at a set position on the isolated browser of the client, and the icon of the floating point corresponds to the image of the plug-in; When the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation.

9. A plug-in synchronization device for a remote isolated browser according to claim 8, characterized in that: The plug-in request module is specifically as follows: the server end performs DOM reconstruction on the website according to the received user request website, obtains a first DOM structure, replaces the URL in the first DOM structure with a pre-configured domain name, and obtains a second DOM structure; A security protection SDK is set up; the security protection SDK is used to intercept all JavaScript executions and XHR requests of the client; and compare them with the set security rules. If they meet the requirements, the operation is allowed; if they do not meet the requirements, the operation is rejected; The server reconstructs the second DOM structure and detects the reconstructed page. If there is no risk, a suspension point is added to the second DOM structure, and then it is sent to the client together with the security protection SDK. The client runs the security protection SDK and displays the page according to the second DOM structure. If there is a risk, the reconstructed page is reconstructed again to obtain a third DOM structure, and the URL with risk in the third DOM structure is replaced with a pre-configured domain name, and a suspension point is added to the third DOM structure to obtain a fourth DOM structure. The fourth DOM structure and the security protection SDK are sent to the client, and the client runs the security protection SDK and displays the page according to the fourth DOM structure; The floating point is displayed at a set position on the isolated browser of the client, and the icon of the floating point corresponds to the image of the plug-in; When the user clicks the floating point, the client sends a click event to the server, requesting remote execution of the plug-in operation.

10. A plug-in synchronization device for a remote isolated browser according to claim 6, characterized in that: The data transmission between the server and the client is carried out through an encrypted channel. All data to be transmitted is processed in an encrypted manner before being sent. The encrypted channel adopts the SSL / TLS protocol.

Images