Skip to main content

July 2025 Integration+ Connector Releases

Updates made to the Integration+ connectors in July 2025.

New​

  • Qualys Total Cloud v5.3.19

    Qualys Total Cloud is a Cloud Security tool that helps organizations secure their cloud environments. You can bring cloud resource, host, and other security data from Qualys Total Cloud into Brinqa.

  • Salesforce v3.0.0

    Salesforce is a customer relationship management (CRM) platform that helps organizations manage their customer interactions and data. You can bring Salesforce data into Brinqa.

Updated​

  • Adaptive Shield v3.0.4

    The Adaptive Shield connector has been updated with the following changes:

    • The connector now retrieves the Compliance Control, Device, and Host objects from Adaptive Shield.
    • Added a new additional setting to help manage API throttling: Maximum retries.
    • The STATUS_REASON attribute on the Violation Definition now maps to the Description field in Brinqa.
    • The connector now supports operation options.
    • Added the CONTROL_CODES attribute to the Violation Definition object.
    • The Violation object has been enhanced to create distinct violations based on the affected data from Adaptive Shield.

  • Amazon Inspector v3.0.15

    The Amazon Inspector connector has been updated to fix an issue where the full ARN was not being populated for the Cloud Resource and EC2 Instance objects. As a result, the CLOUD_ACCOUNT_ID attribute has been added to the AWS EC2 Instance and Cloud Resource objects.

  • AssetNote v3.0.7

    The AssetNote connector has been updated with the following changes:

    • Improved how the connector retrieves SSL certificate details on the Sub Domain object. The connector now retrieves only the most recent SSL certificate from AssetNote.

    • Modified the Sub Domain GraphQL query to improve performance by moving common fields across assets, such as ip, subdomain, and cloud, into the BaseAsset section of the query.

  • BitSight v3.0.4

    The BitSight connector has been updated with the following changes:

    • 3.0.4:

      • The EVIDENCE_KEY attribute on the Finding object now maps to the TARGETS attribute. This ensures that the affected asset is properly identified using the evidence key from the Finding API response, even if the asset is not included in BitSight’s asset inventory.
      • Added the ROLLEDUP_ID attribute to the Violation object.
      • Added the DESCRIPTION attribute to the Violation Definition object.
      • Moved the RECOMMENDATION attribute from the Violation object to the Violation Definition object.

    • 3.0.3:

      • Updated how severity is handled to ensure that each Finding includes its own severity information, rather than inheriting it from the Finding Definition.
      • Added the following attributes to the Finding object: SEVERITY, SOURCE_SEVERITY, SEVERITY_SCORE, CVSS_BASE_SCORES, and CVSS_BASE_SCORE_MAX.
      • Updated the UID and TYPE generation logic for Finding and Finding Definition objects. These changes require that you purge existing data and run a new beginning-of-time sync.

  • Checkmarx One v3.2.1

    The Checkmarx One connector has been updated to fix an issue where the Open Source Finding object sync was failing.

  • CrowdStrike Endpoint Security v3.2.2

    The CrowdStrike Endpoint Security connector has been updated to replace the EVALUATION_LOGIC attribute on the Vulnerability object with EVALUATION_RESULTS. The previous attribute only collected evaluation logic IDs. The new attribute collects the full evaluation logic details provided by CrowdStrike.

  • GitHub v4.0.13

    The GitHub connector has been updated with the following changes:

    • 4.0.13: Fixed an issue where the format of the PATH attribute on the Code Scanning Alert object included an extra dash between the end line and end column values. The correct format is now path#L1C2-L3C4.

    • 4.0.12: Added the END_COLUMN, END_LINE, START_COLUMN, and START_LINE attributes to the Code Scanning Alert object. These values identify where the code scanning alert begins and ends in the source code and are used to construct the PATH attribute in the format of path#L1C2-L3C4, where L1/C2 represent the start line and number, and L3/C4 represent the end line and column number.

  • Google Security Command Center v3.2.4

    The Google Security Command Center connector has been updated with the following changes:

    • The connector now retrieves the Repository object from Google Cloud.
    • Fixed an issue where the TARGETS values on the Alert, Violation, and Vulnerability objects were populated with asset names instead of unique identifiers, which prevented proper consolidation with asset records.
    • Fixed an issue where the Vulnerability Definition object sync was not retrieving any data.
    • Added a new operation option on all Finding-related objects (Alert, Alert Definition, Violation, Violation Definition, Vulnerability, and Vulnerability Definition) to filter records by asset type: asset_type.

  • Prisma Cloud v3.2.2

    The Prisma Cloud connector has been updated to change the FIRST_FOUND and LAST_SEEN attribute types on the Violation object from long to instant to resolve a data type mismatch error, which was causing the connector sync to fail.

  • Rapid7 Nexpose v3.4.15

    The Rapid7 Nexpose connector has been updated with the following changes:

    • 3.4.15: Added the LAST_SEEN attribute to the Host object.

    • 3.4.14:

      • The site-id operation option on the Asset and Vulnerability objects has been updated to support multiple site IDs.

      • Added the LAST_CAPTURED attribute to the Asset object. This timestamp can be used to support advanced Data Lifecycle Management conditions.

  • Salesforce v3.0.1

    The Salesforce connector has been updated to fix an issue where the wrong API endpoints were being used to send data to Salesforce environments.

  • Sonatype Nexus IQ v3.0.1

    The Sonatype Nexus IQ connector has been updated with the following changes:

    • Added a new additional setting to help manage how the connector handles missing or purged scan reports from Sonatype Nexus IQ. When enabled, the connector skips missing reports, continues the connector sync, and logs a warning instead of failing.
    • Added the DESCRIPTION and RECOMMENDATION attributes to the Policy Violation object.

  • TeamDynamix v3.0.6

    The Team Dynamix connector has been updated with the following changes:

    • 3.0.6:

      • The connector now retrieves the Account object from TeamDynamix.

      • Added the DESCRIPTION attribute to the Ticket object.

    • 3.0.5: Updated attribute mappings to support create and update operations for tickets. The connector now maps standard and custom attributes according to the TeamDynamix API specifications.

    • 3.0.4: Fixed an issue where pushing tickets to TeamDynamix environments was throwing a ClassCastException error.

  • Tenable Web App Scanning v3.1.32

    The Tenable Web App Scanning connector has been updated to fix an issue where the Dynamic Code Finding Definition object sync was failing.

  • Wiz v3.3.14

    The Wiz connector has been updated with the following changes:

    • 3.3.14: Added a new additional setting to make the report timeout configurable: Report timeout. This setting allows you to specify the maximum number of hours to wait for a report to be generated before giving up and reporting a failure. The default setting is 4 hours.

    • 3.3.13: Added the following attributes to the Issue object:

      • ENTITY_EXTERNAL_ID
      • ENTITY_ID
      • ENTITY_NAME
      • ENTITY_STATUS
      • ENTITY_TYPE
      • SUBSCRIPTION_EXTERNAL_ID
      • SUBSCRIPTION_ID
Last updated on