Brave Browser Compatibility

[An ESET Fanboy 1]

Hello,

I am a long term ESET customer. I switch browsers occasionally and currently using Brave browser. I suspect NOD32 doesn't support web filtering on Brave Browser.

I observed NOD32 simply failed on AMTSO phishing test page at https://www.amtso.org/feature-settings-check-phishing-page/ while using Brave Browser. However the same test page was flagged successfully by NOD32 while on Microsoft Edge (chromium) browser. 

Please add web filtering support on Brave Browser if it was not there.

Regards

[itman 1,659]

Refer to this posting: https://forum.eset.com/topic/19969-brave-browser-not-protected-by-anti-phishing/?do=findComment&comment=97520 .

In Eset List of SSL/TLS filtered applications, set the executable for Brave browser from Auto to Scan and save your settings. Now retest at AMTSO web site.

Edited May 24, 2021 by itman

[Marcos 5,074]

As itman wrote, enforce SSL filtering for brave.exe and it will work. You will need to restart the browser and possibly also clear cache to re-test it:

 

[An ESET Fanboy 1]

15 hours ago, Marcos said:

As itman wrote, enforce SSL filtering for brave.exe and it will work. You will need to restart the browser and possibly also clear cache to re-test it:

 

 

 

Thanks for the helping out and it works. Why can't ESET do this on its own instead of its user had to go through this ? One of the features I love in ESET AV is its exceptional Web Filtering capability and if it doesn't work as consistently across usage scenarios then its a turn off.  

Regards

[peteyt 393]

2 hours ago, An ESET Fanboy said:

 

 

Thanks for the helping out and it works. Why can't ESET do this on its own instead of its user had to go through this ? One of the features I love in ESET AV is its exceptional Web Filtering capability and if it doesn't work as consistently across usage scenarios then its a turn off.  

Regards

I presume this is due to the browser not properly supported but this is just me guessing.

[itman 1,659]

3 hours ago, An ESET Fanboy said:

Why can't ESET do this on its own instead of its user had to go through this ?

Appears Eset currently has no way of determining what are browser based executables and setting the default scanning option to "Scan."

At a minimum, Eset should update their documentation in regards to SSL/Protocol scanning to state that this option needs to be manually set for browsers other that IE11, Edge, Chrome, and Firefox.

Edited May 25, 2021 by itman

[An ESET Fanboy 1]

20 hours ago, itman said:

Appears Eset currently has no way of determining what are browser based executables and setting the default scanning option to "Scan."

At a minimum, Eset should update their documentation in regards to SSL/Protocol scanning to state that this option needs to be manually set for browsers other that IE11, Edge, Chrome, and Firefox.

I expect ESET to support browsers outside IE11, Edge, Chrome, Firefox as and when they become reasonably popular in use. Browsers like Brave, Opera, Yandex etc probably used by millions combined and we cannot ignore them.