📙 You will learn

How to configure Black Duck with ThreadFix.

Prerequisites

Audience: IT Professional or End User
Difficulty: Basic
Time needed: Approximately 5 minutes
Tools required: N/A

Authentication

ThreadFix uses Black Duck's Access Token to authenticate and establish a connection with its service layer. This token is generated from Profile Page of the target Black Duck instance. 

Here's how to create your token:

1. Go to the Profile Page in Black Duck.
   

   

2. Scroll to the bottom to find the User Access Token section.
   

3. Enter a name.
   

4. Select at least Read access for the scope.
   

5. Click Generate.
   

   

6. Copy the resulting API Token to Clipboard and Enter it into the Remote Providers section in ThreadFix.
   

   

Obtain Bearer Token/Authenticate

The following call is used to get the Bearer Token:

/api/tokens/authenticate

Get Applications

The following call is used to get applications:

/api/projects

Get Versions

The following call is used to get versions:

api/projects/{{projectId}}/versions	

Get Scans & Scan Dates

ThreadFix no longer uses Black Duck's hub-common library to authenticate and pull application, version and vulnerability information. The following API call is now used to fetch scans:

Get Scans:

/api/projects/{{projectId}}/versions/{{version}}/vulnerable-bom-components

Get Remediation-Guidance:

/remediating

Import Options

As of 3.1.1, a selection has been added allowing multiple users the option to import applications by Application or Application Version, as seen below.

Parsing Vulnerabilities

ThreadFix parses the VulnerableComponentViews pulled from Black Duck into a Finding-Dependency pair. Most of the component information is stored in the VulnerableComponentView, while the vulnerability information is stored in the VulnerabilityWithRemediationView within it.

Dependency:

• CVE: If the Vulnerability Name pulled from the VulnerabilityWithRemediationView is a CVE, ThreadFix records it here.

• Component File Path: Component Version Origin Id pulled from the VulnerableComponentView. The value is a combination of the Origin, Component Name and Component Version.

• Component Name: Combination of the Componenet Name and Component Version Name pulled from the VulnerableComponentView.

• Description: Description pulled from the VulnerabilityWithRemediationView.

Finding:

• Native Id: Hashed together from Component Id, Component Version Id and Origin Id pulled from the Vulnerabilities URL stored in the VulnerableComponentView's Meta Data and the Vulnerability Name pulled from the VulnerabilityWithRemediationView.

• Severity Code: Rounded down Base Score pulled from the VulnerabilityWithRemediationView.

• Detail: Description pulled from VulnerabilityWithRemediationView.

• CWE: Not always included, but when available its pulled from CWE Id in the VulnerabilityWithRemediationView.

• Vulnerability Code: If a CWE Id is provided, it is used to catagorize the finding using ThreadFix's Generic Vulnerability table. If not present, it's catagorized as Configuration.

• Created Date: Remediation Created At date pulled from the VulnerabilityWithRemediationView.

• Modified Date: Remediation Updated At date pulled from the VulnerabilityWithRemediationView.

Vulnerability Statuses:

ThreadFix will not ingest findings with the following statuses, closing them if they were ingested in a previous scan:

• Patched

• Remediation Complete

• Mitigated

ThreadFix will mark findings false positive if they have the following statuses:

• Duplicate

• Ignored

ThreadFix will ingest all other status as an open finding.