How to add a Security Risk Exception in the Symantec Endpoint Protection Manager

Article:TECH103120  |  Created: 2007-01-18  |  Updated: 2014-08-18  |  Article URL http://www.symantec.com/docs/TECH103120
Article Type
Technical Solution


Issue



Symantec Endpoint Protection (SEP) scans are detecting files on client systems as risks. The detected files have been confirmed harmless. You want to create exceptions in the Symantec Endpoint Protection Manager (SEPM) to prevent subsequent scans from inadvertently quarantining or deleting these files, until new definitions are released which remove this False Positive (FP).


Solution




Any file that appears to be detected due to a False Positive should be submitted to the Symantec Security Response "Report a Suspected Erroneous Detection (False Positive)" Site. If a False Positive is confirmed to have caused this detection, newer definition sets will be developed in such a way as to not trigger on these files.

As a temporary measure until new definitions are available, you can make a Centralized Exception in the SEPM for known risks, files, folders, and extensions:

  1. Select the Policy tab in the Symantec Endpoint Protection Manager.
  2. Under "View Policies" select Centralized Exceptions.
  3. In the "Available Tasks" select Add a Centralized Exception policy...
  4. A window will open to allow you to define the policy. Provide a descriptive name and a description of the policy you are adding.
  5. Select Centralized Exceptions. Click the Add button to view the drop down menu options: "Security Risk Exceptions", "Proactive Threat Scan Exceptions", and "Tamper Protection Exception".
  6. Select an item from the list to create an exception.
  7. After selecting the exception type, enter in the specific exception, or exceptions (one exception at a time), in the window.
  8. Click OK when finished adding exceptions. Click OK again to finish creating the policy.
  9. When prompted to assign the policy to a group, click YES. You can then choose the group you wish to assign the policy to and the policy changes will be sent out to members of the group.

 




Legacy ID



2007121808365448


Article URL http://www.symantec.com/docs/TECH103120


Terms of use for this information are found in Legal Notices