# connector parity

GLOSSARY, read 10 Nov 2026

**Definition.** Connector parity means the new platform ingests every source the old one did, at the same depth and on the same schedule. Count by source, not by headline total. Nucleus's Kenna page states Kenna has fewer than 40 integrations and Nucleus more than 200, while Nucleus's catalog lists 183.

List every scanner, cloud and ticketing feed in the old platform and mark each as covered, partly covered or none found in the new one. Kenna's API exposes connector management, including running connectors and uploading a data file to a file-based connector.

Treat headline connector counts as vendor claims. ArmorCode's own pages give 400+, 375+ and 325+ in different places.

## A sourced example

Nucleus's Kenna comparison table states fewer than 40 integrations for Kenna against more than 200 for Nucleus, and the Nucleus catalog lists 183 connectors in the repo data of 2026-11-10.

## Related terms

- [field mapping](/glossary/field-mapping/)
- [migration runbook](/glossary/migration-runbook/)
- [spreadsheet tracker](/glossary/spreadsheet-tracker/)
- [ticket re-linking](/glossary/ticket-re-linking/)

## Sources

- Source for the example: connector parity: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/connector-parity/
