Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 3994 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How do I programatically add a file to Sophos's exclusion list?

dencolp

Hi Sophos Gurus,

I have no Sophos experience so please forgive my newbie question.

I'm a software developer for a team that distributes an exe (let's call it myexe.exe) that is getting flagged by Sophos Anti-virus for suspicious activity.  When my team's application is installed it installs myexe.exe.  At install time, I want to add an "Exclusion" for myexe.exe to Sophos Anti-virus so that Sophos Anti-virus doesn't flag myexe.exe for suspicious activity.  How can this be accomplished?  Can this be done from a command-line command?  Thank you in advance for your help.

Note that I work at a company where Sophos Anti-virus is installed on most people's PCs.  Also note that I don't administer Sophos Anti-virus at my company, I am a software developer who distributes an .exe that is getting flagged by Sophos Anti-virus for suspicious activity.

Thanks,
DenColp

:3513


This thread was automatically locked due to age.
Parents
  • 0

    Hi Sophos experts

    I have a similar question.  My team delivers an exe (say for example myexe.exe) to a company which has Sophos antivirus installed in all user's PCs.    This myexe has been detected by Sophos as a file exhibiting 'Suspicious Behavior'.  Our company where this exe is developed does not have Sophos installed.  I could see from websites that one way to get over this is to 'authorize' the exe and hence the application.  But I would like to know what causes the myexe to be detected as a file of suspicious behavior.  How do we get to know that and how do we get rid of that behavior from that exe?  Please help.

    :4870
Reply
  • 0

    Hi Sophos experts

    I have a similar question.  My team delivers an exe (say for example myexe.exe) to a company which has Sophos antivirus installed in all user's PCs.    This myexe has been detected by Sophos as a file exhibiting 'Suspicious Behavior'.  Our company where this exe is developed does not have Sophos installed.  I could see from websites that one way to get over this is to 'authorize' the exe and hence the application.  But I would like to know what causes the myexe to be detected as a file of suspicious behavior.  How do we get to know that and how do we get rid of that behavior from that exe?  Please help.

    :4870
Children
No Data
Unfiltered HTML