cyclonedx-maven-plugin VS cyclonedx-gradle-plugin

As others have already commented:

The US government has added SBOMs to a proposed rule to update the Federal Acquisition Regulation. So if you want to sell to the US Government you'll have to provide SBOMs: https://www.federalregister.gov/documents/2023/10/03/2023-21...

Lots of large companies require SBOMs from their supplier.

In the EU we will get the Cyber Resilience Act which will make them mandatory as well in certain cases: https://data.consilium.europa.eu/doc/document/ST-12536-2023-...

And yes, there's bascially two technical standards to provide them: SPDX and CycloneDX: https://cyclonedx.org/

Usually there is a requirement through a risk in the risk register, new project etc. appsec engineers perform an analysis of what is available in the market paid and/or open source and match it against the list of requirements and come up with an proposal to be signed off by relevant stakeholders. Usually (there may be exceptions) security engineers take care of the implementation. Which snyk product are talking about? SCA? If so have a look in https://cyclonedx.org/ open source or jfrog (paid) but it will depend much on your current processes mainly around CI/CD tools

We use https://cyclonedx.org/ to auto generate them.

The recent govulncheck effort made me think of the possibility of having the go tool create an SBOM (Software Bill of Materials) in a standard format like CycloneDX that could be consumed by existing tools like DependencyTrack. Somewhat similar to the recent docker sbom feature.

Alternative it would be nice, if there is way to get an SBOM (Software Bill of Materials). Microsoft created an Open Source Tool to get an SBOM for many programming languages, but pascal is not one of this. With a SBOM file, it should be possible to run it against a tool like CycloneDX.

A Software-Bill-of-Materials (SBOM) lists all the software components included in an image. Buildpacks support SBOMs in CycloneDX, Syft and SPDX formats.

CycloneDX is OWASP's lightweight SBOM standard for application security and software composite analysis. It comes with multiple tools for all environments. Its maven plugin generates SBOM featuring all types of dependencies in your projects.

There is a CylconeDX plugin available on Maven central and Github that appears to be well-maintained and commonly used.

This sample project is using Maven build system for generating artifacts. cyclonedx-maven-plugin is used for generating CycloneDX SBom file.

There is a CyconeDX plugin available for Gradle. Just like the Maven plugin we discussed earlier, the Gradle plugin is released by the CycloneDX organization on Github with some of the same maintainers as the Maven plugin.

I am not sure if it fits your use case https://github.com/CycloneDX/cyclonedx-gradle-plugin

OP - rather than jumping in with a “solution”, I would be Irving you to use this as an opportunity for change in your company to improve the governance around software installation in your company (a software catalog and white listing applications would be the best approach), reduce the exposure of licensing costs (or pirated software) in your environment and simplify your ongoing support requirements. Software Bill Of Materials software such as Cyclone DX as a possible solution to collate the information along with vulnerability information, to focus on the known vulnerabilities vs oldest software would be my recommendation. This is a priority in the US under the Executive Order 14208 to improve the nations’s cyber security - The minimum requirements for a Software Bill Of Materials.

I think CycloneDX [1] is the go-to SBOM specification these days.

[1] https://cyclonedx.org/