# From Kenna to Brinqa: export, rebuild, then run both

SWITCH GUIDE, read 10 Nov 2026

**The short answer.** Moving from Kenna to Brinqa: export everything through the REST API data export (JSON, JSON Lines or XML) first, then rebuild connectors, scoring rules and ticket links. Brinqa is 1st on the Kenna alternatives list at 7.2 and states 260+ connectors plus an adapter for unlisted sources, by its own account.

- **Destination:** Brinqa Exposure Management Platform
- **Place on this list:** 1st of 11 at 7.2
- **Unify score:** 9 of 10
- **Automation score:** 8 of 10
- **FedRAMP:** none found on 10 Nov 2026

## The five steps

1. **Export.** From Kenna: REST API data export (json, jsonl, xml, gzip); Daily full export via support. Export closed findings and exceptions too, not only open ones.
2. **Ingest.** Brinqa states 260 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover.
3. **Score.** Kenna scores with the Cisco Security Risk Score, an integer from 0 to 100 per vulnerability (asset groups carry a Risk Meter score whose scale is not stated). Brinqa scores with a risk score built from a base score plus risk factors on a 0 to 10 scale. [Read the score mapping](/score-mapping/kenna-to-brinqa/).
4. **Tickets.** Re-link open tickets by finding identifier, not by title; Brinqa scores 8 of 10 on automation at enterprise scale.
5. **Run in parallel.** Keep Kenna read-only until two SLA cycles match. Cisco supports Kenna to 30 Jun 2028, but your own contract term may end sooner: plan the parallel run inside the term you hold.

## Where Brinqa is strongest

Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors.

## Other destinations

- [Kenna to Nucleus](/switch/kenna-to-nucleus/)
- [Kenna to Tenable](/switch/kenna-to-tenable/)
- [Kenna to Qualys](/switch/kenna-to-qualys/)
- [Kenna to ServiceNow Vulnerability Response](/switch/kenna-to-servicenow-vr/)

## Sources

- API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk Score, continuously updated; manual override stops dynamic updates and is logged.: https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026)
- Request Data Export API runs asynchronously for models asset, fix, vulnerability or finding in json, jsonl or xml; search IDs valid 30 days.: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026)
- Export downloads are gzip; fields can be selected via export_settings.: https://apidocs.kennasecurity.com/docs/downloading-export-files.md (read 10 Nov 2026)
- A daily full gzipped asset/vulnerability export can be arranged through tech support.: https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026)
- Final risk score equals base risk score plus the sum of risk factor scores on a 0-10 scale.: https://docs.brinqa.com/docs/risk-factors (read 10 Nov 2026)
- BQL API gives programmatic access via asynchronous POST/GET with API-token authentication.: https://docs.brinqa.com/docs/brinqa-api (read 10 Nov 2026)
- BrinqaDL is a BigQuery pipeline publishing views for BI tools and SQL; marketing page says it is an add-on with separate pricing.: https://www.brinqa.com/platform/data-layer (read 10 Nov 2026)
- Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026)
- A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026)
- Documentation connector pages exist for scanners Tenable (io, sc, nessus), Qualys (VM, WAS, container, (excerpt): https://docs.brinqa.com/sitemap.xml (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/kenna-to-brinqa/
