SW360 SBOM and License Obligation Management
summary
SW360 manages software bill of materials, links projects → components → releases → licenses and aggregates obligation text; it does no scanner built in and instead ingests SPDX outputs from license detection tools (for example Fossology). The GUI imports license metadata and imports SPDX and obligation entries from external sources, pulling about 50 license obligations into editable templates, shows full license text, compatibility and patent notes, and lets teams generate per-product license bundles and obligation views.
AI-written summary · about
chapters (13)
- 0:00Start
- 0:49Overview
- 3:03Now for Licenses
- 6:38Manage OSS license and obligations
- 7:35Import and Add license Obligations
- 8:32Architecture Licensee / License Obligations
- 9:14Import License Obligation from OSDAL
- 10:07License information in SW360
- 10:55Importing results of License Obligations
- 11:14OSDAL licenses obligation
- 11:40Add New License Obligation Like OSDAL format
- 12:28Select Obligation Element
- 13:03Thank you!
related talks
36mSW360 SBOM: Managing Vulnerability Information, SPDX Documents and New Depen...
43mUsing SBOMs for Linux Foundation Projects
39mSBOM Automation - Making Compliance Effortless by Consuming, Enrichin...
37mSBOM Implementation Reality: From Crawl to Walk - SPDX Lite Pro...
37mStreamlining Open-Source License Compliance With the Continuous Clearing Tool
53mAdvancing Transparency and Security in Software: A Deep Dive into SBOM and SPDX
42mBoF: State of SBOM Tools
47mThe Missing Link - How we collect and leverage SBOMs