• ditty
      link
      fedilink
      English
      2614 hours ago

      Yet another reason to not do auto-updates in an enterprise environment for mission-critical services.

      • @[email protected]OP
        link
        fedilink
        English
        2714 hours ago

        In an enterprise environment, you rely on a service that tracks CVEs, analyzes which ones apply to your environment, and prioritizes security critical updates.
        The issue here is that one of these services installed a release upgrade because Microsoft mislabelled it as security update.

        • @NocturnalEngineer
          link
          English
          1213 hours ago

          Should still be doing phased rollouts of any patches, and where possible, implementing them on pre-prod first.

          • @SomeGuy69
            link
            English
            77 hours ago

            For security updates in critical infrastructure, no. You want that right away, in best case instant. You can’t risk a zero day being used to kill people.

          • @[email protected]
            link
            fedilink
            English
            7
            edit-2
            8 hours ago

            Pre-prod is ideal, but a pipe dream for many. Lots of folks barely get prod.

            We still stagger patching so things like this only wipe some of the critical infrastructure, but that still causes needless issues.