• ditty
      link
      fedilink
      English
      2714 days ago

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

      • @[email protected]OP
        link
        fedilink
        English
        4014 days 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.

        • @[email protected]
          link
          fedilink
          English
          1214 days ago

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

          • @[email protected]
            link
            fedilink
            English
            11
            edit-2
            14 days 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.

          • @[email protected]
            link
            fedilink
            English
            1114 days 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
              0
              edit-2
              12 days ago

              Even security updates can be uncritical or supercritical. Consult the patch notes or get burned lol