February 2024 Integration+ Connector Releases

Updates made to the Integration+ connectors in February 2024.

New

• JSON Connector v3.0.0

  The JSON Connector facilitates the ingestion of data from JSON files. JavaScript Object Notation (JSON) is a lightweight and text-based data interchange format. JSON files organize data into a structured hierarchy, containing arrays and objects to represent data, making it an ideal format for storing and transporting data across a network.

• Mend.io v3.0.0

  The Mend (formerly WhiteSource) connector is an application security tool used for scanning, prioritizing, and remediating security vulnerabilities in your organization's applications and code projects. You can bring application, code project, package, and security data from Mend.io into the Brinqa Platform.

Updated

• Axonius v3.0.3

  The Axonius connector no longer uses the Immutableset class.

• Burp Suite Professional v3.1.3

  The Burp Suite Professional connector has been updated to allow for setting custom app names through various naming conventions.

• Checkmarx One v3.0.2

  The Checkmarx One connector has restructured the code to align with the latest Connector Framework.

• CISA v3.0.3

  The CISA connector has been updated to fix an issue where the Date added field was displaying erroneous dates. The type of the Date added field is now set to "Instant" rather than "Long".

• CrowdStrike v3.1.4

  The CrowdStrike connector has been updated with the following changes:

  • v3.0.24: Recommendations for vulnerabilities now display in the Results field.

  • v3.1.0: Changed the logic for how Brinqa generates Vulnerability Definitions records from CrowdStrike. Brinqa now uses part of a CrowdStrike Vulnerability ID, which is unique per vulnerability type, in its Vulnerability Definitions ID. See the CrowdStrike connector documentation for additional information.

  • v3.1.4: Removed the updated_timestamp field from the lastFound attribute on the Vulnerability object.

• GitHub v3.0.6

  The GitHub connector has been updated to fix an issue that caused a "406: status failed" error when attempting to sync the Secret Scanning Alert, Static Code Finding, or Static Code Finding Definition objects.

• LDAP v3.0.8

  The LDAP connector has been updated to add error logs for improved troubleshooting.

• LeanIX EAM v3.0.1

  The LeanIX EAM connector has been updated to fix an issue where users were showing up in LeanIX EAM, but were missing in Brinqa.

• Microsoft Defender for Endpoint v3.1.15

  The Microsoft Defender for Endpoint connector has been updated with the following changes:

  • v3.1.14: Set the INSTANCE_ID attribute in the Machine object if the source specifies a value using the instanceId tag.

  • v.3.1.15: Fixed an issue where the EXPLOITABILITY attribute in all Vulnerability Definition records was incorrectly set to Actively used.

• Prisma Cloud v3.0.8

  The Prisma Cloud connector has been updated with the following changes.

  • v3.0.7: Now retrieves the "Asset Type" information from Prisma. Also added Host to the list of connector objects retrieved.

  • v3.0.8: Increased the read timeout.

• Qualys Policy Compliance v5.1.9

  The Qualys Policy Compliance connector has been updated to fix an issue where Control and Violation syncs were failing intermittently.

• Qualys Vulnerability Management v5.1.9

  The Qualys Vulnerability Management has been updated to refactor the API endpoints.

• Rapid7 InsightVM v3.1.2

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

  • Fixed an issue where the Rapid7 InsightVM connector would get stuck during the Vulnerability Definition sync, causing data orchestration to remain in a waiting state.

  • Improved the results and recommendation field for Vulnerabilities and Vulnerability Definitions.

  • Severity scores are now normalized for Vulnerabilities.

• Rapid7 Nexpose DataWarehouse v3.0.10

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

  • Added the Categories attributes on the Vulnerability object.

  • Now assigns a fixed status to vulnerabilities when a remediation_date is specified in the corresponding data table. This status update indicates that the issue has been successfully remediated based on the presence of this date.

• Snyk v3.0.8

  The Snyk connector has been updated with the following changes:

  • Added logs for the Open Source Issue object.

  • Improved performance by parallelizing project streams for retrieving Open Source and Static Code Issue details.

• SQL Connector v3.1.6

  The SQL Connector has been updated to support Boolean conversions to accommodate for MySQL's lack of native Boolean support. It accepts all case-insensitive representations of the following:

  • true, yes, t, y, or 1 converts to true

  • false, no, f, n, 0, empty, null, or unknown converts to false.

• Tenable.io v3.1.19

  The Tenable.io connector has been updated with the following changes:

  • Renamed the Finding object to Violation.

  • Added the Results attribute, aggregating the following fields:

    • CHECK_NAME
    • CHECK_ERROR
    • AUDIT_FILE
    • EXPECTED_VALUE
    • ACTUAL_VALUE

  • Divided Vulnerability Definition into two distinct models: Vulnerability Definition and Violation Definition, based on the plugin family (Compliance Policy).

• Tenable.sc v3.1.19

  The Tenable.sc connector has been updated to retrieve the Published field and published date information for vulnerabilities.

• Veracode v3.0.10

  The Veracode connector has been updated to add a new attribute, ISSUE_ID_NUMBER, to enhance sorting (ascending/descending) issues.

• VulnDB v3.0.2

  The VulnDB connector has been updated to make the Unaffected products attribute multi-valued.

• Wiz v3.1.11

  The Wiz connector has been updated with the following changes:

  • Switched the order of adding attributes to allow native or specific attributes to take higher precedence.

  • Fixed an issue where the Vulnerability and Vulnerability Definition syncs were failing.