Skip to main content

WhiteHat Sentinel

WhiteHat Sentinel by Synopsys is an application security tool that identifies vulnerabilities across your web applications. You can bring attack vector, dynamic code, and site data from WhiteHat Sentinel into Brinqa to centralize your applications attack surface, thus strengthening your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with WhiteHat Sentinel and how to obtain that information from WhiteHat Sentinel. See create a data integration for step-by-step instructions on setting up the integration.

Required connection settings

When setting up a data integration, select WhiteHat Sentinel from the Connector drop-down list. You must provide the following information to authenticate WhiteHat Sentinel with Brinqa:

  • Service URL: The WhiteHat Sentinel service URL. The default URL is

  • API Key: The access key associated with the WhiteHat Sentinel account, which must have permissions to log in to the API server and return data.

Generate a WhiteHat Sentinel API key

For the WhiteHat Sentinel connector to access the WhiteHat Sentinel API, you must provide an API key. You can access an existing API key or generate a new one. To obtain an API key, follow these steps:

  1. Log in to your organization's WhiteHat Sentinel account.

  2. Click My Profile and then the API Key tab.

  3. Type your password in the Verify password field and click Authenticate.

    The API key displays. If this is your first time requesting an API key, a new key is generated. Click Regenerate API key if you want to replace your existing key.


If you do not have the permissions to create an API key, contact your WhiteHat Sentinel administrator. For additional information, see WhiteHat Sentinel documentation.

Additional settings

The WhiteHat Sentinel connector contains additional options for specific configuration:

  • Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100.

  • Parallel requests: The maximum number of parallel API requests. The default setting is 4.

Types of data to retrieve

The WhiteHat Sentinel connector can retrieve the following types of data from the WhiteHat Sentinel API:

Table 1: Data retrieved from WhiteHat Sentinel

Connector ObjectRequiredMaps to Data Model
Attack VectorNoNot mapped
Dynamic Code FindingYesDynamic Code Finding
Dynamic Code Finding DefinitionYesDynamic Code Finding Definition

For detailed steps on how to view the data retrieved from WhiteHat Sentinel in the Brinqa Platform, see How to view your data.

Attribute mappings

Click the tabs below to view the mappings between the source and the Brinqa data model attributes.

Table 2: Dynamic Code Finding attribute mappings

Source Field NameMaps to Attribute
acceptedLocal variable
cvssBaseScoreUse CVSS calculator
cvssBaseVectorUse CVSS calculator
cvssEnvScoreUse CVSS calculator
cvssEnvVectorUse CVSS calculator
customRiskLocal variable
impactLocal variable
isAccessibleLocal variable
lastRetestedLocal variable
likelihoodLocal variable
manualLocal variable
outOfScoreReasonsLocal variable
reasonLocal variable
riskLocal variable
severityseverity, severityScore
siteIDtargets, Local variable
siteNameLocal variable
statusstatus, statusCategory
subIDLocal variable
threatLocal variable
unreachableLocal variable

Local variable indicates that the field is processed within a specific context, such as a particular workflow or calculation. Unlike other attributes, local variables aren't mapped to the unified data models (UDM). They only exist on the source data model (SDM).

Use CVSS calculator indicates that the CVSS (Common Vulnerability Scoring System) vectors and scores aren't directly mapped to a specific attribute on the UDM. Instead, a specialized library calculates the CVSS scores from the provided CVSS vector strings.

Operation options

The WhiteHat Sentinel connector supports the following operation options. See connector operation options for information about how to apply them.

Table 5: WhiteHat Sentinel connector operation options

Connector ObjectOptionAll Possible ValuesDescriptionExample
Attack Vectorstatusaccepted, certified, closed, openRetrieve attack vector information based on the specific status as determined by WhiteHat Sentinel.Key: status Value: accepted. This key and value combination only retrieves attack vector information with a status of accepted.
Dynamic Code Findingstatusaccepted, closed, invalid, mitigated, out_of_scopeRetrieve findings based on the specified status as determined by WhiteHat Sentinel.Key: status Value: mitigated This key and value combination only retrieves findings with a status of mitigated.

The option keys and values are case-sensitive as they are shown in this documentation.


The WhiteHat Sentinel connector uses the WhiteHat Sentinel API v2. Specifically, it uses the following endpoints:

Table 6: WhiteHat Sentinel API Endpoints

Connector ObjectAPI Endpoint
Attack VectorGET
Dynamic Code FindingGET
Dynamic Code Finding DefinitionGET


The WhiteHat Sentinel connector has undergone the following changes: