We have a SQL Server running SentryOne and the entire time the Sophos File Scanner causes the CPU usage to run at 50-60% making the server stay at 100%. I killed the File Scanner and then SentryOne spiked to 50-60%. After this I started the File Scanner and left SentryOne off and no CPU spike. Once I start back up the SentryOne service the File Scanner spikes. I have certain directories and file types excluded from scanning just like our other SQL servers that do not have SentryOne but this one server is still having issues. This leads me to ask is there a conflict with these 2 that anyone knows of?
Thank you for reaching community forum. I believe this is expected behavior as SentinelOne may be designed to operate similarly to our Sophos endpoint. I'll be sharing this documentation to explain further how our Sophos endpoint runs alongside Other 3rd party security software.