ws reputation 1 symantec endpoint protection

One set is invoked when I try to install software that was successful downloaded. The challenge for me to understand the functionality was the two sets of popups I have seen when trying to download unknown software. I believe that once I do this, these files that continue to get redetected will be deleted. My next step is to get approval to implement the policy to delete unknown files in production.

I then saw the corresponding reputation events in the risk log on the local client and on the SEPM. I set the policy to '5' and changed the setting for unknown software to log, prompt, quarantine and delete to see what would happen. Once I figured out that the popup from Download Insight appears after I try to execute the software, I was able to manipulate through policy change how SEP responds. I realized that it may not really intervene until the downloaded software is executed. The first problem I had was my misunderstanding of how Download Insight is invoked. This is only our second time experiencing this but we want to explore with Solarwinds if there is a better way this can be addressed to prevent or greatly minimize these outages.After some further investigating and experimenting, I have answered most of my questions. Do you make an exception at your Symantec EndPoint administration console corporate wide? We have a request for a conference call with Solarwinds and some of our team members to see if there can be some type of solution which may include dual certificate existence for a few days along with Solarwinds notifying major security vendors like Symantec and McAfee of their digital signature change to allow them time to implement it in their signature updates before killing the old signature. I am curious as to how other companies with Symantec EndPoint Protection deal with this. Our only workaround is to manually submit the new Dameware file with the updated signature to Symantec for them to exclude it. Does any other company face this? Every time Solarwinds change their digital certificates, Symantec flags the newest installation with the digital certificate change as WS.Reputation.1 (it does not recognize it or has only seen it a few times) and halts all installations.

Ws reputation 1 symantec endpoint protection