Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 31 replies
  • Subscribers 1 subscriber
  • Views 94951 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 Updates over https

faygate

For the past 3 or 4 years we have posed the question to Sophos as to why we cannot update our clients out in the field using a web CID over https. So far this has failed to materialise, which I found bizarre for a company that deals with security. We are a large University and to ensure we our students and staff are protected from viruses and malware, they are allowed to install Sophos on their computers. Now as we like to ensure that we adhere to our licence our users must update Sophos using their University credentials.

As our University credentials are being used to grant access to more and more sensitive systems, this is becoming a real security issue and we are not happy about this credentials being passed over effectively in plain text! Of course we'd have the overhead of the encryption on our webservers, but I'm happy to take that hit and the servers can handle it.

Does anyway else have this requirement for updates via https? I can't believe we are the only ones.

My understanding is that this is now being discussed as a feature request, but it would be good to have some more people on board. Please post your comments below.

Regards, Richard

:226


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

    Okay I realise I'm resurrecting an ancient thread here, but I also find it surprising that there's no support for https updating.  I'm aware of the over head using https (and don't really care about it to be honest), and setting up a separate account for updating only doesn't really fit in here.  We have a lot of temporary staff, and using AD accounts ensures that when people leave the organisation they can't keep using our Sophos licence.  With a stand-alone account former employees would probably still keep using it, and since the username and password would no longer be 'personal' to our users, there's more chance they'd start distributing the credentials to their friends and family.


    AD authentication helps keep our licencing in check, but having these details sent over a standard http connection still causes concern, especially given all the resources that can be accessed externally with an active account.

    :2890
Reply
  • 0

    Okay I realise I'm resurrecting an ancient thread here, but I also find it surprising that there's no support for https updating.  I'm aware of the over head using https (and don't really care about it to be honest), and setting up a separate account for updating only doesn't really fit in here.  We have a lot of temporary staff, and using AD accounts ensures that when people leave the organisation they can't keep using our Sophos licence.  With a stand-alone account former employees would probably still keep using it, and since the username and password would no longer be 'personal' to our users, there's more chance they'd start distributing the credentials to their friends and family.


    AD authentication helps keep our licencing in check, but having these details sent over a standard http connection still causes concern, especially given all the resources that can be accessed externally with an active account.

    :2890
Children
No Data
Unfiltered HTML