this post was submitted on 04 Jul 2023
13 points (100.0% liked)
Cybersecurity
5687 readers
19 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Notable mention to [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Microsoft and Okta (that I know of) have implemented this number matching to deal with Push MFA fatigue, but also when certain risk factors make your login look riskier (i.e. impossible travel from an IP located so far away from your last login IP, you couldn’t have physically travelled to the new location in the time since the last login).
More info: https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/advanced-microsoft-authenticator-security-features-are-now/ba-p/2365673
edited to share a better link
Right, what is described in that link is reasonable, none of those seem to have a reasonable chance of accidental approval (Even so I wouldn't want for them to appear without me entering my password.), but that's not what I got, while I doubt I personally would accidentally approve the 3 number one I got I can easily imagine someone doing it.
This kind of thing is what I got. https://janbakker.tech/number-matching-with-microsoft-authenticator-app-in-azure-mfa/ in the picture on that site it's also one fat-finger from granting access to an attacker should it have been someone else. EDIT: To be fair this is 2 clicks on what I get, doesn't change much though.
Also about the far away IP thing. I get this everywhere I try to log in, I tried my main PC and a separate PC on VPN in 3 different locations, not once did I have to enter my password for the prompt to appear on my phone.
I was gonna say, contrast this to Steam where I have to enter my username and password and only then get prompted to enter a 6 digit code from the phone on the PC where I want to log in. But they seem to have done away with the code for convenience (I assume) as well, anyway it's still better because I have to enter my password for the prompt to appear so I know that if it does appear my password is compromised (What I assumed had happened for my email.). Add to this that steam also has a QR code you can scan with your phone for instant login without entering your pass or username so they win on convenience anyway.