They are complementary rather than interchangeable. Passkeys and PKI both provide phishing-resistant authentication, but different environments may need different authenticators and recovery methods. Organisations should compare them by assurance strength, device compatibility, and recovery model, then standardise the policy layer while allowing multiple approved authenticators.
How phishing-resistant MFA, passkeys, and PKI fit together in practice
They solve the same problem at different layers. Phishing-resistant MFA is the requirement, passkeys are one way to satisfy it, and PKI is one of the underlying trust models that can also support strong authentication. The practical question is not which label wins, but which authenticator, policy, recovery path and device model fit the environment.
That is why teams should compare them by assurance strength, usability, device compatibility and recovery risk rather than treating them as competing product categories. A well-run identity program can support more than one approved authenticator, as long as the policy layer stays consistent and the recovery process does not become the weakest link.
For a deeper primer on the social engineering side of the problem, see Social Engineering Guide, which covers the attack patterns that make phishing-resistant sign-in necessary in the first place.
Where passkeys and PKI overlap, and where they differ
Passkeys and PKI both can deliver phishing-resistant authentication, but they do so through different operational models. Passkeys are usually easier to deploy for end users because the authenticator experience is built into modern platforms and browsers. PKI is often better aligned with managed-device estates, smart cards, hardware tokens, or environments that already have certificate issuance and lifecycle processes.
The real difference is less about “strong vs weak” and more about how authentication is bound to the user, the device and the recovery story. Passkeys may simplify sign-in while shifting attention to device binding, sync behaviour and account recovery. PKI may offer very strong assurance, but it tends to require more careful certificate issuance, revocation and lifecycle management.
If you are comparing rollout options, the most useful baseline is NIST SP 800-63 Digital Identity Guidelines, which frames authenticators by assurance and phishing resistance rather than by brand or implementation style. For organisations building around passkeys specifically, Passwordless and Passkeys Guide explains the rollout and recovery trade-offs, while the MFA Guide is useful when you need to compare passkeys against legacy MFA methods in one policy view.
What standardisation should happen at the policy layer
The right pattern is to standardise the policy and allow multiple authenticators underneath it. In other words, define the assurance target, the enrollment rules, the recovery rules and the step-up requirements once, then let different approved authenticators meet that policy when they are appropriate for a given population or device estate.
That approach avoids a common mistake: forcing every user into one authenticator because the policy team wants simplicity. A single authenticator can become fragile when mobile platforms, shared devices, regulated desktops, privileged users and external users all have different constraints. Standardisation belongs in the rules, not necessarily in the factor itself.
For certificate-backed environments, the CA/Browser Forum is the useful reference point for public trust and certificate issuance expectations, and NIST SP 800-57 Key Management helps when the deployment depends on key lifecycle discipline. In mixed estates, IAM and Identity Provider Buyer's Guide is a practical lens for evaluating how a platform supports SSO, phishing-resistant MFA and recovery without fragmenting governance.
Risk and Threat Considerations
The main risk is not choosing the wrong buzzword, it is building a phishing-resistant front end and leaving recovery, enrollment or fallback paths too weak. If a user can be reset through a help desk workflow, weak proofing, reusable backup codes or an unprotected legacy path, the security gain from passkeys or PKI can be undercut quickly.
Failure mechanism: Attackers target the weakest alternative path, such as account recovery, device re-registration, help desk override or a still-enabled legacy authenticator. Once they control that path, the phishing-resistant factor no longer protects the account.
Impact: The account becomes vulnerable to takeover even though the primary login method is strong. In practice, that can expose sessions, administrative access, downstream applications and any workflows that trust the compromised identity.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, NIST SP 800-57 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | Covers phishing-resistant authenticators, assurance levels and recovery choices. |
| Recommendation — Use assurance levels to compare passkeys and PKI, then set enrollment and recovery rules accordingly. | ||
| NIST SP 800-57 | Key Management Recommendations | Applies when PKI depends on key lifecycle, cryptoperiod and revocation handling. |
| Recommendation — Define key lifecycle, renewal and revocation processes for certificate-backed authentication. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Covers lifecycle control of authenticators, recovery and replacement paths. |
| IA-2 — Identification and Authentication (Organizational Users) | Applies to workforce sign-in assurance when choosing phishing-resistant methods. | |
| Recommendation — Manage authenticator issuance, replacement and recovery under a controlled lifecycle. Require strong organizational-user authentication for the chosen sign-in methods. | ||
Practitioner Guidance
What to prioritise: Define the assurance target first, then decide whether passkeys, PKI or both can meet it for each user population. Workforce users, privileged users and constrained-device users often need different approved authenticators even when the same policy applies.
What to verify: Test the recovery path, not just the sign-in path. A phishing-resistant authenticator is only as strong as the process used to replace a lost device, re-enrol a user or override a lockout.
Trade-off: Passkeys usually reduce user friction, while PKI often gives you more explicit lifecycle control and better fit for managed hardware estates. The best choice is the one that fits the operating model without creating a brittle exception process.
Practitioner takeaway: Treat phishing resistance as a policy outcome, not a single factor choice, and make sure your fallback and recovery controls are strong enough to preserve that outcome.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org