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

Option to prevent tampering with Sophos services and settings

Hello Folks -

We just recently implemented Sophos S&C 9.0 for our end-users.  The product works great but we are looking for some sort of mechanism to prevent our limited number of users who are also local administrators on their laptops from stopping the Sophos services.  I know with other vendors products that regardless of whether the user is an admin or not they still provided some sort of setting(s) that would prevent the users from doing so.

I do realize (and I saw this on other posts in this forum) that it doesn't go along with "safe computing practices" but in some companies (i.e. telecoms) it is often at times cumbersome to lock down certain departments (RF engineers, field crews, etc) especially when these departments are in direct contact with vendors, etc.  I can restrict with a Group Policy the "Install with Elevated Privilges" settings but many applications are hard coded to require an administrator installing the software.

I saw that Sophos Professional Services can assist with this type of configuration but in my honest opinion this is something that should be included in an enterprise class endpoint solution.  I also may be searching on the wrong keywords so if there is an article / suggestion on how to accomplish this please steer me in the correct direction.

Thanks!

:2028


This thread was automatically locked due to age.
Parents
  • I realize this is an old post but I came across it in my searches for understanding how Sophos can possibly be compliant with PCI when the process can easily be killed by any local administrator.

    PCI DSS 3.0 regulation 5.3 states that all anti-virus mechanisms anti-virus must be actively running and unable to be disabled or altered by users.   Note: Anti-virus solutions may be temporarily disabled only if there is legitimate technical need, as authorized by management on a case-by-case basis. If anti-virus protection needs to be disabled for a specific purpose, it must be formally authorized. Additional security measures may also need to be implemented for the period of time during which anti-virus protection is not active.

    I don't see how Sophos's tamper protection feature meets this requrement at all when anyone who is a local admin is able to do this.

    Can someone from Sophos please comment on this?

    :55122
Reply
  • I realize this is an old post but I came across it in my searches for understanding how Sophos can possibly be compliant with PCI when the process can easily be killed by any local administrator.

    PCI DSS 3.0 regulation 5.3 states that all anti-virus mechanisms anti-virus must be actively running and unable to be disabled or altered by users.   Note: Anti-virus solutions may be temporarily disabled only if there is legitimate technical need, as authorized by management on a case-by-case basis. If anti-virus protection needs to be disabled for a specific purpose, it must be formally authorized. Additional security measures may also need to be implemented for the period of time during which anti-virus protection is not active.

    I don't see how Sophos's tamper protection feature meets this requrement at all when anyone who is a local admin is able to do this.

    Can someone from Sophos please comment on this?

    :55122
Children
No Data