🤖 AI Summary
This study addresses the lack of secure portability and disaster recovery mechanisms for device-bound credentials by proposing Vaulted Passkeys. The architecture prevents plaintext private key exposure through decoupled registration and export workflows, a role separation model, and dedicated key derivation. Furthermore, it enables secure credential migration by integrating HKDF-based key separation, AEAD configuration, and device-bound encrypted envelopes. A prototype implementation validates the feasibility of this approach, accompanied by a comprehensive threat analysis and a falsifiable evaluation plan. Collectively, this work effectively bridges the critical gap in secure recovery mechanisms for hardware authenticators, offering a robust solution for managing device-bound credentials without compromising their underlying security guarantees during transfer or restoration processes.
📝 Abstract
Hardware authenticators deliberately resist private-key extraction, yet replacement, disaster recovery, and controlled migration create a legitimate need for portability. Existing guidance for device-bound credentials commonly reduces recovery risk by registering an additional authenticator before failure. That creates an independent credential registration and requires replacement hardware to exist in advance; it is redundancy, not a backup of the original credential. This paper addresses the resulting recovery gap by exporting protected credential state while the source is available and restoring it to hardware acquired later, without cloning a complete authenticator or exposing plaintext private keys to routine desktop software. We propose Vaulted Passkeys, a device-bound architecture in which a random 256-bit Kvault protects authenticated PKV1 credential envelopes through HKDF-separated keys and four explicit AEAD profiles. The design separates enrollment from export/import and the required vault from optional identity. We contribute a role-separated system model, wire format, threat analysis, implementation mapping, and falsifiable evaluation plan. The prototype demonstrates feasibility but is neither a formal security proof nor a proposed final standard.