Kusari Platform SBOM

SBOMs for the stack you actually run.

One dependency graph across every language, repo and acquired codebase. SBOM and VEX that stay current as new vulnerabilities land.

YOUR STACK OPEN SOURCE GENERATOR MULTIPLE LANGUAGES MONOREPOS GITHUB + GITLAB ACQUIRED CODE FIRMWARE (Rust, C/C++) CONTAINERS Build-aware for Pants, Nix, Bazel, Conan, Yocto, CMake and more. Waybill + Kusari graph your_app lib-a lib-b lib-c core-x core-y core-z DIRECT TRANSITIVE OPS LICENSE VULN EOL SBOM · CYCLONEDX / SPDX VEX · NOT AFFECTED PROVENANCE · SLSA
Commercial and Open Source Partners
Google Microsoft Intel Red Hat VMware Yahoo DTCC Guidewire Roche Clear Alpha Purdue University Altana Greybeam
"
We're generating hundreds of SBOMs each week and now have the data we need to manage license compliance and coordinate vulnerability evaluations across more than 1500 CNCF projects and subprojects. Waybill provides the data quality and flexibility we need at this scale in a way we haven't been able to get before.
Mario Fahlandt · CNCF Technical Oversight Committee member

Built by the people who wrote the standards.

Kusari's founders ran software security at Bridgewater and Citi. The team built GUAC with Google, now under OpenSSF, and still maintains SLSA. Waybill, the SBOM generator, is open source.

What you get

SBOMs you can defend.

One inventory across a complicated stack
  • Many languages, monorepos, several GitHub and GitLab instances and acquired codebases land in one graph
  • Build-aware generators for examples like Pants, Nix, Bazel, Yocto and CMake, plus custom setups
  • Gaps are flagged where the graph can't follow further, so you know what is covered
An SBOM that stays current
  • Live vulnerability and lifecycle feeds, so a new CVE or an end-of-life package shows up against the SBOMs you already hold
  • Every version kept as a time series, with the raw data and VEX available to download
  • Merges the SBOMs your other tools and vendors produce, so teams stop stitching reports together by hand
Evidence for whoever asks
  • CycloneDX and SPDX SBOMs, with SLSA provenance for where each artifact came from
  • VEX statements with the reasoning attached, updated as new findings come in
  • An audit trail and API, so security, compliance and customers pull from the same record
Risk correlation

Every component, with its risk attached.

Kusari correlates each SBOM with the risk data that decides what to do next, so the inventory tells you what to fix, replace or accept.

Vulnerabilities

Findings are matched to live feeds and scored on exploitability signals like CISA KEV and EPSS, fix availability and where the component sits in your environment. Dynamic reachability and VEX reasoning say which ones apply.

Lifecycle

End-of-life and unmaintained components are flagged before they become a finding, so you can plan the replacement.

License

Declared and discovered licenses are compared, and copyleft or non-open-source terms are flagged against your policy.

Operational

Signals that a component is risky to depend on, such as an abandoned project or a thin maintainer base.

One graph, one record, and the same answer for security, legal and engineering.

How it works

Connect, graph, deliver.

Stage 01 · Connect
  • Source control and CI/CDConnect the platforms you already run, including more than one instance of the same platform.
  • WaybillThe open source generator reads source and build files directly, including ELF headers for linked dependencies.
  • Existing SBOMsBring in what your vendors, acquired teams and other tools already produce.
Stage 02 · Graph
  • One data modelComponents from different languages and teams sit in the same graph, so the whole platform applies to each repository.
  • Transitive depthTraced as far as the information goes, because 96% of vulnerabilities sit at least two layers below the dependency a developer changed (JP Morgan Patchmageddon research, 2026).
  • Risk correlationEach component carries its vulnerability, lifecycle, license and operational risk.
  • Releases as componentsGroup SBOMs into the products you ship, from a single service to a package of dozens of builds.
Stage 03 · Deliver
  • SBOMCycloneDX or SPDX, for customers, regulators and auditors.
  • VEX with reasoningWhat is affected, what is not, and why, tied to reachability.
  • Evidence and accessA versioned record with an audit trail, available through the UI, API and MCP.

An SBOM that is generated once answers last quarter's question. A graph that updates on every build and every new CVE answers today's.

FAQ

SBOMs, answered.

What counts as a complicated stack?

Several languages in one product, monorepos, more than one source control platform, codebases that came in through acquisition, firmware next to cloud services, and builds nobody has documented. Kusari builds one graph across them. Pants, Nix, Bazel, Yocto and CMake are examples of builds we read directly.

What does a Kusari SBOM include?

Every direct and transitive dependency found across your repositories, images and pipelines, with provenance and lineage for each. Where the graph can't follow a dependency further, the SBOM says so.

What risk data does Kusari correlate with my SBOM?

Vulnerabilities, scored on exploitability, fix availability and where the component sits in your environment. Lifecycle, including end-of-life and unmaintained components. License, comparing declared and discovered licenses against your policy. Operational risk, such as abandoned projects. All four attach to the same component in the graph, so one record answers security, legal and engineering.

Does it cover C, C++ and firmware?

Coverage depends on the build setup. CMake, Conan and Yocto are supported, and Waybill reads ELF headers to find linked dependencies. When a component can't be identified, you can set its identity yourself. Bespoke file formats take some scoping, and we work through them with you.

Which formats do you produce?

CycloneDX and SPDX for SBOMs, OpenVEX for VEX, and SLSA provenance. They are open formats, so the files work in the tools your customers and auditors already use.

How current is the SBOM?

Kusari subscribes to live vulnerability feeds. A new vulnerability triggers reachability analysis and a VEX update within the EU Cyber Resilience Act's 24-hour reporting window.

Do I have to replace my existing SBOM tools?

You keep them. Kusari ingests the SBOMs and VEX you already produce, merges them, and adds the graph, reachability and evidence on top.

Where does it run, and what leaves my network?

Kusari runs as SaaS, in your own cloud account, or on-premises on Kubernetes. On-premises, your data stays inside your network and only vulnerability feeds and license metadata come in. AI features can run through your own model gateway.

Which requirements ask for an SBOM?

PCI DSS 6.3.2 asks for an inventory of custom software and its third-party components. NYDFS Part 500 and DORA ask for asset inventory and vulnerability management. FedRAMP's new vulnerability rules become mandatory Dec 7, 2026. EU Cyber Resilience Act reporting has applied since Sep 11, 2026, and SBOM requirements follow on Dec 11, 2027. Security is the reason to act. These are the reason finance signs.

Get started

Send the SBOM they actually asked for.