SophosAutoUpdate on Mac writes a lot of data every day

Hello there,

Thank you for contacting the Sophos Community.

What files are you looking at and where are you seeing this traffic?

Regards,

I see those numbers in Activity Monitor. For example, I just started my laptop:


At the end of the day it will write about 3Gb.
What does it constantly updating and writing?

Two hours later.

Three hours later.

Hello there,

Thank you for the screenshots, however, can you upload them directly in the post, rather than using 3rd party links, you can click Insert >> Image/Video/File >> Upload (This should open a new window and you can search and find the image you want to upload), I am sharing this information with our Sophos Home team.

Regards,

Hello there,

Thank you for the screenshots, however, can you upload them directly in the post, rather than using 3rd party links, you can click Insert >> Image/Video/File >> Upload (This should open a new window and you can search and find the image you want to upload), I am sharing this information with our Sophos Home team.

Regards,

1 hour later:

2 hours later:

Hello Dmytro,

Thank you for the screenshots.

The Sophos team is currently investigating, and I will be updating this thread once I hear back from the Sophos Home Dev Team.

Regards,

3 hours from the laptop start. So it's a common behavior of SophosUpdate.

Any updates?
How can I set update interval in macos for sophos home?

Hello Dmytro,

I heard that they’ll be updating me on Wednesday.

If you have Sophos Home specific question  you can search on https://support.home.sophos.com/hc/en-us

Regards,

There is no information on changing the update interval. Is that possible at all?

Hello Dmytro,

I relayed your question, they mention it's not possible to change the update interval, this is to keep the computer updated with the latest features/malware updates. 

I am still waiting on feedback about the Sophos Autoupdate.

Regards,

Hello,

Thank you for your patience, the Sophos Home development team has reviewed the situation and logged an internal ticket to address it in a future release.

Regards,