[{"data":1,"prerenderedAt":1248},["ShallowReactive",2],{"search-index":3,"dev-pkg-firmware-sboms-spdx-cyclonedx-2026":105},[4,9,13,17,21,26,31,36,41,46,51,56,61,66,71,76,81,86,91,96,101],{"_path":5,"title":6,"description":7,"date":8},"/dev/eu-cyber-resilience-act-firmware-evidence-pack","CRA Firmware Evidence: Scope, Dates and Preparation","Practical breakdown of the EU Cyber Resilience Act requirements for embedded firmware teams, covering technical obligations, SBOM requirements, vulnerability handling, and the evidence pack needed for compliance.","2026-04-19T08:00:00.000Z",{"_path":10,"title":11,"description":12,"date":8},"/dev/pkg/firmware-sboms-spdx-cyclonedx-2026","Firmware SBOMs: SPDX, CycloneDX and Publication Workflows","Practical comparison of SPDX and CycloneDX for firmware SBOMs, covering what to include, automation approaches, tooling, and publication strategies for embedded Linux products.",{"_path":14,"title":15,"description":16,"date":8},"/dev/pkg/spdx-3-0-embedded-builds-practical","SPDX 3.0 for Embedded Builds: Packages, Files, and Relationships Engineers Actually Use","Practical guide to SPDX 3.0 for embedded Linux, covering the data model, package and file elements, relationship types, and how to produce useful SPDX documents from Yocto and Buildroot builds.",{"_path":18,"title":19,"description":20,"date":8},"/dev/slsa-build-provenance-firmware-sign-verify","SLSA Build Provenance for Firmware: What to Collect, How to Sign, How to Verify","Practical implementation guide for SLSA build provenance in firmware pipelines, covering provenance generation, signing with Sigstore, verification workflows, and integration with SBOMs.",{"_path":22,"title":23,"description":24,"date":25},"/dev/vex-csaf-embedded-not-affected-scale","VEX and CSAF for Embedded Vulnerability Status","How to produce and distribute VEX documents and CSAF advisories for embedded firmware, enabling downstream consumers to filter false positives from vulnerability scans.","2026-04-15T20:03:00.000Z",{"_path":27,"title":28,"description":29,"date":30},"/dev/yocto-5-2-walnascar-highlights-embedded-2026","Yocto 5.2 Walnascar: Release Changes and Migration Context","Key changes in Yocto 5.2 Walnascar relevant to embedded product teams, covering toolchain updates, security improvements, SPDX 3.0 support, and migration notes.","2026-04-12T08:14:00.000Z",{"_path":32,"title":33,"description":34,"date":35},"/dev/yocto-esdk-faster-iteration-2026","Yocto eSDK in 2026: Faster Application Iteration Without Full Rebuild Cycles","How to use Yocto's extensible SDK to speed up application development by building and testing packages without running full BitBake builds.","2026-04-11T07:09:00.000Z",{"_path":37,"title":38,"description":39,"date":40},"/dev/yocto-layers-maintainable-strategy-2026","Maintaining Yocto Layers: Appends, Forks and Upgrades","Practical guidance on structuring Yocto layers for long-term maintainability, covering layer boundaries, naming conventions, version pinning, and upgrade workflows.","2026-04-07T13:41:00.000Z",{"_path":42,"title":43,"description":44,"date":45},"/doc/bootlin-toolchains-arm-riscv-2026","Bootlin Toolchains in Practice: Picking the Right Prebuilt Toolchain for ARM and RISC-V","How to select and validate Bootlin prebuilt cross-compilation toolchains for ARM Cortex-A, Cortex-M, and RISC-V targets in embedded Linux projects.","2026-03-10T16:05:00.000Z",{"_path":47,"title":48,"description":49,"date":50},"/doc/buildroot-vs-yocto-2026","Buildroot vs Yocto: BSPs, Build Workflow and Maintenance","A detailed comparison of Buildroot and Yocto for embedded Linux, covering build performance, long-term maintenance, layer ecosystems, and practical decision criteria for product teams in 2026.","2026-03-05T08:12:00.000Z",{"_path":52,"title":53,"description":54,"date":55},"/doc/cross-compilation-toolchain-triplet-clib-2026","Cross-Compilation: Target Triplets and glibc vs musl","Practical guidance on selecting cross-compilation toolchains for embedded Linux, understanding target triplets, and choosing between glibc and musl for your production firmware.","2026-03-07T07:43:00.000Z",{"_path":57,"title":58,"description":59,"date":60},"/doc/erofs-vs-squashfs-2026","EROFS vs SquashFS: Compression, Performance and OTA Trade-offs","Detailed comparison of EROFS and SquashFS for embedded Linux in 2026, covering read performance, compression ratios, deduplication, and integration with OTA update schemes.","2026-03-22T14:22:00.000Z",{"_path":62,"title":63,"description":64,"date":65},"/doc/ota-updates-rauc-swupdate-mender-2026","RAUC vs SWUpdate vs Mender: Embedded Linux OTA Compared","Comparison of RAUC, SWUpdate, and Mender for embedded Linux OTA updates, covering update models, rollback strategies, fleet management, and integration with Yocto and Buildroot.","2026-03-28T19:07:00.000Z",{"_path":67,"title":68,"description":69,"date":70},"/doc/plat/device-tree-debugging-overlays-validation-2026","Device Tree Debugging for Embedded Linux: Overlays, Common Errors, and Validation","Practical guide to debugging device tree issues in embedded Linux, covering overlay mechanics, common DTS errors, validation tools, and runtime debugging techniques.","2026-04-05T06:58:00.000Z",{"_path":72,"title":73,"description":74,"date":75},"/doc/plat/porting-checklist-bootloader-kernel-rootfs-2026","Porting Checklist 2026: Bootloader → Kernel → RootFS for New Boards","Complete checklist for porting embedded Linux to a new board, from bootloader bring-up through kernel configuration to root filesystem validation, with practical tips for each stage.","2026-04-02T15:16:00.000Z",{"_path":77,"title":78,"description":79,"date":80},"/doc/real-time-linux-preempt-rt-latency-2026","PREEMPT_RT Linux: Configuration and Cyclictest Latency Tests","Practical guide to PREEMPT_RT on embedded Linux covering kernel configuration, IRQ threading, latency measurement with cyclictest, and tuning techniques with explicit test conditions and interpretation limits.","2026-03-23T05:48:00.000Z",{"_path":82,"title":83,"description":84,"date":85},"/doc/rootfs-integrity-dm-verity-immutable-images","dm-verity for Rootfs Integrity: Design, Trust and Recovery","How to design and implement dm-verity-protected root filesystems for embedded Linux, covering hash tree generation, kernel integration, error handling, and update strategies.","2026-03-19T08:56:00.000Z",{"_path":87,"title":88,"description":89,"date":90},"/doc/rtos-vs-embedded-linux-zephyr-2026","RTOS vs Embedded Linux: Zephyr, FreeRTOS and Linux Compared","Practical comparison of RTOS (Zephyr, FreeRTOS) and embedded Linux for product design, covering latency, memory footprint, ecosystem maturity, and hybrid architectures.","2026-03-30T09:35:00.000Z",{"_path":92,"title":93,"description":94,"date":95},"/doc/secure-boot-uboot-fit-signatures-chain-of-trust","U-Boot Secure Boot: FIT Signatures and Chain of Trust","Understand U-Boot FIT signatures, trusted control device trees and boot-chain limits with a versioned example and explicit rejection and recovery tests.","2026-03-14T06:29:00.000Z",{"_path":97,"title":98,"description":99,"date":100},"/doc/verified-boot-patterns-uboot-keys-failure-modes","Verified Boot Patterns in U-Boot: What to Verify, Where Keys Live, and Failure Modes","Deep dive into U-Boot verified boot patterns covering signature scopes, key storage options, common failure modes, and practical debugging techniques for embedded Linux platforms.","2026-03-16T18:11:00.000Z",{"_path":102,"title":103,"description":104},"/image-manifest","ProteanOS Image Manifest","This document lists all hero and supporting images needed for the website.",{"_path":10,"_dir":106,"_draft":107,"_partial":107,"_locale":108,"title":11,"description":12,"date":8,"lastmod":109,"draft":107,"hero":110,"tags":111,"category":115,"body":116,"_type":1242,"_id":1243,"_source":1244,"_file":1245,"_stem":1246,"_extension":1247},"pkg",false,"","2026-11-18T00:00:00.000Z","/images/hero/firmware-sboms-spdx-cyclonedx-2026-1600x900.jpg",[112,113,114],"Embedded Linux","ProteanOS","SBOMs","dev-pkg",{"type":117,"children":118,"toc":1210},"root",[119,127,149,156,161,168,173,182,212,222,228,233,240,268,277,283,441,446,452,458,486,492,497,520,526,530,553,559,565,579,599,612,618,639,684,697,703,708,777,782,788,809,815,821,834,840,845,853,859,864,870,875,881,894,927,940,945,968,974,1010,1016,1021,1044,1050,1055,1107,1113,1118,1176,1181,1193,1199,1204],{"type":120,"tag":121,"props":122,"children":123},"element","p",{},[124],{"type":125,"value":126},"text","Choose the firmware software bill of materials (SBOM) format your recipient and validator can read. Start with SPDX if your build already generates it and the recipient accepts that version. Use CycloneDX if the recipient's inventory or vulnerability workflow requires it. In either case, tie the SBOM to the exact firmware image and check which components the generator misses.",{"type":120,"tag":121,"props":128,"children":129},{},[130,132,139,141,147],{"type":125,"value":131},"The ",{"type":120,"tag":133,"props":134,"children":136},"a",{"href":135},"https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng",[137],{"type":125,"value":138},"EU Cyber Resilience Act",{"type":125,"value":140}," calls for a machine-readable SBOM covering at least top-level dependencies for products in scope. The regulation generally applies from 11 December 2027. Earlier reporting duties have a separate timetable. In US federal procurement, agencies can include terms requiring an SBOM on request. Check the actual contract against ",{"type":120,"tag":133,"props":142,"children":144},{"href":143},"https://www.whitehouse.gov/wp-content/uploads/2026/01/M-26-05-Adopting-a-Risk-Based-Approach-to-Software-and-Hardware-Security.pdf",[145],{"type":125,"value":146},"OMB memorandum M-26-05",{"type":125,"value":148},".",{"type":120,"tag":150,"props":151,"children":153},"h2",{"id":152},"spdx-vs-cyclonedx-format-comparison",[154],{"type":125,"value":155},"SPDX vs CycloneDX: format comparison",{"type":120,"tag":121,"props":157,"children":158},{},[159],{"type":125,"value":160},"The table compares SPDX 3.0 and CycloneDX 1.6. Record the exact version in your release workflow, since a tool that accepts one version of a format may reject another.",{"type":120,"tag":162,"props":163,"children":165},"h3",{"id":164},"spdx",[166],{"type":125,"value":167},"SPDX",{"type":120,"tag":121,"props":169,"children":170},{},[171],{"type":125,"value":172},"SPDX originated in the Linux Foundation. ISO/IEC 5962:2021 covers SPDX 2.2.1. The SPDX 3.0 model and serialisation need their own version checks.",{"type":120,"tag":121,"props":174,"children":175},{},[176],{"type":120,"tag":177,"props":178,"children":179},"strong",{},[180],{"type":125,"value":181},"Strengths:",{"type":120,"tag":183,"props":184,"children":185},"ul",{},[186,192,197,202,207],{"type":120,"tag":187,"props":188,"children":189},"li",{},[190],{"type":125,"value":191},"A versioned standard provides a common interchange reference",{"type":120,"tag":187,"props":193,"children":194},{},[195],{"type":125,"value":196},"Rich license expression support (SPDX license identifiers are the industry standard)",{"type":120,"tag":187,"props":198,"children":199},{},[200],{"type":125,"value":201},"SPDX 3.0 includes security (VEX), build, and AI profiles",{"type":120,"tag":187,"props":203,"children":204},{},[205],{"type":125,"value":206},"Yocto generates SPDX natively",{"type":120,"tag":187,"props":208,"children":209},{},[210],{"type":125,"value":211},"Deep integration with Linux kernel and open-source compliance workflows",{"type":120,"tag":121,"props":213,"children":214},{},[215,220],{"type":120,"tag":177,"props":216,"children":217},{},[218],{"type":125,"value":219},"Format options:",{"type":125,"value":221}," SPDX 2.x has tag-value and JSON serialisations, among others. SPDX 3.0 uses a different model with a JSON-LD serialisation.",{"type":120,"tag":162,"props":223,"children":225},{"id":224},"cyclonedx",[226],{"type":125,"value":227},"CycloneDX",{"type":120,"tag":121,"props":229,"children":230},{},[231],{"type":125,"value":232},"CycloneDX is an OWASP standard focused on security use cases. It originated in the application security community and has strong integration with vulnerability scanning tools.",{"type":120,"tag":121,"props":234,"children":235},{},[236],{"type":120,"tag":177,"props":237,"children":238},{},[239],{"type":125,"value":181},{"type":120,"tag":183,"props":241,"children":242},{},[243,248,253,258,263],{"type":120,"tag":187,"props":244,"children":245},{},[246],{"type":125,"value":247},"Designed for security workflows (VEX, vulnerability references, services)",{"type":120,"tag":187,"props":249,"children":250},{},[251],{"type":125,"value":252},"Simpler schema for common use cases",{"type":120,"tag":187,"props":254,"children":255},{},[256],{"type":125,"value":257},"Strong tooling ecosystem (Grype, Syft, Trivy)",{"type":120,"tag":187,"props":259,"children":260},{},[261],{"type":125,"value":262},"XML and JSON formats with clear schemas",{"type":120,"tag":187,"props":264,"children":265},{},[266],{"type":125,"value":267},"Good support for hardware component inventory (BOM for devices)",{"type":120,"tag":121,"props":269,"children":270},{},[271,275],{"type":120,"tag":177,"props":272,"children":273},{},[274],{"type":125,"value":219},{"type":125,"value":276}," XML, JSON, Protocol Buffers",{"type":120,"tag":162,"props":278,"children":280},{"id":279},"comparison-matrix",[281],{"type":125,"value":282},"Comparison matrix",{"type":120,"tag":284,"props":285,"children":286},"table",{},[287,311],{"type":120,"tag":288,"props":289,"children":290},"thead",{},[291],{"type":120,"tag":292,"props":293,"children":294},"tr",{},[295,301,306],{"type":120,"tag":296,"props":297,"children":298},"th",{},[299],{"type":125,"value":300},"Feature",{"type":120,"tag":296,"props":302,"children":303},{},[304],{"type":125,"value":305},"SPDX 3.0",{"type":120,"tag":296,"props":307,"children":308},{},[309],{"type":125,"value":310},"CycloneDX 1.6",{"type":120,"tag":312,"props":313,"children":314},"tbody",{},[315,334,352,370,388,406,424],{"type":120,"tag":292,"props":316,"children":317},{},[318,324,329],{"type":120,"tag":319,"props":320,"children":321},"td",{},[322],{"type":125,"value":323},"Specification",{"type":120,"tag":319,"props":325,"children":326},{},[327],{"type":125,"value":328},"SPDX Project 3.0",{"type":120,"tag":319,"props":330,"children":331},{},[332],{"type":125,"value":333},"OWASP CycloneDX 1.6, ECMA-424 first edition",{"type":120,"tag":292,"props":335,"children":336},{},[337,342,347],{"type":120,"tag":319,"props":338,"children":339},{},[340],{"type":125,"value":341},"Licence information",{"type":120,"tag":319,"props":343,"children":344},{},[345],{"type":125,"value":346},"SPDX licence expressions",{"type":120,"tag":319,"props":348,"children":349},{},[350],{"type":125,"value":351},"SPDX identifiers and expressions supported",{"type":120,"tag":292,"props":353,"children":354},{},[355,360,365],{"type":120,"tag":319,"props":356,"children":357},{},[358],{"type":125,"value":359},"Vulnerability data",{"type":120,"tag":319,"props":361,"children":362},{},[363],{"type":125,"value":364},"Via Security profile",{"type":120,"tag":319,"props":366,"children":367},{},[368],{"type":125,"value":369},"Native VEX support",{"type":120,"tag":292,"props":371,"children":372},{},[373,378,383],{"type":120,"tag":319,"props":374,"children":375},{},[376],{"type":125,"value":377},"Build provenance",{"type":120,"tag":319,"props":379,"children":380},{},[381],{"type":125,"value":382},"Via Build profile",{"type":120,"tag":319,"props":384,"children":385},{},[386],{"type":125,"value":387},"Via formulation",{"type":120,"tag":292,"props":389,"children":390},{},[391,396,401],{"type":120,"tag":319,"props":392,"children":393},{},[394],{"type":125,"value":395},"File-level detail",{"type":120,"tag":319,"props":397,"children":398},{},[399],{"type":125,"value":400},"Check whether generation includes file records",{"type":120,"tag":319,"props":402,"children":403},{},[404],{"type":125,"value":405},"Check whether generation includes file components",{"type":120,"tag":292,"props":407,"children":408},{},[409,414,419],{"type":120,"tag":319,"props":410,"children":411},{},[412],{"type":125,"value":413},"Yocto integration",{"type":120,"tag":319,"props":415,"children":416},{},[417],{"type":125,"value":418},"Use the selected release's SPDX generator",{"type":120,"tag":319,"props":420,"children":421},{},[422],{"type":125,"value":423},"Check whether your chosen exporter preserves relationships",{"type":120,"tag":292,"props":425,"children":426},{},[427,432,437],{"type":120,"tag":319,"props":428,"children":429},{},[430],{"type":125,"value":431},"Receiving workflow",{"type":120,"tag":319,"props":433,"children":434},{},[435],{"type":125,"value":436},"Confirm accepted schema version",{"type":120,"tag":319,"props":438,"children":439},{},[440],{"type":125,"value":436},{"type":120,"tag":121,"props":442,"children":443},{},[444],{"type":125,"value":445},"Choose the format and version your downstream tools support. Schema validity and format selection cannot establish compliance, component accuracy or vulnerability absence.",{"type":120,"tag":150,"props":447,"children":449},{"id":448},"what-to-include-in-a-firmware-sbom",[450],{"type":125,"value":451},"What to include in a firmware SBOM",{"type":120,"tag":162,"props":453,"children":455},{"id":454},"inventory-starting-point",[456],{"type":125,"value":457},"Inventory starting point",{"type":120,"tag":183,"props":459,"children":460},{},[461,466,471,476,481],{"type":120,"tag":187,"props":462,"children":463},{},[464],{"type":125,"value":465},"Shipped open-source and proprietary components with versions",{"type":120,"tag":187,"props":467,"children":468},{},[469],{"type":125,"value":470},"Licence information per package",{"type":120,"tag":187,"props":472,"children":473},{},[474],{"type":125,"value":475},"Supplier (upstream project) for each package",{"type":120,"tag":187,"props":477,"children":478},{},[479],{"type":125,"value":480},"The firmware image as the top-level component",{"type":120,"tag":187,"props":482,"children":483},{},[484],{"type":125,"value":485},"Dependency relationships",{"type":120,"tag":162,"props":487,"children":489},{"id":488},"recommended-useful-for-security",[490],{"type":125,"value":491},"Recommended (useful for security)",{"type":120,"tag":121,"props":493,"children":494},{},[495],{"type":125,"value":496},"Everything above, plus:",{"type":120,"tag":183,"props":498,"children":499},{},[500,505,510,515],{"type":120,"tag":187,"props":501,"children":502},{},[503],{"type":125,"value":504},"File-level checksums for key binaries",{"type":120,"tag":187,"props":506,"children":507},{},[508],{"type":125,"value":509},"Build tool versions (GCC, binutils, kernel version)",{"type":120,"tag":187,"props":511,"children":512},{},[513],{"type":125,"value":514},"Known vulnerability status (or reference to VEX document)",{"type":120,"tag":187,"props":516,"children":517},{},[518],{"type":125,"value":519},"Source repository URLs for each package",{"type":120,"tag":162,"props":521,"children":523},{"id":522},"advanced-full-supply-chain-transparency",[524],{"type":125,"value":525},"Advanced (full supply chain transparency)",{"type":120,"tag":121,"props":527,"children":528},{},[529],{"type":125,"value":496},{"type":120,"tag":183,"props":531,"children":532},{},[533,538,543,548],{"type":120,"tag":187,"props":534,"children":535},{},[536],{"type":125,"value":537},"Build configuration (compiler flags, enabled features)",{"type":120,"tag":187,"props":539,"children":540},{},[541],{"type":125,"value":542},"Link to SLSA provenance document",{"type":120,"tag":187,"props":544,"children":545},{},[546],{"type":125,"value":547},"Transitive dependency tree (not just direct dependencies)",{"type":120,"tag":187,"props":549,"children":550},{},[551],{"type":125,"value":552},"Patch metadata (which upstream patches were applied)",{"type":120,"tag":150,"props":554,"children":556},{"id":555},"automation-approaches",[557],{"type":125,"value":558},"Automation approaches",{"type":120,"tag":162,"props":560,"children":562},{"id":561},"from-yocto",[563],{"type":125,"value":564},"From Yocto",{"type":120,"tag":121,"props":566,"children":567},{},[568,570,577],{"type":125,"value":569},"Yocto generates SPDX documents as part of the build process. Enable it in ",{"type":120,"tag":571,"props":572,"children":574},"code",{"className":573},[],[575],{"type":125,"value":576},"local.conf",{"type":125,"value":578},":",{"type":120,"tag":580,"props":581,"children":585},"pre",{"code":582,"language":583,"meta":108,"className":584,"style":108},"INHERIT += \"create-spdx\"\n","bitbake","language-bitbake shiki shiki-themes github-dark",[586],{"type":120,"tag":571,"props":587,"children":588},{"__ignoreMap":108},[589],{"type":120,"tag":590,"props":591,"children":594},"span",{"class":592,"line":593},"line",1,[595],{"type":120,"tag":590,"props":596,"children":597},{},[598],{"type":125,"value":582},{"type":120,"tag":121,"props":600,"children":601},{},[602,604,610],{"type":125,"value":603},"Check whether the distribution already inherits this class before adding it. Verify the serialisation and schema version of the generated image document. See the ",{"type":120,"tag":133,"props":605,"children":607},{"href":606},"/dev/yocto-5-2-walnascar-highlights-embedded-2026/",[608],{"type":125,"value":609},"Yocto 5.2 highlights",{"type":125,"value":611}," for release context.",{"type":120,"tag":162,"props":613,"children":615},{"id":614},"from-buildroot",[616],{"type":125,"value":617},"From Buildroot",{"type":120,"tag":121,"props":619,"children":620},{},[621,623,629,631,637],{"type":125,"value":622},"Buildroot's ",{"type":120,"tag":571,"props":624,"children":626},{"className":625},[],[627],{"type":125,"value":628},"make legal-info",{"type":125,"value":630}," collects licensing information. On a release that includes ",{"type":120,"tag":571,"props":632,"children":634},{"className":633},[],[635],{"type":125,"value":636},"utils/generate-cyclonedx",{"type":125,"value":638},", use the package metadata from the configured build to generate a separate CycloneDX file:",{"type":120,"tag":580,"props":640,"children":644},{"code":641,"language":642,"meta":108,"className":643,"style":108},"make show-info | utils/generate-cyclonedx > sbom.cdx.json\n","bash","language-bash shiki shiki-themes github-dark",[645],{"type":120,"tag":571,"props":646,"children":647},{"__ignoreMap":108},[648],{"type":120,"tag":590,"props":649,"children":650},{"class":592,"line":593},[651,657,663,669,674,679],{"type":120,"tag":590,"props":652,"children":654},{"style":653},"--shiki-default:#B392F0",[655],{"type":125,"value":656},"make",{"type":120,"tag":590,"props":658,"children":660},{"style":659},"--shiki-default:#9ECBFF",[661],{"type":125,"value":662}," show-info",{"type":120,"tag":590,"props":664,"children":666},{"style":665},"--shiki-default:#F97583",[667],{"type":125,"value":668}," |",{"type":120,"tag":590,"props":670,"children":671},{"style":653},[672],{"type":125,"value":673}," utils/generate-cyclonedx",{"type":120,"tag":590,"props":675,"children":676},{"style":665},[677],{"type":125,"value":678}," >",{"type":120,"tag":590,"props":680,"children":681},{"style":659},[682],{"type":125,"value":683}," sbom.cdx.json\n",{"type":120,"tag":121,"props":685,"children":686},{},[687,689,695],{"type":125,"value":688},"Check the selected release's ",{"type":120,"tag":133,"props":690,"children":692},{"href":691},"https://buildroot.org/downloads/manual/manual.html#_generating_cyclonedx_sbom",[693],{"type":125,"value":694},"Buildroot manual",{"type":125,"value":696}," for availability and options. Compare the generated inventory with the shipped image to catch firmware blobs or files copied in by a post-build script.",{"type":120,"tag":162,"props":698,"children":700},{"id":699},"from-containerimage-scanning",[701],{"type":125,"value":702},"From container/image scanning",{"type":120,"tag":121,"props":704,"children":705},{},[706],{"type":125,"value":707},"Tools like Syft can scan a filesystem or container image and generate an SBOM:",{"type":120,"tag":580,"props":709,"children":711},{"code":710,"language":642,"meta":108,"className":643,"style":108},"syft dir:output/rootfs -o spdx-json > sbom.spdx.json\nsyft dir:output/rootfs -o cyclonedx-json > sbom.cdx.json\n",[712],{"type":120,"tag":571,"props":713,"children":714},{"__ignoreMap":108},[715,748],{"type":120,"tag":590,"props":716,"children":717},{"class":592,"line":593},[718,723,728,734,739,743],{"type":120,"tag":590,"props":719,"children":720},{"style":653},[721],{"type":125,"value":722},"syft",{"type":120,"tag":590,"props":724,"children":725},{"style":659},[726],{"type":125,"value":727}," dir:output/rootfs",{"type":120,"tag":590,"props":729,"children":731},{"style":730},"--shiki-default:#79B8FF",[732],{"type":125,"value":733}," -o",{"type":120,"tag":590,"props":735,"children":736},{"style":659},[737],{"type":125,"value":738}," spdx-json",{"type":120,"tag":590,"props":740,"children":741},{"style":665},[742],{"type":125,"value":678},{"type":120,"tag":590,"props":744,"children":745},{"style":659},[746],{"type":125,"value":747}," sbom.spdx.json\n",{"type":120,"tag":590,"props":749,"children":751},{"class":592,"line":750},2,[752,756,760,764,769,773],{"type":120,"tag":590,"props":753,"children":754},{"style":653},[755],{"type":125,"value":722},{"type":120,"tag":590,"props":757,"children":758},{"style":659},[759],{"type":125,"value":727},{"type":120,"tag":590,"props":761,"children":762},{"style":730},[763],{"type":125,"value":733},{"type":120,"tag":590,"props":765,"children":766},{"style":659},[767],{"type":125,"value":768}," cyclonedx-json",{"type":120,"tag":590,"props":770,"children":771},{"style":665},[772],{"type":125,"value":678},{"type":120,"tag":590,"props":774,"children":775},{"style":659},[776],{"type":125,"value":683},{"type":120,"tag":121,"props":778,"children":779},{},[780],{"type":125,"value":781},"An image scan sees only what the scanner can identify from the files it receives. Reconcile its output with your build manifest to spot stripped binaries or copied files with missing package metadata. Keep build dependencies in the build record even when they never reach the device.",{"type":120,"tag":162,"props":783,"children":785},{"id":784},"from-proteanos",[786],{"type":125,"value":787},"From ProteanOS",{"type":120,"tag":121,"props":789,"children":790},{},[791,793,799,801,807],{"type":125,"value":792},"ProteanOS package metadata includes the information needed for SBOM generation. The ",{"type":120,"tag":133,"props":794,"children":796},{"href":795},"/dev/pkg/spf-2.0/",[797],{"type":125,"value":798},"packaging system",{"type":125,"value":800}," records component names, versions, licenses, and upstream sources in control files. Check the selected ",{"type":120,"tag":133,"props":802,"children":804},{"href":803},"/dev/prokit/",[805],{"type":125,"value":806},"ProKit",{"type":125,"value":808}," source and validate any exporter before relying on its output.",{"type":120,"tag":150,"props":810,"children":812},{"id":811},"publication-strategies",[813],{"type":125,"value":814},"Publication strategies",{"type":120,"tag":162,"props":816,"children":818},{"id":817},"embed-in-firmware",[819],{"type":125,"value":820},"Embed in firmware",{"type":120,"tag":121,"props":822,"children":823},{},[824,826,832],{"type":125,"value":825},"Include the SBOM in the firmware image itself, accessible via a well-known path (e.g., ",{"type":120,"tag":571,"props":827,"children":829},{"className":828},[],[830],{"type":125,"value":831},"/usr/share/sbom/",{"type":125,"value":833},"). This ensures the SBOM always accompanies the firmware.",{"type":120,"tag":162,"props":835,"children":837},{"id":836},"publish-alongside-releases",[838],{"type":125,"value":839},"Publish alongside releases",{"type":120,"tag":121,"props":841,"children":842},{},[843],{"type":125,"value":844},"Host SBOMs on your release infrastructure, named to match the firmware version:",{"type":120,"tag":580,"props":846,"children":848},{"code":847},"firmware-v2.1.0.bin\nfirmware-v2.1.0.spdx.json\nfirmware-v2.1.0.vex.json\n",[849],{"type":120,"tag":571,"props":850,"children":851},{"__ignoreMap":108},[852],{"type":125,"value":847},{"type":120,"tag":162,"props":854,"children":856},{"id":855},"api-access",[857],{"type":125,"value":858},"API access",{"type":120,"tag":121,"props":860,"children":861},{},[862],{"type":125,"value":863},"For fleet-managed devices, provide SBOM access through a device management API. This allows automated compliance scanning across your deployed fleet.",{"type":120,"tag":150,"props":865,"children":867},{"id":866},"validation",[868],{"type":125,"value":869},"Validation",{"type":120,"tag":121,"props":871,"children":872},{},[873],{"type":125,"value":874},"Before publishing, validate your SBOM:",{"type":120,"tag":162,"props":876,"children":878},{"id":877},"spdx-validation",[879],{"type":125,"value":880},"SPDX validation",{"type":120,"tag":121,"props":882,"children":883},{},[884,886,892],{"type":125,"value":885},"The following command applies to a supported SPDX 2.x document with ",{"type":120,"tag":571,"props":887,"children":889},{"className":888},[],[890],{"type":125,"value":891},"spdx-tools",{"type":125,"value":893}," installed:",{"type":120,"tag":580,"props":895,"children":897},{"code":896,"language":642,"meta":108,"className":643,"style":108},"# Using SPDX tools\npyspdxtools -i sbom.spdx.json\n",[898],{"type":120,"tag":571,"props":899,"children":900},{"__ignoreMap":108},[901,910],{"type":120,"tag":590,"props":902,"children":903},{"class":592,"line":593},[904],{"type":120,"tag":590,"props":905,"children":907},{"style":906},"--shiki-default:#6A737D",[908],{"type":125,"value":909},"# Using SPDX tools\n",{"type":120,"tag":590,"props":911,"children":912},{"class":592,"line":750},[913,918,923],{"type":120,"tag":590,"props":914,"children":915},{"style":653},[916],{"type":125,"value":917},"pyspdxtools",{"type":120,"tag":590,"props":919,"children":920},{"style":730},[921],{"type":125,"value":922}," -i",{"type":120,"tag":590,"props":924,"children":925},{"style":659},[926],{"type":125,"value":747},{"type":120,"tag":121,"props":928,"children":929},{},[930,932,938],{"type":125,"value":931},"For SPDX 3.0, use a validator that explicitly supports the producer's JSON-LD model and patch level. The ",{"type":120,"tag":133,"props":933,"children":935},{"href":934},"https://github.com/spdx/tools-python/issues/760",[936],{"type":125,"value":937},"SPDX tools discussion on Yocto-generated JSON-LD",{"type":125,"value":939}," shows how validator support can be mistaken for a defect in the document. Keep one known file from your own build as a fixture for tool upgrades, and test that the recipient can ingest it.",{"type":120,"tag":121,"props":941,"children":942},{},[943],{"type":125,"value":944},"Check for:",{"type":120,"tag":183,"props":946,"children":947},{},[948,953,958,963],{"type":120,"tag":187,"props":949,"children":950},{},[951],{"type":125,"value":952},"Valid SPDX license expressions",{"type":120,"tag":187,"props":954,"children":955},{},[956],{"type":125,"value":957},"All required fields present",{"type":120,"tag":187,"props":959,"children":960},{},[961],{"type":125,"value":962},"Consistent package identifiers",{"type":120,"tag":187,"props":964,"children":965},{},[966],{"type":125,"value":967},"Correct relationship types",{"type":120,"tag":162,"props":969,"children":971},{"id":970},"cyclonedx-validation",[972],{"type":125,"value":973},"CycloneDX validation",{"type":120,"tag":580,"props":975,"children":977},{"code":976,"language":642,"meta":108,"className":643,"style":108},"# Using CycloneDX CLI\ncyclonedx validate --input-file sbom.cdx.json\n",[978],{"type":120,"tag":571,"props":979,"children":980},{"__ignoreMap":108},[981,989],{"type":120,"tag":590,"props":982,"children":983},{"class":592,"line":593},[984],{"type":120,"tag":590,"props":985,"children":986},{"style":906},[987],{"type":125,"value":988},"# Using CycloneDX CLI\n",{"type":120,"tag":590,"props":990,"children":991},{"class":592,"line":750},[992,996,1001,1006],{"type":120,"tag":590,"props":993,"children":994},{"style":653},[995],{"type":125,"value":224},{"type":120,"tag":590,"props":997,"children":998},{"style":659},[999],{"type":125,"value":1000}," validate",{"type":120,"tag":590,"props":1002,"children":1003},{"style":730},[1004],{"type":125,"value":1005}," --input-file",{"type":120,"tag":590,"props":1007,"children":1008},{"style":659},[1009],{"type":125,"value":683},{"type":120,"tag":162,"props":1011,"children":1013},{"id":1012},"content-validation",[1014],{"type":125,"value":1015},"Content validation",{"type":120,"tag":121,"props":1017,"children":1018},{},[1019],{"type":125,"value":1020},"Automated validation catches format errors but not content errors. Manual checks:",{"type":120,"tag":183,"props":1022,"children":1023},{},[1024,1029,1034,1039],{"type":120,"tag":187,"props":1025,"children":1026},{},[1027],{"type":125,"value":1028},"Are all packages in the firmware represented in the SBOM?",{"type":120,"tag":187,"props":1030,"children":1031},{},[1032],{"type":125,"value":1033},"Are versions accurate (not just \"latest\")?",{"type":120,"tag":187,"props":1035,"children":1036},{},[1037],{"type":125,"value":1038},"Are licenses correct (not just \"unknown\")?",{"type":120,"tag":187,"props":1040,"children":1041},{},[1042],{"type":125,"value":1043},"Does the dependency tree match the actual build?",{"type":120,"tag":150,"props":1045,"children":1047},{"id":1046},"maintaining-sboms-over-time",[1048],{"type":125,"value":1049},"Maintaining SBOMs over time",{"type":120,"tag":121,"props":1051,"children":1052},{},[1053],{"type":125,"value":1054},"An SBOM is a snapshot. Maintain them by:",{"type":120,"tag":1056,"props":1057,"children":1058},"ol",{},[1059,1069,1079,1089],{"type":120,"tag":187,"props":1060,"children":1061},{},[1062,1067],{"type":120,"tag":177,"props":1063,"children":1064},{},[1065],{"type":125,"value":1066},"Generating fresh SBOMs with every release:",{"type":125,"value":1068}," Automated in CI.",{"type":120,"tag":187,"props":1070,"children":1071},{},[1072,1077],{"type":120,"tag":177,"props":1073,"children":1074},{},[1075],{"type":125,"value":1076},"Storing historical SBOMs:",{"type":125,"value":1078}," Set retention from the product's legal and support obligations, including any longer documentation-retention requirement.",{"type":120,"tag":187,"props":1080,"children":1081},{},[1082,1087],{"type":120,"tag":177,"props":1083,"children":1084},{},[1085],{"type":125,"value":1086},"Monitoring for new vulnerabilities:",{"type":125,"value":1088}," Run vulnerability scans against published SBOMs periodically.",{"type":120,"tag":187,"props":1090,"children":1091},{},[1092,1097,1099,1105],{"type":120,"tag":177,"props":1093,"children":1094},{},[1095],{"type":125,"value":1096},"Updating VEX statements:",{"type":125,"value":1098}," When new CVEs are published, update VEX documents. The ",{"type":120,"tag":133,"props":1100,"children":1102},{"href":1101},"/dev/vex-csaf-embedded-not-affected-scale/",[1103],{"type":125,"value":1104},"VEX guide",{"type":125,"value":1106}," covers this workflow.",{"type":120,"tag":150,"props":1108,"children":1110},{"id":1109},"integration-with-the-broader-compliance-stack",[1111],{"type":125,"value":1112},"Integration with the broader compliance stack",{"type":120,"tag":121,"props":1114,"children":1115},{},[1116],{"type":125,"value":1117},"SBOMs are one piece of the compliance puzzle:",{"type":120,"tag":183,"props":1119,"children":1120},{},[1121,1131,1141,1159],{"type":120,"tag":187,"props":1122,"children":1123},{},[1124,1129],{"type":120,"tag":177,"props":1125,"children":1126},{},[1127],{"type":125,"value":1128},"SBOM",{"type":125,"value":1130}," → What is in the firmware?",{"type":120,"tag":187,"props":1132,"children":1133},{},[1134,1139],{"type":120,"tag":177,"props":1135,"children":1136},{},[1137],{"type":125,"value":1138},"VEX",{"type":125,"value":1140}," → Which vulnerabilities apply?",{"type":120,"tag":187,"props":1142,"children":1143},{},[1144,1149,1151,1157],{"type":120,"tag":177,"props":1145,"children":1146},{},[1147],{"type":125,"value":1148},"Provenance",{"type":125,"value":1150}," → How was it built? (",{"type":120,"tag":133,"props":1152,"children":1154},{"href":1153},"/dev/slsa-build-provenance-firmware-sign-verify/",[1155],{"type":125,"value":1156},"SLSA guide",{"type":125,"value":1158},")",{"type":120,"tag":187,"props":1160,"children":1161},{},[1162,1167,1169,1175],{"type":120,"tag":177,"props":1163,"children":1164},{},[1165],{"type":125,"value":1166},"Evidence pack",{"type":125,"value":1168}," → Complete compliance documentation (",{"type":120,"tag":133,"props":1170,"children":1172},{"href":1171},"/dev/eu-cyber-resilience-act-firmware-evidence-pack/",[1173],{"type":125,"value":1174},"CRA guide",{"type":125,"value":1158},{"type":120,"tag":121,"props":1177,"children":1178},{},[1179],{"type":125,"value":1180},"Together, these artifacts provide full supply chain transparency for your firmware.",{"type":120,"tag":121,"props":1182,"children":1183},{},[1184,1185,1191],{"type":125,"value":131},{"type":120,"tag":133,"props":1186,"children":1188},{"href":1187},"/dev/pkg/spdx-3-0-embedded-builds-practical/",[1189],{"type":125,"value":1190},"SPDX 3.0 guide",{"type":125,"value":1192}," covers the specifics of SPDX 3.0's package and relationship model for embedded Linux images.",{"type":120,"tag":150,"props":1194,"children":1196},{"id":1195},"summary",[1197],{"type":125,"value":1198},"Summary",{"type":120,"tag":121,"props":1200,"children":1201},{},[1202],{"type":125,"value":1203},"Produce SBOMs for every firmware release. Choose SPDX if your ecosystem is Yocto-centric and license-focused. Choose CycloneDX if your ecosystem is security-tool-centric. Automate generation in CI, validate before publication, and maintain historical SBOMs for the product's lifetime. Budget validation and ownership alongside generation, including packages that the selected exporter cannot identify.",{"type":120,"tag":1205,"props":1206,"children":1207},"style",{},[1208],{"type":125,"value":1209},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":108,"searchDepth":750,"depth":750,"links":1211},[1212,1218,1223,1229,1234,1239,1240,1241],{"id":152,"depth":750,"text":155,"children":1213},[1214,1216,1217],{"id":164,"depth":1215,"text":167},3,{"id":224,"depth":1215,"text":227},{"id":279,"depth":1215,"text":282},{"id":448,"depth":750,"text":451,"children":1219},[1220,1221,1222],{"id":454,"depth":1215,"text":457},{"id":488,"depth":1215,"text":491},{"id":522,"depth":1215,"text":525},{"id":555,"depth":750,"text":558,"children":1224},[1225,1226,1227,1228],{"id":561,"depth":1215,"text":564},{"id":614,"depth":1215,"text":617},{"id":699,"depth":1215,"text":702},{"id":784,"depth":1215,"text":787},{"id":811,"depth":750,"text":814,"children":1230},[1231,1232,1233],{"id":817,"depth":1215,"text":820},{"id":836,"depth":1215,"text":839},{"id":855,"depth":1215,"text":858},{"id":866,"depth":750,"text":869,"children":1235},[1236,1237,1238],{"id":877,"depth":1215,"text":880},{"id":970,"depth":1215,"text":973},{"id":1012,"depth":1215,"text":1015},{"id":1046,"depth":750,"text":1049},{"id":1109,"depth":750,"text":1112},{"id":1195,"depth":750,"text":1198},"markdown","content:dev:pkg:firmware-sboms-spdx-cyclonedx-2026.md","content","dev/pkg/firmware-sboms-spdx-cyclonedx-2026.md","dev/pkg/firmware-sboms-spdx-cyclonedx-2026","md",1795338687291]