Cliets show againt 5.7.220 what's meen?

These articles are super helpful: https://community.sophos.com/kb/en-us/128053 and https://community.sophos.com/kb/en-us/128060. However, 128060 only specifies that the update is "being applied over a number of days".  It would be helpful if this article could give us range of days- what's the maximum number of days we should expect for the update to reach us?

The schedule is a staggered for all the products and is expected to change as we do it. We will confirm when products have been completed.

For reference though the first group of SEC managed and standalone customers started on Friday with the majority going out on Monday and a few on Tuesday. Most of Central managed machines will be completed today. Sophos Home also started on Friday. UTM managed and SVE will start shortly.

At now same situation of 6th, still 5.7.220..

Hello!

We (our company) received updates today, which is pretty late.

How can we get to the "first" group for updating? 

Regards

Hi,

The groups used for this update are not a permanent setup, just part of this roll out. Please note this is not a Sophos patch or anything that adds protection for these exploits. All our update does is adds the registry key that Microsoft have asked AV vendors to add once they confirm that are compatible with their patch. Sophos confirmed all our products were compatible with the patch Thursday 4th last week, at which point you could set the registry key yourself and deploy it to all your endpoints via a GPO for example.

Further to this the Microsoft patch is just the first step to protect your systems against these vulnerabilities, for servers there are 3 additional registry keys that need to be set according to Microsoft and these are not being set by AV vendors. There will also be firmware upgrades for the different Intel/AMD/ARM chips involved (most not released yet). 

For everyone reading this post, the Meltdown and Spectre exploits are not a simple patch and forget situation, resolving these will require multiple patches/upgrades from Microsoft/Apple/Linux as well and the firmware upgrades from Intel/AMD/ARM and others. Please ensure you are reading all the advice carefully. Sophos has published 3 articles on this:

Main article: Advisory: Kernel memory issue affecting multiple OS (aka F**CKWIT, KAISER, KPTI, Meltdown & Spectre)

Checking our update: Kernel memory issue affecting multiple OS: How to confirm you have the Sophos update

Naked Security blog (technical details): F**CKWIT, aka KAISER, aka KPTI – Intel CPU flaw needs low-level OS patches

Hi,

The groups used for this update are not a permanent setup, just part of this roll out. Please note this is not a Sophos patch or anything that adds protection for these exploits. All our update does is adds the registry key that Microsoft have asked AV vendors to add once they confirm that are compatible with their patch. Sophos confirmed all our products were compatible with the patch Thursday 4th last week, at which point you could set the registry key yourself and deploy it to all your endpoints via a GPO for example.

Further to this the Microsoft patch is just the first step to protect your systems against these vulnerabilities, for servers there are 3 additional registry keys that need to be set according to Microsoft and these are not being set by AV vendors. There will also be firmware upgrades for the different Intel/AMD/ARM chips involved (most not released yet). 

For everyone reading this post, the Meltdown and Spectre exploits are not a simple patch and forget situation, resolving these will require multiple patches/upgrades from Microsoft/Apple/Linux as well and the firmware upgrades from Intel/AMD/ARM and others. Please ensure you are reading all the advice carefully. Sophos has published 3 articles on this:

Main article: Advisory: Kernel memory issue affecting multiple OS (aka F**CKWIT, KAISER, KPTI, Meltdown & Spectre)

Checking our update: Kernel memory issue affecting multiple OS: How to confirm you have the Sophos update

Naked Security blog (technical details): F**CKWIT, aka KAISER, aka KPTI – Intel CPU flaw needs low-level OS patches