Alternative to Path Exception for .exe

[Dayiz 0]

Hello everyone,

I'm writing small scripts for my firm (mostly string manipulation) and we are using ESET Endpoint Security. The scripts get compiled to .exe and uploaded to a fileserver, from where the users in our firm can execute and use it.

The problem: It generally takes up to 2 minutes to start the script since ESET scans the communication, which slows down our work process immensly.

The Question: I found the possibility to add path exceptions to ESET so the file won't get scanned anymore when being executed, but the IT department in our firm isn't a big fan of adding path exceptions. So I'm wondering, if there is a way to get ESET recognize those scripts. I was looking into issuing certificates from ESET for my scripts, but I'm not sure, if that is even possible.

Can anyone recommend me a way how I get my scripts to be ignored internally by ESET?

Thanks in advance

 

Dear Regards

Dayiz

[Marcos 5,074]

10 minutes ago, Dayiz said:

Can anyone recommend me a way how I get my scripts to be ignored internally by ESET?

This is not possible. However, you could consider using process exclusions if it helps to exclude a process that cannot execute malware (e.g. it would not be safe to execute a script interpreter, such as wscript.exe).

However, we would like to check what's going on there since scanning relatively small scripts should not cause noticeable delays.

Please carry on as follows:
- temporarily disable Protected service in the HIPS setup and reboot the machine
- start logging with Procmon
- reproduce the issue
- stop logging
- save the PML log
- collect logs with ESET Log Collector and add the PML log to the archive
- upload the archive here or to a safe location and drop me a private message with a download link and information about the script name that was used during issue replication.

 

[Dayiz 0]

Hello Marcos,

Thank you for your answer. I will try to learn some things about process exclusions and see if that helps.

About the Log:

I will try to follow your steps and get that file to you asap. A bit more Information on the scripts (if it helps): they are written in Python to edit .xml files and i'm using pyinstaller to compile those .py scripts into .exe executables. the user open can access them from the fileserver and upon execution, they insert the path to the files, the folder gets scanned and the files edited (usually new files are created by the script)