Aboubacar Diawara | Senior Product Manager, Workforce IAM
More About This Author >
Aboubacar Diawara | Senior Product Manager, Workforce IAM
More About This Author >
Identity has become the primary attack surface in the enterprise.
Credential theft continues to drive the majority of breaches, and attackers are getting more effective at bypassing traditional defenses. Phishing kits are widely available. Deepfake technology makes helpdesk social engineering all the more convincing. MFA fatigue attacks are easy to execute. MITM techniques can intercept credentials and session tokens in real time. And all of this is only further accelerated by AI, making the same old attack techniques faster, and more effective.
At the same time, organizations are under pressure from regulators to not only adopt phishing-resistant authentication, but to drive 100% adoption and accountability across their workforce and third-party identities. Doing this at an enterprise scale is no easy feat.
The problem usually comes down to balancing convenience (what users actually adopt) and security (what prevents attacks).
Multi-factor authentication (MFA) improved security, but it didn’t fundamentally change the model of authentication.
Most MFA methods still depend on something that can be captured, replayed, or socially engineered, such as:
That leaves gaps:
Even with MFA in place, the system still relies on reusable shared secrets moving across networks and devices that can be intercepted by an attacker.
An organization becomes phishing-resistant by eliminating reusable shared secrets used for authentication, which is what FIDO2 passkeys achieve.
Instead of transmitting credentials:
There’s nothing reusable for an attacker to steal, making it phishing-resistant authentication.
But even within the category of phishing-resistant FIDO2 authentication, there’s a lot to choose from; all having different use cases and benefits.
A device-bound passkey is a FIDO2 credential that is:
A device-bound passkey is cryptographically tied to a single device and cannot leave it. Authentication is then completed by unlocking the device, typically with biometrics, which allows the private key to be used locally.
Device-bound passkeys eliminate the failure points of traditional authentication:
As passkeys have evolved, two models have emerged:
| Device-Bound Passkeys | Synced Passkeys | |
| Storage | Single device | Cloud-synced |
| Security | Very high | High |
| Attack surface | Minimal | Broader |
| Enterprise control | Strong | Limited |
For the scale of enterprise authentication, security and usability are extremely important. But so are governance and control. While synched passkeys are still a good option, most organizations—especially those in regulated industries—can’t tolerate the risk that comes with distributing access across devices and ecosystems.
Enterprise environments operate under different constraints than on an individual basis.
You’re securing:
Which is why assurance, control, and policy enforcement remain a priority at this scale and level of complexity.
Device-bound passkeys with enterprise policy enforcement support that by:
Credentials remain on a single device, limiting where they can be attacked.
They are inherently resistant to phishing, MFA prompt-bombing, and man-in-the-middle (MITM) attacks.
Authentication is tied to both the trusted user and their device, not just a credential.
They align with growing regulatory requirements for phishing-resistant MFA.
Enterprises can enforce which devices and authentication methods are allowed depending on the context of the access event.
Most organizations aren’t enforcing MFA for the first time but rather growing in their MFA maturity. Security teams aren’t ripping and replacing outdated methods, but layering in stronger authentication where it drives the most impact:
At the same time, they still need to support:
SafeNet MobilePASS+ doesn’t just “support passkeys” in a generic sense. It operates as a device-based authenticator and passkey manager, that flexibly offers a range of other MFA methods (i.e. push OTP, PIN verification) depending on risk and access scenario.
This model gives enterprises something they typically don’t get with other passkeys:
In reality, most organizations need to support both:
MobilePASS+ seamlessly connects these two environments, offering convenience to most users who probably have their phone handy. If someone chooses not to—or is unable to—use their phone for authentication, a FIDO2 device might be a more suitable option.
While the industry's reliance on shared secrets is exploitable by attackers, device-bound passkeys are proving to deliver an optimal mix of security assurance and user convenience. Their implementation ensures robust protection and gives individuals greater control. For enterprises operating in regulated or high-risk environments, governance remains equally vital alongside security. As organizations transition to phishing-resistant, passwordless authentication, device-bound passkeys managed by authenticators like MobilePASS+ stand out as the practical and reliable solution.