What is a connector? (API vs File-based)

A Connector is the definition of how Kenna can connect to tools that already exist in customer environments. Connectors fall into several general categories and can be related to vulnerability management, application scanning, ticketing, and more. By setting up a connector in your environment, you facilitate a connection between the tool and the Kenna platform. The connectors come with a number of settings including what credentials to use, how often Kenna should import the data, which reports/templates Kenna should import, etc.

There are two types of connectors available in the platform:

  • API Connectors
  • File based connectors

API Connectors are direct integrations between Kenna and a tool. These integrations are more automated. For these connectors a number of fields can be set to determine what level of data Kenna will import and how often you would like that data imported. Example: QualysGuard 



File based connectors are the more manual integrations. For file based connectors, Kenna supports the creation of a connector, but then a manual drag and drop is required to run the connector. Automation can be achieved through scripting, however file based connectors are not schedulable via the UX.
Example: HCL AppScan (though Kenna does also offer an HCL AppScan Enterprise API connector)


here for a full list of tools with which Kenna can integrate.

If you don’t see a particular tool on the list and would like to be able to ingest data from that tool, you may be able to do so via the Kenna Data Importer (KDI). More information on the KDI can be found here.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Please sign in to leave a comment.