Google Adding Chrome Admin Policy to Uninstall Blacklisted Extensions – Digitalmunition




Cyber Attack | Data Breach Chrome Security

Published on April 6th, 2019 📆 | 3310 Views ⚑

0

Google Adding Chrome Admin Policy to Uninstall Blacklisted Extensions

Google is adding a new admin policy to Chrome that will automatically uninstall browser extensions that are blacklisted by administrators.

Currently, administrators can enable a policy called “Configure extension installation blacklist” to create a blacklist of Chrome extension. These blacklisted extensions are added as individual extension ids, and once added, will prevent managed users from installing the associated extensions.

To do this, Windows administrators can download Chrome’s policy templates and add them to the Group Policy Editor.  Once added, they will be able to configure various group polices such as the blacklist below.

Windows Configure extension installation blaclist Policy
Windows Configure extension installation blaclist Policy

While this policy prevents users from installing an extension, it does not do anything for those users who have already installed the extension. Due to this, administrators have been requesting a new group policy that will cause Chrome to remove any extension that is listed under the “Configure extension installation blacklist” policy.

Google agrees and have started working on a new Chrome policy called “Uninstall blacklisted extensions that will uninstall any extensions whose IDs have been blacklisted. In addition to removing the extensions, it will remove any associated local user data as well.

The full description of this new extension can be read below.

This will remove extensions appearing in the ExtensionInstallBlacklist and will purge local user data with it. Refer to the extensions privacy policy or data retention policy to understand what may happen with the user data that is not stored locally. 

When the policy is set to enabled, the extension (if already installed on a machine) will be removed from that machine in its entirety (including local user data). 

When the policy is set to disabled or left unset, the extension (if already installed on a machine and existing in the blacklist ExtensionInstallBlacklist) will be disabled on the machine and not uninstalled.

As this new policy has just started being developed, it is currently targeted for Chrome 75, which is heading to beta in May and expected to be released to the Stable channel in June.

Source link

Tagged with:



Leave a Reply

Your email address will not be published. Required fields are marked *


loading...