Application Control Browser Extensions - not being blocked?

Hello Cache,

so in your policy Enable on-access scanning is set, Detect but allow to run is not, and some (but not all) of the applications of type Browser plug-in are in the Blocked list?
Which browser(s) do you use and which plug-ins should be blocked? With don't appear to be [blocked] you mean they are actually running, or you don't get the expected alert? picking up the Chrome variant as a PUP - I assume that a PUA detection has precedence over Application Control (PUA detection and Application Control might "overlap" to some extent). Do you get a specific detection or a generic?

Christian

Hi Christian

That's right.

I've tried in both Firefox and Chrome to block the BrowSec plugin specifically and the plugins run without being blocked. The Chrome version gets a single .js script detected as Adaware or PUA, Item details Browsec VPN Browser Plugin.

As an experiment, I put Opera into the Application Control and installed it, after it is installed I'm unable to use it because of the Application Control Policy.

Thanks

Hi Christian

That's right.

I've tried in both Firefox and Chrome to block the BrowSec plugin specifically and the plugins run without being blocked. The Chrome version gets a single .js script detected as Adaware or PUA, Item details Browsec VPN Browser Plugin.

As an experiment, I put Opera into the Application Control and installed it, after it is installed I'm unable to use it because of the Application Control Policy.

Thanks

Hello Cache,

obviously Application Control (AC) is working. Of course if your AV policy excludes the very files that AC needs to identify a certain application then you won't get the desired results - but this is not the case here as at least the .js is detected as PUA. Likely the detection needs some refinement. All you can do is to use the Contact Form to raise a ticket, supplying if possible the plugin code.

Christian 

Ok will do.

thanks for the help.