Contoso wants a group of highly privileged administrators to sign in with phishing-resistant passkeys. The authenticator model must be verifiable at registration, and passkeys that sync to a cloud provider such as iCloud Keychain must not be allowed. What should you configure?
Show answer and explanation
Answer: C
Explanation
Attestation verifies the authenticity of the passkey provider or device during registration, and when it’s enforced, relying parties can validate the authenticator model. Attestation is enforced at the passkey profile level, and when it’s enabled, only device-bound passkeys are allowed and synced passkeys are excluded.[1] FIDO2 security keys are recommended for users with elevated privileges, and passkeys in Microsoft Authenticator are another option for them.[1]
A is wrong because Hardware OATH tokens are marked as preview in the article and aren’t in the list of phishing-resistant authentication methods.[2] B is wrong because approving push notifications is traditional multifactor authentication (MFA) that is prone to remote phishing attacks.[2] D is wrong because synced passkeys are phishing-resistant but don’t support attestation, so the authenticator model can’t be validated, and allowing them contradicts the requirement to block synced passkeys.[1]