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

Sophos doesn't move malware/virus

Hello,

I have a problem with Sophos Endpoint Security & Control managed over the Sophos Enterprise Console. I did set the policy if a virus gets detected Sophos should deny access and move it to the default location C:\ProgramData\Sophos\Sophos Anti-Virus\INFECTED

But if a virus/malware appears Sophos only denies access and doesn’’’’t move the file into the target folder. However the virus appears in the quarantine-manager and is still in the source directory e.g. C:\Users\test\Desktop but won’’’’t appear in C:\ProgramData\Sophos\Sophos Anti-Virus\INFECTED

I think it’’’’s a Sophos Client problem, the policy is transmitted successfully, because in the client options all the right settings are set.

The Sav log file only says that Sophos denied access, but nothing about moving the file to the infected folder.

Tested on Windows 7 and Windows Server 2008 R2, Sophos Client Version 10.2.

Best Regards and thanks in advance!

:43899


This thread was automatically locked due to age.
Parents
  • Hello Nordfol,

    it works here (I know, this is a much hated answer :smileywink:). SAVTEST attempts to write to the root of the drive, with the standard security settings you have to run as administrator. With on-access scanning on the file is correctly moved. When it is turned off, SAVTEST complains.

    There's one twist - if you copy the file as administrator to a protected location (e.g. C:\) while on-access scanning is off . After turning it on again the "threat" is detected but move fails (as it would require confirmation) - you should see this both in SAV.txt (The attempt to move the infected file "C:\eicar.com" failed. The user does not have the rights to perform the action on the infected file.) and SEC (under Alert and Error Details - Scanning errors).

    That's how it's supposed to work - if it doesn't, hmm ...

    Christian

    :43961
Reply
  • Hello Nordfol,

    it works here (I know, this is a much hated answer :smileywink:). SAVTEST attempts to write to the root of the drive, with the standard security settings you have to run as administrator. With on-access scanning on the file is correctly moved. When it is turned off, SAVTEST complains.

    There's one twist - if you copy the file as administrator to a protected location (e.g. C:\) while on-access scanning is off . After turning it on again the "threat" is detected but move fails (as it would require confirmation) - you should see this both in SAV.txt (The attempt to move the infected file "C:\eicar.com" failed. The user does not have the rights to perform the action on the infected file.) and SEC (under Alert and Error Details - Scanning errors).

    That's how it's supposed to work - if it doesn't, hmm ...

    Christian

    :43961
Children
No Data