# Connector

GLOSSARY, read 10 Nov 2026

**Definition.** A connector is the integration that pulls findings or asset data from one source, or pushes tickets to one destination, on a schedule or by event. Vendor connector counts are marketing figures, counted differently by each vendor, and a high count says little about whether the connectors your program needs exist.

Check three things per connector: what it ingests (findings, assets, both), how often it syncs, and what it maps. A connector that imports only vulnerabilities and not asset tags leaves ownership rules with nothing to match.

The Connector Census on this site records each vendor's own count and the page it came from, and keeps vendors' differing counts side by side.

## A sourced example

On 2026-11-10 Brinqa's connectors page stated over 260 tool integrations across application security, infrastructure, cloud, threat intelligence and ticketing, while its Data Layer page gave 300+ data integrations.

## Related terms

- [Universal adapter](/glossary/universal-adapter/)
- [Flat-file import](/glossary/flat-file-import/)
- [Normalization](/glossary/normalization/)
- [Bi-directional ticket sync](/glossary/bi-directional-ticket-sync/)

## Sources

- Source for the example: Connector: https://www.brinqa.com/connectors (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/connector/
