Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why RFPs Now Ask Vendors About Their Software Supply Chain
Transcript
- Lucas: Luna, I was reading through a recent RFP from a regional hospital network, and there it was, buried in the security section: a request for a software bill of materials, and they wanted it in SPDX format. Luna: An SBOM. That's not exactly standard procurement fare. What does a hospital network care about a software inventory list? Lucas: That's the thing. It's becoming standard. This hospital had a whole subsection on software supply chain transparency, and they wanted the SBOM updated quarterly. Ten years ago, nobody in procurement even knew what that was. Luna: So what's driving this? Is it just the security folks getting louder, or is there something else? Lucas: I think you can trace a direct line to the 2021 executive order on cybersecurity, the one that came after the Colonial Pipeline hack and the SolarWinds mess. It required federal agencies to demand SBOMs from their vendors, and that sent a signal through the whole market. Luna: Right, and public sector requirements have a way of leaking into the private sector. I've seen that with things like SOC two, where it started as a government thing and now every enterprise expects it. Lucas: Exactly. And it's not just the big banks and tech giants. I talked to a mid-sized CRM vendor last week, and they lost a healthcare deal because their SBOM listed an old logging library with known vulnerabilities. The procurement team used the SBOM as a screening tool. Luna: Ouch. So they didn't even get to the demo. That's a concrete example of what used to be a checkbox item now becoming a deal-breaker. Lucas: And the interesting part is how they're using them. It's not just checking for the presence of an SBOM. They're actually scanning them, looking for outdated components, known CVEs, even comparing dependency lists across vendors. Luna: So it's like a nutrition label for software. You can see what ingredients went in, and if there's something you don't like, you put it back on the shelf. Lucas: That's a good analogy. And the format matters too. The most common standards are SPDX and CycloneDX. If you show up with a PDF, that's not an SBOM, that's a brochure. Luna: Now you've got me thinking about the practical side. If I'm a startup selling to enterprises, how do I even produce one of these things? Lucas: So there are tools like Syft and FOSSA that can generate SBOMs automatically from your codebase. It's not a manual exercise. You configure the tool, it scans your dependencies, and spits out a machine-readable file. Luna: But is it really that easy? Because I've seen SBOMs that are a mile long and nobody reads them. Lucas: That's the key point. The value isn't in the SBOM itself, it's in how you maintain it. Procurement teams aren't just looking for a snapshot. They want to see that you have a process to update it as your software evolves. Luna: So it's about the process, not the artifact. That's a subtle but important distinction. Lucas: And that's where a lot of vendors fall short. They generate an SBOM once, send it off, and never think about it again. But the enterprise is going to ask, how often do you update it? What happens when a new CVE comes out? Do you have an automated pipeline? Luna: It's like the difference between having a fire escape plan and having a fire drill. One is a document, the other is a culture. Lucas: That's a great line. And by the way, this is exactly the kind of thing that keeps our conversations on the show possible. A small group of listeners chips in monthly through buy me a coffee dot com slash fexingo, and that literally funds us making these deep dives. No ads, no sponsors, just listener support. Luna: And we're glad to keep it that way. It means we can talk about things like SBOMs without having to spin them into a product pitch. Lucas: Exactly. So coming back to that hospital RFP, they didn't just ask for the SBOM. They also wanted to know how we handle known vulnerabilities. And that's where the conversation gets really interesting. Luna: Because an SBOM is just a list. The real question is what you do with it. Lucas: Right. So we're seeing RFPs that ask for a vulnerability management policy, a remediation SLA, and sometimes even a history of how you've handled past incidents. It's no longer enough to say you care about security. Luna: So it's like a personal credit check, but for software. They want to see your payment history before they trust you with a loan. Lucas: Exactly. And this is where the SBOM connects to the broader trend we've been covering on the show. Remember the episode about vendor security questionnaires? The SBOM is becoming a standard part of that questionnaire. Luna: So it's not replacing the questionnaire, it's augmenting it. It gives procurement a data point they can actually verify. Lucas: And verify is the operative word. With an SBOM, they can check if a vendor is using a component with a known CVE, and they can do that without relying on the vendor's self-assessment. Luna: That's a power shift. Procurement is no longer just taking your word for it. Lucas: And it's a shift that's happening across industries. I was talking to a procurement officer at a manufacturing firm, and she said she now runs every SBOM through a vulnerability scanner before even scheduling a tech demo. Luna: What percentage of vendors do you think are prepared for that? I'm guessing it's not the majority. Lucas: From what I've seen, maybe one in three. The rest are either scrambling to generate an SBOM on the fly or they don't even know what one is. Luna: So there's a real opportunity for a vendor to stand out by just having their act together on this front. Lucas: Absolutely. And it's not just about winning deals. Some of the larger enterprises are starting to require SBOMs in their ongoing vendor risk management programs. So if you're not on the ball, you might get cut from the approved vendor list. Luna: That's a strong incentive. So what's your advice for a SaaS founder listening to this? Where should they start? Lucas: First, don't panic. Start by mapping your dependencies. Tools like Syft can scan your codebase and generate an SBOM in minutes. Then, set up a process to update it on a regular basis, ideally as part of your CI/CD pipeline. Luna: And if you don't have a CI/CD pipeline, that's a whole other conversation. Lucas: Right, but the point is to treat the SBOM like any other piece of engineering output. It needs to be maintained, versioned, and reviewed. It's not a one-time compliance exercise. Luna: So a living document, not a dead one. And that's what enterprises want to see. Lucas: And the best part is, it's not just for them. A good SBOM process can help your own team catch vulnerabilities earlier, which is good for your product and your customers. Luna: So it's a win-win. You're not just checking a box, you're actually improving your security posture. Lucas: Exactly. And that's what I think we'll see more of as this becomes the norm. The companies that embrace it will be the ones that come out ahead, and the ones that ignore it will find themselves locked out of enterprise deals. Luna: I'm curious if you think we'll see any pushback. Some vendors might argue this is too burdensome. Lucas: There's always pushback, but the trend is clear. The federal government is already requiring it, and the private sector is following. It's not a matter of if, it's a matter of when it becomes table stakes. Luna: So the sooner you get on board, the better. And for our listeners who are already selling to enterprises, this is your chance to get ahead of the curve. Lucas: And for the procurement folks out there, keep asking for it. You're driving the change. Luna: Well, this has been a great deep dive. I walk away with a clear picture of why the SBOM is becoming a deal-breaker, and what to do about it. Lucas: Same here. And if you want to keep these conversations going, you know where to find us. We'll be back next week with more on the business of software.