SEP 14.3 RU2 and above - Chrome Browser Extensions

[Randal Hendrix]

Has anyone determined how to turn off chrome browser extensions AND not get the Browser Intrusion Prevention is malfunctioning message on the SEP client?

When we configure group policy to not allow Chrome Browser Extension to be installed the client eventually comes back with the status "Browser Intrustion Prevention is malfunctioning........"

[atb86]

Hi,

You need to upgrade to SEPM 14.3 RU5 (Just the manager), as the Chrome Browser Extension now unloads when you uncheck Browser Intrusion Prevention.

It's documented here, https://knowledge.broadcom.com/external/article?articleId=226741.

"NOTE: The above change is only for cloud enrolled SES clients. SEP clients managed with on-premises SEPM will include this feature in version 14.3 RU5 (only the manager needs be updated to RU5). Until then, disabling Browser Intrusion Prevention in SEP policy still requires the extension to be installed - it is just put into pass-through mode - and to prevent this error you must allow its installation or disable/withdraw the SEP IPS policy entirely."

[Randal Hendrix]

Thanks for the info.

We have already upgraded SEPM to 14.3 RU5.  I have read about disabling the Browser Intrusion Prevention option and I'm not sure I like that.

[atb86]

I'm not sure i understand why this is a problem if you want to use it then?

[Tal Fisher]

Instead of disabling it, go ahead and enable it to NOT get the malfuction message. Installing the Endpoint Protection Chrome Browser Extension using an Active Directory Group Policy Object (broadcom.com)

[Randal Hendrix]

Have you successfully done this?

[testerics]

I think this activation procedure for Chrome Browser Extensions using AD policy and registry it is a proof of incompetence of Broadcom.
Why we need to modify a lot of thinks to be able to make the product to work well? We are already paying for licenses, please make your product to function without our intervention at this level!!
Thanks!

[atb86]

You need to conform to the rules set by Google and Microsoft in this case. Can you ellaborate on this a bit more @testerics?​