FIDO2 Authenticator(s)(Single factor) Vs FIDO2 Authenticator(s)(Single factor)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

FIDO2 Authenticator(s)(Single factor) Vs FIDO2 Authenticator(s)(Single factor)

L3 Networker

Hi Experts, Anyone please help me understand the real difference between FIDO2 Authenticator(s)(Single factor) and FIDO2 Authenticator(s)(Single factor). It will be great if you could throw some light by referencing any use case.

 

The CyberArk documentation doesn't clear up the difference and actual use case.

 

Field_Content_versions_oct20__068Vy00001FlmpmIAB.png

8 REPLIES 8

L3 Networker

I struggled with this one recently. The to my knowledge the Multi-Factor version is only related to the "On-Device Authenticator" option. There is a separate checkbox to "Enable On-Device Authenticator" and in the user portal where users can setup factors there would be a separate enrollment option for the on-device authenticator. The single-factor variant is any other FIDO option like a generic security key (even if you use something like a YubiKey BIO that uses fingerprint to complete the FIDO request its still under that single-factor option).

Thanks @Chris Kubiak​  for sharing your experience.

 

when I set the Authentication profile with challange1 = Email OR FIDO2 Authentication(s)(Single Factor) then it authenticate me just by touching the Yubikey it doesn't ask me Yubikey PIN , any idea why is that so. Because when i use the YubiKey to authenticate my Microsoft ecosystem it always ask me to enter PIN and then touch. Why it doesn't behave same with CyberArk.

Take my words with a grain of salt as I only recently started diving into FIDO2\Passkeys.

 

A regular YubiKey can act as a FIDO2 security key, and it can also store Passkeys. My initial thought based on your experience is in Identity you have a FIDO2 authenticator defined (which only requires "user presence", so touch not pin) and possibly in your Microsoft example you have a Passkey defined (which does user verification). IIRC if you have the Yubikey authenticator app that will show you registered Passkeys if my theory holds true you should see one for Microsoft and likely not see an entry for Identity (dont believe FIDO2 authenticators are shown, but been a while since I played with that).

Yes the option is available, By default its called FIDO2 Authenticator, and gives option to rename it, Since I am planning to use yubikey as FIDO2 authenticator, i renamed it to Yubikey. Basically when it allows to Add the Yubikey, It ask you the PIN once. But once setup then during authentication it doesn't ask PIN, You just touch the key and it logs you in. Which is kind of risky from security perspective. Field_Content_versions_oct20__068Vy00001FmFzjIAF.png 

 

Yes, and for the FIDO2 Authenticator option that only requires "user presence" which is why it only requires touch rather than pin.

L4 Transporter

I haven't tested it in practice, but i believe a "FIDO2 multi-factor" device is something like a "Yubikey Bio", which has a fingerprint reader on it.

L4 Transporter

The difference is whether you are using the FIDO2 token as a "universal second factor" (u2f) or requesting the FIDO2 token to actually perform 2 factor authentication within itself.

 

The "factors" are often summarised as 'something you know', 'something you have', and 'something you are'.

 

When challenging a FIDO2 token, the IDP (CyberArk) can request either simple user-presence (typically the user must touch the key to satisfy this) or PIN, or PIN/biometric. If you are using FIDO2 as with just user-presence (single-factor in CyberArk language) then the user is expected to provide some other authentication factor such as password, and will just need to have the token and press the button. The user is only presenting the token itself as a factor (something you have).

 

The much stronger use-case is to use the FIDO2 to completely replace the password in the login process - FIDO2 multifactor in CyberArk language. In this workflow CyberArk will not only test that the FIDO2 token is present but also require the user to use either PIN or Biometric to satisfy the login. The user is thus presenting CyberArk with the token itself (something you have) and either a PIN (something you know) or a biometric (something you are) and has satisfied multi-factor authentication. It's a really powerful approach - both very secure and very easy to use.

L4 Transporter

note that you can also use the TPM in Windows or Mac devices to generate a Passkey which behaves like FIDO2 (multifactor). And a FIDO2 token can also be used as a Passkey, so a great approach is to use Passkey as an alternative to password+2FA. Users love it and it is very strong authn.

  • 100 Views
  • 8 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!