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.