Endpoint Protection

Expand all | Collapse all

How to avoid WS.Reputation.1 error

Jump to Best Answer
  • 1.  How to avoid WS.Reputation.1 error

    Posted 08-21-2012 10:58 AM
      |   view attached

    I have an application which we are about to distribute to a few thousand resellers and one of our test clients was running Norton 360.  When he tried to pull the exe down from our site, Norton threw up alerts and he could not run the application.  The error he is getting is a WS.Reputation.1 message which seems to indicate that Norton simply has never seen the app before (which makes sense as it is new).

     

    Is there some way to submit this for review so Norton will not throw this kind of message?  Is there a way to tell the user how to work around this message?  When I carried the .exe over to his machine on a thumb drive we were able to install without issue, but it seems the act of downloading it caused Norton to go apoplectic.

     

    Attached error from the end client machine.

     

     



  • 2.  RE: How to avoid WS.Reputation.1 error
    Best Answer

    Posted 08-21-2012 11:08 AM


  • 3.  RE: How to avoid WS.Reputation.1 error

    Posted 08-21-2012 11:25 AM

    You can send it in to have it whitelisted:

    https://submit.symantec.com/whitelist/isv/

    You can also add the file as an exception.



  • 4.  RE: How to avoid WS.Reputation.1 error

    Posted 08-21-2012 11:47 AM

    Hello,

    In case, you want to Whitelist an Application, then check this Article:

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

    http://www.symantec.com/docs/TECH132220

     

    Hope that helps!!



  • 5.  RE: How to avoid WS.Reputation.1 error

    Posted 08-21-2012 11:29 PM

    Perftect, that is exactly what I needed.  Thank you.



  • 6.  RE: How to avoid WS.Reputation.1 error

    Posted 08-22-2012 05:35 AM

    Hi Kevin,

    I also recommend checking out the .pdf available here: https://www-secure.symantec.com/connect/downloads/sep-sizing-and-scalability-recommendations-v23

    Though that white paper is mainly devoted to "Sizing and Scalability Recommendations for Symantec Endpoint Protection" it concludes with an excellent section on Preventing and Correcting False Positive Detections with Symantec Endpoint Protection 12.x.

    One excerpt:

    Step 1 – Using Digital Signatures

    One of the easiest ways to identify that a file is good is to know where it came from and who created it. One of the most important factors in building a positive file reputation is to check its digital signature. Executable files without a digital signature are at risk of being identified as unknown.

    Custom or home grown application should be digitally signed with class three digital certificates

    Customers should insist that their software vendors digitally sign their application

     

    Hope this helps! &: )