Security Risks and Best Practices for Passkey Authentication in Enterprises
Passkeys are emerging as a modern alternative to traditional passwords, offering a more secure and user-friendly authentication method by leveraging cryptographic key pairs tied to user accounts. Unlike passwords, passkeys are resistant to phishing attacks and cannot be easily stolen or reused, as they are typically stored locally on a user's device and accessed through biometric or device-based authentication. Major organizations and technology providers, including those aligned with the FIDO Alliance, are promoting passkeys as a next-generation security solution. However, the implementation of passkeys introduces new considerations, particularly regarding how they are stored and synchronized across devices. There are two primary types of passkeys: device-bound, which remain on a single device or hardware security key, and synced passkeys, which are stored in consumer cloud services such as iCloud or Google Cloud and synchronized across multiple devices for convenience. While synced passkeys improve usability and account recovery for consumers, they introduce significant security risks for enterprises. If an attacker compromises a user's cloud account or abuses account recovery processes, they can authorize new devices and gain access to enterprise resources, undermining the integrity of the authentication system. Additionally, if employees use personal cloud accounts on corporate devices, passkeys may be inadvertently synced outside the organization's security perimeter, greatly expanding the attack surface. Attackers can also exploit help desk and account recovery workflows to copy protected keychains to unauthorized devices. Furthermore, adversary-in-the-middle (AiTM) attacks and malicious browser extensions can manipulate WebAuthn requests, force authentication fallbacks, and potentially leak credentials or one-time codes. Security experts and organizations such as the FIDO Alliance and Yubico recommend that enterprises mandate device-bound passkeys, preferably stored on hardware security keys, to maintain higher assurance and administrative control. Enterprises evaluating passkey deployments must carefully assess the risks associated with synced passkeys and implement policies that restrict their use in favor of more secure, device-bound alternatives. The adoption of passkeys should be accompanied by robust administrative controls, user education, and careful integration with existing identity and access management systems. Organizations must also review and strengthen their help desk and account recovery procedures to prevent attackers from exploiting these channels. As passkeys become more widely adopted, ongoing vigilance and adaptation of security practices will be essential to fully realize their benefits while minimizing new risks. The transition to passkey-based authentication represents a significant shift in enterprise security strategy, requiring both technical and operational adjustments. Ultimately, the effectiveness of passkeys in protecting enterprise assets depends on thoughtful implementation and a clear understanding of the associated risks and mitigations.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
1 event from the most recent confirmed update back to the earliest known activity.
Story first reported
Initial story creation
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
2 references tracked. Mallory keeps watching after this page renders.
See the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


