Announcement

Collapse
No announcement yet.

Disable security component on endpoint without using security profile setting

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Disable security component on endpoint without using security profile setting

    What is the best way to disable a security component such as firewall, Hips, or Auto containment from an endpoint without having to make changes to the security profile

    I know that the endpoint communicates with the server/portal every 5mins or less to reinforce the profile settings

    Issue: We have customers who have their own internal IT support staff, when they try to install a piece of software and comodo blocks it they have no way to disable components of ccs
    as they donnot have access to the profile section of our dashboard

    what is a goodway to resolve this issue please advise
    i need to write a procedure document for our customer to follow when ever they encounter such a problem

  • #2
    Nevillo1 ,

    You can utilize the Client Access Control Feature in this manner, wherein a password is required to be set on the profile, since they do not have access to the profile settings to make changes, you can share the password to the local IT support staff so they can temporarily make changes on the local CCS settings (enabling the -extra options = Enable local user to override profile configuration). After they have completed the installation you can the disable the extra options to get the disabled feature back in normal operation once the device syncs back to the EM Portal. If you are hesitant about the password being shared, you can set a different password the same time, while making changes on the extra options. Please make sure to save your changes on your profile settings

    Comment


    • #3
      we already have a password set & shared with the customer only problem is...they will have to call us for every software install that comodo blocks
      that is a major problem for us as this is a large organisation with multiple users

      it is a pain point for the customer as they have to call us for minor things like software installs
      they are so frustrated that they have suggested we change to another product

      Comment


      • #4
        Hello Nevillo1, we are unhappy about the inconvenience this may have caused you and to your customers. We will communicate with you thru email and have our team's attention directed on resolving the situation.

        We are hoping for your continued understanding and patience of this matter.

        Comment


        • #5
          Originally posted by Nevillo1 View Post
          we already have a password set & shared with the customer only problem is...they will have to call us for every software install that comodo blocks
          that is a major problem for us as this is a large organisation with multiple users

          it is a pain point for the customer as they have to call us for minor things like software installs
          they are so frustrated that they have suggested we change to another product
          Shouldn’t you be responsible for software installs?

          Comment

          Working...
          X