Blocking Google Chrome from logging into google (bookmark/settings/plugin sync)?
Suppose we'd like to block Google Chrome from authenticating to google for Bookmark/settings and (most problematically) plugin syncing.
We've seen a few instances where a plugin someone thought was awesome for their home use sneaks into the corp environment if they login to google with the browser itself.
For this client, allowing authentication to google services as web pages (mail.google.com docs.google.com and the like ) is something that needs to be allowed generally, but I'm looking to just block the scenario of users logging their browsers into the google cloud.
Anyone solved this use case? If not, I'll go to work with a policy trace and a few scenarios, but if the wheel is invented, I'm all ears!
Note also that logging into Chrome also makes it generate a lot of https://mtalk.google.com:5228 traffic if chat is enabled for that google account. If you have to block instant messaging in your environment, this sure causes a lot of noise in logs, which is another nice reason to block users from associating their user account to Chrome.