Enterprise browser plug-in execution permission data leakage prevention method and device

Abstract

The invention provides an enterprise browser plug-in execution permission data leakage prevention method and device, and the method comprises the steps: setting a black list and a white list, and forcibly installing a corresponding plug-in on an enterprise browser according to the content of the white list; according to the blacklist, forcibly unloading the corresponding plug-ins in the enterprise browser; the server configures a security application strategy, sends the security application strategy to the enterprise browser, and prohibits all plug-ins according to the security application strategy when the webpage enters the corresponding page; when the page jumps, all the plug-ins are started; configuring a security policy; the enterprise browser obtains the latest security policy from the server regularly; the enterprise browser writes the security policy into a registry of local equipment; and the enterprise browser executes the gpupdate / force command as a system administrator identity, and the security policy is forcibly updated, so that the data security of the enterprise browser is greatly improved.

Description

Technical Field

[0001] The present invention relates to the technical field of browser data security, and in particular to a method and device for preventing data leakage from execution permissions of enterprise browser plug-ins. Background Art

[0002] While Chrome browser plugins enhance browser functionality, they can also pose a threat to user security. Here are some key aspects of how Chrome plugins affect browser security:

[0003] 1. Permission request

[0004] Many Chrome extensions request extensive permissions when they are installed, such as accessing all websites, reading and modifying browser tabs, accessing storage, etc. These permissions enable the extension to perform a variety of operations, but also increase the risk of being exploited maliciously. More than half of the existing browser extensions have overly loose permission settings, which can lead to potential malicious behavior.

[0005] 2. Malware and data breaches

[0006] Some plug-ins may contain malicious code that can steal sensitive user information, such as passwords and credit card information. Malicious plug-ins can trick users into installing them by disguising themselves as legitimate apps, thereby performing inappropriate operations in the background. When installing plug-ins, if users do not carefully review their sources and permissions, they may install malicious plug-ins and expose their data to attackers.

[0007] 3. Security vulnerabilities

[0008] Outdated or unupdated plugins may contain known security vulnerabilities that can be exploited by hackers to attack the user's device. Regularly updating plugins is an important measure to prevent such risks, but many users may ignore this, leading to security risks.

[0009] 4. Social Engineering Attacks

[0010] Plugins can also become tools for social engineering attacks, where attackers gain the trust of users by disguising themselves as trusted extensions in order to conduct phishing attacks or other forms of fraud.

[0011] Therefore, it is difficult to control the permissions of existing plug-ins. Although Google reviews plug-ins when they are put on the store and requires plug-ins to state in a prominent position whether the plug-in itself reads private data, malicious plug-ins cannot be avoided. In addition, the website's web page permissions are insufficient and plug-ins cannot be controlled. Plug-ins can inject scripts into web pages. There is also a sandbox environment between plug-ins. Security plug-ins can only obtain a list of installed plug-ins, uninstall and disable plug-ins, and cannot control a certain permission in a fine-grained manner. In addition, the browser's security policy cannot be loaded automatically. During the update process, if the user is using the browser, its security policy cannot take effect, resulting in browser risks. Summary of the invention

[0012] The technical problem to be solved by the present invention is to provide a method and device for preventing data leakage of enterprise browser plug-in execution permissions, which is convenient for controlling plug-in permissions and ensuring that the user's enterprise browser is in a safe environment.

[0013] In a first aspect, the present invention provides a method for preventing data leakage from executing permissions of an enterprise browser plug-in, wherein the enterprise browser is based on a Chromium kernel and specifically comprises the following steps:

[0014] Step 1: Set a blacklist and a whitelist, and according to the content of the whitelist, forcibly install the corresponding plug-in on the enterprise browser; according to the blacklist, forcibly uninstall the corresponding plug-in in the enterprise browser;

[0015] Step 2: The server configures the security application policy and sends it to the enterprise browser. According to the security application policy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled;

[0016] Step 3, configure the ExtensionSettings security policy; the enterprise browser periodically obtains the latest security policy from the server; the enterprise browser writes the security policy into the registry of the local device; the enterprise browser executes the gpupdate / force command as a system administrator to force the update of the security policy.

[0017] In a second aspect, the present invention provides a device for preventing data leakage of enterprise browser plug-in execution permissions, wherein the enterprise browser is based on the Chromium kernel and comprises:

[0018] Setting a plug-in module, setting a blacklist and a whitelist, and forcibly installing a corresponding plug-in on the enterprise browser according to the content of the whitelist; forcibly uninstalling the corresponding plug-in in the enterprise browser according to the blacklist;

[0019] Security application module: The server configures the security application policy and sends it to the enterprise browser. According to the security application policy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled;

[0020] The security policy module configures the ExtensionSettings security policy; the enterprise browser periodically obtains the latest security policy from the server; the enterprise browser writes the security policy into the registry of the local device; the enterprise browser executes the gpupdate / force command as a system administrator to force the security policy to be updated.

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

[0022] Blacklists and whitelists are set up on the server so that the enterprise browser can clearly identify the plug-ins that can be installed and those that cannot be installed, which serves as the first line of defense. Security application policies are then configured on the server so that the behavior of the plug-ins can be guaranteed when the browser accesses specific pages, further making the browser more secure. Security policy configuration is then used to standardize the behavior of the plug-ins in the enterprise browser, allowing the server to conduct timely plug-in prevention and control. When a vulnerability in a plug-in is temporarily known, prevention and control can be carried out in a timely manner.

[0023] 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

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

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

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

[0027] The embodiments of the present application provide a method and device for preventing data leakage by using execution permissions of enterprise browser plug-ins, thereby solving the technical problem that browser plug-ins in the prior art cannot prevent and control, and ensuring the security of enterprise browser data.

[0028] The technical solution in the embodiment of the present application has the following general idea:

[0029] After starting the Enterprise Browser, it will instantiate the Chromium kernel and start running. After successful running, a new window will appear and the kernel will force the Enterprise Browser plug-in to be loaded into it.

[0030] 1. Rights Management Solution

[0031] Enterprise browser level: forced installation or uninstallation of plug-ins

[0032] By providing a blacklist or whitelist of plug-ins, you can control which plug-ins cannot be installed, or those that have already been installed will be forcibly uninstalled. This is specifically implemented by enterprise browsers. Second, at the application level:

[0033] 1. Define the security application (page) group in two ways:

[0034] (1) Domain name or specific URL

[0035] (2) Use AI models (multimodal) to identify interfaces, such as login interface, password change interface, payment interface, etc. This method can be used to respond to the revision of third-party application platforms. For example, the login interface URL of a certain platform was originally https: / / xxx.com / login, and after the revision, the URL path was changed to https: / / xxx.com / v1 / login.

[0036] 2. Set to disable all plug-ins (excluding the product's own plug-ins) when accessing a high-security application (page) group

[0037] (1) Get the installed plugin list code:

[0038] chrome.management.getAll(

[0039] callback:function / / callback function )

[0041] (2) Enable or disable plugin code:

[0042] chrome.management.setEnabled(

[0043] id: string, / / The plugin ID that needs to be enabled or disabled

[0044] enabled:boolean, / / Is it enabled?

[0045] callback:function / / callback function )

[0047] 3. Set the behavior of blocking plug-ins when accessing the application (page) group, including:

[0048] (1) Inject JS code

[0049] (2) Modify and view WebRequest / WebNavigation

[0050] (3) View and modify cookies

[0051] Plug-in level: configure Chrome's ExtensionSettings security policy;

[0052] 3. The security policy content is explained as follows:

[0053] 1. Specify which types of plug-ins are installed on the enterprise browser (allowed_types)

[0054] 2. Specify the installation source of the plug-in (install sources)

[0055] 3. Specify how to add the plug-in to the enterprise browser (installation_mode), for example: allow installation, force installation, etc.

[0056] 4. Specify the minimum version requirement of the plugin (minimum_version_required)

[0057] 5. Specify the plugin version update address (update_url)

[0058] 6. Specify that plugins are not allowed to interact with or modify these websites, including blocking JavaScript injection, cookie access, and web request modification (runtime_blocked_hosts)

[0059] 7. Specify that plugins are allowed to interact with or modify these websites, including blocking JavaScript injection, cookie access, and web request modification (runtime_allowed_hosts)

[0060] 8. Specify certain API permissions that the plugin is not allowed to execute (allowed_permissions)

[0061] Based on the above explanation, here is an example of a security policy:

[0062]

[0063]

[0064] Security policy loading scheme:

[0065] Administrators configure security policies through the management backend;

[0066] The plug-in periodically pulls the latest security policy from the management console;

[0067] After the plug-in pulls the latest security policy, it assembles it into a JSON that meets the requirements and sends it to the enterprise browser client;

[0068] The enterprise browser client writes the security policy into the registry;

[0069] The Enterprise Browser client runs the gpupdate / force command as a system administrator to force the update of the group policy.

[0070] 4. Verify that the policy is effective:

[0071] If the security policy is in effect, the specified third-party plug-in will throw an exception when executing the relevant permissions again, and the relevant error log will usually be output in the console of the developer tools (DevTools) of the enterprise browser;

[0072] When the Enterprise Browser client instantiates the Chromium kernel and runs it, it adds a startup parameter (--enable-experimental-extension-apis) to ensure that the Enterprise Browser plug-in can read the console output;

[0073] The Enterprise Browser plugin uses the following two APIs to read the console output:

[0074] chrome.experimental.devtools.console.getMessages(function callback);

[0075] chrome.experimental.devtools.console.onMessageAdded.addListener(function on callback).

[0076] This enterprise browser can be used by employees within the company to ensure the security of internal company data.

[0077] Embodiment 1

[0078] like Figure 1 As shown, this embodiment provides a method for preventing data leakage from executing permissions of enterprise browser plug-ins, wherein the enterprise browser is based on the Chromium kernel and specifically includes the following steps:

[0079] Step 1: Set a blacklist and a whitelist, and according to the content of the whitelist, forcibly install the corresponding plug-in on the enterprise browser; according to the blacklist, forcibly uninstall the corresponding plug-in in the enterprise browser; by sending the blacklist and the whitelist from the server, the plug-in prevention and control can be carried out in real time;

[0080] Step 2: The server configures the security application policy and sends it to the enterprise browser. According to the security application policy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled. The server sends the security application policy to ensure data security when accessing a specific website or page.

[0081] Step 3, configure the ExtensionSettings security policy; the enterprise browser periodically obtains the latest security policy from the server; the enterprise browser writes the security policy into the registry of the local device; the enterprise browser executes the gpupdate / force command as a system administrator to force the update of the security policy.

[0082] This embodiment preferably further includes step 4, when the enterprise browser instantiates the Chromium kernel and runs, adding a startup parameter --enable-experimental-extension-apis, so that the output content of the enterprise browser console can be read;

[0083] Verify whether the security policy is effective. Specifically, if the security policy is effective, when the designated third-party plug-in executes the corresponding permission again, an exception is thrown, and the relevant error log is output through the console in the developer tool of the enterprise browser;

[0084] The output related error log of the console is read by using the setting API, and the related error log is sent to the server; the setting API includes:

[0085] chrome.experimental.devtools.console.getMessages(function callback) and chrome.experimental.devtools.console.onMessageAdded.addListener(functioncallback);

[0086] The server determines whether the security policy is effective based on the relevant error log. If it is effective, no processing is performed; if it is not effective, the server sends the latest security policy to the enterprise browser to verify whether the security policy is effective again. If it is still not effective, the setting personnel are notified.

[0087] In this embodiment, preferably, the step 2 is specifically: the server configures a security application policy and sends the security application policy to the enterprise browser, wherein the security application policy includes a first application policy and a second application policy;

[0088] According to the first security application policy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled; the first security policy includes a first set domain name or a first set URL;

[0089] According to the second security application strategy, when the page enters the corresponding page, all plug-in setting behaviors are blocked, including: injecting JS code, modifying and viewing WebRequest / WebNavigation, and viewing and modifying Cookie; the second security policy includes the second set domain name or the second set URL.

[0090] In this embodiment, preferably, the step 2 is specifically: the server configures a security application policy, and sends the security application policy to the enterprise browser, wherein the security application policy includes a third application policy and a fourth application policy; the enterprise browser is provided with an AI multimodal model, and the AI ​​multimodal model is used to identify the interface type;

[0091] According to the third security application strategy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled; the third security strategy includes the third setting interface type;

[0092] According to the fourth security application strategy, when the page enters the corresponding page, all plug-in setting behaviors are blocked, including: injecting JS code, modifying and viewing WebRequest / WebNavigation, and viewing and modifying Cookie; the fourth security strategy includes the fourth setting interface type.

[0093] In this embodiment, preferably, the step 3 specifically includes: configuring the ExtensionSettings security policy; the enterprise browser periodically obtains the latest security policy from the server; the enterprise browser writes the security policy into the registry of the local device; the enterprise browser executes the gpupdate / force command as a system administrator to force the security policy to be updated;

[0094] The security policy includes:

[0095] Set the type of plug-ins installed on the enterprise browser;

[0096] Set the installation source of the plugin;

[0097] Set the plug-in installation method, including mandatory installation, allowed installation, and prohibited installation;

[0098] Set the minimum version of the plugin;

[0099] Set the plugin version update address;

[0100] Setting a first plug-in library, wherein the plug-ins in the first plug-in library are not allowed to interact with or modify a set website;

[0101] Setting a second plug-in library, wherein the plug-ins in the second plug-in library allow interaction with a set website or modification of the website, wherein the modification includes blocking JavaScript injection, Cookie access, and Web request modification;

[0102] A third plug-in library is set, and plug-ins in the third plug-in library are not allowed to execute set API permissions.

[0103] 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.

[0104] Embodiment 2

[0105] like Figure 2 As shown, in this embodiment, a device for preventing data leakage of enterprise browser plug-in execution permissions is provided, and the enterprise browser is based on the Chromium kernel and includes:

[0106] Setting a plug-in module, setting a blacklist and a whitelist, and forcibly installing a corresponding plug-in on the enterprise browser according to the content of the whitelist; forcibly uninstalling the corresponding plug-in in the enterprise browser according to the blacklist;

[0107] Security application module: The server configures the security application policy and sends it to the enterprise browser. According to the security application policy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled;

[0108] The security policy module configures the ExtensionSettings security policy; the enterprise browser periodically obtains the latest security policy from the server; the enterprise browser writes the security policy into the registry of the local device; the enterprise browser executes the gpupdate / force command as a system administrator to force the security policy to be updated.

[0109] In this embodiment, preferably, a policy verification module is further included. When the enterprise browser instantiates the Chromium kernel and runs, a startup parameter --enable-experimental-extension-apis is added to read the output content of the enterprise browser console;

[0110] Verify whether the security policy is effective. Specifically, if the security policy is effective, when the designated third-party plug-in executes the corresponding permission again, an exception is thrown, and the relevant error log is output through the console in the developer tool of the enterprise browser;

[0111] The output related error log of the console is read by using the setting API, and the related error log is sent to the server; the setting API includes:

[0112] chrome.experimental.devtools.console.getMessages(function callback) and chrome.experimental.devtools.console.onMessageAdded.addListener(functioncallback);

[0113] The server determines whether the security policy is effective based on the relevant error log. If it is effective, no processing is performed; if it is not effective, the server sends the latest security policy to the enterprise browser to verify whether the security policy is effective again. If it is still not effective, the setting personnel are notified.

[0114] In this embodiment, preferably, the security application module is specifically: the server configures a security application policy, and sends the security application policy to the enterprise browser, wherein the security application policy includes a first application policy and a second application policy;

[0115] According to the first security application policy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled; the first security policy includes a first set domain name or a first set URL;

[0116] According to the second security application strategy, when the page enters the corresponding page, all plug-in setting behaviors are blocked, including: injecting JS code, modifying and viewing WebRequest / WebNavigation, and viewing and modifying Cookie; the second security policy includes the second set domain name or the second set URL.

[0117] In this embodiment, preferably, the security application module is specifically: the server configures a security application policy, sends the security application policy to the enterprise browser, and the security application policy includes a third application policy and a fourth application policy; the enterprise browser is provided with an AI multimodal model, and the AI ​​multimodal model is used to identify the interface type;

[0118] According to the third security application strategy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled; the third security strategy includes the third setting interface type;

[0119] According to the fourth security application strategy, when the page enters the corresponding page, all plug-in setting behaviors are blocked, including: injecting JS code, modifying and viewing WebRequest / WebNavigation, and viewing and modifying Cookie; the fourth security strategy includes the fourth setting interface type.

[0120] In this embodiment, preferably, the security policy module specifically includes: configuring ExtensionSettings security policy; the enterprise browser periodically obtains the latest security policy from the server; the enterprise browser writes the security policy into the registry of the local device; the enterprise browser executes the gpupdate / force command as a system administrator to force the security policy to be updated;

[0121] The security policy includes:

[0122] Set the type of plug-ins installed on the enterprise browser;

[0123] Set the installation source of the plugin;

[0124] Set the plug-in installation method, including mandatory installation, allowed installation, and prohibited installation;

[0125] Set the minimum version of the plugin;

[0126] Set the plugin version update address;

[0127] Setting a first plug-in library, wherein the plug-ins in the first plug-in library are not allowed to interact with or modify a set website;

[0128] Setting a second plug-in library, wherein the plug-ins in the second plug-in library allow interaction with a set website or modification of the website, wherein the modification includes blocking JavaScript injection, Cookie access, and Web request modification;

[0129] A third plug-in library is set, and plug-ins in the third plug-in library are not allowed to execute set API permissions.

[0130] 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.

[0131] 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 method for preventing data leakage by using execution permissions of enterprise browser plug-ins, characterized in that: The enterprise browser is based on the Chromium kernel and specifically includes the following steps: Step 1: Set a blacklist and a whitelist, and according to the content of the whitelist, forcibly install the corresponding plug-in on the enterprise browser; according to the blacklist, forcibly uninstall the corresponding plug-in in the enterprise browser; Step 2: The server configures the security application policy and sends it to the enterprise browser. According to the security application policy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled; Step 3, configure the ExtensionSettings security policy; the enterprise browser periodically obtains the latest security policy from the server; the enterprise browser writes the security policy into the registry of the local device; the enterprise browser executes the gpupdate / force command as a system administrator to force the security policy to be updated.

2. According to claim 1, a method for preventing data leakage of enterprise browser plug-in execution permissions is characterized by: The step also includes step 4, when the enterprise browser instantiates the Chromium kernel and runs, adding the startup parameter --enable-experimental-extension-apis, so that the output content of the enterprise browser console can be read; Verify whether the security policy is effective. Specifically, if the security policy is effective, when the designated third-party plug-in executes the corresponding permission again, an exception is thrown, and the relevant error log is output through the console in the developer tool of the enterprise browser; Read the console output related error log by using the setting API, and send the related error log to the server; The configuration API includes: chrome.experimental.devtools.console.getMessages(function callback) and chrome.experimental.devtools.console.onMessageAdded.addListener(functioncallback); The server determines whether the security policy is effective based on the relevant error log. If it is effective, no processing is performed; if it is not effective, the server sends the latest security policy to the enterprise browser to verify whether the security policy is effective again. If it is still not effective, the setting personnel are notified.

3. The method for preventing data leakage of enterprise browser plug-in execution permissions according to claim 1, characterized in that: The step 2 specifically includes: the server configures a security application policy and sends the security application policy to the enterprise browser, wherein the security application policy includes a first application policy and a second application policy; According to the first security application policy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled; the first security policy includes a first set domain name or a first set URL; According to the second security application strategy, when the page enters the corresponding page, all plug-in setting behaviors are blocked, including: injecting JS code, modifying and viewing WebRequest / WebNavigation, and viewing and modifying Cookies; The second security policy includes a second set domain name or a second set URL.

4. The method for preventing data leakage of enterprise browser plug-in execution permissions according to claim 1, characterized in that: The step 2 is specifically as follows: the server configures a security application policy, and sends the security application policy to the enterprise browser, wherein the security application policy includes a third application policy and a fourth application policy; the enterprise browser is provided with an AI multimodal model, and the AI ​​multimodal model is used to identify the interface type; According to the third security application strategy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled; The third setting interface type included in the third security policy; According to the fourth security application strategy, when the page enters the corresponding page, all plug-in settings are blocked, including: injecting JS code, modifying and viewing WebRequest / WebNavigation, and viewing and modifying Cookies; The fourth security policy includes a fourth setting interface type.

5. The method for preventing data leakage of enterprise browser plug-in execution permissions according to claim 1, characterized in that: The step 3 specifically includes: configuring the ExtensionSettings security policy; the enterprise browser periodically obtains the latest security policy from the server; the enterprise browser writes the security policy into the registry of the local device; the enterprise browser executes the gpupdate / force command as a system administrator to force the security policy to be updated; The security policy includes: Set the type of plug-ins installed on the enterprise browser; Set the installation source of the plugin; Set the plug-in installation method, including mandatory installation, allowed installation, and prohibited installation; Set the minimum version of the plugin; Set the plugin version update address; Setting a first plug-in library, wherein the plug-ins in the first plug-in library are not allowed to interact with or modify a set website; Setting a second plug-in library, wherein the plug-ins in the second plug-in library allow interaction with a set website or modification of the website, wherein the modification includes blocking JavaScript injection, Cookie access, and Web request modification; A third plug-in library is set, and plug-ins in the third plug-in library are not allowed to execute set API permissions.

6. An enterprise browser plug-in execution permission prevention data leakage device, characterized by: The enterprise browser is based on the Chromium kernel and includes: Setting a plug-in module, setting a blacklist and a whitelist, and forcibly installing a corresponding plug-in on the enterprise browser according to the content of the whitelist; forcibly uninstalling the corresponding plug-in in the enterprise browser according to the blacklist; Security application module: The server configures the security application policy and sends it to the enterprise browser. According to the security application policy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled; The security policy module configures the ExtensionSettings security policy; the enterprise browser periodically obtains the latest security policy from the server; the enterprise browser writes the security policy into the registry of the local device; the enterprise browser executes the gpupdate / force command as a system administrator to force the security policy to be updated.

7. The device for preventing data leakage of enterprise browser plug-in execution permissions according to claim 6, characterized in that: It also includes a policy verification module. When the enterprise browser instantiates the Chromium kernel and runs, it adds the startup parameter --enable-experimental-extension-apis to read the output content of the enterprise browser console; Verify whether the security policy is effective. Specifically, if the security policy is effective, when the designated third-party plug-in executes the corresponding permission again, an exception is thrown, and the relevant error log is output through the console in the developer tool of the enterprise browser; Read the console output related error log by using the setting API, and send the related error log to the server; The configuration API includes: chrome.experimental.devtools.console.getMessages(function callback) and chrome.experimental.devtools.console.onMessageAdded.addListener(functioncallback); The server determines whether the security policy is effective based on the relevant error log. If it is effective, no processing is performed; if it is not effective, the server sends the latest security policy to the enterprise browser to verify whether the security policy is effective again. If it is still not effective, the setting personnel are notified.

8. The device for preventing data leakage of enterprise browser plug-in execution permissions according to claim 6, characterized in that: The security application module is specifically: the server configures a security application policy and sends the security application policy to the enterprise browser, wherein the security application policy includes a first application policy and a second application policy; According to the first security application policy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled; the first security policy includes a first set domain name or a first set URL; According to the second security application strategy, when the page enters the corresponding page, all plug-in setting behaviors are blocked, including: injecting JS code, modifying and viewing WebRequest / WebNavigation, and viewing and modifying Cookies; The second security policy includes a second set domain name or a second set URL.

9. The device for preventing data leakage of enterprise browser plug-in execution permissions according to claim 6, characterized in that: The security application module is specifically: the server configures a security application policy, and sends the security application policy to the enterprise browser, wherein the security application policy includes a third application policy and a fourth application policy; the enterprise browser is provided with an AI multimodal model, and the AI ​​multimodal model is used to identify the interface type; According to the third security application strategy, when the web page enters the corresponding page, all plug-ins are disabled; when the page jumps, all plug-ins are enabled; The third setting interface type included in the third security policy; According to the fourth security application strategy, when the page enters the corresponding page, all plug-in settings are blocked, including: injecting JS code, modifying and viewing WebRequest / WebNavigation, and viewing and modifying Cookies; The fourth security policy includes a fourth setting interface type.

10. The device for preventing data leakage of enterprise browser plug-in execution authority according to claim 6, characterized in that: The security policy module specifically includes: configuring the ExtensionSettings security policy; the enterprise browser periodically obtains the latest security policy from the server; the enterprise browser writes the security policy into the registry of the local device; the enterprise browser executes the gpupdate / force command as a system administrator to force the security policy to be updated; The security policy includes: Set the type of plug-ins installed on the enterprise browser; Set the installation source of the plugin; Set the plug-in installation method, including mandatory installation, allowed installation, and prohibited installation; Set the minimum version of the plugin; Set the plugin version update address; Setting a first plug-in library, wherein the plug-ins in the first plug-in library are not allowed to interact with or modify a set website; Setting a second plug-in library, wherein the plug-ins in the second plug-in library allow interaction with a set website or modification of the website, wherein the modification includes blocking JavaScript injection, Cookie access, and Web request modification; A third plug-in library is set, and plug-ins in the third plug-in library are not allowed to execute set API permissions.

Images