> 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/security-testing-orchestration/use-sto/artifacts.md).

# Artifacts

Learn how to investigate container artifacts, review security findings and SBOMs, and configure artifact settings and agents.

Artifacts provides a centralized view of the artifacts scanned by Harness Security Testing Orchestration (STO) and their associated security findings. It helps you identify artifacts with security risks without having to trace findings across individual pipeline executions. You can search and filter artifacts, review their types and versions or tags, assess findings by severity, and check when they were last scanned. The artifact-level view provides a way to identify artifacts that require further security investigation.

***

## What you will learn from this topic <a href="#what-you-will-learn-in-this-topic" id="what-you-will-learn-in-this-topic"></a>

By the end of this topic, you will be able to understand:

* The purpose and structure of Artifacts in STO.
* The way STO decides which version and which scan an artifact row represents.
* The steps to filter, sort, and search the artifact list.
* The steps to investigate an artifact's findings, scan history, and individual findings.
* The steps to set the baseline version for an artifact.

***

## Before you begin <a href="#before-you-begin" id="before-you-begin"></a>

* Make sure that STO is enabled for your account, organization, and project.
* Make sure that at least one artifact has been scanned in the current project. An artifact appears on this page only after STO ingests a scan for it.
* You must have the necessary permissions to view findings and configure settings.
* To use the **Harness AI** sub-tab on the **Remediation** tab, Harness AI must be enabled for your account. Navigate to **Account Settings** → **Default Settings** → **Harness AI** and enable the setting. For more information, go to [Fix security vulnerabilities using Harness AI](https://developer.harness.io/security-testing-orchestration/use-sto/sto-remediate-issues/ai-based-remediations).

***

## Understand artifacts

STO models an artifact as a scan target, and each version or tag of that artifact as a variant of the target. When a security scan runs, STO ingests the scan results and associates the reported findings with the artifact and the specific version or tag that was scanned. This allows STO to track security findings across different versions of the same artifact and maintain their scan history.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2F9ve2L45GdWOatVKoFbbX%2Fartifacts-overview.png?alt=media&amp;token=6514597e-a370-468c-9ab9-e88910a79cf6" alt="Artifacts overview"><figcaption><p>Artifacts page overview</p></figcaption></figure>

Each artifact can have multiple versions or tags, and STO uses the configured baseline version to determine which variant represents the artifact in the summary. STO selects that version as follows:

* If you have set a baseline version for the artifact, STO uses the most recent scan of that baseline version.
* If you have not set a baseline version, STO uses the most recent scan across the available versions or tags of that artifact.

The baseline helps establish a consistent reference version for tracking security findings. Without a configured baseline, STO uses the most recently scanned version or tag as the reference for the artifact.

STO maintains a pre-computed summary of the ingested scan data. This allows the artifact list and its summary information to remain responsive even when a project contains a large number of artifacts and findings.

Summary counts refresh a few seconds after a scan completes, rather than within the scan itself. As a result, findings from a recently completed scan may take a short time to appear in the artifact summary.

The following table provides a structured overview of why Artifacts is used, when it should be used, and how to leverage it within STO to assess artifact security, track findings across versions, and investigate security risks.

| Why use it?                                                                                                                                                                                                    | When to use it?                                                           | How can you leverage it?                                                                                                                                                    |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pipeline-centric views show scan results for individual executions, making it difficult to assess and compare the security posture of different artifacts.                                                     | You need to identify artifacts with the most security findings.           | Sort the artifact list by Total findings to identify artifacts with the most security findings, then investigate the artifacts that need attention.                         |
| Without a baseline version, STO uses the most recently scanned version or tag as the reference for the artifact-level summary.                                                                                 | You are rolling out STO across artifacts with multiple versions or tags.  | Use the Baseline set and Not set split in the Artifacts widget to identify artifacts that still need a baseline version configured.                                         |
| Findings are associated with the artifact and the specific version or tag that was scanned. Reviewing them at the artifact level helps you understand the security risks associated with a particular version. | You need to investigate security findings in a specific artifact version. | Open the artifact to review its scan details and findings. Investigate individual findings to understand their severity, the components affected, and remediation guidance. |

***

## Key components of the artifacts page

Navigate to **Security Testing Orchestration** → **Artifacts** to open the page. It has three parts: a row of summary widgets, a controls row, and the artifact table.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2Fti9xJixcd8bXIb3OdDlF%2Fartifact-key-components.png?alt=media&amp;token=a2467e1f-8882-4c77-b527-06e0e96647a2" alt="Artifacts page components"><figcaption><p>Components of the artifacts page</p></figcaption></figure>

#### Summary widgets

The three widgets at the top summarize artifact posture across all artifacts scanned in the current project. The **Artifacts** and **Findings by severity** widgets each include an information icon that explains what the widget counts.

The widgets display the following information:

| Widget                         | Description                                                                                                                                                                                                                                                                                             |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Artifacts**                  | The total number of artifacts in the project, followed by the number of artifacts ingested from each provider, displayed as a provider icon and a count. A coverage bar below splits the total into **Baseline set** and **Not set**, indicating how many artifacts have a baseline version configured. |
| **Findings by severity**       | The total number of active findings across the artifacts, broken down into **C**, **H**, **M**, and **L** counts for Critical, High, Medium, and Low severity.                                                                                                                                          |
| **Deployments by environment** | The total number of deployments associated with the artifacts, split into **Production** and **Non-production** environments.                                                                                                                                                                           |

{% hint style="info" %}
Severity counts on this page use each finding's scanner-reported severity. Severity overrides and exemptions are not applied to these list counts.
{% endhint %}

#### Controls row

The controls row is displayed between the summary widgets and the artifact table. It provides the following options to search and filter artifacts:

* **Search Artifacts**: Enter all or part of an artifact name to narrow the list.
* **Severity**: Select one or more of the following severities from the dropdown to show only artifacts that have at least one finding at the selected severity.
  * Choose **Critical** to show artifacts that have at least one Critical finding.
  * Choose **High** to show artifacts that have at least one High finding.
  * Choose **Medium** to show artifacts that have at least one Medium finding.
  * Choose **Low** to show artifacts that have at least one Low finding.
* **+ Add filter**: Select one of the following additional attributes from the dropdown to filter the artifact list.
  * **Source**: Choose a source to show only artifacts ingested from the selected source. Available options depend on the types of artifacts scanned.
  * **Scanner**: Choose a scanner to show only artifacts scanned by the selected scanner. The available options depend on the scanners used to scan the artifacts.

Filters combine with *AND* across categories and *OR* within a category. For example, selecting *Critical* and *High* shows artifacts that have either a *Critical* or a *High* finding.

#### Artifact table

The table lists one row per artifact. You can sort the **Findings** and **Last scanned** columns. By default, the list is sorted by **Last scanned** in descending order, with the most recently scanned artifacts appearing first.

The table displays the following information:

| Column            | Description                                                                                                                                                                                                      |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Artifact Name** | Displays the provider icon and the artifact name.                                                                                                                                                                |
| **Source**        | Displays the source from which the artifact was ingested, such as Docker Hub or a local image.                                                                                                                   |
| **Artifact Type** | Displays the type of artifact scanned, such as Container.                                                                                                                                                        |
| **Findings**      | Displays severity-bucketed finding counts using **C, H, M, and L** labels for Critical, High, Medium, and Low. Sorting orders artifacts by severity weight, from Critical to Low, rather than by the label text. |
| **Version / Tag** | Displays the version or tag of the artifact represented by the row. This is the baseline version when one is configured, and the most recently scanned version or tag otherwise.                                 |
| **Last scanned**  | Displays how long ago the artifact was last scanned, as a relative timestamp.                                                                                                                                    |

Selecting a row opens the artifact detail view. The action menu at the end of each row provides artifact-level actions.

**Row actions**: Select the three-dot menu at the end of an artifact row to access the following actions:

* **View execution result**: Opens the execution result associated with the artifact.
* **Set baseline**: Sets the selected artifact version as the baseline version.

The **Columns** dropdown is located at the right hand top of the artifact table. It lets you choose which columns to display in the artifact table. Select or clear the available columns to customize the table according to the information you want to view. The control also displays the number of currently visible columns against the total number of available columns, for example, *7/7*.

***

## Investigate an artifact

Harness enables you to click an artifact in the artifact table to view it in detail. The artifact detail page has three tabs: **Overview**, **Scan History**, and **Configuration**. The **Overview** tab opens by default. The version selector at the top of the page controls which variant each tab reports on. The header beside it displays the total number of versions available for the artifact and the last scan date.

### Step 1: Review the Overview tab

The **Overview** tab summarizes the selected artifact's security posture, including findings from content digests and available software bill of materials (SBOMs). The baseline version is selected by default. You can use the version dropdown to select another available version or tag and review its associated scan data. The tab also displays general artifact information, such as its name, type, source, registry URL, and content digest.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2FUSbjuCP89cIl5lv6r3IK%2Fartifact-overview-tab.png?alt=media&amp;token=b469c2c9-4590-420b-a5bc-f9e0ed2d265c" alt="artifact scan overview"><figcaption><p>Overview of a single artifact</p></figcaption></figure>

The Overview tab displays the following information:

* **General information:** Displays the artifact's name, type, source, registry URL, and content digest. You can copy the registry URL and digest values. An artifact can have multiple content digests. When additional digests are available, the remaining digests are grouped into a **+n** chip.
* **Findings:** Displays the total number of active findings for the selected artifact version, split into **C, H, M, and L** for Critical, High, Medium, and Low.
* **SBOM:** Displays the total number of SBOM components associated with the artifact.
* **Findings by digest:** Displays active findings by severity across each content digest associated with the artifact. The table includes *Critical*, *High*, *Medium*, *Low*, and *Total counts* for each digest.

### Step 2: Review scan history

The **Scan History** tab lists every scan recorded against the artifact, with the most recent scans appearing first. Each row represents a scan execution and provides details about the artifact version and content digest scanned, the findings reported, and the scanner used.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2FKrVYBlPLWT1cjmambqlj%2Fartifact-scan-history.png?alt=media&amp;token=0e9b3ce6-bdf5-420e-8f31-648b74051bfd" alt="Artifact scan details"><figcaption><p>Scan details of an artifact</p></figcaption></figure>

You can filter the scan history using the following attributes:

* **Source:** Choose a CI source to show scans triggered through the selected source. Available options include *Harness*, *Jenkins*, and *GitHub Actions*.
* **Version / Tag:** Choose an artifact version or tag to show scans associated with that variant.
* **Digest:** Choose a content digest to show scans associated with that digest.
* **Scan type:** Choose one or more scan types to show scans that include the selected types. Available options include *SAST*, *SCA*, *Secret*, *Container*, *DAST*, and *IaC*.
* **Scanner:** Choose one or more scanners to show scans performed by the selected scanners. Available options include *Aqua Trivy*, *CheckmarxOne*, *Grype*, *Harness Container*, *Prisma Cloud*, *Snyk*, and *Wiz.*

The available options for **Version / Tag** and **Digest** depend on the artifacts scanned, while the options for **Scan type** and **Scanner** depend on the scans performed.

The **Columns** control shows how many columns are currently visible out of the total available. For example, *10/10* means all columns are visible. You can use this control to show or hide columns.

The table displays the following information:

| Column            | Description                                                                                                                                                       |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Scan ID**       | Displays the scan number and the name of the scanner or pipeline that produced the scan. Selecting the scan ID opens the findings reported by that scan.          |
| **CI Source**     | Displays the CI source associated with the scan, such as Harness.                                                                                                 |
| **Digest**        | Displays the content digest associated with the scanned artifact.                                                                                                 |
| **Version / Tag** | Displays the artifact version or tag that the scan ran against.                                                                                                   |
| **Findings**      | Displays the **C, H, M, and L** counts for Critical, High, Medium, and Low findings reported by the scan.                                                         |
| **Scanner**       | Displays the scanner or scanners that ran during the scan. When more scanners run than the column can fit, the remaining scanners are grouped into a **+n** chip. |
| **Scan type**     | Displays the scan types performed during execution. When more scan types run than the column can fit, the remaining types are grouped into a **+n** chip.         |
| **Triggered by**  | Displays the identity that started the scan.                                                                                                                      |
| **Started**       | Displays how long ago the scan started, as a relative timestamp.                                                                                                  |
| **Duration**      | Displays how long the scan took to execute.                                                                                                                       |

### Step 3: Review the findings for a scan

Select a **Scan ID** in the Scan History table to open the scan details view. This view provides access to the findings and SBOM generated by that scan. It has two tabs: **Findings** and **SBOM**, with a count of the records available in each tab.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2F47nmZ2tUY11CmDyG8qIh%2Fartifact-scan-findings.png?alt=media&amp;token=dd444ced-99f1-408b-b643-94ec27337d11" alt="scan findings"><figcaption><p>Investigating scan findings</p></figcaption></figure>

#### Filter the findings

The **Findings** tab lists the security findings reported by the scan. You can search for a finding by its name, CVE, or CWE and use filters to narrow down the results.

The following filters are available:

* **Severity:** Choose one or more severity levels to show findings classified as *Critical*, *High*, *Medium*, or *Low*.
* **Scanner:** Choose one or more scanners to show findings reported by the selected scanners. Available options depend on the scanners that ran during the scan.
* **Issue Type:** Choose one or more issue types to show findings belonging to the selected categories, such as *SAST*, *DAST*, *SCA*, *IaC*, *Secret Detection*, *Misconfiguration*, *Bug Smells*, *Code Smells*, *Code Coverage*, and *External Policy*.
* **+ Add filter:** Select additional attributes from the dropdown to filter the findings.
  * **Fix Available:** Choose **Yes** or **No** to filter findings based on whether a fix is available.
  * **Reachability:** Choose **Reachable**, **Not Reachable**, or **Unproven** to filter findings by their reachability status.
  * **EPSS Probability:** Choose a probability threshold (**≥ 15%**, **≥ 5%**, or **≥ 1%**) or **N/A** to filter findings by their EPSS probability.
  * **EPSS Percentile:** Choose a percentile threshold (**≥ 99th**, **≥ 90th**, or **≥ 80th**) or **N/A** to filter findings by their EPSS percentile.
  * **CISA KEV:** Choose **Yes** or **No** to filter findings based on whether they are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
  * **AI Triaged:** Choose **Likely False Positive**, **Likely True Positive**, or **Not Evaluated Yet** to filter findings by their AI triage status.

#### Components of the finding table

The findings table displays the following information:

| Column              | Description                                                                                                                                                                                                                                                                                   |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Severity**        | Displays the severity assigned to the finding.                                                                                                                                                                                                                                                |
| **Finding**         | Displays the finding name or identifier.                                                                                                                                                                                                                                                      |
| **Reference ID**    | Displays the reference identifiers associated with the finding, such as CVE and CWE. The identifiers are clickable. When multiple identifiers are available, the remaining identifiers are grouped into a **+n** chip. Hover over the chip to view the remaining identifiers.                 |
| **Scanner**         | Displays the scanner that reported the finding.                                                                                                                                                                                                                                               |
| **Issue Type**      | Displays the category of the finding, such as *SCA*.                                                                                                                                                                                                                                          |
| **CVE**             | Displays the Common Vulnerabilities and Exposures (CVE) identifiers associated with the finding. The identifiers are clickable. When multiple CVE identifiers are available, the remaining identifiers are grouped into a **+n** chip. Hover over the chip to view the remaining identifiers. |
| **CWE**             | Displays the Common Weakness Enumeration (CWE) identifiers associated with the finding. The identifiers are clickable. When multiple CWE identifiers are available, the remaining identifiers are grouped into a **+n** chip. Hover over the chip to view the remaining identifiers.          |
| **Fix Available**   | Indicates whether a fix is available for the finding.                                                                                                                                                                                                                                         |
| **Reachability**    | Displays the reachability status of the finding, where available.                                                                                                                                                                                                                             |
| **EPSS Score**      | Displays the Exploit Prediction Scoring System (EPSS) score associated with the finding.                                                                                                                                                                                                      |
| **EPSS Percentile** | Displays the EPSS percentile associated with the finding.                                                                                                                                                                                                                                     |
| **CISA KEV**        | Indicates whether the vulnerability is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.                                                                                                                                                                                      |
| **AI Triaged**      | Displays the AI triage status of the finding.                                                                                                                                                                                                                                                 |

The **Columns** control lets you show or hide columns in the findings table. It also displays the number of currently visible columns against the total number available.

**Finding actions**: Select the three-dot menu at the end of a finding row to access the following actions:

* **Create Ticket**: Creates a Jira ticket for the selected finding.
* **Request Exemption**: Lets you request an exemption for the selected finding.

### Step 4: Open a finding

Select a finding to open its detail view. The view has two tabs: **Overview** and **Remediation**.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2FRmhPcvC5Vh84aQ9mWsbC%2Fartifact-scan-finding-details.png?alt=media&amp;token=3a5c6eb4-5518-4a33-aea5-0e0433a4c905" alt="Findings overview"><figcaption><p>Investigating finding details</p></figcaption></figure>

The header provides a quick summary of the selected finding:

* **Severity:** Displays the severity assigned to the finding, such as Critical or High.
* **Finding name:** Displays the finding identifier and title. For package vulnerabilities, it also includes the affected package name and version.
* **Target:** Identifies the artifact associated with the finding. The artifact name and icon indicate which artifact the finding was reported against.

Use the **back and forward arrows** at the top of the panel to navigate to the previous or next finding without returning to the findings list.

The **Overview** tab displays the following information:

* **Details:** Displays the finding *description*, *issue type*, *scanner*, *target*, and *target type*. Click **Show more** to view the complete description.
* **Metadata:** Displays additional information about the finding, including:
  * **Reference Identifiers:** Lists the associated CVE, CWE, and other reference identifiers.
  * **File Name:** Displays the name of the affected file.
  * **Library Name:** Displays the name of the affected library or package.
  * **Current Version:** Displays the version of the affected package.
  * **Upgrade Version:** Displays the recommended version to upgrade to, when available.
  * **CVSS Vector:** Displays the CVSS vector associated with the finding.
  * **CVSS Version:** Displays the CVSS version used to assess the finding.
  * **Issue ID:** Displays the unique identifier assigned to the finding.
  * **Target Name and Target Type:** Identify the affected target and its type.
  * **Variant Name:** Displays the artifact version or tag associated with the finding.
  * **Scanner Severity:** Displays the severity reported by the scanner.
  * **Reference URLs:** Lists external references associated with the finding. Click **Show more** to view additional URLs.
* **Occurrence Raw Details:** Displays the raw JSON data reported by the scanner for the finding occurrence. Use the copy icon to copy the raw details.

{% hint style="info" %}
The availability of these sections may depend on the scan type.
{% endhint %}

### Step 5: Review remediation guidance

The **Remediation** tab provides remediation guidance from two sources, selectable as sub-tabs.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2FCP2xGIuPzmli9Y1Oi3r0%2Fartifact-scan-finding-remediation-harness-ai.png?alt=media&amp;token=cbafb492-ed36-4537-b3fc-de8a5102d24d" alt="Remediate findings"><figcaption><p>Investigating remediation options</p></figcaption></figure>

{% tabs %}
{% tab title="Harness AI" %}
**Harness AI** provides guidance generated by Harness AI, under the heading **AI Remediation**. The guidance is based on public information about the CVE or CWE, along with the vulnerable code snippet where the scanner captured one.

{% hint style="info" %}

* When generated guidance does not pass validation, the tab displays a dismissible message at the top and you can click **Regenerate** to try again.
* Harness AI always returns an answer, but where no remediation exists in the model's training data the answer can be invalid. Assess a suggestion against your own target and use case before you apply it, and check the usage and license requirements of any component it tells you to install.
  {% endhint %}

Harness AI provides the following details in separate collapsible sections:

| Section                    | Description                                                                                                        |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Vulnerability overview** | What the vulnerability is and why it matters.                                                                      |
| **Attack scenario**        | How an attacker would exploit it, with an example payload you can copy.                                            |
| **Remediation Steps**      | Numbered steps to fix the finding, including any command to run.                                                   |
| **Secure coding pattern**  | A code example showing the safe pattern to adopt.                                                                  |
| **Root cause analysis**    | The underlying cause and the security principle that was violated.                                                 |
| **Test cases**             | Positive and negative tests, each with a description, an input, and the expected behavior.                         |
| **Verification checklist** | Checks to confirm the fix worked.                                                                                  |
| **Further considerations** | Additional hardening beyond the immediate fix.                                                                     |
| **References**             | Related standards and guidance, such as the CWE entry, the relevant OWASP Top 10 category, and OWASP cheat sheets. |

{% hint style="info" %}
The availability of these sections may depend on the scan type.
{% endhint %}

Code blocks in these sections have a copy icon. Below the guidance, the panel shows when it was generated, a **Regenerate** control to produce it again.
{% endtab %}

{% tab title="Scanner" %}
**Scanner** presents the fix that the scanner itself recommends, such as the version to upgrade a package to.
{% endtab %}
{% endtabs %}

### Step 6: Review the SBOMs for a scan

Select the **SBOM** tab to review the Software Bill of Materials generated by the scan. The tab displays the dependencies identified in the scanned artifact, along with their versions, types, licenses, and associated vulnerability information. The count beside the tab indicates the total number of SBOM components.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2Fmlm5pDMsJchLCdenloHs%2Fartifact-findings-sbom.png?alt=media&amp;token=acfcd2d3-dbd4-429d-846b-be2b35e5106b" alt="Scan SBOM details"><figcaption><p>Investigating SBOM details of a scan</p></figcaption></figure>

Use the search field to find a dependency by its name. You can also narrow down the list using the following filters:

* **Type**: Choose a dependency category to show only components belonging to that category. The available options depend on the types of components identified in the scanned artifact.
* **License**: Choose one or more licenses to show only dependencies associated with the selected licenses. The available options depend on the licenses identified in the scanned artifact.

The SBOM table displays the following information:

| Column               | Description                                                                                                                      |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **Dependency**       | Displays the name of the dependency identified in the SBOM.                                                                      |
| **Version**          | Displays the version of the dependency.                                                                                          |
| **Type**             | Displays the dependency type, such as `apk`.                                                                                     |
| **License**          | Displays the license associated with the dependency. If the license cannot be identified, the value is displayed as **Unknown**. |
| **Total CVEs**       | Displays the total number of CVEs associated with the dependency.                                                                |
| **Reachable CVEs**   | Displays the number of CVEs identified as reachable in the dependency.                                                           |
| **Exploitable CVEs** | Displays the number of CVEs identified as exploitable in the dependency.                                                         |
| **First seen**       | Displays when the dependency was first identified.                                                                               |

Select the **Export** button in the top-right corner of the SBOM tab to export the SBOM component information.

### Step 7: Open an SBOM dependency

Select a dependency in the SBOM tab to open its detail view. The detail view displays the dependency name and version, along with its package type. It has two tabs: **Overview** and **Findings**.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2Fx3kzBCnRIwwR1X9lt0S8%2Fartifact-scan-findings-sbom-detail.png?alt=media&amp;token=f5511652-a6b7-40a9-bcc3-8744cb9efe28" alt="SBOM dependency details"><figcaption><p>Investigating SBOM dependency</p></figcaption></figure>

The **Overview** tab displays the following information:

* **Current Version**: The version of the selected dependency.
* **License**: The license associated with the dependency.
* **Type**: The package type, such as `apk`.
* **PURL**: The Package URL (PURL) that uniquely identifies the dependency.

Select the **Findings** tab to view the findings associated with the selected dependency. The tab also displays the total number of findings.

***

## Set the baseline version

STO compares each artifact version against the configured baseline version to identify findings that are new to the artifact. You can configure the baseline on the **Configuration** tab, under **Harness Settings**. These settings are managed directly by Harness and are not read from the artifact registry.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2FOeDcjemTtB6iNxf3POs4%2Fartifact-set-baseline.png?alt=media&amp;token=82b70bad-4937-451e-8f10-b4850b4bcfb3" alt="General settings configuration"><figcaption><p>General settings configuration</p></figcaption></figure>

To set the baseline version, complete the following steps:

1. Open the artifact and select the **Configuration** tab.\
   The **General** settings opens by default.
2. Expand **Default version** if not expanded by default.
3. Under **Baseline definition**, select how to identify the baseline version:
   * **Fixed Values**: A specific version that you select and that does not change at runtime.
   * **RegEx**: A regular expression that is matched against version names. Use this when the baseline version name varies between scans.
4. Select the version from the **Baseline version** list. This field is required. The version currently set as the baseline is marked in the list.
5. Click **Save** in the page header. To abandon your changes, click **Discard**.

{% hint style="info" %}
The baseline version serves as the reference for identifying new findings in subsequent artifact scans.
{% endhint %}

For more information, go to [Set up target baselines in STO](https://developer.harness.io/security-testing-orchestration/troubleshooting-and-resources/sto-use-cases/set-up-sto-pipelines/set-up-baselines).

***

## Enable the triage agent

Enable the Triage Agent to automatically triage findings for selected artifact image variants.

<figure><img src="https://2033425938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fna57sNwixrWxOX8cOMRg%2Fuploads%2FsxGSS5ZHD4np7O3byfDN%2Fartifact-enable-triage-agent.png?alt=media&amp;token=f0c75987-0143-43ab-9fbc-8da10e3b0808" alt="Triage agent settings"><figcaption><p>Triage agent settings</p></figcaption></figure>

To enable the Triage Agent, complete the following steps:

1. Open the artifact and select the **Configuration** tab.\
   The **General** settings opens by default.
2. Select **Agents** to open the agents settings.
3. Under **Agents**, select **Triage Agent**.
4. Enable the **Enable Triage Agent** toggle.
5. Under **Tag variant**, select one or more image variants for which you want the agent to run.
   * If you leave this field empty, the agent runs against the configured baseline tag by default.
6. Click **Save** in the page header to apply your changes. To abandon your changes, click **Discard**.

{% hint style="info" %}
The Triage Agent runs only against the selected image variants. You can select multiple variants if you want the agent to triage findings across them.
{% endhint %}

***

## Next Steps

* [Set up target baselines in STO](https://developer.harness.io/security-testing-orchestration/troubleshooting-and-resources/sto-use-cases/set-up-sto-pipelines/set-up-baselines): Understand how baselines separate issues in your branch from issues already in the baseline.
* [Fix security vulnerabilities using Harness AI](https://developer.harness.io/security-testing-orchestration/use-sto/sto-remediate-issues/ai-based-remediations): Refine AI remediation suggestions with additional context and code snippets.
* [AI-based remediations](https://developer.harness.io/security-testing-orchestration/use-sto/sto-remediate-issues): Create pull requests and code suggestions from AI remediation advice.
* [Key concepts](https://developer.harness.io/security-testing-orchestration/new-to-sto/key-concepts): Learn about scan targets, baselines, severities, and exemptions.
