SBOMS and supply chains

Bringing Functional Safety to the SBOM: Automating Compliance with the SPDX Safety Profile

UD2.208 (Decroly)
Nicole Pappler
<p>Functional safety is crucial for open-source components used in safety-critical domains like automotive, medical, and industrial control. However, the current practice for managing the Safety Case—the collection of documents (requirements, tests, analyses, and evidence) proving compliance with standards like IEC 61508 or ISO 26262—is manual, chaotic, and inefficient. These artifacts are often fragmented across proprietary lifecycle systems, spreadsheets, or PDFs, leading to broken traceability and overwhelming manual effort in the supply chain. This talk introduces the SPDX Functional Safety Profile, a critical extension built on the upcoming SPDX 3.1 specification. We will demonstrate how this profile moves the entire Safety Case into a single, standardized, and machine-readable exchange format. The profile achieves this by introducing new classes beyond the SPDX Core: - REQUIREMENT: Capturing functional, non-functional, and design needs. - VERIFICATION: Defining specifications for tests, reviews, and analyses. - EVIDENCE: Storing test reports, build logs, and compliance evidence. Attendees will learn how to use machine-readable relationships to trace requirements through the V-Model, connecting code, design documents, and test results automatically. This profile is the key to building an automated, auditable, and tool-agnostic safety documentation pipeline, finally delivering the ability to exchange comprehensive Safety SBOMs across complex, multi-party supply chains.</p>

Additional information

Live Stream https://live.fosdem.org/watch/ud2208
Type devroom
Language English

More sessions

2/1/26
SBOMS and supply chains
UD2.208 (Decroly)
<p>Welcome to another year of the SBOM devroom, now also including more general Supply Chain topics!</p> <p>The organizers will introduction the topics and the structure of the devroom.</p>
2/1/26
SBOMS and supply chains
Anthony Harrison
UD2.208 (Decroly)
<p>The growing use of Software Bill of Materials (SBOMs) has introduced a new challenge with six different types exist (Design, Source, Build, Analysed, Deployed, and Runtime). As each type captures component information at a unique point in the development lifecycle, it is no longer sufficient to say that you want an SBOM' you need the right one which meets your use case. So how do you determine which SBOM type is the right fit for your specific use case?</p> <p>This session attempts to provide ...
2/1/26
SBOMS and supply chains
Marta Rybczynska
UD2.208 (Decroly)
<p>Modern embedded products are no longer single-processor devices. A typical architecture combines a Linux-based main system, one or more microcontrollers running RTOS workloads, and cloud-side processing also running on Linux. Each of these components produces its own SBOM - often using different formats, tooling, and levels of detail.</p> <p>But what happens when you need to use all of them together for vulnerability management?</p> <p>This talk shares a real-world journey of attempting to ...
2/1/26
SBOMS and supply chains
UD2.208 (Decroly)
<p>Various tools producing SBOMs for pre-built artifacts, such as container images, usually provide only a flat list of components - packages, libraries, RPMs, and binaries - without explaining where any of them originated. But why does this origin information matter, and how can we obtain it?</p> <p>To simply introduce the concept, imagine your build ecosystem as a bakery: the built container is the loaf of bread, and your SBOM is the ingredient label on the package. While customers only see a ...
2/1/26
SBOMS and supply chains
UD2.208 (Decroly)
<p>When a new CVE surfaces in an open-source dependency, teams face an immediate question: Do we really need to update? Is the vulnerability <strong>eploitable</strong>? In practice, nearly 90% of reported issues never affect the consuming application, but identifying the critical 10% is far from trivial. Reachability analysis offers a path forward by tracing vulnerable functions from the upstream component through multi-hop call graphs to determine whether the affected code is ever invoked ...
2/1/26
SBOMS and supply chains
Stefano Pentassuglia
UD2.208 (Decroly)
<p>The modern software supply chain is no longer suffering from a lack of data. Between SBOMs, SLSA provenance, and vulnerability scans, DevOps teams are drowning in attestations. However, a critical gap remains: the ability to aggregate this diverse evidence and enforce consistent, automated security decisions. Simply having an SBOM does not secure your pipeline; verifying its content against a trusted policy does.</p> <p>In this talk, we introduce <strong>Conforma</strong>, an open-source tool ...
2/1/26
SBOMS and supply chains
Viktor Petersson
UD2.208 (Decroly)
<p>As one of the co-leaders of the CISA working group on <a href="https://github.com/SBOM-Community/SBOM-Generation">SBOM Generation</a> and a contributor to its accompanying <a href="https://github.com/SBOM-Community/SBOM-Generation/blob/main/whitepaper/Draft-SBOM-Generation-White-Paper-Feb-25-2025.pdf">whitepaper</a>, I’ve spent the last few years deep in the trenches of SBOM creation. With the EU’s Cyber Resilience Act (CRA) raising the bar for software transparency and lifecycle ...