Skip to main content

Connectors S-Z

ServiceNow

The ServiceNow Connector integrates with the [ServiceNow](https://www.servicenow.com/) IT Service Management platform via the ServiceNow REST Table API. It synchronizes Configuration Management Database (CMDB) records — computers, servers, virtual machines, network gear, printers, mass-storage devices, communication devices, clusters, generic hardware, applications, and business services — along with users, groups, group memberships, locations, tasks, and configuration-item relationships. It can also discover and sync any additional ServiceNow table configured by the customer. The connector reads each table's `sys_dictionary` schema at runtime, so synced attributes are driven by the live ServiceNow table definitions. Computer-derived records are additionally normalized into the Brinqa unified `Host` model.

Snyk

The Snyk Connector integrates with the [Snyk](https://snyk.io/) developer-security platform and synchronizes Snyk's organization, project, and security data into the Brinqa platform. It collects code projects, package dependencies, code repositories (targets), open-source (SCA) findings and their definitions, static (SAST) code findings and their definitions, infrastructure-as-code (IaC) violations and their definitions, and finding ignore (suppression) records. Findings are normalized into Brinqa unified data models so that Snyk vulnerability data can be correlated with assets and risk across the platform.

SonarQube

The SonarQube Connector integrates with a [SonarQube](https://www.sonarsource.com/products/sonarqube/) server to synchronize static code analysis data. It syncs three models: **Code Projects** (the analyzed projects together with their quality metrics and ratings), **Static Code Findings** (the issues SonarQube raises against project code), and **Static Code Finding Definitions** (the rules that describe and categorize those issues). Together these provide visibility into code quality, security, reliability, and maintainability across analyzed projects.

Splunk

The Splunk Connector integrates with a Splunk Enterprise / Splunk Cloud instance through the Splunk REST API. It synchronizes data by executing a configured SPL (Search Processing Language) search: the connector creates a search job, waits for the job to finish, and retrieves the paginated search results. Each result row is mapped to a Brinqa Connector Object whose attributes are derived dynamically from the fields returned by the search, so the synced data model adapts to whatever the configured search produces.

SQL Connector

The SQL Connector integrates Brinqa with any relational database reachable over JDBC. Rather than targeting a single fixed schema, it is a generic, query-driven connector: an operator supplies the SQL queries used to test connectivity, discover the schema, and retrieve data, and the connector turns each returned row into a connector object. Because the synced data is defined entirely by the customer-supplied query, the connector is schema-agnostic and can be pointed at any table, view, or join that the configured database user can read.

VulnDB

The VulnDB connector integrates with [Flashpoint VulnDB](https://vulndb.flashpoint.io), a commercial vulnerability intelligence database. It syncs vulnerability records (mapped to CVE Records), along with the supporting software vendors, software products, and software product versions that those vulnerabilities affect. Vulnerability data includes CVSS v2 and v3 metrics, classifications, affected/unaffected product versions, exploit and vendor references, and a range of disclosure/remediation timestamps. Vendor and product records additionally carry VulnDB analytics such as ratings, cost-of-ownership, and time-to-event (VTEM) metrics.

watchTowr

The watchTowr connector integrates with the [watchTowr](https://www.watchtowr.com/) Attack Surface Management and Continuous Automated Red Teaming platform. It synchronizes the assets watchTowr discovers across your external attack surface — cloud storage, container images, domains, subdomains, IP addresses, IP ranges, mobile applications, code repositories, and SaaS platforms — together with the security findings raised against those assets and the underlying finding definitions (vulnerability definitions, including CVSS and EPSS scoring).