WhiteHat Sentinel

Key Features and Benefits

• Synchronizes artifacts across the lifecycle, allowing information to flow freely between WhiteHat Sentinel and other tools
• Improve team collaboration by connecting WhiteHat Sentinel to third party tools and allowing artifacts to be synchronized across the lifecycle.
• Support cross-tool traceability and reporting, removing the need for manual processes and spreadsheets — supports real-time reporting of the status of security vulnerabilities and improves security and compliance by providing traceability between security vulnerabilities and their fixes

Example Use Case

• New vulnerabilities from WhiteHat flow to Jira (or other purpose-built system) along with current status

• Once vulnerability is resolved in Jira, updated status flows to WhiteHat, and re-test in WhiteHat is invoked

• If a resolved vulnerability gets reopened in WhiteHat, so does the corresponding Jira issue

Demo Videos

Minimal User Permissions & Hub User

We recommend that you create a new user within your external tool, to be used only for your Hub integration. This is the user information you will enter when setting up your repository connection within Planview Hub. By creating a new user, you will ensure that the correct permissions are granted, and allow for traceability of the modifications that are made by the synchronization. 

In general, your user account should have sufficient permissions to create, read, and update artifacts in your repository. However, depending on the use case, your user may need different permissions. For example, if you are only interested in flowing data out of your repository, your user may not need to have full CRUD access, as the 'create' and 'update' permissions may not be needed.

Your user should have a secure password or token. Please be aware that Hub will not allow you to save a repository connection utilizing a weak password/token, such as 'tasktop.'

Request a new account in WhiteHat Sentinel through the WhiteHat Security Customer Success Center.

There are no minimal user permissions required for the WhiteHat Sentinel connector.

Connecting to the WhiteHat Repository

Artifact Creation Flow

As users cannot create artifacts (vulnerabilities) within WhiteHat Sentinel, the WhiteHat connector does not support artifact creation. As such, you will see that only one-way artifact creation (out of WhiteHat) can be configured from the Artifact Creation Flow screen: 

Retesting Vulnerabilities

To retest DAST vulnerabilities, you will need to have a transition script as the transform from the model to the ‘Retest Vuln Status’ single select field.

Here is an example (where 'Send For Retest' is a select item in the “Retest Status’ field in the model):

function transitionArtifact(context, transitions) {
      if (context.sourceArtifact. retest_status=== 'Send For Retest') {
           return transitions[0];
     }
}

Full Scan

Due to third party API limitations, changes to the following fields may not trigger change detection or cause a synchronization immediately.  To ensure these updates synchronize, a high fidelity full scan must occur or another qualifying change must be made to the artifact:

• Description field
• Industry field
• Language field

Learn more about how to configure change detection and full scan intervals in Planview Hub here. 

Special Features Supported

Supported Work Items

Learn about the difference between containers and work items in Planview Hub here.