SBOM Submission Requirements
1. Standard Data Formats
SK Telecom supports both formats that have become established as global standards. Suppliers may choose and submit the format supported by the tool they use.
| Format | Version | Recommended Use | File Format |
|---|---|---|---|
| CycloneDX | v1.3, v1.4, v1.5, v1.6, v1.7 | Application security, vulnerability management focus | JSON (recommended), XML |
| SPDX | v2.2, v2.3 | License compliance focus | JSON, Tag-Value |
Note: Both formats are recognized equally, but CycloneDX (JSON) format is recommended for internal system interoperability.
Requirement Levels at a Glance
The requirement level of each item. A missing required item leads to rejection. A missing recommended item does not, but including it is encouraged.
| Item | Level | Details |
|---|---|---|
| Standard format and version (CycloneDX or SPDX) | Required | 1. Standard Data Formats |
| Metadata (timestamp, generation tool, top-level component) | Required | 2.1 Metadata |
| Component name and version | Required | 2.2 Component Information |
| Direct and transitive dependencies | Required | 2.3 Dependency Scope |
PURL (Package URL, a standard identifier that points to a software package; pkg: form, a type defined by the spec, and no empty namespace where the type requires one) | Required | 3. PURL Compliance |
| Dev-only dependencies | Recommended | 2.3 Dependency Scope |
| License information | Recommended | 4. Sample Documents |
| First-party components (the executables, libraries, firmware and archives the supplier builds and ships, plus vendor binaries and copied-in source that scans cannot find; with supplier, license and hash) | Recommended | 5. First-Party Components |
Download the example SBOM file (CycloneDX 1.6 JSON) that meets the acceptance criteria and compare its structure.
2. Required Information
The SBOM document you submit must include the following information. Missing information may result in rejection.
2.1 Metadata
Information about the document itself and the generation tool.
- Timestamp: Generation date and time (ISO 8601 format)
- Tool Info: Vendor, name, and version of the generation tool (e.g.,
CycloneDX-Maven-Plugin v2.7.9) - Component Info: Name and version of the top-level software being delivered
The Component Info name must be a unique value that identifies the specific device or product. An empty value, a meaningless value such as
., or a fixed path value that a generation tool fills in automatically (e.g.,/scan) will collide with a different submission and cause registration to be rejected. SK Telecom treats this value as an identifier that must be unique across all submissions.
Matching the File Name
When you submit multiple layers (OS, application, and so on), each layer’s top-level component name and version must match the leading part of that SBOM’s file name ({name}_{version}). For example, if the file name is myserver-os_1.0.0_bom.json, metadata.component.name (CycloneDX) or DocumentName (SPDX) must be myserver-os and the version must be 1.0.0.
Keep this name the same on a resubmission. It is the identity of the scan, so a changed name leaves the previous submission in place and vulnerabilities you have already fixed keep being counted.
Generating with BomLens fills this field in automatically from --project and --version, so you do not need to edit it by hand. For the per-layer file naming rule, see the “Submit each layer” section of How to Generate an SBOM.
Generation Tool Specification Format
Generation tool information must be recorded in the following fields depending on the format.
- SPDX: Record the tool name and version in the
creationInfo.creatorsfield with theTool:prefix - CycloneDX: Record
vendor,name, andversionin themetadata.toolsarray
// SPDX creationInfo example
"creationInfo": {
"created": "2026-04-06T03:22:00Z",
"creators": ["Tool: Syft-0.98.0", "Organization: VendorName"]
}
2.2 Components
Information about the individual libraries and packages that make up the software. Components the supplier builds itself can be listed here too (see 5. First-Party Components).
- Name: Component name (e.g.,
commons-lang3) - Version: Component version (e.g.,
3.12.0) — required. Record the exact version in SPDX’sversionInfofield or CycloneDX’sversionfield; without a version, vulnerability mapping is impossible. - PURL (Package URL): [Required] Package identifier
2.3 Dependency Scope
Important: Transitive dependencies must be included.
SK Telecom analyzes vulnerabilities based on the submitted SBOM. An SBOM that includes only direct dependencies may miss hidden vulnerabilities and may therefore be rejected.
| Dependency Type | Description | Inclusion |
|---|---|---|
| Direct | Libraries explicitly declared by the project | Required |
| Transitive | Libraries that the direct dependencies in turn depend on | Required |
| Dev-only | Libraries not included at runtime, such as test and build tools | Inclusion recommended |
What are transitive dependencies?
For example, if a project uses library-A directly, and library-A internally uses library-B, then library-B is a transitive dependency. Even if library-B has a vulnerability, it cannot be detected unless it is included in the SBOM.
Prerequisites for generating a correct SBOM
For transitive dependencies to be included accurately, the SBOM must be generated with the build (or package installation) completed. When only source code is present, transitive dependencies may be omitted.
- Java (Maven): Generate after running
mvn packageormvn dependency:resolve - Java (Gradle): Generate after running
./gradlew dependencies - Python: Generate after
pip install -r requirements.txt(with the virtual environment activated) - Node.js: Generate after running
npm installoryarn install - Go: Generate after running
go mod download
For how to include transitive dependencies with each tool, refer to the Using Open Source Tools guide.
3. Package URL (PURL) Compliance
PURL (Package URL) is a standard URL format for uniquely identifying a software package. SK Telecom’s vulnerability analysis system operates based on PURL, so a valid PURL must be included for every component.
Here, “component” means an entry in the SBOM’s components list (an individual library or package); it does not apply to the top-level product itself (the component information in the SBOM’s metadata). A first-party component that has a supplier and a SHA-512 hash may also be submitted without a PURL (see 5. First-Party Components).
A PURL must be in the standard format beginning with the
pkg:prefix. Free text such asname:versionororg/repo:tagis not allowed; in such cases vulnerability mapping is impossible and the SBOM will be rejected.
Some PURLs look well formed and still fail to match. The three rules below are not caught by schema validation, so check them with particular care.
3.1 Types Defined by the Spec
The type slot may only hold a type defined by the Package URL specification. These are names such as maven, npm, pypi and rpm that identify both the ecosystem and the repository to query; the full list is in purl-types-index.json in the specification repository.
An invented name (for example pkg:applications/java@11.0.25) passes format validation, but there is no way to tell which repository to query, so matching fails. pkg:generic/, which identifies no ecosystem, is not allowed for the same reason.
3.2 Types That Require a Namespace
The namespace is the slot between the type and the package name. The specification makes it required for these types:
alpm apk bitbucket composer deb git github golang huggingface maven qpkg rpm swift vscode-extension
When that slot is empty the identifier looks well formed but names no specific package, so matching fails and the SBOM is rejected. The two patterns seen most often in actual intake are these:
- Maven: the groupId belongs in the namespace.
pkg:maven/org.slf4j/jcl-over-slf4j@2.0.15is the correct form;pkg:maven/org.slf4j.jcl-over-slf4j@2.0.15, with the groupId and artifactId joined by a dot, is a coordinate that does not exist in the repository and is rejected. - OS packages (rpm, deb, apk): the distribution belongs in the namespace (
pkg:rpm/rhel/bind@9.11.36-16.el8_10.6). For Red Hat family packages, bothrhelandredhatare accepted.
The distribution value is only recognized in that position (the namespace). Placing it in a query parameter after the question mark (e.g. ?distro=rhel-8.10) is not accepted; that value is treated as auxiliary information and is not used for matching, so an empty namespace is rejected the same way as above.
3.3 What Belongs in the Namespace
The namespace must hold the identifier the repository itself uses. A human-readable company name or a URL is not an identifier. When a generation tool copies the vendor string from a manifest into the groupId slot, the result looks like pkg:maven/The%2BApache%2BSoftware%2BFoundation/poi@5.4.1 or pkg:maven/http%3A/www.jboss.org/jbossxts@1.1; neither coordinate exists in the repository, so neither matches. For Maven, record the real groupId, as in pkg:maven/org.apache.poi/poi@5.4.1.
3.4 PURL Examples by Language
| Ecosystem | PURL Format Example |
|---|---|
| Java (Maven) | pkg:maven/org.springframework/spring-core@5.3.20 |
| JavaScript (NPM) | pkg:npm/express@4.18.2 |
| Python (PyPI) | pkg:pypi/django@4.1.0 |
| Go | pkg:golang/github.com/gin-gonic/gin@v1.8.1 |
| .NET (NuGet) | pkg:nuget/Newtonsoft.Json@13.0.1 |
| Ruby (RubyGems) | pkg:gem/rails@7.0.4 |
| GitHub (Actions / source hosting) | pkg:github/actions/checkout@v3 |
| OS package (RPM) | pkg:rpm/centos/glibc@2.17-317.el7?arch=x86_64 |
3.5 Correct / Incorrect PURL Examples
| Incorrect | Correct |
|---|---|
commons-lang3:3.12.0 | pkg:maven/org.apache.commons/commons-lang3@3.12.0 |
actions/checkout:v3 | pkg:github/actions/checkout@v3 |
lodash@4.17.21 | pkg:npm/lodash@4.17.21 |
pkg:generic/foo@1.0 | (Change to a type appropriate for the ecosystem) |
pkg:applications/java@11.0.25 | (Change to a type defined by the spec) |
pkg:maven/org.slf4j.jcl-over-slf4j@2.0.15 | pkg:maven/org.slf4j/jcl-over-slf4j@2.0.15 |
pkg:maven/The%2BApache%2BSoftware%2BFoundation/poi@5.4.1 | pkg:maven/org.apache.poi/poi@5.4.1 |
pkg:rpm/bind@9.11.36-16.el8_10.6 | pkg:rpm/rhel/bind@9.11.36-16.el8_10.6 |
pkg:rpm/bind@9.11.36-16.el8_10.6?distro=rhel-8.10 | pkg:rpm/rhel/bind@9.11.36-16.el8_10.6 |
For detailed PURL specifications, refer to the official Package URL spec.
4. Sample Document
CycloneDX Sample
{
"bomFormat": "CycloneDX",
"specVersion": "1.6",
"version": 1,
"metadata": {
"timestamp": "2026-04-06T10:30:00Z",
"tools": [{
"vendor": "Example Corp",
"name": "cyclonedx-maven-plugin",
"version": "2.7.9"
}],
"component": {
"type": "application",
"name": "PaymentModule",
"version": "2.1.0",
"purl": "pkg:maven/com.example/payment-module@2.1.0"
}
},
"components": [{
"type": "library",
"name": "spring-core",
"version": "5.3.20",
"purl": "pkg:maven/org.springframework/spring-core@5.3.20",
"licenses": [{
"license": {
"id": "Apache-2.0"
}
}]
}]
}
5. First-Party Components
A source code scan finds the open source that comes in through package managers and lock files. It does not find the executables or libraries the supplier builds itself, binaries from a chip vendor, or code copied into the source tree without a package manager, so these are missing from the SBOM. SK Telecom recommends listing these components in the SBOM as well. This is a recommended item, so an SBOM without them is not rejected.
Why is this recommended?
- BSI TR-03183-2 v2.1.0, the technical guideline of Germany’s Federal Office for Information Security (BSI), defines the scope of an SBOM as every software part created by the supplier or a third party and delivered with the product (8.1.11). Executables and archives must be listed as components (3.2.1).
- Annex I, Part II(1) of the EU Cyber Resilience Act (CRA) requires manufacturers to draw up an SBOM covering at least the top-level dependencies of the product.
- Some European customers ask for an SBOM that covers the supplier’s own software as well as open source. The same SBOM can then serve both the SK Telecom submission and other customers.
What goes in?
List only the components the scan does not find. Do not list again the open source that came in through a package manager and that the scan already found.
- Deployable artifacts you build: executables, libraries, firmware images and archives. List one component per file you ship.
- Binaries from a vendor: drivers or prebuilt libraries from a chip vendor
- Third-party code copied in as source: code such as a HAL or an RTOS placed in the source tree without a package manager
For each component, give the name, version, supplier (a name with a URL or email address) and distribution license, and add a SHA-512 hash for components shipped as files. A license that is not on the SPDX License List, such as your own proprietary license, is written as a name starting with LicenseRef- (for example LicenseRef-ExampleCorp-Proprietary).
First-party components are not published to a package repository, so they have no PURL. A first-party component that has a supplier and a SHA-512 hash is exempt from the PURL requirement in section 3. Components obtained elsewhere, such as vendor binaries or copied-in source, still need a PURL.
Example declaration file
With BomLens, the components the scan cannot find are written into a sbom-declared.cdx.json file kept in the repository. The file is a CycloneDX document that holds only components, and it uses the CycloneDX field names as they are. The bomlens:origin property tells components you built (first-party) from components obtained elsewhere (third-party), and the bomlens:artifact property gives the path of the build artifact.
{
"bomFormat": "CycloneDX",
"specVersion": "1.6",
"components": [
{
"type": "application",
"name": "media-daemon",
"supplier": { "name": "Example Corp", "url": ["https://example.com"] },
"licenses": [ { "license": { "name": "LicenseRef-ExampleCorp-Proprietary" } } ],
"properties": [
{ "name": "bomlens:origin", "value": "first-party" },
{ "name": "bomlens:artifact", "value": "out/bin/media-daemon" }
]
},
{
"type": "library",
"name": "vendor-hal",
"version": "4.2.0",
"supplier": { "name": "Example Chip Vendor", "url": ["https://chip.example.com"] },
"licenses": [ { "license": { "id": "BSD-3-Clause" } } ],
"properties": [
{ "name": "bomlens:origin", "value": "third-party" }
]
}
]
}
A first-party component with no version takes the product version (--version). A third-party component must give the version you received. A component with no file of its own, such as a HAL compiled into the firmware, is listed without bomlens:artifact.
Adding them to the SBOM with BomLens
Run the build first so the artifacts the declaration file points to exist, then scan. BomLens adds the declared components to the SBOM and fills in, from each build artifact, the SHA-512 and SHA-256 hashes, the file name, and whether the file is an executable and whether it is an archive. A sbom-declared.cdx.json at the root of the scan target is read without any option; a file elsewhere is passed with --components (repeat the option for several files).
make # builds the artifacts the declaration file points to (e.g. out/bin/media-daemon)
/path/to/scripts/scan-sbom.sh --project "MediaBox" --version "2.1.0" \
--components sbom-declared.cdx.json \
--generate-only
To check against BSI TR-03183-2, add the options below. --supplier records the product’s supplier, --sbom-author the SBOM author, and --license the product’s distribution license. If the SBOM does not meet the guideline, --fail-on-conformance makes the CI job fail.
/path/to/scripts/scan-sbom.sh --project "MediaBox" --version "2.1.0" \
--components sbom-declared.cdx.json \
--generate-only \
--conformance-profile bsi-tr-03183-2 --fail-on-conformance \
--supplier "Example Corp <https://example.com>" \
--sbom-author "Example Corp <sbom@example.com>" \
--license Apache-2.0
The scan refuses a declaration file that breaks its rules (for example, a component without bomlens:origin, or a build artifact that does not exist), and the CI job fails. The --components option and the bsi-tr-03183-2 profile are available from BomLens v1.14.0. For the file format, the refusal rules, examples by platform (Android, Zephyr, bare-metal firmware, Yocto) and a GitHub Actions example, see the BomLens guide Declaring your own components.
References
Related Documents
- Supplier Guide Home
- BomLens: SK Telecom’s SBOM generation tool
- Using Open Source Tools: Guidance on open source tools such as cdxgen and Syft
- Validation Checklist: Items to verify before submission, plus the validation tools (BomLens automated validation, CycloneDX Validator)
- Submission Process: Submission method and email template
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.