A hardware security key rollout only works if the keys get activated. The inventory tracks pre-registered keys from provisioning to first login, resolves make, model and certification per key and shows the same view for every synced authenticator your users rely on day to day: iCloud Keychain, Google Password Manager, Windows Hello and more.
Pre-registered keys tracked from provisioning to first login
Vendor and certification resolved per hardware key
Synced authenticators covered in the same view
One inventory answers both
A hardware key program is only as good as its activation rate, and that number is invisible without a way to trace individual keys. Software authenticators need the same visibility for a different reason: which credential manager holds a passkey decides its sync behavior, recovery path and risk posture. When a specific authenticator misbehaves, Passkey Errors shows what breaks and User Debugging shows for whom.
Pre-registered security keys can be tagged at procurement, for example by serial number, and tracked from shipment to first successful login. Certification and transport detail come resolved per key, so a rollout has a real activation rate instead of a shipping count.
The same view covers iCloud Keychain, Google Password Manager, Windows Hello and third-party managers, with credentials and users per row: the inventory is one fleet, not a hardware-only report.
Every authenticator row links to the user journeys behind it, so a stalled activation number becomes a debuggable session in two clicks.
Common questions about tracking the security key and passkey fleet
Procurement wants an activation rate, security wants provenance, support wants context: the inventory answers all three, for hardware keys and every synced authenticator, from one view.