Native SBOM support vs. Syft scanning for standard Ubuntu L4T rootfs

Hi team,

I’m currently integrating our Jetson [Orin/Thor] project into an automated CI/CD pipeline and need to generate SBOM and CVE reports during the build process.

I’ve reviewed the “Jetson Software Architecture” documentation in the Jetson Linux Developer Guide, which provides a great conceptual overview of the stack. However, it doesn’t seem to provide a standard, machine-readable SBOM file (like CycloneDX or SPDX) out-of-the-box for the standard Ubuntu L4T image.
Jetson Software Architecture — NVIDIA Jetson Linux Developer Guide

Could you advise on the recommended approach to actually generate these files? Is relying on open-source tools like Syft to scan the final rootfs the only viable method for standard L4T, or are there plans to provide native SPDX support without requiring a full switch to Yocto/OE4T?

Thanks in advance for your insights!

We don’t have the SBOM provided for current release, bur targeting to prepare for new SW from.

Hi

Thanks for the clarification on the SBOM status for the current release.

Given that a pre-built SBOM isn’t available yet, could you share NVIDIA’s recommended approach for tracking and auditing CVEs on the standard Ubuntu L4T rootfs in the meantime?

Specifically, for developers who need to generate CVE compliance reports now (e.g., for security audits), what is the best practice? Should we rely solely on scanning the final filesystem with tools like Trivy/Grype, or is there a specific vulnerability feed or process you recommend aligning with for L4T?

Looking forward to the new SW release with SBOM support!