FCP FIDO Attestation and Metadata

Question 1

What is the primary purpose of attestation in FIDO2/WebAuthn?

Accepted Answer

To prove the authenticity and integrity of an authenticator to a relying party

Answer

To verify the identity of the user during login

Answer

To encrypt the public key during credential registration

Answer

To validate the relying party's domain against a whitelist

Question 2

Which of the following is NOT a standard attestation statement format defined in WebAuthn?

Accepted Answer

OAuth attestation

Answer

Packed attestation

Answer

TPM attestation

Answer

FIDO U2F attestation

Question 3

What does the FIDO Metadata Service (MDS) primarily provide to relying parties?

Accepted Answer

Metadata statements describing authenticator properties, certifications, and trust anchors

Answer

A directory of registered FIDO relying parties and their policies

Answer

Real-time credential revocation status for individual user accounts

Answer

A certificate revocation list for compromised user identities

Question 4

What is a WebAuthn attestation statement?

Accepted Answer

A data structure signed by the authenticator proving its identity and the binding of the new credential

Answer

A cryptographic signature from the relying party server confirming successful registration

Answer

A user consent record stored in the authenticator's secure enclave after registration

Answer

A JSON Web Token issued by the FIDO Alliance after successful certification

Question 5

What does 'none' attestation convey in WebAuthn?

Accepted Answer

No attestation information is provided, making it impossible to verify the authenticator's origin

Answer

An error state indicating the authenticator failed its self-test before attesting

Answer

A deprecated format that has been replaced by packed attestation in modern deployments

Answer

An attestation type reserved exclusively for platform authenticators built into devices

Question 6

What role does an Attestation Certificate Authority (CA) play in FIDO?

Accepted Answer

It signs attestation certificates embedded in authenticators, forming the root of a verifiable trust chain

Answer

It issues TLS certificates for FIDO relying parties to authenticate to users

Answer

It manages the lifecycle of individual user credentials stored in cloud HSMs

Answer

It encrypts FIDO protocol messages exchanged between the client and the relying party server

Question 7

Which of the following fields is typically found in a FIDO Metadata Statement?

Accepted Answer

Authenticator AAGUID, supported cryptographic algorithms, and attestation root certificates

Answer

User credentials and their associated public keys for a given relying party

Answer

Relying party domain names and their per-site authentication security policies

Answer

Session tokens, their associated scopes, and their expiration timestamps