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

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

  • QC wrote:

    The major concern is not about a user giving away the credentials (and obfuscation wont help as you he monitor the http traffic) but the password travelling in (practically) clear text over "foreign" territory (wire or air).


    Understood - it's the reason I recommend a single, read only HTTP user account for remote updates, not AD accounts or similar. Our remote update doesn't need that kind of access :)

    :257
Reply

  • QC wrote:

    The major concern is not about a user giving away the credentials (and obfuscation wont help as you he monitor the http traffic) but the password travelling in (practically) clear text over "foreign" territory (wire or air).


    Understood - it's the reason I recommend a single, read only HTTP user account for remote updates, not AD accounts or similar. Our remote update doesn't need that kind of access :)

    :257
Children
No Data