Webauthn (Passkeys) are only going to become more important in the future and as this grows, deployments with higher security risks and criticality are going to need to start to understand and embrace attestation of their keys.
In their current form, almost all software products and IDM’s today allow you to enroll any cryptographic authenticator. It doesn’t matter what make or model it is, it will be allowed.
However, not all authenticators are made equal. They each have different properties, security features, and some even have security issues affecting their hardware or software. Because webauthn is a self contained multiple factor authenticator, this means we need to be even more careful to ensure these devices are secure.
It is possible to restrict FIDO2 keys enrollment by their AAGUIDs. Not something the general public will encounter, but a business using FIDO2 keys as their MFA can limit which hardware can be used, for example limit the enrollment to specific AAGUIDs from Yubico
https://support.yubico.com/hc/en-us/articles/360016648959-YubiKey-Hardware-FIDO2-AAGUIDs
That’s something I had to look into when configuring our Azure environment.