Skip to main content

Contrast Security

Contrast Security is an application security tool. You can bring application, library, server, and security check data from Contrast Security into Brinqa to gain a unified view of your attack surface and strengthen your cybersecurity posture.

This document details the information you must provide for the connector to authenticate with Contrast Security and how to obtain that information from Contrast Security. 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 Contrast Security from the Connector drop-down. If you cannot find the connector in the drop-down, make sure that you have installed it first. You must provide the following information to authenticate Contrast Security with Brinqa:

  • Server URL: The Contrast Security server URL. The default URL is https://app.contrastsecurity.com.

  • Username: The username associated with the Contrast Security account, which must have permissions to log in to the API server and return data.

  • Service key and API key: The access keys associated with the Contrast Security account, which must have permissions to log in to the API server and return data.

Obtain Contrast Security API keys

For the Contrast Security connector to use the Contrast Security API, you must generate a service key and API key. To do so, follow these steps:

  1. Log in to your organization's Contrast Security portal as an administrator.

  2. Navigate to your user profile and click User Settings.

  3. The API Key and Service Key are displayed in the Your Keys > Your API Keys section on the page.

    Although you can return to this page to view the access keys, you should handle them with care by ensuring that they are stored in a secure location.

    Contrast API keys

  4. If you are unsure of the API URL needed for authentication, click Generate Sample API Request.

    The API request includes the correct API URL.

    Contrast Security API URL

note

If you do not have permissions to create API keys, contact your Contrast Security administrator. For additional information, see Contrast Security documentation.

Additional settings

The Contrast Security 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.

  • Maximum retries: The maximum number of times that the integration attempts to connect to the Contrast Security API before giving up and reporting a failureThe default setting is 5.

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

  • Include vulnerability analysis, consequence, and solution: Specifies whether to retrieve additional vulnerability details. When enabled, the connector retrieves the following attributes for vulnerabilities and vulnerability definitions:

    • ANALYSIS
    • CONSEQUENCE
    • RECOMMENDATION
    • REFERENCES
    • WEAKNESSES

    The connector makes two additional API calls when this setting is enabled:

    • /ng/{orgUuid}/traces/{traceUuid}/story (retrieves ANALYSIS and CONSEQUENCE)

    • /ng/{orgUuid}/traces/{traceUuid}/recommendation (retrieves RECOMMENDATION, REFERENCES, and WEAKNESSES)

    caution

    Enabling this setting increases the number of API requests, which may impact performance.

Types of data to retrieve

The Contrast Security connector can retrieve the following types of data from the Contrast Security API:

Table 1: Data retrieved from Contrast Security

Connector ObjectRequiredMaps to Data Model
ApplicationYesApplication
LibraryYesPackage
ServerYesHost
VulnerabilityYesVulnerability
Vulnerability DefinitionYesVulnerability Definition
info

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

Attribute mappings

Expand the sections below to view the mappings between the source and the Brinqa data model attributes:

Application

Table 2: Application attribute mappings

Source Field NameMaps to Attribute
app_iduid
archivedLocal variable
assessLocal variable
assessPendingLocal variable
categoriescategories
codeLocal variable
code_shorthandLocal variable
createdfirstSeen
defendLocal variable
defendPendingLocal variable
importanceLocal variable
importance_descriptionLocal variable
last_seenlastSeen
languagelanguage
license.levelLocal variable
masterLocal variable
namename
notesLocal variable
parentApplicationIdLocal variable
pathpath
platform.gradeLocal variable
platform.letter_gradeLocal variable
rolesLocal variable
scores.gradeLocal variable
scores.letter_gradeLocal variable
security.gradeLocal variable
security.letter_gradeLocal variable
servers_without_defendLocal variable
short_nameLocal variable
sizeLocal variable
size_shorthandLocal variable
statusstatus, sourceStatus
tagstags
techsLocal variable
total_modulesLocal variable
Library

Table 3: Library

Source Field NameMaps to Attribute
agePenaltyLocal variable
app_languagelanguage
appsLocal variable
categoriescategories
classes_usedLocal variable
class_countLocal variable
customLocal variable
file_namename
file_versionLocal variable
gradeLocal variable
groupLocal variable
hashuid
invalid_versionLocal variable
latest_release_dateLocal variable
latest_versionLocal variable
locLocal variable
loc_shorthandLocal variable
months_outdatedLocal variable
ossEnabledLocal variable
release_dateLocal variable
restrictedLocal variable
scoreLocal variable
serversLocal variable
source_statussourceStatus
statusstatus
tagstags
total_vulnerabilitiesLocal variable
versioncurrentVersion
versionPenaltyLocal variable
versions_behindLocal variable
Server

Table 4: Server attribute mappings

Source Field NameMaps to Attribute
Categoriescategories
agent_versionLocal variable
applicationsLocal variable
assessLocal variable
assessPendingLocal variable
assess_last_updateLocal variable
assess_sensorsLocal variable
containerLocal variable
defendLocal variable
defendPendingLocal variable
defend_sensorsLocal variable
defense_last_updateLocal variable
environmentLocal variable
hostnamehostnames
languageLocal variable
last_activityLocal variable
last_startupLocal variable
latest_agent_versionLocal variable
namename
num_appsLocal variable
out_of_dateLocal variable
pathpath
server iduid
statusstatus, sourceStatus
syslog_enabledLocal variable
syslog_ip_addressipAddresses, publicIpAddresses, privateIpAddresses
tagstags
typeLocal variable
Vulnerability

Table 5: Vulnerability attribute mappings

Source Field NameMaps to Attribute
applicationtargets
closed_timelastFixed
confidenceLocal variable
discoveredLocal variable
evidenceresults
first_time_seenfirstFound
hasParentAppLocal variable
last_time_seenlastFound
last_vuln_time_seenLocal variable
likelihoodLocal variable
organization_nameLocal variable
requestLocal variable
statusstatus, sourceStatus, statusCategory
story.riskLocal variable
story.textLocal variable
sub_statusLocal variable
tagstags
total_traces_receivedLocal variable
uuiduid, type
visibleLocal variable
Vulnerability Definition

Table 6: Vulnerability Definition attribute mappings

Source Field NameMaps to Attribute
categorycategories
languagelanguage
recommendationrecommendation
recommendation.cweweaknesses, references
rule_nameLocal variable
rule_titleLocal variable
severityseverity, sourceSeverity, severityScore
titlename
Local 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. They only exist on the source data model.

Operation options

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

Table 7: Contrast Security connector operation options

The Contrast Security connector supports the following operation options:

Connector ObjectOptionAll Possible ValuesDescriptionExample
ApplicationmaxRetriesAny numeric valueSpecifies the maximum number of times the integration attempts to retrieve application data before failing.Key: maxRetries Value: 5. This key and value combination limits retry attempts to 5 for applications.
LibrarymaxRetriesAny numeric valueSpecifies the maximum number of times the integration attempts to retrieve library data before failing.Key: maxRetries Value: 5. This key and value combination limits retry attempts to 5 for libraries.
ServermaxRetriesAny numeric valueSpecifies the maximum number of times the integration attempts to retrieve server data before failing.Key: maxRetries Value: 5. This key and value combination limits retry attempts to 5 for servers.
Vulnerability,
Vulnerability Definition
maxRetriesAny numeric valueSpecifies the maximum number of times the integration attempts to retrieve vulnerability data before failing.Key: maxRetries Value: 5. This key and value combination limits retry attempts to 5 for vulnerabilities.
severitiesLOW, MEDIUM, HIGH, CRITICALA comma-separated list of severity levels. Filters vulnerabilities by their severity level, as determined by Contrast Security.Key: severities Value: HIGH,CRITICAL. This key and value combination retrieves only high and critical vulnerabilities.
statusConfirmed, Fixed, NotAProblem, Remediated, SuspiciousA comma-separated list of vulnerability status categories. Filters vulnerabilities by their status category, as determined by Contrast Security. For more information on vulnerability status categories, see Contrast Security documentation.Key: status Value: Confirmed,Suspicious. This key and value combination retrieves only vulnerabilities with a status of confirmed or suspicious.
trackedtrue, falseFilters vulnerabilities based on whether they are being tracked by a bug tracker tool, as specified by Contrast Security. For more information, see Contrast Security documentation.Key: tracked Value: true. This key and value combination retrieves only vulnerabilities that are currently tracked in a bug tracker.
untrackedtrue, falseFilters vulnerabilities based on whether they are not being tracked by a bug tracker tool, as specified by Contrast Security. For more information, see Contrast Security documentation.Key: untracked Value: false. This key and value combination retrieves only vulnerabilities that are not tracked in a bug tracker.
note

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

APIs

The Contrast Security connector uses the Contrast Security API. Specifically, it uses the following endpoint:

Table 8: Contrast Security API Endpoint

Connector ObjectAPI Endpoint
ApplicationGET /Contrast/api/ng/{organization_uuid}/applications
LibraryGET /Contrast/api/ng/{organization_uuid}/libraries
ServerGET /Contrast/api/ng/{organization_uuid}/servers
VulnerabilityGET /Contrast/api/ng/{organization_uuid}/orgtraces/filter
GET /Contrast/api/ng/{organization_uuid}/traces/{trace_uuid}/recommendation
GET /Contrast/api/ng/{organization_uuid}/traces/{trace_uuid}/story
Vulnerability DefinitionGET /Contrast/api/ng/{organization_uuid}/orgtraces/filter
GET /Contrast/api/ng/{organization_uuid}/traces/{trace_uuid}/recommendation
GET /Contrast/api/ng/{organization_uuid}/traces/{trace_uuid}/story

Changelog

The Contrast Security connector has undergone the following changes:

Table 9: Contrast Security connector changelog

VersionDescription
3.0.0Initial Integration+ release.