Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Buyers Now Demand a Vendor Passwordless Authentication Mandate
Transcript
- Lucas: You're seeing a new procurement clause appear in enterprise software contracts, and it's one that would have seemed extreme five years ago. Buyers are now demanding that vendors offer passwordless authentication as a condition of the deal. Luna: Wait — no passwords at all? Or just that they have to offer an alternative? Lucas: The mandate is that the vendor must support FIDO2 or WebAuthn-based passkeys as a primary authentication method. Some buyers are going further and requiring that passwords be completely disabled in the production environment. Luna: That is a big shift. I know the security world has been talking about passwordless for years, but making it a contractual requirement—that's a different level. Lucas: It started getting real in late 2024 after a breach at a major identity provider — I'm thinking of the Microsoft incident that exposed hundreds of thousands of credentials. A CISO at a top five U.S. bank told his procurement team: no more passwords in any new software we buy. That became a template. Luna: So one influential buyer sets a hard line and then it spreads through the industry. Lucas: Exactly. By early 2025, several large financial services firms had standard contract language that said — and I'm paraphrasing — 'vendor must implement passwordless authentication per FIDO2 specification, and must not store or transmit passwords in any form.' If you couldn't meet that, you were disqualified. Luna: What about the software vendors that don't have passwordless yet? I'm thinking of smaller SaaS companies or legacy on-premise players that are still in the middle of a cloud migration. Lucas: They're losing deals. There's a data point from a sales intelligence platform — I've seen it referenced in a few analyses — that says from late 2025 to mid-2026, about 12 percent of enterprise software RFPs included a passwordless clause. And of those, vendors without support saw their close rate drop by roughly 30 percent. Luna: Thirty percent is a big haircut. So this is not a nice to have anymore. It's a table-stakes checkbox. Lucas: It is. And the interesting thing is that the mandate is coming from a specific set of industries first — financial services, healthcare, and critical infrastructure. But it's starting to bleed into mid-market and even some B2B SaaS buyers. Luna: Is there a standard way the clause is written? Or is every company inventing its own language? Lucas: There's a growing consensus around language from the FIDO Alliance and the Identity Theft Resource Center. The typical clause says the vendor must support at least one FIDO2 authenticator, provide a mechanism for users to register and manage passkeys, and ensure that the authentication system is phishing-resistant. Some also require that the vendor undergo an annual audit of their authentication implementation. Luna: And how do you audit an authentication system? That sounds like a pretty specialized skill. Lucas: It is. Usually the buyer hires a third-party security firm to review the vendor's implementation. They look at whether the passkeys are bound to the device, whether the cryptographic keys are stored in hardware-backed secure enclaves, and whether the protocol prevents credential theft even if the server is compromised. The audit can add a month or two to the sales cycle. Luna: So this actually lengthens the procurement timeline. Which is ironic because the whole point of passwordless is supposed to be better user experience and faster onboarding. Lucas: Right. In the short term, it slows things down because the vendor has to prove compliance. But once you're through that gate, the ongoing friction is lower. No password resets, no MFA fatigue, no account lockouts. The trade-off is front-loaded. Luna: Are there any vendors that have embraced this as a differentiator? Like, 'we've been passwordless since day one'? Lucas: A few. One that comes to mind is 1Password — they launched passkey support early and made a big deal about their zero-knowledge architecture. But for most enterprise SaaS vendors, this is a retrofit. They have legacy password-based authentication that's deeply integrated into their product. Luna: Retrofitting a passwordless system into an existing product is not trivial. You have to rebuild the login flow, the session management, the backup and recovery mechanisms. Lucas: Exactly. And that takes engineering time and money. But the alternative is losing enterprise deals. So we're seeing a lot of vendors prioritize this in their 2026 roadmaps. Some are even setting up internal certification programs to shortcut the audit process. Luna: What about the user side? If I'm an employee at a company that just mandated passwordless, do I suddenly lose my old login? Or is there a transition period? Lucas: Almost always a transition. The buyer usually allows a grace period — maybe six to twelve months — during which the vendor must support both password and passwordless. After that, passwords are disabled. The user has to register a passkey, usually via a biometric like Face ID or a hardware security key. Luna: And what happens if someone loses their phone or their hardware key? That's the classic fear with passwordless. Lucas: That's where the backup and recovery clause comes in. The vendor has to provide a way to re-register a new device using a recovery code or an admin-approved process. The FIDO2 spec actually includes a mechanism for multi-device passkeys, so you can have a backup on a tablet or a YubiKey in a safe. Luna: So the infrastructure is there, but it requires the vendor to have thought about it. Which again goes back to the audit — the buyer wants to see that you've designed for recovery, not just checked a box. Lucas: Exactly. And the buyers are sophisticated. They're not just asking 'do you support passkeys?' They're asking 'show me your key management architecture. Show me your recovery flow. Show me your compliance with the FIDO2 spec version 2.1.' Luna: That's a pretty deep technical conversation for a procurement meeting. I imagine the vendor's sales engineers are earning their keep. Lucas: Absolutely. The days of a sales rep just saying 'we have SSO' are over. Now they need to explain cryptographic attestation and hardware-backed key storage. It's raising the technical bar for the whole B2B SaaS sales process. Luna: And I think that's actually a healthy thing. If you're selling security software, you should be able to talk security. But I also think about the smaller vendors who might not have the resources. Is this creating a barrier to entry? Lucas: It could be. If you're a startup with three engineers, implementing FIDO2 from scratch is a heavy lift. But there are third-party libraries and services — like Auth0 or Okta — that offer passwordless out of the box. So the barrier is more about integration effort than capability. Luna: Right. But then you're tied to a third-party identity provider, which some enterprise buyers might also have concerns about. They want to know that the authentication isn't dependent on another vendor that could be compromised. Lucas: That's a real tension. Some buyers actually prefer that the authentication be built in-house, because they see it as core infrastructure. But then you're asking a small SaaS company to become an authentication expert. It's a tough spot. Luna: So what's the forward-looking trend here? Do you think passwordless mandates become universal across all enterprise software within the next three years? Lucas: I think within three years, passwordless support will be a baseline requirement for any enterprise sale above a certain threshold — say, fifty thousand dollars annual contract value. Below that, buyers might be more lenient. But for large deals, it's already becoming standard. Luna: And the interesting thing is that this is being driven by security teams, not IT. CISOs are the ones pushing procurement to add these clauses. IT might be fine with passwords still, but the security folks have seen too many credential-stuffing attacks. Lucas: Exactly. And the credential-stuffing numbers are staggering. One report I saw said that in 2025, over 10 billion credential-stuffing attempts were detected globally. That's a problem that passwords can't solve. Passkeys eliminate that attack vector entirely because there's no shared secret to steal. Luna: It's one of those rare cases where security and user experience actually align. No one likes managing passwords. So the mandate might actually make life better for everyone. Lucas: It's rare to find a win-win in enterprise security. But passwordless might be it. And the procurement clause is the lever that's making it happen. Luna: Speaking of levers — a quick observation. This show is ad-free and listener-supported. A handful of listeners chip in monthly at buy me a coffee dot com slash fexingo, and that's what makes episodes like this possible. So if you find this useful, that's the link. Lucas: Yeah, it's a small group that keeps this going. And we want to keep it that way — no ads, just the conversation. Luna: So back to the topic — do you see any pushback from vendors against these mandates? Or are they mostly compliant? Lucas: Most are compliant because they have to be. But there's some grumbling about audit costs and the engineering effort. I've heard of a few large vendors trying to negotiate down the scope — like 'we'll offer passwordless but only for admin accounts, not all users.' Buyers are generally not accepting that. Luna: It's an all-or-nothing demand. Which makes sense from a security perspective — you're only as strong as your weakest authentication method. Lucas: Right. And the most forward-leaning buyers are already looking ahead to the next step — continuous authentication, where the system verifies the user's identity throughout the session, not just at login. But that's a future episode. Luna: We've got a lot to cover. But for now, if you're a SaaS vendor and you don't have a passwordless roadmap, your enterprise pipeline might be at risk. Lucas: That's the bottom line. The mandate is here, and it's only going to spread. Time to get your keys in order.