However, developers may experience a higher FP rate than typical users. We use all of these factors to ensure we can provide the maximum protection for users while preventing false positives. When our reputation technology encounters a brand-new file (including items that you may create on your own) it relies on a number of factors to determine reputation. (Select the 'Exclude this File ID' check box if you would like Norton to exclude this file in the future scans) Now select Quarantine from the pull down and select the file that you wish to restore and click on the “ Restore” button under the recommended action.įrom the Quarantine Restore window, Select the " Yes" button to restore your file. To do so, open the main window and click on “ History” as shown: If you are confident that you are experiencing a false positive and cannot wait for the dispute process, the product allows you to manually remove items from quarantine. This page is monitored 24 hours a day so that we can immediately begin to research and correct any issue.
If you believe a file has been mistakenly detected by WS.Reputation.1, you can submit a dispute at.
We are constantly tuning the reputation system to avoid these problems, but they do occur on occasion. Now, like any security technology, there is a small chance that we have made a mistake on a file. The reputation-based system uses "the wisdom of crowds" (Symantec’s tens of millions of end users) connected to cloud-based intelligence to compute a reputation score for an application, and in the process identify malicious software in an entirely new way beyond traditional signatures and behavior-based detection techniques. Because this detection is based on a reputation score, it does not represent a specific class of threat like adware or spyware, but instead applies to all threat categories. Detections of this type are based on Symantec’s reputation-based security technology. WS.Reputation.1 is a detection for files that have a low reputation score based on analyzing data from Symantec’s community of users and therefore are likely to be security risks. First off, we have published a write-up on our Security Response site.
In order to clear things up, we thought it was important to explain this detection and provide more information about how you should deal with it. There have been several recent posts about the WS.Reputation.1 detection.
0 kommentar(er)
