• Ideas General

  • FIDO2 support (example Yubikey)

Will 2FA with hardware keys like Yubikey supported in the near future?

    Good morning Nico,

    Sounds like a plan. Instead of fingerprint for example or to replace the hand scanner?

    bunq 🌈 always love to surprise​ their users so, unfortunately that also means that bunq won't give us a hint on what is coming in the future.

    But the more bunqers will give High Five 👐🏼... the bigger the chance.

    For those who dont know what a Yubikey is: https://vimeo.com/271185452

    ​

      I think its one of the most secure 2FA solutions at this moment. Hope it will be implemented.

        3 months later

        @Klaas-Magenta-Dragon#114333 I'd personally like to see one with type-c only + NFC for mobile (which is also supported by iOS since some time I think) :)

          I prefer the NFC type also! 👌🏻

            I prefer the NFC type also! 👌🏻i have that key already and easier for daily use

              16 days later

              Would love to see this feature soon :)

                Nu op account van me vrouw werkt handherkenning niet meer. Zie graag FIDO2/2FA als extra verificatie. Dit in plaats van verificatie doormiddel van Sofort storting(wij hebben allebij geen andere bank dan bunq).

                  This would be really nice 😁👍

                    Great idea, huge +1 from me. A W3 standard for using these keys on the web has been published recently and big services such as Dropbox or Github already support them. I expect that these keys will become more popular and supersede 2fa apps and SMS eventually

                      21 days later

                      It would be awesome if it was possible to use a FIDO2 authenticator as a supplementary Authorization for Transactions (via App or API with Key). I really would prefer a real 2FA solution for SCA, esp. when authorizing transactions, instead of a single-app-solution which is not really two factors (a two-app-solution is not much better). I like the German chipTAN generator model, but FIDO2 also would be awesome. (It does not support displaying of transaction data like chipTAN generators, but on the other hand it is a standardized protocol and convenient.) Would at least be a really nerd-friendly optional factor.

                        I use a YubiKey to authenticate on some services on my laptop. But the only reason is because it is the only standard (FIDO2) that is kind of cross browser and platform. On phone apps you should be able to verify the user with a very high confidence by mixing input (PIN, password) + biometrics (fingerprint, face ID, iris scan etc...) + location info. All the necessary sensors and data are there, you just need to make good use of them. The only real advantage I can see is having a single (hardware FIDO2) key that can be used everywhere and regardless if the phone was reset or not (in which case you have to set the biometric stuff again).

                        Plus some Android phones can now be used as FIDO2 security keys (https://fidoalliance.org/news-your-google-android-7-phone-is-now-a-fido2-security-key/). So having another FIDO2 key feels like... having a security key for the security key?

                        But this is just my opinion. Please correct me if I said anything that doesn't make sense :-)

                          The Yubikey should not replace an existing process but "add" a higher security level, if user want that. For example transactions with amounts over 10.000 Euro or something like that.

                            a month later

                            @grossartig#130352
                            Whatever you do: you have to give the 1st posting in this thread a high five.

                              8 months later

                              @bunq kan deze functie in v3 Kommen als toevoeging aan voor wachtwoordzin, handtekening. En voor de e-mail en sms codes

                                2 months later

                                @bunq kunnen we dit er bij krijg ik vind de linkjes in de email niet echt een goede oplossing