Endpoint Protection

 View Only
Expand all | Collapse all

file-level scanning exceptions

GeoGeo

GeoGeoJan 25, 2017 07:31 AMBest Answer

artk1

artk1Jan 25, 2017 12:15 PM

  • 1.  file-level scanning exceptions

    Posted Jan 25, 2017 07:10 AM

    Hi,  I'm running SEP12.1.6 Is it possible to exclude file level scanning on processes (.exe) ? I have a long list that I need to exclude. I think the proper way is to:

    1. Open SEPM and go to policies

    2. open Exceptions policie

    3. click on add - windows exceptions- file

    4. add the executable (.exe) example - EdgeTransport.exe

    Thanks

     

     



  • 2.  RE: file-level scanning exceptions

    Trusted Advisor
    Posted Jan 25, 2017 07:17 AM

    That's correct also make sure the policy you've added it to is active in the group you want the exceptions to be applied to. Below is a link to the various scanning exceptions you can add. 

    https://support.symantec.com/en_US/article.HOWTO80919.html



  • 3.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 07:28 AM

    I have one policy for all Servers. That should be fine as far as I know.

     



  • 4.  RE: file-level scanning exceptions
    Best Answer

    Trusted Advisor
    Posted Jan 25, 2017 07:31 AM

    That's fine then you're good to go :)



  • 5.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 08:59 AM

    No, you are not good to go.

    When putting an exception on an executable, you have to enter the entire drive:path as well.

    Just entering the executable name is not enough.

    And you cannot use wild card either. Just entering the executable name is considdered a wild card.

     

    Example of a correct exception:

    C:\Program Files\Application\ EdgeTransport.exe

     

    *Tip: enter all your data in either lower case or upper case.

    Makes sorting a lot easier.

    Apparently, Symantec decided to make the sort case-sensitive.

    And for the actual exception, upper or lower case makes no differense.

     



  • 6.  RE: file-level scanning exceptions

    Trusted Advisor
    Posted Jan 25, 2017 09:02 AM

    All explained in the link on first post John ;) 



  • 7.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 09:05 AM

    GOOD catch, johnsnnl. Some of us need our hand held and a better explanation than just posting a link.



  • 8.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 10:11 AM

    Thanks Johnsnnl, I didn't realize that. I guess I'm one the those people that need hand holding. Thank again

     



  • 9.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 10:13 AM

    you and me both mate, luckily someone knew what's up



  • 10.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 10:21 AM

    One more question - If I'm already excluding C:\Program Files\Application directory do I still need to exclude C:\Program Files\Application\ EdgeTransport.exe ?

     

     

     



  • 11.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 10:25 AM
      |   view attached

    Not if you have that directory excluded and have 'Include subfolders' checked (for sub-folders):

     



  • 12.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 11:01 AM

    So if I have multiple exe running in C:\Program Files\Application directory I would have to list them individually or is there a way to capture all?

     



  • 13.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 11:04 AM

    By excluding the entire Application directory it would capture everything. There would be no need to add additional exceptions for anything in this folder or sub-folders (if you checked the box).



  • 14.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 12:15 PM

    Thanks all



  • 15.  RE: file-level scanning exceptions

    Posted Jan 25, 2017 02:30 PM

    Depends on how many executables you have.

    If it is just a few, do the files.

    Remember that when you eclude a directory, including sub directories, that entire directory is not scanned.

    Up to you if that is exceptable.

    Example: some hacker/disgruntled employee can copy some malicious executable into that directory, or the sub directories, and it will never be detected.



  • 16.  RE: file-level scanning exceptions

    Posted Jan 26, 2017 06:25 AM

    Therese about 30+ executable in the directory so its easier to exclude that directory then add specific paths.