Video Screencast Help

Whitelisting browser addons

Created: 21 Mar 2014 • Updated: 16 Jul 2014 | 4 comments
djd's picture
This issue has been solved. See solution.


My company maintains add-ons on Chrome and Firefox for several years now.

Recently, one of our customer reported that a Symantec product was classifying one of our Firefox add-on as a malware.

A possibility to avoid it would be to go through the whitelisting process, however FF releases a new version of their browser every 6 weeks on average and the whitelisting process takes several weeks to take effect. So it looks like this process is not adapted to us since as soon or before an add-on is added to the whitelist, we would have moved to another release of our add-on to stay compatible.

Do you have an idea on how to prevent our add-ons to be classified as malware?

Thank you

Comments 4 CommentsJump to latest comment

Brɨan's picture

Have you tried this:

Software developer would like to add his/her software to the Symantec white-list.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Doraemon's picture

Try to add your FF in whitelist, so even that theres a new add on SEP wont block it.


James007's picture

You can White-List your software

Software developer would like to add his/her software to the Symantec White-List.

Article:TECH132220 | Created: 2010-01-04 | Updated: 2013-10-18 | Article URL

Software White-Listing Request Form:

djd's picture

Thanks for your feedbacks!

I had a look to those links before to post my question.

My concern is that this whitelist process is specific to an installer (specific SHA 256) however, if my installer changes every 4 to 6 weeks (because of a new FF release for instance), will I have to follow the process again for every version of my add-ons? In this case, since the whitelist process takes weeks to be completed, doesn't it defeats the purpose?

thank you