Guest User!

You are not Sophos Staff.

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

Policy non-compliance: Automatic Updates

Just recently received this event message from 25+ computers across the company (all Macs using High Sierra 10.13 or Mojave 10.14). Seems to affect randomly. I couldn't find any related posts in the community. Any help would be appreciated. Thanks!



This thread was automatically locked due to age.
Parents
  • Hi Everyone,

    We have an official announcement on the reported issue. 

    On October 21, 2018, we released a policy update for Macs, which updated the strength of the updating password encryption. This has resulted in some Macs reporting Policy Non-Compliance: Updating, as the systems took in the new encryption. The systems have moved over to the updated policy automatically, so this alert in central can be acknowledged. For more details please refer the below KBA.

    Central Dashboard shows Policy Non-Compliance: Updating for Macs

    Regards,

    Gowtham Mani
    Community Support Engineer | Sophos Technical Support

    Knowledge Base  |  @SophosSupport | Sign up for SMS Alerts
    If a post solves your question use the 'This helped me' link.

  • Gowtham - This is poor response on Sophos's part. Sophos botched a roll out. The answer is simple, fix it. It may have been meant to have this in place when the new encryption was available but that failed. Remove it until Sophos either learns how to have it in place without causing invalid alerts or until the new encryption is in place.

     

    Also, your date is incorrect. The first reported instance of this alert in my Sophos Central was Oct 20th at 4:33 PM CDT (GMT -5). The alert does not post until 2 hour after the non-compliance was detected, that puts us at 2:33 PM CDT. Germany is 7 hours ahead of CDT so that would make it Oct 20th at 9:33 PM at the latest, which is still not Oct 21st.

Reply
  • Gowtham - This is poor response on Sophos's part. Sophos botched a roll out. The answer is simple, fix it. It may have been meant to have this in place when the new encryption was available but that failed. Remove it until Sophos either learns how to have it in place without causing invalid alerts or until the new encryption is in place.

     

    Also, your date is incorrect. The first reported instance of this alert in my Sophos Central was Oct 20th at 4:33 PM CDT (GMT -5). The alert does not post until 2 hour after the non-compliance was detected, that puts us at 2:33 PM CDT. Germany is 7 hours ahead of CDT so that would make it Oct 20th at 9:33 PM at the latest, which is still not Oct 21st.

Children
No Data