> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/concepts/sbom-and-supply-chain.md).

# SBOM and software supply chain

Understand Software Bills of Materials, SLSA provenance, and how Harness Artifacts and SCS help you secure and verify your software supply chain.

A Software Bill of Materials (SBOM) is a machine-readable inventory of every component inside a software artifact: every package, version, license, and dependency.

Most of the code in a modern application is open-source: libraries, packages, and base images you did not write and do not control. Every npm package, Python library, Maven dependency, and Docker base image you depend on is part of that surface. Your software supply chain is as much a security concern as the code you write yourself.

## What is an SBOM?

A **Software Bill of Materials (SBOM)** is a machine-readable inventory of every component in a software artifact. Think of it as the ingredient list on packaged food: it tells you exactly what is inside, where each component came from, what version it is, and what license it carries.

A complete SBOM includes:

* Every package and library included in the artifact
* The version of each component
* The supplier or origin of each component
* The license under which each component is distributed
* The relationships between components (what depends on what)

Two standard formats are in wide use:

| Property                       | CycloneDX                                                    | Software Package Data Exchange (SPDX)                                      |
| ------------------------------ | ------------------------------------------------------------ | -------------------------------------------------------------------------- |
| Primary use case               | Security, designed for vulnerability management              | License compliance, originally developed for license audits                |
| Vulnerability database support | Well-supported by vulnerability databases and scanning tools | Growing support, historically weaker than CycloneDX                        |
| Open-source tooling adoption   | Strong in security tooling                                   | Broader adoption across general open-source tooling                        |
| Standards body                 | Open Worldwide Application Security Project (OWASP)          | Linux Foundation, ISO/IEC (International Electrotechnical Commission) 5962 |

Harness Supply Chain Security (SCS) supports both formats.

## Where does Harness generate SBOMs?

When security scanning is configured on a Docker or Helm registry, Harness generates an SBOM alongside the vulnerability scan as part of the **HARNESS ARTIFACT SCAN PIPELINE**. The SBOM is attached to the artifact and accessible on the **SBOM tab** of the artifact detail page.

The SBOM tab shows the complete dependency list for the scanned image: package names, versions, software suppliers, package manager origins, and the total component count. You can download the full SBOM document for use in audits, compliance submissions, or further analysis.

No connector or additional configuration is required to reference an artifact stored in Harness Artifacts from an SCS pipeline step. The integration is built in.

SBOM generation through the Harness Artifact Scan Pipeline covers Docker and Helm OCI images only. For other artifact types, use Harness SCS pipeline steps with an external scanner that supports your package format.

## SBOM scoring

Harness computes an **SBOM score** for each scanned artifact. The score reflects:

* **Completeness**: How much of the SBOM was successfully resolved (missing versions or suppliers lower the score).
* **License risk**: Whether any component carries a high-risk license (GPL, AGPL, or unknown).
* **Vulnerability exposure**: The aggregate CVE count and severity distribution across all components.

The score gives a quick, at-a-glance health signal before you drill into individual findings.

## SLSA provenance

An SBOM tells you what is in an artifact. **SLSA provenance** tells you how and where that artifact was built.

SLSA (Supply-chain Levels for Software Artifacts, pronounced "salsa") is a framework developed by Google and the Open Source Security Foundation that defines levels of build integrity from Level 0 (no guarantees) to Level 4 (fully hermetic, reproducible builds). Each level adds verifiable evidence about the build process.

Harness SCS can generate **SLSA provenance attestations**: cryptographically signed documents that record:

* The exact source commit the artifact was built from
* The build system and pipeline that ran
* The timestamp of the build
* The digest of the output artifact

The attestation is signed with a key that consumers can verify. If the attestation cannot be verified, the artifact is not what it claims to be. This makes SLSA provenance a strong defense against supply chain attacks where a build system is compromised to inject malicious code into an otherwise legitimate artifact.

## Regulatory context

Two regulatory requirements are driving SBOM adoption:

* **US Executive Order 14028 (2021)**: Requires SBOMs for software sold to the US federal government. The NTIA has defined minimum elements that a compliant SBOM must include.
* **EU Cyber Resilience Act**: Requires manufacturers of products with digital components to provide SBOMs as part of their security documentation.

Harness Artifacts combined with SCS is designed to support both requirements: SBOMs are generated automatically at push time, stored alongside the artifact, downloadable on demand, and include the NTIA-defined minimum elements for Docker and Helm images.

## Use cases

**Blast-radius analysis after a CVE is announced**

A critical vulnerability is published in a popular base image library. A security engineer searches the SBOM index in Harness SCS to find every artifact in every registry that includes the affected component and version. The blast-radius report is available in minutes, not days.

**License compliance audit**

A legal team requires that no commercial product ship with GPL-licensed code. A platform engineer runs an SBOM-based license scan across all production registries. Any artifact containing GPL components surfaces immediately. The finding is addressed before the release ships.

**SLSA Level 2 compliance for a government contract**

A software vendor must demonstrate that their build pipeline meets SLSA Level 2 requirements. They configure Harness SCS to generate SLSA provenance attestations for every build. When the customer audits the delivery, the vendor provides the signed attestation for each artifact, proving build integrity.

## Next steps

* To view, score, and download SBOMs, go to [SBOM: view, score, and download](https://developer.harness.io/artifact-registry/3.0/security-and-compliance/sbom-view-score-and-download.md).
* To understand how vulnerability scanning integrates with SBOM generation, go to [Vulnerability scanning](https://developer.harness.io/artifact-registry/3.0/security-and-compliance/vulnerability-scanning.md).
* To reference an artifact directly in a Security Testing Orchestration (STO) or SCS pipeline step, including the SLSA Generation step, go to [Security Testing Orchestration and Supply Chain Security](https://developer.harness.io/artifact-registry/3.0/platform-integrations/sto-scs-integration.md).
* For deeper supply chain security capabilities including SLSA policy enforcement and attestation verification, refer to the [Harness Supply Chain Security](https://developer.harness.io/software-supply-chain-assurance/) documentation.

{% @harness-feedback/feedback %}
