Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Buyers Now Demand a Vendor SBOM
Transcript
- Lucas: Luna, I have been watching enterprise RFPs for over a decade, and I have never seen a requirement spread as fast as the Software Bill of Materials mandate. It has gone from a niche cybersecurity concept to a deal-breaker in about eighteen months. Luna: And I think a lot of SaaS founders still hear 'SBOM' and think it is something only defense contractors need to worry about. But that is changing fast. Lucas: It is. Let me give you a concrete example. A mid-market cybersecurity vendor — sixty employees, strong product, decent revenue — was up for a two-point-four-million-dollar contract with a large healthcare system. The deal was essentially won. Then the buyer's procurement team asked for an SBOM within 48 hours. Luna: And the vendor couldn't deliver? Lucas: They had never generated one. They scrambled, tried to piece something together from their CI/CD pipeline, but it was incomplete. They lost the deal. The buyer went with a competitor who had an automated SBOM generation process already in place. Luna: Ouch. So what exactly is an SBOM, for listeners who haven't encountered it yet? Lucas: A Software Bill of Materials is essentially an ingredient list for your software. It lists every open source library, third-party component, and direct dependency, along with version numbers, license information, and the dependency tree. The National Telecommunications and Information Administration — NTIA — published a framework that standardizes the format, usually in SPDX or CycloneDX. Luna: So it is like a nutrition label, but for code. And the demand for this really started with the Executive Order on cybersecurity in May 2021, right? Lucas: Exactly. The Biden administration's Executive Order on Improving the Nation's Cybersecurity explicitly required any software sold to the federal government to include an SBOM. And that has cascaded down. Healthcare, finance, critical infrastructure — they all adopted similar requirements. Now enterprise procurement teams in the private sector are adding SBOM language to their standard RFPs. Luna: And I think the Log4j vulnerability in late 2021 really accelerated this. Suddenly every CISO realized they had no idea what components were running in their supply chain. Lucas: That was the wake-up call. Log4j was a single library embedded in thousands of products. If you had an SBOM, you knew immediately whether you were affected. Without one, you were searching manually. So buyers started demanding SBOMs as a basic hygiene requirement. Luna: And this is not just for large enterprises either. We are seeing mid-market companies adding SBOM clauses to their vendor contracts. Lucas: Right. The requirement is filtering down. And if you are a B2B SaaS company, you need to be prepared. Let's talk about what a good SBOM looks like and how to generate one. Lucas: First, it should be machine-readable — usually in JSON or XML format following the SPDX or CycloneDX standard. Second, it must include the complete dependency tree, not just direct dependencies. Transitive dependencies are often where vulnerabilities hide. Luna: And it needs to be updated with every release. A static SBOM from six months ago is almost useless. Lucas: That is the biggest mistake vendors make. They generate an SBOM once and call it done. But software changes. Libraries get updated, new dependencies get added. An SBOM needs to be part of your CI/CD pipeline, generated automatically with every build. Luna: And there are tools for this. GitHub offers a dependency graph and Dependabot alerts. There are commercial tools like Snyk, Black Duck, and Fossa that can generate and manage SBOMs. Lucas: For a small SaaS company, you can start with open source tools like Syft or Tern. They can generate an SBOM from a container image or a filesystem. The goal is to have a process that is automated and auditable. Luna: If today's conversation was useful for something you are building or running — maybe you are evaluating your own SBOM strategy — I think it is worth mentioning that these episodes stay ad-free because of listener support. If you want to help keep that going, you can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, that is really what keeps this show independent. No sponsors, no ads. Just useful conversations. And we appreciate everyone who chips in. Luna: Absolutely. So back to SBOMs — what about the format wars? SPDX versus CycloneDX? Lucas: There is a bit of a religious debate, but honestly, most enterprise buyers don't care which format you use as long as it is a standard one. NTIA recommends SPDX, but CycloneDX is also widely accepted. The key is consistency. Luna: And some buyers are starting to ask for a signed SBOM, to prove it hasn't been tampered with. Lucas: Yes. Cryptographic signing is becoming more common. You can use a tool like in-toto or Sigstore to sign your SBOM. That provides an extra layer of trust. Luna: So if I am a SaaS founder listening, what is the one thing I should do this week? Lucas: Generate your first SBOM. Even if it is just for your main product. Use an open source tool, get the output, and review it. You will likely find dependencies you forgot about. Then put it into your build pipeline so it updates automatically. Luna: And then you can respond to that RFP in 48 hours. Lucas: Exactly. And honestly, having an SBOM ready also helps you internally. You can respond faster to vulnerabilities like the next Log4j. It is a security best practice that also becomes a sales differentiator. Luna: We are starting to see procurement teams ask for SBOMs from all vendors, not just those selling to the government. It is becoming table stakes. Lucas: And if you don't have one, you are not even considered. I have heard of deals where the buyer simply eliminated any vendor that couldn't produce an SBOM within the RFP response window. Luna: That is a hard filter. But it makes sense from a risk perspective. If a vendor can't track their own components, how can they be trusted with sensitive data? Lucas: Right. And the cost of generating an SBOM is low. It is mostly automation. The real cost is in maintaining accurate dependency information, which you should be doing anyway for security patching. Luna: One thing we haven't mentioned — some buyers are also asking for a Software Supply Chain Security attestation, which goes beyond the SBOM to include your build process, code review practices, and CI/CD security. Lucas: That is the next wave. The SBOM is the foundation. The attestation is the proof that you have secure practices around it. But you need the SBOM first. Luna: So for listeners, if you are in B2B SaaS, start your SBOM journey now. Even if no buyer has asked yet, they will. Lucas: And when they do, you will be ready. The vendor who lost that two-point-four-million-dollar deal learned the hard way. Don't be that vendor. Luna: Great advice. And a good place to leave it for this episode.