GitHub user ppkarwasz created a discussion: CloudStack SBOM improvements

apache/cloudstack#14570 generates SBOMs for the main building blocks of 
CloudStack (the Java modules, the UI and Marvin). That is a good basis, and I 
would like to discuss which SBOMs would actually be useful to **downstream 
users**, and how to produce them.

I see two candidates:

1. **A source SBOM** (`pre-build`) that accompanies each source release. It 
would mainly flag the files that are not under `Apache-2.0` or that come from 
other projects, think of it as a `NOTICE` file on steroids, and give an idea of 
the **external** dependencies needed to run CloudStack. This kind of SBOM is 
not useful for vulnerability analysis.
2. **A package SBOM** (`build`) for each `.deb` and `.rpm` we publish. Ideally 
it is complete: every component the package contains, whatever the language 
(Java, JavaScript, Python, C) and however deeply nested (a JAR shaded into 
another JAR, a native library inside a JAR).

On how to produce them: SBOM generators either read the build files (`pom.xml`, 
`package-lock.json`, `debian/rules`, ...) to know what **should** be in an 
artifact, or scan the artifact to find what is **actually** in it. Both have 
blind spots. For example, `cloudstack.jar` shades both `commons-logging` and 
`jcl-over-slf4j`, which contain the same class names, and no build file tells 
you which copy ended up in the JAR. My preference is for the project to publish 
build-based SBOMs, since users can run a scanner just as easily as we can.

If you use CloudStack, or package or redistribute it, it would help to hear 
from you:

- Do you consume SBOMs today, and with which tools? Which format (CycloneDX or 
SPDX) and version?
- Which artifacts matter to you: the source release, the packages, the system 
VM templates?
- What would you use them for: vulnerability management, license compliance, 
regulatory requirements (e.g. the EU Cyber Resilience Act)?

License compliance is not my area, so opinions on what the source SBOM should 
contain are especially welcome.


GitHub link: https://github.com/apache/cloudstack/discussions/14657

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to