Thread Info
  • State Not Answered
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Subscribers 4 subscribers
  • Views 30955 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

Sophos Endpoint Security and Visual Studio

Aarongu

Hi, 

We run Sophos Endpoint Secuirty on our desktop machines and a few of those machines have Visual Studio on them. When we was in the process of setting Sophos up, we imported a list of file types (extensions relating to Visual Studio) that we wanted to excluce from being scanned and they have been specified in both the 'on-access scanning' and Windows exclusions areas of the Enterprise Console. 

However, my collaegues are reporting that when compiling a program in Visual Studio, it is taking a considerable time for the project to compile and they have noted that the CPU % utililisation is higher than before Sophos was placed on to the machine. 

Do you have any specific recommendations to make regarding what changes can be made to stop Sophos causing the issues stated above?

:45447


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

    Hi Christian, 

    We were using CA and then MSE before moving on to Sophos. Both of these AV providers were incredibly CPU hungry so we moved to Sophos, we advertised a lower use of CPU.

    In the 'Sophos Enterprise Console' when specifying the policies for a group of PC's you can specify exclusions. The 'Anti-virus and HIPS' policy allows for an admin to specify what extensions they do not want Sophos to scan. There are several tabs such as 'Extensions', 'Windows Exclusions', 'Mac Exclusions' etc. etc. In both the Extensions and Windows Exclusions areas of this policy, I have specified certain file types that should not be scanned. For the most part these are working but we are still seeing an increase in CPU usage that is hampering the developers system's. 

    I accept the fact that AV is going to cause an increase on CPU, this is only naturally. However, I expected that listing files to be excluded would limit the amount of scanning that is performed on the developers machines. What I want to find out, is if there are specific file types that you could recommend that would limit the impact of the AV on machines that are running Visual Studio?

    Just as a note, yes we have tested disabling 'on-access' scanning but that didn't have an impact on the increase in CPU when compiling a program in Visual Studio. Disabling 'on-access' scanning is also not really something we want to do because it severely reduces our protection levels.

    Thanks, 

    Aaron

    :45467
Reply
  • 0

    Hi Christian, 

    We were using CA and then MSE before moving on to Sophos. Both of these AV providers were incredibly CPU hungry so we moved to Sophos, we advertised a lower use of CPU.

    In the 'Sophos Enterprise Console' when specifying the policies for a group of PC's you can specify exclusions. The 'Anti-virus and HIPS' policy allows for an admin to specify what extensions they do not want Sophos to scan. There are several tabs such as 'Extensions', 'Windows Exclusions', 'Mac Exclusions' etc. etc. In both the Extensions and Windows Exclusions areas of this policy, I have specified certain file types that should not be scanned. For the most part these are working but we are still seeing an increase in CPU usage that is hampering the developers system's. 

    I accept the fact that AV is going to cause an increase on CPU, this is only naturally. However, I expected that listing files to be excluded would limit the amount of scanning that is performed on the developers machines. What I want to find out, is if there are specific file types that you could recommend that would limit the impact of the AV on machines that are running Visual Studio?

    Just as a note, yes we have tested disabling 'on-access' scanning but that didn't have an impact on the increase in CPU when compiling a program in Visual Studio. Disabling 'on-access' scanning is also not really something we want to do because it severely reduces our protection levels.

    Thanks, 

    Aaron

    :45467
Children
No Data
Unfiltered HTML