Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Buyers Now Demand a Vendor CISO Reference Call
Transcript
- Lucas: So there's a new line item showing up in enterprise procurement checklists, and it's not a document. It's a person. Specifically, a phone call with the vendor's Chief Information Security Officer. Luna: I've heard whispers about this. Buyers want to talk directly to the CISO before they sign? Not just read the SOC 2 report? Lucas: Exactly. And it's not a courtesy chat. These are structured, often adversarial calls where the buyer's security team grills the vendor CISO on specific controls. I'm tracking a case from Q2 this year — a large healthcare system was evaluating a cloud-based analytics platform, about two point four million dollars in annual recurring revenue. The deal fell apart after the CISO call. Luna: What happened? Did the CISO fumble a technical question? Lucas: Two questions, actually. First, the buyer asked where exactly their data would reside at rest — not just 'US regions,' but which specific data centers, and whether any replicas would be stored outside the continental US. The vendor CISO gave a vague answer about 'AWS US East' and couldn't commit to no cross-border replication. Second question: how often do you run full-scope incident response tabletop exercises, and who participates? The CISO said 'quarterly' but couldn't name which business units were included. The buyer's security lead told me later they lost confidence because the CISO wasn't operationally granular enough. Luna: That's brutal. But also — isn't this what the security questionnaire is supposed to cover? Why the call? Luna: I mean, questionnaires can be gamed. A CISO who's been through a real incident sounds different from one who's just reviewed a deck. Lucas: That's exactly the argument buyers are making. The National Institute of Standards and Technology actually published guidance last year on 'executive-level vendor security interviews' — they recommend them for any contract above a certain risk threshold. And I'm seeing it in practice with Fortune 500 companies in financial services, healthcare, and critical infrastructure. Luna: So what are the four questions you mentioned? Lucas: First: data residency, down to the provider and region. Second: incident response testing frequency and scope. Third: how the vendor handles sub-processor risk — meaning if you use a third-party AI model or a cloud provider, what's your oversight? Fourth: what's your vulnerability disclosure program and average patch time for critical CVEs? If the CISO can't answer those four with specifics and a straight face, the deal is at risk. Luna: Interesting. I wonder if this trend started with that big breach at the cloud HR platform in 2025 — the one that exposed payroll data for dozens of companies. Lucas: You're right on. That was a turning point. The vendor had excellent SOC 2 reports and a glowing security questionnaire, but their CISO was a part-time consultant who wasn't involved in day-to-day operations. When the breach happened, the buyer's security teams realized they'd never actually spoken to the person responsible. Now, procurement departments are mandating that the CISO be a full-time employee and agree to a reference call. Luna: That's a big shift. Especially for startups where the CISO might be the CTO wearing a second hat. How are vendors supposed to prepare? Lucas: The honest answer is: get your CISO ready to talk operations, not just policy. I've seen vendors create a one-page playbook with specific answers to those four questions, backed by evidence. For example, 'We use AWS us east-1 and us-east-2 only, with no cross-region replication. Here's our last tabletop exercise report from May, which included engineering, product, and legal.' The CISO should bring concrete examples. And if your CISO is also the VP of Engineering, you need to be upfront about that — buyers actually respect honesty more than a slick title. Luna: I can see that working. But I also wonder: is this just another barrier for small vendors? A startup might not have a dedicated CISO at all. Lucas: It is a barrier, no question. But the buyers I've talked to say they're willing to work with smaller vendors if the ciso equivalent — even if it's the founder — can demonstrate genuine depth. One procurement VP told me she'd rather talk to a founder who built the infrastructure herself than a hired CISO who read a script. The key is authenticity and specificity. Luna: So the bar is higher, but it's not impossible. What about the cost of all this? Every hour a CISO spends on reference calls is an hour not spent on actual security. Lucas: That's a fair trade-off question. But the counterargument is: if a reference call prevents a bad deal that leads to a breach, it's net positive. And vendors are starting to specialize their sales process — some have a dedicated security sales engineer who handles the technical deep dive, and the CISO only joins the most strategic calls. That's what I'm seeing at companies that close large enterprise deals efficiently. Luna: Right. So the CISO call becomes a signal of seriousness, not just a hurdle. Lucas: Exactly. And one more thing — the buyer side is also evolving. Some companies are now requiring a CISO reference call from the vendor's own customers, not just the vendor's CISO. They want to talk to a peer who's been through an incident with that vendor and can speak to how the CISO handled it. Luna: That's next-level. Almost like a reverse reference check. Lucas: It is. And it's happening. I know of a large bank that, during due diligence for a SaaS contract, asked the vendor for a list of three customers who had experienced a security incident in the past two years. They called those customers and asked directly about the vendor's response time, transparency, and remediation. Luna: Wow. That's pretty invasive. But I can see why — if you're trusting your critical data to a vendor, you want to know they've been tested. Lucas: Exactly. And that's the through line here: enterprise buyers are shifting from checking boxes to stress-testing people. The CISO call is just the most visible manifestation of that trend. Luna: I want to talk about the legal side for a second. Is there any liability risk for the CISO in these calls? If they misspeak about a control, could that become part of a lawsuit later? Lucas: Great question. Yes, absolutely. Some vendors are now including a disclaimer at the start of the call — something like 'This conversation is for informational purposes and does not create contractual obligations beyond what's in the MSA.' But smart buyers push back on that because they're trying to establish a record. The CISO needs to be trained to avoid making promises they can't keep. For example, saying 'We guarantee 99.99 percent uptime for our API' when the SLA says 99.9 percent — that's a problem. Luna: So it's a delicate dance. You need to be transparent and specific, but also legally careful. Lucas: Right. And that's why some vendors are starting to send a security attorney or a sales engineer alongside the CISO to handle the contractual language. But buyers are wise to that too — they want to hear from the CISO, not the lawyer. Luna: It's like a whole new skill set for security leaders. Not just technical chops, but sales acumen and legal awareness. Lucas: Absolutely. And I think we'll see more ciso as buyer advocate roles emerge. Actually, I know of a consulting firm that now offers 'ciso for hire' specifically for pre-sales calls. They prep a seasoned CISO to represent the vendor for a fixed fee per call. It's a new mini-industry. Luna: That's fascinating. So the market is adapting. Vendors who can't afford a full-time CISO can still compete. Lucas: Exactly. And the best part is, it forces everyone to raise their game. If you're a vendor and you know your CISO is going to be on the line, you're going to make sure your security practices are actually solid, not just documented. Luna: It's like the ultimate accountability mechanism. I imagine the CISO call is going to become standard in most enterprise deals within the next year or two. Lucas: I think so too. And it might eventually replace the SOC 2 report as the primary trust signal. Because a report is static, but a conversation reveals how the CISO thinks under pressure. Luna: Let's take a quick step back. For our listeners who are building or selling B2B SaaS, what's the one actionable takeaway from today? Lucas: If you haven't already, start preparing your CISO — or your security lead — for a structured buyer interview. Draft answers to the four questions I mentioned. Run a mock call with a friendly buyer. And if you don't have a dedicated CISO, consider hiring a fractional one who can speak with authority. The era of the checkbox security questionnaire is ending. The era of the security conversation is here. Luna: I love that framing. And I think it's a good moment to mention — if this conversation was useful to you, if it helps you think about your own sales process or procurement strategy, the reason episodes like this stay ad-free and independent is listener support. You can buy us a coffee at buy me a coffee dot com slash fexingo. It's a small gesture that keeps these conversations going. Lucas: Yeah, that really does make a difference. Every contribution helps us dedicate time to digging into topics like this one. So thank you to those who've already supported. Luna: Now, back to the CISO call trend — I want to ask about the buyer's perspective. Are these calls also helping buyers improve their own security posture? I imagine they learn a lot from asking tough questions. Lucas: Absolutely. I've heard from security teams that they benchmark their own practices against what vendors' CISOs describe. If a vendor says they do weekly vulnerability scans and the buyer only does monthly, it sparks an internal conversation. So there's a spillover effect. Luna: That's a nice unintended consequence. The whole ecosystem gets smarter. Lucas: Exactly. And I think that's why this trend is sticky. It's not just a procurement hoop — it's actually making everyone better at security. And that's ultimately good for business. Luna: Couldn't agree more. Thanks for breaking this down, Lucas. Lucas: My pleasure. If you're a CISO listening, I'd love to hear how your reference calls are going. Reach out to us on the Fexingo network. And for everyone else, see you next time.