Microsoft’s research team studied this extensively. They looked at what actually happens when you enforce complexity requirements. Users don’t create randomly generated passwords. They follow predictable patterns. Capital letter at the start. Numbers at the end. Exclamation point at the very end. The word “Password” appears in about eight percent of “complex” passwords. When you force rotation, users increment numbers. Summer2024 becomes Fall2024. Or they add exclamation points. Or they change a single character and call it done. The false sense of security is dangerous. IT departments see compliance numbers go up. Everyone is following the password policy. The auditors are happy. Meanwhile, actual security hasn’t improved at all.

    • sawdustprophet@midwest.social
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      4 hours ago

      It’s monthly at my company. Combined with other complexity requirements, it’s pushed everyone into such predictable patterns that I could probably guess my way into any manager’s PC in probably a few minutes.

      Also, there’s no lockdown after X attempts. I can try infinitely, as far as I’m aware.

    • Corkyskog@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      7
      ·
      8 hours ago

      Our organization got hacked and there was about a year after where CISO had us changing passwords every two weeks.

      • scytale@piefed.zip
        link
        fedilink
        English
        arrow-up
        11
        ·
        22 hours ago

        It was commonly 90 days for regular user accounts, and 30 days for admin/privileged accounts.

        • vrighter@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          3
          ·
          13 hours ago

          with automated password rotation, and no api access (no permission to use api access, that is) to the keyvault. And they expected us to automate stuff too!