---
title: "Black Duck Polaris Connector Guide"
slug: "blackduck-polaris"
updated: 2026-07-23T06:38:55Z
published: 2026-07-23T06:38:55Z
canonical: "docs.safe.security/blackduck-polaris"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.safe.security/llms.txt
> Use this file to discover all available pages before exploring further.

# Black Duck Polaris Connector Guide

### **Overview**

Black Duck Polaris helps organizations identify and manage application security risks through **SCA (Software Composition Analysis)**, **SAST (Static Application Security Testing)**, and **DAST (Dynamic Application Security Testing)**. By consolidating results from these methods, Polaris delivers centralized visibility into vulnerabilities, license compliance issues, and code flaws across the development lifecycle.

The **Balbix integration** automatically ingests Polaris application inventory and findings, normalizes the data, and enriches it with context for accurate prioritization.

Balbix leverages AI to aggregate, normalize, and deduplicate data ingested from across your IT and security ecosystem. This unified view of inventory and exposures enriched with operational and business context, enables deployment gap analysis, risk-based exposure management, and cyber risk quantification. These insights help organizations drive faster, more informed, and more scalable risk reduction.

### **Integration Summary**

| **Integration Type** | Application Security Testing |
| --- | --- |
| **Types of Assets Fetched** | Applications |
| **Types of Data Fetched** | Application inventory AppSec SCA Findings AppSec SAST Findings AppSec DAST Findings *note: you need to have subscribed to the respective product to see SCA/SAST/DAST findings |

### **Prerequisites**

1. **Base URL:**

- Default: https://polaris.blackduck.com
- If using the older Synopsys platform, contact Synopsys support for your organization’s base URL.

1. **API Token:**

- Generate from the Polaris UI:
  1. Log in to Polaris.
  2. Navigate to **User Menu → Access Tokens**.
  3. Click **Create Token**.
  4. Provide a name (e.g., *Balbix Connector*).
  5. Copy the generated token — this will serve as the API Access Key in Balbix UI. (store securely — it will not be shown again).
- Reference: [Polaris API Quickstart Guide](https://polaris.synopsys.com/developer/default/documentation/t_api-quickstart) (Only Step 1 is needed).

**3. Permissions:**

- The API token must have:
  - Read access to application inventory.
  - Read access to SCA/SAST/DAST findings (depending on modules purchased).

**4. Network Requirements:**

Ensure outbound HTTPS access to *.blackduck.com from the connector host.

  

### **Set Up Your Connector**

You can find these options in the [Connectors](https://rs002tra.balbix.net/app/d3/data-sources/connectors) menu.

[Embedded content](https://scribehow.com/embed/Black_Duck_Polaris_Connector__EpAFND29Q86az76ZcIV84A?as=scrollable)

You can also see the walkthrough [in this link](https://scribehow.com/viewer/Black_Duck_Polaris_Connector__EpAFND29Q86az76ZcIV84A).

### **Field Mapping**

| **From Black Duck Polaris API** | **Mapped to: Balbix Field** |
| --- | --- |
| app_dependency_name | Application Dependency Name |
| app_dependency_version | Application Dependency Version |
| app_codebase_file_path | Application Codebase File Path |
| app_codebase_file_line | Application Codebase File Line Number |
| app_vuln_name | Application Vulnerability Name |
| app_vuln_description | Application Vulnerability Description |
| app_vuln_state | Application Vulnerability State |
| app_vuln_foa | Application Vulnerability First Observed At |
| app_vuln_loa | Application Vulnerability Last Observed At |
| app_vuln_resolution_due_date | Application Vulnerability Resolution Due Date |
| app_vuln_assessment_type | Application Vulnerability Assessment Type |
| app_vuln_solution | Application Vulnerability Solution |
| app_vuln_details | Application Vulnerability Details |
| application_name | Application Name |
| application_tags | Application Tags |
| app_vuln_cwe_ids | Application Vulnerability CWE IDs |

### **API Reference Documentation**

[Polaris API Documentation](https://documentation.blackduck.com/bundle/polaris-developer/page/documentation/c_api-intro.html)