Most organizations already know they need a Software Bill of Materials (SBOM), whether they’ve been asked for one or they will be soon. But generating one and filing it away is no longer enough.
This post explains what changes when you treat the SBOM and its partner, Vulnerability Exploitability eXchange (VEX), as a working system instead of a compliance artifact.
Why most of your software is open source (and why your SBOM matters)
Think of your SBOM as a shipping manifest, not a certificate
Most of the software your company builds and ships was written by someone else. Black Duck’s 2026 Open Source Security and Risk Analysis (OSSRA) report analyzed audits of 947 commercial codebases and found that
- 98% of audited codebases contained open source.
- The average application contained 1,180 open source components, up 30% year over year.
- The average codebase contained 581 known open source vulnerabilities, up 107% from the prior year.
The question is no longer whether you’ll produce an SBOM. It’s how well you’ll do it, and what you’ll get back for the effort.
EU CRA and product liability deadlines for SBOM compliance
Think of an SBOM less as a certificate that hangs on a wall and more as a shipping manifest. It travels with the product, and someone reads it at every step along the way.
The challenge: Every reader asks a different question about the same product.
| Audience | What they ask |
| Regulators | “Are you meeting essential cybersecurity requirements?” |
| Customers and procurement | “Can this specific vulnerability in your product hurt me?” |
| Your security and dev teams | “Which of our products are affected by this new CVE?” |
The goal is to build two assets, the SBOM and the VEX statement, and answer every one of these questions from them.
The regulatory clock is already ticking
One regulatory milestone has already arrived; the others are close.
- September 11, 2026 – EU CRA Reporting Obligations (in effect now): Manufacturers placing “products with digital elements” on the EU market must now report actively exploited vulnerabilities and severe incidents through ENISA’s Single Reporting Platform (SRP).
- December 9, 2026 – EU Product Liability Directive: Software is explicitly defined as a “product” for the first time. For products placed on the EU market after this date, a missing security update that’s within the manufacturer’s control can make a product legally defective—and this liability is no-fault, with no contractual escape.
- December 11, 2027 – CRA Main Obligations: Essential cybersecurity requirements and SBOM generation mandates kick in. Market surveillance authorities can request SBOMs as part of the technical documentation. (Outside the EU, the FDA already requires SBOMs in premarket submissions for “cyber devices.”)
Every one of these deadlines comes back to two questions:
- What’s in your product? (SBOM)
- Does a given vulnerability affect it? (VEX)
None of these rules demand perfection. They just ask manufacturers to know what’s in their products and show their work.
Compliance drift and the thermostat problem in embedded products
The CRA isn’t just about software you install. For many manufacturers, it covers physical products too, including
- Controllers
- Sensors
- Industrial devices
- Consumer electronics with embedded firmware
These ship once and live in the field for years.
As a colleague puts it, “There’s no CI/CD in a thermostat.” The CRA requires a support period of at least five years (unless the product is expected to be in use for less time), and vulnerability handling runs across that entire period. The firmware is frozen at ship time, and so is the SBOM. But the list of known vulnerabilities keeps growing. That widening gap is compliance drift.
Some devices get over-the-air updates, but you still need to track which units received them. Some depend on manual updates, and some never get updated at all. For those devices, a maintained VEX statement is how owners and regulators stay informed about whether each new vulnerability matters.
If a vulnerability is actively exploited, the CRA clock is tight: An early warning within 24 hours, a notification within 72 hours, and a final report within 14 days after a corrective measure is available.
Why an SBOM can’t double as a vulnerability feed
A common shortcut is to embed current vulnerability data in the SBOM and treat it as a vulnerability feed. Three things go wrong.
- It can’t tell whether a CVE is exploitable. The SBOM lists components and versions. It won’t say if Log4Shell is actually reachable in the product.
- New CVEs appear daily. Refreshing the SBOM to reflect updated data overwrites what was known at ship time and destroys the audit trail.
- It can’t tell customers what to do. The fix might be a mitigation, a config change, or a pending patch. Buyers are left to investigate every CVE themselves, which stalls security reviews.
What is VEX? Keep your SBOM fixed and your vulnerability answers current
The Vulnerability Exploitability eXchange (VEX) fills this gap, and it’s not a new obligation. The CRA already requires manufacturers to identify, document, and address vulnerabilities in their products. Your security team is already making those judgments. VEX determines whether anyone outside the team gets to see them.
VEX puts that judgment into a standard, machine-readable format (such as the CSAF 2.0 VEX profile, CycloneDX, or OpenVEX) so it can leave the building.
Here’s how it works.
- The SBOM is written once per release, capturing components, versions, and relationships as of that day. That record stays fixed.
- Everything after ship lives in VEX.
- Day 30: New vulnerability disclosed. Status: “Investigating.”
- Day 45: Analysis complete. Code not reachable. Status: “Not affected.”
- Day 90: A different issue affects the product. Status: “Affected” — action required.
No one had to reissue the SBOM. The release record stays intact for regulators and liability questions. Customers get up-to-date status without needing a new SBOM.
From compliance win to revenue engine
The same VEX report a security team produces to manage internal risk can go straight to a sales engineer for an RFP response or security questionnaire. The answer is already attached—here’s the exploitability assessment, here’s what’s fixed, here’s what’s not affected.
In most deals, an SBOM is a qualifier. It gets you through the RFP gate, but it doesn’t win the deal.
What moves the deal forward is how fast and clearly the buyer’s next questions can be answered: How will we know when we’re affected? Does your product ship with any known exploitable vulnerabilities?
A fast, evidence-backed answer shortens the security review and helps sales reps maintain momentum. This is where security shifts from a cost center to something closer to a revenue engine.
Why you should validate and consume third-party SBOMs
Every company is also a downstream consumer. Your products include components from open source projects, contractors, and commercial off-the-shelf software vendors. Their SBOMs are only useful if they’re accurate.
Analysis presented in Black Duck’s Compliance Paradox webinar, drawing on the report Navigating Software Supply Chain Risk in a Rapid-Release World, found a clear correlation between validation and response speed.
- Teams that always validate third-party SBOMs: 59% fix critical issues within a day.
- Teams that only validate sometimes: Same-day fixes drop to 30%.
- Teams that never validate: 13% take up to a month to fix critical issues, compared to 2% of teams that always validate.
The recommendation: Import vendor SBOMs into an SCA tool so each component maps automatically against vulnerability feeds, under the same risk tolerance policies applied to internal code.
The result: Vendor risk no longer lives in a separate spreadsheet. One search finds every affected product, whether the vulnerable component is in your code or a vendor’s. No rescan required.
How to tailor SBOMs for regulators, customers, and the public
Not every audience needs the same level of detail. A regulator may need the full dependency tree; an enterprise customer needs exploitability status but not the entire build architecture; public exports should be minimal.
Black Duck SCA addresses this with SBOM and VEX templates. Define configurations once per audience type, save as templates, and make them accessible across teams. The regulator’s copy and the customer’s copy don’t contradict each other because they’re drawn from a single source of truth. No manual field-stripping, and no oversharing by default.
Use AI and an MCP server to find affected projects in plain language
For a security team managing a large portfolio, the bottleneck when a new critical CVE lands is the time it takes to query every project.
The Black Duck SCA MCP server connects to tools like Claude, Copilot, and Cursor, letting engineers ask, in plain language, things like: “Which projects use Log4j core below 2.17? Find it, fix it.”
They get back a list of affected projects and their status. The MCP server doesn’t replace the platform. Instead, it removes a point of friction between security, compliance, and engineering.
3 SBOM and VEX steps to take next week
None of these steps require a budget decision. They’re about starting the right conversations.
| Role | What to focus on |
| AppSec | Triage process, efficiency, and risk tolerance policies |
| Engineering / Platform | Accurate, up-to-date information without missing ship dates |
| Legal / GRC | Downstream audience relevance and scalable, documented processes supporting both sales and audit |
Tips for success
- Assign owners and establish a cadence for refining SBOM/VEX processes.
- Determine whether what’s done for downstream customers can also be pulled in from upstream suppliers.
- Start the conversation across teams and across the organization.
The bottom line: SBOM gets you through the gate, VEX wins the deal
An SBOM generated once and treated as static paperwork is already obsolete.
When you treat the SBOM and VEX as a working system, regulators aren’t the only ones satisfied. Security teams get faster triage. Developers get less friction. Sales teams get shorter review cycles. And customers get proof that you take security seriously.
The SBOM gets you through the gate. VEX and the processes around it win the deal.
Learn more in our on-demand webinar, Your SBOM Is a Business Asset, Not Paperwork.