---
title: Build JFrog configurations
slug: build-jfrog-configurations
docTags: 
createdAt: 2026-07-17T21:49:50.776Z
---

Before software package and vulnerability data from **JFrog** can be analyzed in DevOps Intelligence , you must configure JFrog as a tool for the application and onboard the associated Technical Service. This process enables DevOps Intelligence to collect software package inventory and vulnerability information from JFrog repositories and artifacts.

The setup consists of two main tasks:

1. **Configure the JFrog tool for the application** by adding a Software Package tool configuration in the Build phase.
2. **Onboard a Technical Service** associated with the application to define the JFrog repository and artifacts that DevOps Intelligence should monitor.

Once the configuration and onboarding are complete, DevOps Intelligence automatically synchronizes software package and vulnerability data from JFrog.&#x20;

# Setting up Tool application configurations from JFrog

To onboard software package data, users need to edit the tool configuration for the application and then onboard the associated Technical Service.&#x20;

Follow this path the edit the tool application configuration from Jfrog:

1. From the Kyndryl Bridge main menu :inlineImage[]{src="https://api.archbee.com/api/optimize/QU1TIK52ntw5Jsos0uOt5/NK7Yw9tQgnlqBGwu7eG4H-20260601-205917.svg" alt caption width="57" height="57"}, go to  **Services** → **Platform Services** → **Toolchain & Pipeline&#x20;**→ **DevOps Intelligence&#x20;**→ **Settings & Utilities&#x20;**→ **Application Configurations**
2. Select the application you want to configure and expand it to display the following sections:&#x20;

- DevOps Phase&#x20;
- Tools Configured&#x20;
- Tools Having Technical Services&#x20;

3. Click the **ellipsis (...)** and select **Edit Tool Configuration**.&#x20;
4. On the Edit Configurations page, locate the **Build** phase and click **Add Tool Configuration**.&#x20;
5. On the Edit Tool Configuration page, configure the following:&#x20;

- **Build Category**: Software Package&#x20;
- **Tool Engine**: JFrog&#x20;
- Ensure that the Tool Category **Out-of-the-box** is **checked,&#x20;**&#x74;his because software package and vulnerability data is collected from JFrog.&#x20;

6. Review the available mappings for:&#x20;

- **Release Format** (can be modified if required).&#x20;
- **Severity**: Critical, High, Medium, and Low.&#x20;
- **Package Status**: Allowed, Denied, Need Approval, and Uncategorized.&#x20;

7. Click **Add Configuration**, then select **Next.**&#x20;
8. Click **Submit** to save the configuration.&#x20;

Once saved, the Software Package tool is added to the application and the configured tool should appear as JFrog under the application's configured tools.&#x20;

# Onboard Technical Service from JFrog

After configuring the tool applications, users need to onboard a technical service to enable DevOps Intelligence to collect software package and vulnerability data from JFrog.&#x20;

Follow these steps to onboard a Technical Service for a Software package:&#x20;

1. Identify the application, **click the ellipsis (...)**, and select **Onboard Technical Service**.&#x20;
2. On the **Onboard Technical Service** page, configure the following settings:&#x20;

- **DevOps Phase:** Build&#x20;
- **Build Category:** Software Package&#x20;
- **Tool Engine:** JFrog&#x20;
- **Connection:** Select the JFrog connection.&#x20;
- **Repository:** Select the repository containing the artifacts to be onboarded.&#x20;
- **Artifacts:** Select the artifacts for which package and vulnerability data should be collected.&#x20;

3. Click **Onboard**.&#x20;

After the onboarding request is submitted, DevOps Intelligence begins synchronizing software package data from the selected JFrog repository and artifacts.&#x20;

Once synchronization is complete, package and vulnerability information becomes available in the **Software Packages** dashboard, where users can analyze package inventory, review vulnerability details and identify the applications and technical services affected by vulnerable packages.&#x20;
