"Wanna" ransomware outbreak. Please see this Sophos article sophos.com/kb/126733 for advice on how to protect your organization. Immediate action recommended.
This article explains how to configure a caching proxy for Patch data files so that endpoint computers can update their Patch data files from the cache rather than connect directly to the Sophos Management server.
The main reason for doing this is to reduce the amount of Wide Area Network (WAN) traffic to remote sites. For a comparison of the data traffic reduction that can be achieved with caching see the Technical Information section at the end of this article.
Known to apply to the following Sophos product(s) and version(s) Enterprise Console 5.1.0
The table below provides an overview of the three types of proxy configuration you can employ. Use the links in the table to jump to detailed information on implementing caching for a particular type of proxy.
Note: This String value needs to contain the fully qualified domain name of the explicit proxy, appended by the port number. Alternatively, a URL to a PAC file can be entered.
Note: This String value needs to contain the fully qualified domain name of the reverse proxy, appended by the port number.
No changes are required.
The tables below show a comparison of data transferred between the endpoint computer (with the Sophos Patch Agent installed) and the Sophos Patch server.
The table below shows a comparison of network traffic volume between Enterprise Console v5.0 and v5.1 for the initial installation of the Sophos Patch Agent to the endpoint computer and download/upload from the Sophos Patch server.
The table below shows a comparison of network traffic volume between Enterprise Console v5.0 and v5.1 for a typical month.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.