So my company decided to migrate office suite and email etc to Microsoft365. Whatever. But for 2FA login they decided to disable the option to choose “any authenticator” and force Microsoft Authenticator on the (private) phones of both employees and volunteers. Is there any valid reason why they would do this, like it’s demonstrably safer? Or is this a battle I can pick to shield myself a little from MS?

  • Carighan Maconar@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    Yeah but that’s a wholly different attack, and oodles more complex to pull off. Doable, sure. But it’s absolutely not the same thing as phishing for a valid 2FA code that is generated user-side.

    And don’t get me wrong, both are overall very security. But there is a case to be made for push auth.

    • Nighed@sffa.community
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      It’s not that different is it? You still need to get a user to share/enter a live code?

      • AtariDump@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        4 months ago

        One requires the user to go to a bad page and get a spoofed 2FA code so the bad guy can log in.

        Do you know how hard that is? Not worth it for 99% of hacks.

        The other requires that the user read off their six digit code on their device.

        Trivial easy since they already have the user’s password.

        • Nighed@sffa.community
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          It requires the bad guy to go to the page and ask the user to enter the code the bad guy gets

          • AtariDump@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            4 months ago

            How does the bad guy get to the page?

            Then how does he get the user to enter in that code into their mobile device?