Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / RFPs Now Ask Vendors About Their Open Source Dependency Policy
Transcript
- Lucas: So Luna, I was prepping for this episode and I pulled up a recent RFP from a global manufacturing firm — twelve pages of security and compliance questions — and there it was, tucked between data residency and incident response: a full section on open source dependency policy. Luna: Not just asking for a list of dependencies, but an actual policy on how they manage them. Lucas: Exactly. Questions like: do you maintain an inventory of all open source components? How do you track vulnerabilities? What's your patch SLA for critical issues? And then the kicker: what is your policy for contributing fixes back upstream? Luna: The upstream contribution question is interesting. That feels like a deeper philosophical ask than a typical vendor questionnaire. Lucas: It is, and it's a signal that procurement teams have gotten a lot more sophisticated. They understand that a vendor's open source posture is a direct indicator of their engineering maturity and their ability to respond to emerging threats. Luna: Can you trace when this shift really started? I mean, open source has been in enterprise software for decades. Lucas: I'd point to two moments. The first was the Log4j vulnerability in late 2021 — that was a wake-up call for everyone. Here's this ubiquitous logging library, and suddenly every Java-based application in the world was exposed. Enterprises realized they had no idea what was actually running inside their vendors' products. Luna: And the second? Lucas: The XZ Utils backdoor attempt in early 2024. That was a supply chain attack on a compression library used everywhere. It showed that even the most trusted open source projects could be compromised. So now procurement isn't just checking if you use open source — they want to know how you're governing it, how you're securing it, and how you're participating in the ecosystem. Luna: So how does a typical SaaS vendor even answer that first question about inventory? I feel like most companies have a spreadsheet, at best. Lucas: That's exactly the problem. I talked to a mid-market SaaS vendor last month — they lost a seven-figure deal because they couldn't produce a comprehensive dependency list. Their engineering team had been using open source libraries for years, but they had no automated system to track them. The RFP asked for a software bill of materials, an SBOM, and they had to admit they didn't have one. Luna: Ouch. And that's a deal-breaker now, even for a mid-sized company? Lucas: For this buyer, absolutely. They were a critical infrastructure provider, and their own customers were asking them for SBOMs. So they needed assurance that their vendors could provide the same. It's a cascading requirement — if you sell to regulated industries, your customers' customers are demanding this data. Luna: So what are the specific RFP sections that are now common? You mentioned inventory, vulnerability tracking, patch SLA, and upstream contribution. Are there others? Lucas: Yeah, a few more. They often ask about license compliance — how you ensure you're not using GPL code in a way that triggers copyleft obligations. They ask about your process for evaluating new open source dependencies before adoption. And they ask about your incident response plan specifically for open source vulnerabilities — how quickly can you remediate if a critical CVE is disclosed? Luna: That's a lot of detail. But I'm curious — do procurement teams actually have the expertise to evaluate these answers? I mean, a lot of these are technical and nuanced. Lucas: Some do, some don't. That's where third-party assessors and security rating firms come in. But even if the procurement person isn't a security expert, they're using these questions as a screening tool. A vendor that can't articulate a clear policy — even at a high level — gets flagged. And in a competitive evaluation, that's often enough to push them to the bottom of the pile. Luna: So it's more about the signal than the substance sometimes. Lucas: Right. If you can't explain how you handle open source dependencies, the buyer assumes you're not handling them well. And given the stakes — we saw with Log4j that a single vulnerable library can compromise millions of applications — they're not willing to take that risk anymore. Luna: I also wonder about the upstream contribution piece. Is that a fair metric? A small vendor might rely on open source but not have the resources to contribute back. Lucas: It's a fair question, and I think it's less about expecting every vendor to be a major contributor, and more about whether they're acting as a responsible member of the ecosystem. For instance, do they report vulnerabilities they find? Do they participate in security mailing lists? If they fork a project, do they track upstream fixes? Luna: So it's a proxy for long-term sustainability. A vendor that only consumes open source without giving back might not have the internal alignment to stay on top of security updates. Lucas: Exactly. And there's a practical angle too: if a vendor contributes fixes upstream, they're more likely to be aware of the latest security patches and more likely to integrate them quickly. It's a sign that they're integrated into the community, not just using it as a free lunch. Luna: I've been in sales cycles where the technical evaluation team asks about this, but now it's in the formal RFP. How much weight does it really carry in the final decision? Lucas: I'd say it's become one of the top three technical risk factors, up there with data security and compliance. Enterprises are aware that software is a chain — and open source is a huge part of that chain. They want to know that every link is strong. Luna: Makes sense. And if a vendor can show a mature open source governance program, that could be a differentiator, not just a checkbox. Lucas: Exactly. In fact, I've seen vendors who proactively include their open source policy in their security whitepaper, even before it's asked. That sends a strong signal — it shows they're thinking ahead, they're transparent, and they understand the buyer's concerns. Luna: So what should a vendor do if they're behind on this? Let's say they don't have an SBOM, they don't have a clear policy, and they're facing an RFP next month. Lucas: Start with the basics. First, inventory everything — use automated tools to generate an SBOM for every product you sell. There are open source tools that do this. Second, establish a vulnerability monitoring process — set up alerts for CVEs affecting your dependencies. Third, define a response SLA — for critical vulnerabilities, maybe 72 hours to patch or have a mitigation plan. And finally, be honest in the RFP. If you're still building your program, say that, but show you have a roadmap. Luna: And that honesty actually aligns with the whole transparency trend we've seen in enterprise procurement — they value candor over a perfect but fictional answer. Lucas: Absolutely. The buyer knows that every vendor has some gaps. What they're looking for is awareness and a credible plan to close them. And that's something any vendor can develop, regardless of size. Luna: It's funny, because this whole conversation reminds me of the ecosystem we're in — we rely on open source for our own platform, and we have to stay on top of these same issues. And that's part of why we keep these conversations going. Lucas: Yeah, and that's actually a good segue. We run this show ad-free, and it's listener support that keeps it that way. If you're getting value from these episodes, you can support us at buy me a coffee dot com slash fexingo. It's a small gesture, but it goes a long way in keeping the podcast sustainable and independent. Luna: And we genuinely appreciate it — it allows us to dive deep into topics like this without worrying about sponsors. But back to open source dependencies. Lucas: Right. So one area we haven't touched on is how this policy affects the actual sales cycle. We talked about the lost deal, but I've also seen vendors use their open source governance as a competitive weapon in late-stage negotiations. Luna: How so? Lucas: When you're in a bake-off with two other vendors, and you're the only one that can provide a complete SBOM and a clear contribution policy, that's a tangible differentiator. It shows engineering discipline, and it directly addresses a top-risk area for the buyer. I've seen procurement teams actually reduce the scope of the security review because they trusted the vendor's answers. Luna: So it can shorten the sales cycle, not just prevent a loss. Lucas: Exactly. And that's a big deal in enterprise software where cycles can stretch on for a year. Any way you can accelerate trust is a win. Luna: Let's zoom out for a second. Is this trend likely to continue? I mean, are we going to see even more granular questions in the future? Lucas: I think so. We're already seeing questions about AI model dependencies — which open source models are you using, and how are you tracking their vulnerabilities? That's a natural extension. And as more software moves to the cloud, the supply chain becomes even more complex. So I'd expect procurement teams to keep digging. Luna: It seems like the bar keeps rising for SaaS vendors. Lucas: It does, but it's also an opportunity. Vendors that embrace this — that treat open source as a first-class part of their risk management — they're going to stand out. The ones that see it as a checkbox are going to keep losing deals. Luna: I'm curious about the role of standards like SPDX or CycloneDX. Are those becoming de facto requirements? Lucas: Definitely. CycloneDX is pretty much the standard for SBOMs now, and many RFPs will specifically ask for an SBOM in that format. SPDX is more common for legal compliance — license expressions. So if you're not generating SBOMs in these formats, you're going to fail the technical review quickly. Luna: And what about the open source licenses themselves? Are we seeing more scrutiny there? Lucas: Yes, especially with the rise of permissive licenses and some recent shifts. We saw the Elastic and MongoDB moves from open source to source-available licenses, which raised eyebrows. Buyers now want to know if a vendor's critical dependencies are on licenses that could be revoked or changed. That's a real business risk. Luna: So it's not just about security — it's about legal and business continuity. Lucas: Exactly. And that ties back to the broader trend of vendor risk management becoming more holistic. Open source dependency policy is one piece of a larger puzzle that includes financial stability, security practices, and AI governance — all things we've covered in past episodes. Luna: It's like enterprises are trying to see the entire supply chain in one lens. Lucas: And that's the direction we're heading. If you're a vendor, the time to get your open source house in order is now, before the RFP lands in your inbox.