The Convenience Trap: Why Seamless Banking Access Can Turn 2FA into 1FA
1–10 of 64 posts
Re: The Convenience Trap: Why Seamless Banking Access Can Turn 2FA into 1FA
#2Re: The Convenience Trap: Why Seamless Banking Access Can Turn 2FA into 1FA
#3For example, it would make a lot of sense to treat them differently for Apple Pay fraud detection, since passcode + device compromise seems a lot more likely in the real world than compelled Face ID.
Edit: there's a newish feature, Stolen Device Protection, that works along these lines - https://support.apple.com/en-us/120340
Re: The Convenience Trap: Why Seamless Banking Access Can Turn 2FA into 1FA
#4It makes the conclusions of types 1 and 4 very different.
Re: The Convenience Trap: Why Seamless Banking Access Can Turn 2FA into 1FA
#5This would be the same as shoulder surfing your card pin and then stealing or cloning your card. There were two factors, the attacker just has access to both.
They needed an authenticated app and the pin at that point which is two factors. Because both are related to your iPhone means nothing, both your card’s pin and your card are related to your card and both can be compromised by the exact same attack with the exact same consequences.
Re: The Convenience Trap: Why Seamless Banking Access Can Turn 2FA into 1FA
#6Problem is, people catch on that with some `expect` scripting and a few open source packages you can still just automate it to be 1 factor, just adding a bit more complexity to eventually leak the user's credentials.
Re: The Convenience Trap: Why Seamless Banking Access Can Turn 2FA into 1FA
#7I stopped here... at least on iPhone, this doesn't work. When a new face is scanned into FaceId, all apps using that FaceId are supposed to (forced to?) re-authenticate.
Re: The Convenience Trap: Why Seamless Banking Access Can Turn 2FA into 1FA
#8I've seen a lot of services (none banks so far) move over to requiring a One Time Password in addition to a password or private key as a way to get "2 factor authentication". Problem is, people catch on that with some `expect` scripting and a few open source packages you can still just automate it to be 1 factor, just adding a bit more complexity to eventually leak the user's credentials.
Also, if someone uses a password manager to store both the password and the OTP credential, that is still an improvement to security. Intercepting (e.g. shoulder surfing) or guessing the password is no longer enough, an attacker needs to get into the password manager's vault.
Re: The Convenience Trap: Why Seamless Banking Access Can Turn 2FA into 1FA
#9For instance on an iPhone, you can register a new face for FaceID if you know the passcode. I stopped here... at least on iPhone, this doesn't work. When a new face is scanned into FaceId, all apps using that FaceId are supposed to (forced to?) re-authenticate.
Re: The Convenience Trap: Why Seamless Banking Access Can Turn 2FA into 1FA
#10> an electronic authentication method in which a user is granted access to a website or application only after successfully presenting two or more distinct types of evidence (or factors) to an authentication mechanism.
and concludes with (emphasis mine):
> For the average user, the smartphone has become a single point of failure, where the theft of one device and one piece of knowledge (the passcode) can lead to total financial compromise.
Looks like 2FA to me, not 1FA.