Application of the Upcoming SPDX Safety Profile
summary
Claims that SPDX 3.1 Safety Profile will model traceability across plans, requirements, tests and build artifacts so teams can produce a curated Safety SBOM for each lifecycle point, run automated impact analyses, and replace fragile Excel lists. Proofs of concept exist, some tools already start implementing the schema, and a hardware model workstream is underway. Adoption is incremental: model details are being finalized, tooling is partial, and weekly Friday meetings coordinate contributors.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:05Functional safety importance
- 5:00Systematic capability explained
- 8:12Manual safety documentation challenges
- 10:00SPDX safety profile benefits
- 12:25Automating safety documentation
- 13:31Model-based safety advantages
- 14:14Contributing to SPDX safety
- 22:55Who needs SPDX safety
- 24:21Q&A
related talks
28mSPDX: Tackling System Risk in Modern Supply Chains
53mAdvancing Transparency and Security in Software: A Deep Dive into SBOM and SPDX
40mStrengthening Software Supply Chains: Harmonizing SLSA Provenance and SPDX SBOM for Better Adoption
30mContinuous Compliance in Open Source: Safety Assurance Through S...
43mHow Do You Know You're Done - After a Security Fix?
42mPractical SBOM Management with Zephyr and SPDX
33mAutomation of SBOM Assessment in AGL Development Process
43mExtending SBOMs to Describe AI Systems