<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SBOM on OpenChain KWG</title><link>https://korea-wg.openchainproject.org/en/tags/sbom/</link><description>Recent content in SBOM on OpenChain KWG</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 10 Nov 2026 18:49:56 +0900</lastBuildDate><atom:link href="https://korea-wg.openchainproject.org/en/tags/sbom/index.xml" rel="self" type="application/rss+xml"/><item><title>OSV-SCALIBR</title><link>https://korea-wg.openchainproject.org/en/guide/tools/4-osvscalibr/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/tools/4-osvscalibr/</guid><description>&lt;p&gt;OSV-SCALIBR (Open Source Vulnerabilities - Software Composition Analysis LIBRary) is an open source software composition analysis tool developed by Google.&#10;It scans filesystems, container images, and binaries to identify included packages and detects known vulnerabilities by cross-referencing the &lt;a href="https://osv.dev/"&gt;OSV (Open Source Vulnerabilities)&lt;/a&gt; database. It also supports SBOM generation in SPDX format.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;GitHub: &lt;a href="https://github.com/google/osv-scalibr"&gt;https://github.com/google/osv-scalibr&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;License: Apache-2.0&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="1-features"&gt;1. Features&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Multiple scan targets&lt;/strong&gt;: Local filesystem, container images, archive files&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Wide ecosystem support&lt;/strong&gt;: Go, Python, Java (Maven), JavaScript (npm), Rust, Ruby, and more&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;OSV DB integration&lt;/strong&gt;: Cross-references scan results with the OSV database to provide CVE and other vulnerability information&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;SBOM output&lt;/strong&gt;: Exports results in SPDX 2.3 format&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;CLI and library&lt;/strong&gt;: Provided as both a standalone binary (CLI) and a Go library&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="2-installation"&gt;2. Installation&lt;/h3&gt;&#10;&lt;p&gt;Build with Go 1.21 or later:&lt;/p&gt;</description></item><item><title>cdxgen</title><link>https://korea-wg.openchainproject.org/en/guide/tools/5-cdxgen/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/tools/5-cdxgen/</guid><description>&lt;p&gt;cdxgen is an open source SBOM generation tool managed by OWASP (Open Web Application Security Project).&#10;It analyzes source code, build artifacts, and container images to automatically generate SBOMs in &lt;a href="https://cyclonedx.org/"&gt;CycloneDX&lt;/a&gt; format.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;GitHub: &lt;a href="https://github.com/CycloneDX/cdxgen"&gt;https://github.com/CycloneDX/cdxgen&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;License: Apache-2.0&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="features"&gt;Features&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Wide language and ecosystem support&lt;/strong&gt;: Java (Maven/Gradle), Node.js, Python, Go, Rust, PHP, Ruby, .NET, and 20+ more&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Multiple scan targets&lt;/strong&gt;: Source code directories, container images, GitHub repositories&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;CycloneDX standard output&lt;/strong&gt;: Supports CycloneDX 1.4/1.5/1.6 in JSON and XML formats&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;REPL mode&lt;/strong&gt;: Interactive interface for exploring and querying SBOMs&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;CI/CD integration&lt;/strong&gt;: Easy integration with GitHub Actions, GitLab CI, and other major pipelines&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="installation"&gt;Installation&lt;/h2&gt;&#10;&lt;p&gt;Install with Node.js 18 or later:&lt;/p&gt;</description></item><item><title>Syft</title><link>https://korea-wg.openchainproject.org/en/guide/tools/6-syft/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/tools/6-syft/</guid><description>&lt;p&gt;Syft is an open source SBOM generation CLI tool developed by Anchore.&#10;It scans container images, filesystems, and archives to identify included packages and generates SBOMs in SPDX or CycloneDX format.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;GitHub: &lt;a href="https://github.com/anchore/syft"&gt;https://github.com/anchore/syft&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;License: Apache-2.0&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="features"&gt;Features&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Multiple scan targets&lt;/strong&gt;: Container images (Docker, OCI), local filesystems, tar archives&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Wide ecosystem support&lt;/strong&gt;: Alpine (apk), Debian/Ubuntu (dpkg), RPM, Python, Java, Go, Node.js, Ruby, Rust, and more&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Standard output formats&lt;/strong&gt;: SPDX 2.2/2.3 (JSON, tag-value), CycloneDX 1.4/1.5 (JSON, XML), Syft JSON&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Grype integration&lt;/strong&gt;: Pairs naturally with Anchore&amp;rsquo;s Grype vulnerability scanner for SBOM-based vulnerability analysis&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Easy installation&lt;/strong&gt;: Single binary distribution, no additional runtime required&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="installation"&gt;Installation&lt;/h2&gt;&#10;&lt;h3 id="script-installation-linuxmacos"&gt;Script Installation (Linux/macOS)&lt;/h3&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;curl -sSfL https://raw.githubusercontent.com/anchore/syft/main/install.sh &lt;span style="color:#1f2328"&gt;|&lt;/span&gt; sh -s -- -b /usr/local/bin&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id="homebrew-macos"&gt;Homebrew (macOS)&lt;/h3&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;brew install syft&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id="docker"&gt;Docker&lt;/h3&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;docker pull anchore/syft&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id="basic-usage"&gt;Basic Usage&lt;/h2&gt;&#10;&lt;h3 id="1-scan-a-container-image"&gt;(1) Scan a Container Image&lt;/h3&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#57606a"&gt;# Scan a Docker image and output SPDX JSON&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;syft ubuntu:22.04 -o spdx-json&lt;span style="color:#0550ae"&gt;=&lt;/span&gt;sbom.spdx.json&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#57606a"&gt;# Output as CycloneDX JSON&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;syft ubuntu:22.04 -o cyclonedx-json&lt;span style="color:#0550ae"&gt;=&lt;/span&gt;sbom.cdx.json&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id="2-scan-a-local-directory"&gt;(2) Scan a Local Directory&lt;/h3&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;syft dir:/path/to/project -o spdx-json&lt;span style="color:#0550ae"&gt;=&lt;/span&gt;sbom.spdx.json&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id="3-view-results-in-terminal"&gt;(3) View Results in Terminal&lt;/h3&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#57606a"&gt;# Print package list to terminal&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;syft ubuntu:22.04&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#57606a"&gt;# Output as JSON to stdout&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;syft ubuntu:22.04 -o json&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h3 id="4-vulnerability-scanning-with-grype"&gt;(4) Vulnerability Scanning with Grype&lt;/h3&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#57606a"&gt;# Generate SBOM with Syft and analyze vulnerabilities with Grype&lt;/span&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;syft ubuntu:22.04 -o json &lt;span style="color:#1f2328"&gt;|&lt;/span&gt; grype&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id="cicd-integration-example"&gt;CI/CD Integration Example&lt;/h2&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-yaml" data-lang="yaml"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#57606a"&gt;# GitHub Actions example&lt;/span&gt;&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;- &lt;span style="color:#0550ae"&gt;name&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;Generate SBOM with Syft&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;&lt;span style="color:#0550ae"&gt;uses&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;anchore/sbom-action@v0&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;&lt;span style="color:#0550ae"&gt;with&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;&lt;span style="color:#0550ae"&gt;image&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;myapp:latest&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;&lt;span style="color:#0550ae"&gt;format&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;spdx-json&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;&lt;span style="color:#0550ae"&gt;output-file&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;sbom.spdx.json&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;- &lt;span style="color:#0550ae"&gt;name&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;Upload SBOM&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;&lt;span style="color:#0550ae"&gt;uses&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;actions/upload-artifact@v4&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;&lt;span style="color:#0550ae"&gt;with&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;&lt;span style="color:#0550ae"&gt;name&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;sbom&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;&lt;span style="color:#0550ae"&gt;path&lt;/span&gt;&lt;span style="color:#1f2328"&gt;:&lt;/span&gt;&lt;span style="color:#fff"&gt; &lt;/span&gt;sbom.spdx.json&lt;span style="color:#fff"&gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id="references"&gt;References&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Syft GitHub: &lt;a href="https://github.com/anchore/syft"&gt;https://github.com/anchore/syft&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;Grype (vulnerability scanner): &lt;a href="https://github.com/anchore/grype"&gt;https://github.com/anchore/grype&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;SPDX Standard: &lt;a href="https://spdx.dev/"&gt;https://spdx.dev/&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;CycloneDX Standard: &lt;a href="https://cyclonedx.org/"&gt;https://cyclonedx.org/&lt;/a&gt;&lt;/li&gt;&#10;&lt;/ul&gt;</description></item><item><title>Dependency-Track</title><link>https://korea-wg.openchainproject.org/en/guide/tools/7-dependency-track/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/tools/7-dependency-track/</guid><description>&lt;p&gt;Dependency-Track is an open source SBOM management and vulnerability analysis platform managed by OWASP.&#10;It continuously monitors component-level vulnerabilities based on uploaded SBOMs (CycloneDX, SPDX) and automatically evaluates policy violations.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;GitHub: &lt;a href="https://github.com/DependencyTrack/dependency-track"&gt;https://github.com/DependencyTrack/dependency-track&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;Official docs: &lt;a href="https://docs.dependencytrack.org/"&gt;https://docs.dependencytrack.org/&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;License: Apache-2.0&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="features"&gt;Features&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;SBOM-based continuous monitoring&lt;/strong&gt;: Automatically tracks the latest vulnerabilities per component after uploading SBOMs in SPDX or CycloneDX format&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Multiple vulnerability data sources&lt;/strong&gt;: NVD, OSV, GitHub Advisories, VulnDB, and more&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Policy engine&lt;/strong&gt;: Define rules for license policies, vulnerability severity thresholds, and component allowlists for automatic evaluation&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;REST API&lt;/strong&gt;: Integrate with CI/CD pipelines to automatically upload SBOMs and receive feedback at build time&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Web UI dashboard&lt;/strong&gt;: View per-project risk scores, vulnerability status, and license distribution at a glance&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Notifications&lt;/strong&gt;: Send new vulnerability alerts via Slack, email, Webhook, and other channels&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="installation"&gt;Installation&lt;/h2&gt;&#10;&lt;p&gt;Using Docker Compose is the simplest approach:&lt;/p&gt;</description></item><item><title>Building an Automated Open Source Management Environment: cdxgen + Dependency-Track</title><link>https://korea-wg.openchainproject.org/en/guide/tools/8-cdxgen-dt/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/tools/8-cdxgen-dt/</guid><description>&lt;p&gt;For companies just starting with open source management, we recommend the&#10;&lt;strong&gt;cdxgen + Dependency-Track&lt;/strong&gt; combination as a toolset that can establish a basic&#10;automation environment within a single day.&lt;/p&gt;&#10;&lt;p&gt;This guide walks you through every step, from installation and configuration to&#10;setting up a license and vulnerability inspection environment and running day-to-day operations.&lt;/p&gt;&#10;&lt;h2 id="why-cdxgen--dependency-track"&gt;Why cdxgen + Dependency-Track&lt;/h2&gt;&#10;&lt;p&gt;Open source management comes down to two essentials.&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;&lt;strong&gt;Know what is inside&lt;/strong&gt; — generating an SBOM (Software Bill of Materials)&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Continuously monitor risk&lt;/strong&gt; — detecting vulnerabilities (CVEs) and license policy violations&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;cdxgen handles the first, and Dependency-Track handles the second.&#10;Both tools are &lt;strong&gt;free open source&lt;/strong&gt; under the Apache-2.0 license.&lt;/p&gt;</description></item><item><title>SCANOSS</title><link>https://korea-wg.openchainproject.org/en/guide/tools/9-scanoss/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/tools/9-scanoss/</guid><description>&lt;p&gt;SCANOSS is a Software Composition Analysis (SCA) tool that can identify open source&#10;components not only at the file level but down to the &lt;strong&gt;snippet (code fragment) level&lt;/strong&gt;.&#10;It detects license and copyright information by matching against a knowledge base&#10;(OSSKB, Open Source Knowledge Base) that indexes more than 100 million files, and&#10;automatically generates SBOMs in CycloneDX and SPDX formats.&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;GitHub: &lt;a href="https://github.com/scanoss"&gt;https://github.com/scanoss&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;Official site: &lt;a href="https://www.scanoss.com"&gt;https://www.scanoss.com&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;License: Apache-2.0&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="1-key-features"&gt;1. Key features&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;strong&gt;Snippet-level matching&lt;/strong&gt;: Can trace the origin even when a portion of code, rather than an entire file, has been copied or modified&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Large-scale knowledge base&lt;/strong&gt;: OSSKB indexes more than 100 million open source files — covering major package repositories and GitHub&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Automatic SBOM generation&lt;/strong&gt;: Supports CycloneDX (JSON/XML) and SPDX format output&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;Both CLI &amp;amp; REST API&lt;/strong&gt;: Provides both the &lt;code&gt;scanoss-py&lt;/code&gt; (Python) CLI and a REST API, making automation integration easy&lt;/li&gt;&#10;&lt;li&gt;&lt;strong&gt;CI/CD pipeline integration&lt;/strong&gt;: Can scan with a single command in CI environments such as GitHub Actions&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="2-installation"&gt;2. Installation&lt;/h2&gt;&#10;&lt;p&gt;Install via pip in a Python 3.8 or later environment.&lt;/p&gt;</description></item><item><title>§3.3.1 SBOM</title><link>https://korea-wg.openchainproject.org/en/guide/iso5230_guide/3-content-review/1-sbom/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/iso5230_guide/3-content-review/1-sbom/</guid><description>&lt;h2 id="1-clause-overview"&gt;1. Clause Overview&lt;/h2&gt;&#10;&lt;p&gt;Without knowing what open source components are included in the supplied software, it is impossible to&#10;fulfill license obligations or respond to security vulnerabilities. §3.3.1 requires the establishment&#10;of a procedure for identifying, tracking, reviewing, approving, and archiving the open source components&#10;that make up supplied software, and maintaining component records (SBOM) that demonstrate the procedure&#10;has actually been followed. This clause forms the foundation for operating the SBOM, which is the core&#10;infrastructure of open source license compliance and Security Assurance.&lt;/p&gt;</description></item><item><title>§4.3.1 SBOM</title><link>https://korea-wg.openchainproject.org/en/guide/iso18974_guide/3-content-review/1-sbom/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/iso18974_guide/3-content-review/1-sbom/</guid><description>&lt;h2 id="1-clause-overview"&gt;1. Clause Overview&lt;/h2&gt;&#10;&lt;p&gt;§4.3.1 has the same basic structure as ISO/IEC 5230 §3.3.1 (SBOM), but the emphasis differs. While 5230 covers the SBOM for license management of open source components, §4.3.1 of 18974 emphasizes &lt;strong&gt;continuously recording and retaining the SBOM throughout the entire software lifecycle&lt;/strong&gt;. In particular, the SBOM must be maintained even after deployment so it can be integrated with the vulnerability monitoring in §4.3.2 Security Assurance. Without an SBOM, post-deployment impact analysis for newly published CVEs (§4.1.5 Method 5) cannot be performed.&lt;/p&gt;</description></item><item><title>TRUSCA</title><link>https://korea-wg.openchainproject.org/en/guide/tools/11-trusca/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/guide/tools/11-trusca/</guid><description>&lt;p&gt;Managing the vulnerabilities and licenses of open source components calls for an SCA (Software Composition Analysis) tool. Several commercial products exist, but some organizations look for an open source tool they can install and run on their own infrastructure.&lt;/p&gt;&#10;&lt;p&gt;TRUSCA is a self-hosted SCA portal published for that purpose. Released under Apache 2.0, it brings vulnerabilities (CVE), license compliance, and SBOM management into a single screen. It is developed by &lt;a href="https://korea-wg.openchainproject.org/en/guide/trustedoss/"&gt;Trusted OSS&lt;/a&gt;, a project that grew out of KWG community work.&lt;/p&gt;</description></item><item><title>28th Meeting</title><link>https://korea-wg.openchainproject.org/en/meeting/2025/28th/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/meeting/2025/28th/</guid><description>&lt;p&gt;&lt;img src="../../../../images/2025_goodbye.png" alt="" loading="lazy" decoding="async"&gt;&#10;&lt;/p&gt;&#10;&lt;h2 id="schedule"&gt;Schedule&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Date and Time: December 9, 2025 (Tuesday), 2:00 PM – 4:50 PM&lt;/li&gt;&#10;&lt;li&gt;Venue: Hancom Tower (Pangyo - &lt;a href="https://maps.app.goo.gl/Nq3XHZtPrg9Zvtzn7"&gt;https://maps.app.goo.gl/Nq3XHZtPrg9Zvtzn7&lt;/a&gt;)&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="agenda"&gt;Agenda&lt;/h2&gt;&#10;&lt;table&gt;&#10;&#9;&lt;thead&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Time&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Agenda&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Speaker&lt;/th&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;th&gt;Slide&lt;/th&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/thead&gt;&#10;&#9;&lt;tbody&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;14:00~14:05&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Welcome &amp;amp; Opening&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Jihwan Jeong CTO, Hancom&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;-&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;14:05~14:20&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;OpenChain Update&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Haksung Jang, SK Telecom&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;a href="https://gamma.app/docs/rgelezj6nhbbw4u?following_id=r2th6vhw2e0c6us&amp;amp;follow_on_start=true"&gt;slide&lt;/a&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;14:20~14:45&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Sharing Hancom&amp;rsquo;s OpenChain Certification Declaration Preparation&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Hyunjoo Ryu, Hancom&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;a href="https://github.com/OpenChain-Project/OpenChain-KWG/releases/download/meeting-slides-legacy/hancom_iso_20251209.pdf"&gt;pdf&lt;/a&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;14:45~15:10&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Introduction to OpenPDF Data Loader and Tips for Open Source Disclosure Using AI&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Bundo Lee, Hancom&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;a href="https://github.com/OpenChain-Project/OpenChain-KWG/releases/download/meeting-slides-legacy/hancom_openpdf_20251209.pdf"&gt;pdf&lt;/a&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;15:10~15:50&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Networking (Group Discussion)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;All&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;-&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;15:50~16:00&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Telechips&amp;rsquo; OpenChain Certification and Remaining Challenges&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Jiyoung Yeon, Telechips&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;a href="https://github.com/OpenChain-Project/OpenChain-KWG/releases/download/meeting-slides-legacy/telechips_iso_20251209.pdf"&gt;pdf&lt;/a&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;16:00~16:10&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;About Cryptography Bill of Materials (CBOM)&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Jinyoung Chae, Samsung SDS&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;-&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;16:10~16:25&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Tooling &amp;amp; Legal Group Major Activities and Review&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Wonjae Park, LG Electronics&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;-&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&#9;&#9;&lt;tr&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;16:25~16:50&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;2025 Review &amp;amp; Awards&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;Darae Ahn, Samsung Electronics&lt;/td&gt;&#10;&#9;&#9;&#9;&#9;&#9;&lt;td&gt;&lt;a href="https://gamma.app/docs/KWG-2025--1fl75t69rtf77u0"&gt;slide&lt;/a&gt;&lt;/td&gt;&#10;&#9;&#9;&#9;&lt;/tr&gt;&#10;&#9;&lt;/tbody&gt;&#10;&lt;/table&gt;&#10;&lt;h2 id="sponsor"&gt;Sponsor&lt;/h2&gt;&#10;&lt;p&gt;&lt;img src="../../../../images/content/about/logo/hancom.png" alt="" loading="lazy" decoding="async"&gt;&#10;&lt;/p&gt;</description></item><item><title>31st Meeting</title><link>https://korea-wg.openchainproject.org/en/meeting/2026/31st/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/meeting/2026/31st/</guid><description>&lt;style&gt;&#10;/* Per-meeting sponsor color — for the next meeting, change just these two values. */&#10;.td-content { --accent: #e30613; --ink: #fff5f3; }&#10;&lt;/style&gt;&#10;&lt;div class="kwg-conf-hero"&gt;&#10; &lt;div class="kwg-conf-hero__body"&gt;&#10; &lt;p class="kwg-conf-hero__eyebrow"&gt;31st Meeting&lt;/p&gt;&#10; &lt;h1 class="kwg-conf-hero__title"&gt;Software Supply Chain Security and Open Source Governance&lt;/h1&gt;&#10; &lt;p class="kwg-conf-hero__sub"&gt;We look at the state of open source governance at CJ Group, how an open source management framework runs from an operations team's perspective, and tools for software supply chain security.&lt;/p&gt;&#10; &lt;div class="kwg-conf-hero__meta"&gt;&#10; &lt;span&gt;&lt;strong&gt;Date&lt;/strong&gt; 2026-09-08 (Tue) 14:00–17:00&lt;/span&gt;&#10; &lt;span&gt;&lt;strong&gt;Venue&lt;/strong&gt; CJ Human Resources Development Center · Jung-gu, Seoul&lt;/span&gt;&#10; &lt;/div&gt;&#10; &lt;p class="kwg-conf-hero__maps"&gt;Directions&#10; &lt;a href="https://maps.app.goo.gl/nQUogVHPvF4VuapX9" target="_blank" rel="noopener"&gt;Google Maps&lt;/a&gt;&#10; &lt;a href="https://map.naver.com/p/search/CJ%EC%9D%B8%EC%9E%AC%EC%9B%90" target="_blank" rel="noopener"&gt;Naver Map&lt;/a&gt;&#10; &lt;a href="https://map.kakao.com/link/search/CJ%EC%9D%B8%EC%9E%AC%EC%9B%90" target="_blank" rel="noopener"&gt;Kakao Map&lt;/a&gt;&#10; &lt;/p&gt;&#10; &lt;p class="kwg-conf-hero__note"&gt;Registration and the detailed program are announced via the OpenChain KWG mailing list. Subscribe to receive the sign-up link.&lt;/p&gt;&#10; &lt;div class="kwg-conf-hero__cta"&gt;&#10; &lt;a class="kwg-conf-cta" href="../../../about/subscribe/"&gt;Join the mailing list&lt;/a&gt;&#10; &lt;/div&gt;&#10; &lt;/div&gt;&#10; &lt;div class="kwg-conf-hero__date"&gt;&#10; &lt;span class="kwg-conf-hero__date-d"&gt;08&lt;/span&gt;&#10; &lt;span class="kwg-conf-hero__date-my"&gt;Sep 2026 · Tue&lt;/span&gt;&#10; &lt;/div&gt;&#10;&lt;/div&gt;</description></item><item><title>CISA 2026 SBOM Minimum Elements: What to Prepare and Which Tools Fill the Gaps</title><link>https://korea-wg.openchainproject.org/en/blog/2026/08/09/cisa-sbom-minimum-elements/</link><pubDate>Sun, 09 Aug 2026 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/blog/2026/08/09/cisa-sbom-minimum-elements/</guid><description>&lt;div class="alert alert-info" role="alert"&gt;&#10;&lt;p&gt;This article was written with Claude Code, and the key facts cited here were cross-checked against primary sources.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;&#10;&lt;p&gt;On July 29, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) and 17 other agencies published a revised set of minimum elements for a Software Bill of Materials (SBOM)&lt;a id="a2-ref-1"&gt;&lt;/a&gt;&lt;a href="https://korea-wg.openchainproject.org/en/blog/2026/08/09/cisa-sbom-minimum-elements/#a2"&gt;A2&lt;/a&gt;. The document states plainly that it replaces, rather than amends, the baseline established in 2021 by the National Telecommunications and Information Administration (NTIA).&lt;/p&gt;</description></item><item><title>What the US AI Executive Order (2026-06-02) Means for Enterprise Open Source Managers</title><link>https://korea-wg.openchainproject.org/en/blog/2026/06/10/us-ai-eo-ospo/</link><pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/blog/2026/06/10/us-ai-eo-ospo/</guid><description>&lt;div class="alert alert-info" role="alert"&gt;&#10;&lt;p&gt;This article was written with Claude Code, and the key facts cited here were cross-checked against primary sources.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Summary&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;The executive order &amp;ldquo;Promoting Advanced Artificial Intelligence Innovation and Security,&amp;rdquo; signed on June 2, 2026, imposes no obligations on enterprises. Its substance is the Treasury Department-led AI Cybersecurity Clearinghouse (a relay body that pools, verifies, and distributes vulnerability information, to be established within 30 days) and a voluntary pre-disclosure framework for frontier models (to be designed within 60 days); mandatory licensing and pre-approval are explicitly excluded &lt;a id="a1-ref-1"&gt;&lt;/a&gt;&lt;a href="https://korea-wg.openchainproject.org/en/blog/2026/06/10/us-ai-eo-ospo/#a1"&gt;A1&lt;/a&gt;. No provision applies directly to enterprise open source managers either. Still, there is a reason to read this order: the context behind it. AI finding open source vulnerabilities faster than humans do has already become reality. Ahead of the executive order, an unreleased Anthropic model found 6,202 high- or critical-severity vulnerabilities in open source projects over two months, and patching has not kept pace &lt;a id="a6-ref-1"&gt;&lt;/a&gt;&lt;a href="https://korea-wg.openchainproject.org/en/blog/2026/06/10/us-ai-eo-ospo/#a6"&gt;A6&lt;/a&gt;·&lt;a id="c1-ref-1"&gt;&lt;/a&gt;&lt;a href="https://korea-wg.openchainproject.org/en/blog/2026/06/10/us-ai-eo-ospo/#c1"&gt;C1&lt;/a&gt;. What open source managers need to prepare is not compliance with the executive order, but a response system that can handle a check of patch-processing capacity, cleanup of end-of-life (EOL) components, and the EU Cyber Resilience Act reporting obligation taking effect September 11, 2026, all at once.&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item><item><title>EU Cyber Resilience Act (CRA) Vulnerability Reporting Obligations — A Research Report for the 2026-09-11 Compliance Date</title><link>https://korea-wg.openchainproject.org/en/blog/2026/05/18/eu-cra/</link><pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/blog/2026/05/18/eu-cra/</guid><description>&lt;div class="alert alert-info" role="alert"&gt;&#10;&lt;p&gt;This article was written with Claude Code, and the key facts cited here were cross-checked against primary sources.&lt;/p&gt;&#10;&lt;/div&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;Summary&lt;/strong&gt;&lt;/p&gt;&#10;&lt;p&gt;The EU Cyber Resilience Act (Cyber Resilience Act, CRA — Regulation (EU) 2024/2847) is the EU&amp;rsquo;s first comprehensive product security regulation, imposing horizontal cybersecurity obligations on every &amp;ldquo;product with digital elements&amp;rdquo; (PDE) placed on the EU market. The regulation entered into force on December 10, 2024, and applies in phases. From September 11, 2026, the Article 14 reporting obligations take effect, requiring manufacturers, importers, and distributors to notify ENISA (the European Union Agency for Cybersecurity) and Member State CSIRTs of actively exploited vulnerabilities and severe incidents within a staged 24-hour, 72-hour, and 14-day window. Companies that have not stood up a reporting workflow by this date face fines of up to €15 million or 2.5% of worldwide annual turnover, and Korean companies that place products on the EU market are subject to the obligation immediately. &lt;a id="a1-ref-1"&gt;&lt;/a&gt;&lt;a href="https://korea-wg.openchainproject.org/en/blog/2026/05/18/eu-cra/#a1"&gt;A1&lt;/a&gt;, &lt;a id="b1-ref-1"&gt;&lt;/a&gt;&lt;a href="https://korea-wg.openchainproject.org/en/blog/2026/05/18/eu-cra/#b1"&gt;B1&lt;/a&gt;, &lt;a id="e1-ref-1"&gt;&lt;/a&gt;&lt;a href="https://korea-wg.openchainproject.org/en/blog/2026/05/18/eu-cra/#e1"&gt;E1&lt;/a&gt;&lt;/p&gt;&#10;&lt;/blockquote&gt;</description></item><item><title>2025-12-04 SBOM 표준화와 최신 이슈들</title><link>https://korea-wg.openchainproject.org/en/resource/telco_work_group/2025-12-04/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/resource/telco_work_group/2025-12-04/</guid><description>&lt;p&gt;source: &lt;a href="https://openchainproject.org/news/2025/12/12/recording-openchain-telco-work-group-2025-12-04"&gt;https://openchainproject.org/news/2025/12/12/recording-openchain-telco-work-group-2025-12-04&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;일시: 2025년 12월 4일&lt;/p&gt;&#10;&lt;p&gt;참석자: Jimmy Ahlberg (Ericsson), Takashi Ninjouji (Honda), Marc-Etienne Vargenau (Nokia)&lt;/p&gt;&#10;&lt;p&gt;주요 의제: CycloneDX 이슈, OpenChain 운영진 변경, CISA 규제 현황, 신규 툴 소개, SPDX 3.0 전환 이슈&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="1-주요-공지사항-및-운영-이슈"&gt;1. 주요 공지사항 및 운영 이슈&lt;/h2&gt;&#10;&lt;h3 id="openchain-general-manager-사임"&gt;OpenChain General Manager 사임&lt;/h3&gt;&#10;&lt;p&gt;OpenChain 프로젝트의 핵심 인물이었던 Shane이 General Manager직을 내려놓게 되었습니다. 그의 마지막 근무일은 12월 12일이며, 현재 후임자는 정해지지 않은 상태입니다. 프로젝트 측에서는 적합한 후보자 추천을 환영하고 있으며, 리더십 공백을 최소화하기 위해 노력하고 있습니다.&lt;/p&gt;</description></item><item><title>2025-11-26 대규모 공급망에서 SBOM을 어떻게 운영 단계에 적용할 것인가?</title><link>https://korea-wg.openchainproject.org/en/resource/sbom_work_group/2025-11-26/</link><pubDate>Wed, 26 Nov 2025 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/resource/sbom_work_group/2025-11-26/</guid><description>&lt;p&gt;source: &lt;a href="https://openchainproject.org/news/2025/11/27/recording-openchain-sbom-work-group-monthly-meeting-2025-11-26"&gt;https://openchainproject.org/news/2025/11/27/recording-openchain-sbom-work-group-monthly-meeting-2025-11-26&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;일시: 2025년 11월 26일 (수)&lt;/p&gt;&#10;&lt;p&gt;주제: 복잡한 대규모 공급망에서 SBOM을 어떻게 &amp;lsquo;운영(Production)&amp;rsquo; 단계에 적용할 것인가?&lt;/p&gt;&#10;&lt;p&gt;발표자: Thomas Graf (Siemens)&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="들어가며-만드는-것을-넘어-쓰는-것으로"&gt;들어가며: &amp;ldquo;만드는 것&amp;quot;을 넘어 &amp;ldquo;쓰는 것&amp;quot;으로&lt;/h2&gt;&#10;&lt;p&gt;지난 11월 26일 열린 OpenChain SBOM Work Group 정기 미팅은 SBOM(Software Bill of Materials) 논의가 이제 새로운 국면에 접어들었음을 보여주는 중요한 자리였습니다. 그동안 업계의 논의가 &amp;ldquo;SBOM을 어떻게 생성할 것인가(How to generate)?&amp;ldquo;에 머물러 있었다면, 이번 미팅의 핵심 질문은 &amp;ldquo;생성된 SBOM을 실제 운영 환경(Production)과 복잡한 공급망에서 어떻게 활용할 것인가?&amp;ldquo;였습니다.&lt;/p&gt;</description></item><item><title>2025-11-06 CISA 셧다운의 영향과 SBOM 품질 가이드 집중 점검</title><link>https://korea-wg.openchainproject.org/en/resource/telco_work_group/2025-11-06/</link><pubDate>Thu, 06 Nov 2025 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/resource/telco_work_group/2025-11-06/</guid><description>&lt;p&gt;source: &lt;a href="https://openchainproject.org/news/2025/11/11/telco-2025-11-06"&gt;https://openchainproject.org/news/2025/11/11/telco-2025-11-06&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;일시: 2025년 11월 6일&lt;/p&gt;&#10;&lt;p&gt;참석자: Marc-Etienne Vargenau (Nokia, 의장), Shane Coughlan (OpenChain), Norio Koboto (Sony), Masahiro Daikoku (KDDI), Jari Koivisto (Analog Devices) 등&lt;/p&gt;&#10;&lt;p&gt;이번 OpenChain Telco Work Group(이하 Telco WG) 정기 미팅에서는 미국 정부 셧다운이 CISA(사이버보안 및 인프라 보안국)의 업무에 미치는 영향부터, 차기 Telco Guide 업데이트 방향, 그리고 최근 업데이트된 SBOM 품질 가이드(Quality Guide)에 대한 심도 있는 기술적 검토가 이루어졌습니다.&lt;/p&gt;&#10;&lt;p&gt;미팅에 직접 참여하지 못하신 분들을 위해 핵심 내용을 상세히 요약해 드립니다.&lt;/p&gt;</description></item><item><title>2025-10-27 SBOM 품질 가이드와 규제 대응의 구체화</title><link>https://korea-wg.openchainproject.org/en/resource/sbom_work_group/2025-10-27/</link><pubDate>Mon, 27 Oct 2025 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/resource/sbom_work_group/2025-10-27/</guid><description>&lt;p&gt;source: &lt;a href="https://openchainproject.org/news/2025/10/27/recording-openchain-sbom-work-group-monthly-meeting-2025-10-22"&gt;https://openchainproject.org/news/2025/10/27/recording-openchain-sbom-work-group-monthly-meeting-2025-10-22&lt;/a&gt;&lt;/p&gt;&#10;&lt;p&gt;작성일: 2025년 10월 27일&lt;/p&gt;&#10;&lt;p&gt;주제: OpenChain SBOM Work Group Monthly Meeting (2025-10-22) 상세 리뷰&lt;/p&gt;&#10;&lt;p&gt;안녕하세요. 오늘은 지난 10월 22일에 진행된 OpenChain SBOM 워크 그룹(OpenChain SBOM Work Group) 정기 미팅의 핵심 내용을 정리해 드립니다.&lt;/p&gt;&#10;&lt;p&gt;이번 미팅은 지난 9월 &amp;lsquo;스터디 그룹(Study Group)&amp;lsquo;에서 &amp;lsquo;워크 그룹(Working Group)&amp;lsquo;으로 승격된 이후 본격적으로 진행된 논의라는 점에서 큰 의미가 있었습니다. 특히, 현재 업계의 가장 큰 화두인 &amp;ldquo;단순히 SBOM을 만드는 것을 넘어, 어떻게 고품질의 SBOM을 만들고 규제에 대응할 것인가?&amp;ldquo;에 대한 구체적인 가이드라인 작업 현황이 공개되었습니다.&lt;/p&gt;</description></item><item><title>2024-12-06 SBOM 가이드라인 업데이트 논의</title><link>https://korea-wg.openchainproject.org/en/resource/telco_work_group/2024-12-06/</link><pubDate>Fri, 06 Dec 2024 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/resource/telco_work_group/2024-12-06/</guid><description>&lt;p&gt;source: &lt;a href="https://openchainproject.org/news/2024/12/12/telco-work-group-2024-12-06"&gt;https://openchainproject.org/news/2024/12/12/telco-work-group-2024-12-06&lt;/a&gt;&lt;/p&gt;&#10;&lt;h2 id="목차"&gt;목차&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;인도의 SBOM 기술 가이드라인 검토&lt;/li&gt;&#10;&lt;li&gt;OpenChain Telco SBOM 가이드 개선 방안&lt;/li&gt;&#10;&lt;li&gt;SBOM 도구 관련 업데이트&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;h2 id="1-웨비나-개요"&gt;1. 웨비나 개요&lt;/h2&gt;&#10;&lt;h3 id="발표자-소개"&gt;발표자 소개&lt;/h3&gt;&#10;&lt;p&gt;이번 웨비나는 OpenChain Telco Work Group의 정기 미팅으로, Nokia의 오픈소스 전문가가 진행을 맡았습니다.&lt;/p&gt;&#10;&lt;h3 id="웨비나-목적"&gt;웨비나 목적&lt;/h3&gt;&#10;&lt;p&gt;SBOM 관련 최신 기술 가이드라인을 검토하고 OpenChain Telco SBOM 가이드의 개선 방안을 논의하기 위해 개최되었습니다.&lt;/p&gt;&#10;&lt;h2 id="2-인도의-sbom-기술-가이드라인-검토"&gt;2. 인도의 SBOM 기술 가이드라인 검토&lt;/h2&gt;&#10;&lt;h3 id="가이드라인-개요"&gt;가이드라인 개요&lt;/h3&gt;&#10;&lt;p&gt;Indian Computer Emergency Response Team (CERT-In)에서 2023년 10월에 발표한 SBOM 기술 가이드라인에 대해 논의했습니다. 이 가이드라인은 주로 공공 부문의 보안 관점에 초점을 맞추고 있습니다.&lt;/p&gt;</description></item><item><title>2024-12-05 리눅스 재단에서 SBOM을 활성화하는 과정</title><link>https://korea-wg.openchainproject.org/en/resource/webinar/2024-12-05/</link><pubDate>Thu, 05 Dec 2024 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/resource/webinar/2024-12-05/</guid><description>&lt;p&gt;source: &lt;a href="https://openchainproject.org/news/2024/12/04/webinar-enabling-sboms-across-the-linux-foundation"&gt;https://openchainproject.org/news/2024/12/04/webinar-enabling-sboms-across-the-linux-foundation&lt;/a&gt;&lt;/p&gt;&#10;&lt;h2 id="목차"&gt;목차&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;발표자 소개&lt;/li&gt;&#10;&lt;li&gt;웨비나 소개와 목적&lt;/li&gt;&#10;&lt;li&gt;SBOM의 개념과 중요성&lt;/li&gt;&#10;&lt;li&gt;리눅스 재단의 SBOM 생성 과정&lt;/li&gt;&#10;&lt;li&gt;주요 도구와 프로세스&lt;/li&gt;&#10;&lt;li&gt;SBOM 통합과 향후 계획&lt;/li&gt;&#10;&lt;li&gt;청중 질의응답&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="1-발표자-소개"&gt;1. 발표자 소개&lt;/h2&gt;&#10;&lt;h3 id="gary-oneall"&gt;&lt;strong&gt;Gary O’Neall&lt;/strong&gt;&lt;/h3&gt;&#10;&lt;p&gt;Gary O’Neall은 &lt;a href="https://spdx.dev/about/overview"&gt;SPDX&lt;/a&gt; 표준에 기여한 전문가로, 오픈소스 소프트웨어의 구성요소, 라이선스, 저작권, 보안 참조 정보를 전달하는 데 중점을 둔 표준을 개발해왔습니다. 그는 Source Auditor Inc.에서 제품 개발 및 기술을 담당하며, 오픈소스 소프트웨어의 기술적 및 법적 위험 관리를 돕는 도구를 개발하고 있습니다.&lt;/p&gt;&#10;&lt;h3 id="jeff-shapiro"&gt;&lt;strong&gt;Jeff Shapiro&lt;/strong&gt;&lt;/h3&gt;&#10;&lt;p&gt;Jeff Shapiro는 &lt;a href="https://www.linuxfoundation.org"&gt;리눅스 재단&lt;/a&gt;의 라이선스 스캐닝 디렉터로, 30년 이상의 소프트웨어 산업 경험을 보유하고 있습니다. 그는 오픈소스 스캐닝 및 OSS(오픈소스 소프트웨어) 라이선스 준수 교육에 전문성을 가지고 있으며, 현재 리눅스 재단에서 중요한 프로젝트들의 코드 관리와 SBOM 생성에 기여하고 있습니다.&lt;/p&gt;</description></item><item><title>2024-11-27 취약점과 미래 - 다층적 소프트웨어 취약점과 대응 전략</title><link>https://korea-wg.openchainproject.org/en/resource/sbom_work_group/2024-11-27/</link><pubDate>Wed, 27 Nov 2024 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/resource/sbom_work_group/2024-11-27/</guid><description>&lt;p&gt;source: &lt;a href="https://openchainproject.org/news/2024/12/04/sbom-study-group-2024-11-27"&gt;https://openchainproject.org/news/2024/12/04/sbom-study-group-2024-11-27&lt;/a&gt;&lt;/p&gt;&#10;&lt;h2 id="목차"&gt;목차&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;소개&lt;/li&gt;&#10;&lt;li&gt;발표자 소개&lt;/li&gt;&#10;&lt;li&gt;웨비나 개요&lt;/li&gt;&#10;&lt;li&gt;Software Bill of Materials (SBOM)의 중요성&lt;/li&gt;&#10;&lt;li&gt;공급망 위험과 취약점&lt;/li&gt;&#10;&lt;li&gt;오픈소스 소프트웨어의 보안 성숙도&lt;/li&gt;&#10;&lt;li&gt;취약점 해결 전략&lt;/li&gt;&#10;&lt;li&gt;Software Heritage 프로젝트 소개&lt;/li&gt;&#10;&lt;li&gt;CycloneDX의 도전과제&lt;/li&gt;&#10;&lt;li&gt;질의응답&lt;/li&gt;&#10;&lt;li&gt;결론&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;h2 id="1-소개"&gt;1. 소개&lt;/h2&gt;&#10;&lt;p&gt;이 블로그 포스트는 &lt;a href="https://www.openchainproject.org/"&gt;OpenChain Project&lt;/a&gt;의 SBOM Study Group 웨비나에서 발표된 &amp;ldquo;취약점과 미래 - 다층적 소프트웨어 취약점과 대응 전략&amp;quot;에 대한 내용을 다룹니다. 이 웨비나는 소프트웨어 공급망 보안과 취약점 관리의 중요성을 강조하며, 현재의 도전과제와 미래의 전략을 탐구합니다.&lt;/p&gt;&#10;&lt;h2 id="2-발표자-소개"&gt;2. 발표자 소개&lt;/h2&gt;&#10;&lt;p&gt;발표자인 Okada San은 &lt;a href="https://owasp.org/"&gt;OWASP&lt;/a&gt; Japan의 전문가로, 일본 기업에서 애플리케이션 보안 강화와 소프트웨어 생산성 팀을 지원하는 보안 연구원입니다. OWASP 재단의 평생 회원으로, 20년 이상 다양한 문서 번역 작업에 참여해 왔습니다.&lt;/p&gt;</description></item><item><title>2024-10-29 SBOM 관련 다양한 규제와 가이드라인에 대한 개요</title><link>https://korea-wg.openchainproject.org/en/resource/sbom_work_group/2024-10-29/</link><pubDate>Tue, 29 Oct 2024 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/resource/sbom_work_group/2024-10-29/</guid><description>&lt;p&gt;source: &lt;a href="https://openchainproject.org/news/2024/10/29/openchain-sbom-study-group-october-2024-10-23-full-recording"&gt;https://openchainproject.org/news/2024/10/29/openchain-sbom-study-group-october-2024-10-23-full-recording&lt;/a&gt;&lt;/p&gt;&#10;&lt;h2 id="목차"&gt;목차&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;세미나 개요&lt;/li&gt;&#10;&lt;li&gt;발표 내용&lt;/li&gt;&#10;&lt;li&gt;질의응답&lt;/li&gt;&#10;&lt;li&gt;결론 및 향후 계획&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;h2 id="1-세미나-개요"&gt;1. 세미나 개요&lt;/h2&gt;&#10;&lt;h3 id="제목"&gt;제목&lt;/h3&gt;&#10;&lt;p&gt;OpenChain SBOM 스터디 그룹 - 2024년 10월 세미나&lt;/p&gt;&#10;&lt;h3 id="발표자-소개"&gt;발표자 소개&lt;/h3&gt;&#10;&lt;p&gt;이번 세미나의 발표자는 &lt;a href="https://www.toshiba.co.jp/"&gt;도시바&lt;/a&gt;의 Ninjouji-san입니다. 도시바는 일본의 대표적인 다국적 전자 기업으로, 오픈소스 및 SBOM 관련 분야에서 풍부한 경험을 보유하고 있습니다.&lt;/p&gt;&#10;&lt;h3 id="웨비나-소개와-목적"&gt;웨비나 소개와 목적&lt;/h3&gt;&#10;&lt;p&gt;이번 &lt;a href="https://www.openchainproject.org/"&gt;OpenChain&lt;/a&gt; SBOM 스터디 그룹 세미나는 다양한 규제와 가이드라인에 대한 개요를 제공하고, 향후 미팅에서 필요한 사항들에 대해 논의하는 것을 목적으로 합니다. &lt;a href="https://www.cisa.gov/sbom"&gt;SBOM(Software Bill of Materials)&lt;/a&gt;은 소프트웨어 구성 요소를 투명하게 관리하고 보안 취약점을 효과적으로 대응하기 위한 중요한 도구로 주목받고 있습니다.&lt;/p&gt;</description></item><item><title>2024-10-29 SBOM 시각화 - SBOM 검토를 위한 대안적 접근법</title><link>https://korea-wg.openchainproject.org/en/resource/webinar/2024-10-29/</link><pubDate>Tue, 29 Oct 2024 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/resource/webinar/2024-10-29/</guid><description>&lt;p&gt;source: &lt;a href="https://openchainproject.org/news/2024/10/29/webinar-sbom-visualization"&gt;https://openchainproject.org/news/2024/10/29/webinar-sbom-visualization&lt;/a&gt;&lt;/p&gt;&#10;&lt;h2 id="목차"&gt;목차&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;소개&lt;/li&gt;&#10;&lt;li&gt;SBOM의 중요성과 과제&lt;/li&gt;&#10;&lt;li&gt;SBOM 시각화 도구 소개&lt;/li&gt;&#10;&lt;li&gt;시각화 요소 및 기능&lt;/li&gt;&#10;&lt;li&gt;Chromium 프로젝트 사례 분석&lt;/li&gt;&#10;&lt;li&gt;Q&amp;amp;A 세션&lt;/li&gt;&#10;&lt;li&gt;결론&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;h2 id="1-소개"&gt;1. 소개&lt;/h2&gt;&#10;&lt;h3 id="발표자-소개"&gt;발표자 소개&lt;/h3&gt;&#10;&lt;p&gt;이번 웨비나의 발표자는 &lt;a href="https://www.bitsea.de/"&gt;Bitsea GmbH&lt;/a&gt;의 창립자이자 CEO인 Andreas Kotulla 박사입니다. Andreas 박사는 소프트웨어 시스템 감사와 기업의 숨겨진 위험 식별 분야의 전문가입니다. 그는 기술 실사를 지원하고 주요 기반 시설(KRITIS) 운영자들에게 조언을 제공합니다. 또한 오픈소스 전략, 거버넌스, 프로세스, 툴체인에 대해 고객들에게 자문을 제공하며, 오픈소스 프로그램 오피스(OSPO) 및 스캐닝 관리 서비스를 제공합니다.&lt;/p&gt;</description></item><item><title>2024-07-30 킥오프 웨비나: SBOM의 실제 활용 방안 모색</title><link>https://korea-wg.openchainproject.org/en/resource/sbom_work_group/2024-07-30/</link><pubDate>Tue, 30 Jul 2024 00:00:00 +0000</pubDate><guid>https://korea-wg.openchainproject.org/en/resource/sbom_work_group/2024-07-30/</guid><description>&lt;p&gt;source: &lt;a href="https://www.slideshare.net/slideshow/openchain-sbom-study-group-kick-off-call-2024-07-30/270623321"&gt;https://www.slideshare.net/slideshow/openchain-sbom-study-group-kick-off-call-2024-07-30/270623321&lt;/a&gt;&lt;/p&gt;&#10;&lt;h2 id="목차"&gt;목차&lt;/h2&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;웨비나 소개&lt;/li&gt;&#10;&lt;li&gt;SBOM의 중요성과 OpenChain 프로젝트의 역할&lt;/li&gt;&#10;&lt;li&gt;SBOM 활용의 실제적 고려사항&lt;/li&gt;&#10;&lt;li&gt;SPDX Lite: SBOM 생성을 위한 간소화된 접근&lt;/li&gt;&#10;&lt;li&gt;향후 계획 및 참여 방법&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;h2 id="1-웨비나-소개"&gt;1. 웨비나 소개&lt;/h2&gt;&#10;&lt;h3 id="제목"&gt;제목&lt;/h3&gt;&#10;&lt;p&gt;OpenChain SBOM Study Group 킥오프 웨비나&lt;/p&gt;&#10;&lt;h3 id="발표자-소개"&gt;발표자 소개&lt;/h3&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Shane Coughlan: OpenChain 프로젝트 총괄 매니저&lt;/li&gt;&#10;&lt;li&gt;Kate Stewart: Linux Foundation의 오픈소스 기술 부사장&lt;/li&gt;&#10;&lt;li&gt;Kobota San: Sony에서 근무하며, 2024년 SBOM Study Group의 의장&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h3 id="웨비나-소개와-목적"&gt;웨비나 소개와 목적&lt;/h3&gt;&#10;&lt;p&gt;이 웨비나는 OpenChain 프로젝트의 새로운 SBOM Study Group의 킥오프 미팅입니다. 주요 목적은 대규모 및 복잡한 공급망에서 SBOM(Software Bill of Materials)을 실제로 어떻게 활용할 수 있는지에 대한 논의를 시작하는 것입니다. 이를 통해 SBOM의 실용적인 적용 방안과 공급망 내에서의 신뢰 구축 방법을 모색하고자 합니다.&lt;/p&gt;</description></item></channel></rss>