• ditty@lemm.ee
    link
    fedilink
    English
    arrow-up
    30
    arrow-down
    4
    ·
    17 days ago

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

    • superkretOP
      link
      fedilink
      English
      arrow-up
      41
      arrow-down
      1
      ·
      17 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.

      • NocturnalEngineer@lemmy.world
        link
        fedilink
        English
        arrow-up
        14
        arrow-down
        3
        ·
        17 days ago

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

        • mosiacmango@lemm.ee
          link
          fedilink
          English
          arrow-up
          11
          ·
          edit-2
          16 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.

        • SomeGuy69@lemmy.world
          link
          fedilink
          English
          arrow-up
          12
          arrow-down
          1
          ·
          16 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.

          • Appoxo@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            2
            ·
            edit-2
            14 days ago

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