Cisco Vulnerability Management (formerly Kenna Security) Connector Guide

The Cisco Vulnerability Management (formerly Kenna Security) platform is a vulnerability assessment solution that provides risk scoring, prioritization, and benchmarking. The Balbix integration with Cisco Vulnerability Management ingests IT infrastructure assets and associated vulnerabilities prioritized by Cisco Vulnerability Management.

Balbix leverages AI to aggregate, normalize, and deduplicate ingested data, along with information integrated from your existing IT and cybersecurity tools. This creates a unified view of your entire asset inventory, including vulnerabilities and their business and operational context. Balbix’s AI models then analyze this data to provide insights such as deployment gap analysis, risk-based vulnerability prioritization (with detailed ranking and scoring), and risk quantification. This process delivers a comprehensive assessment of risk, whether for a single asset, groups of assets, or your entire enterprise, enabling more informed and effective security decisions.

Integration Summary

This table provides a summary of the Balbix integration for the Cisco Vulnerability Management connector.

Prerequisites

To configure the Balbix connector, you must first create Cisco Vulnerability Management API credentials with the appropriate permissions. These credentials are required for completing the configuration process.

1. Identify the Base API URL: To work with the Cisco Vulnerability Management API, start by identifying the base API URL where your Kenna subscription is hosted. You can determine this by examining the subdomain format of your subscription's URL. The user interface URL will match the API base URL format. If you're unsure about the correct API base URL, contact your Cisco/Kenna administrator or account team for assistance. For example, the API base URL might look like: api.kennasecurity.com.

2. Get an API Token: Access to the API is managed through a key, also known as a token. Currently, only users with system roles (administrators, normal, and read-only) have API access, and only administrators can manage or retrieve keys for other users.

   Administrators can view and manage API keys by logging in, clicking the Settings menu in the top-right corner, and selecting API Keys from the dropdown. From this menu, administrators can create, update, or revoke API keys. Note that API keys can only be copied once, immediately after they are generated. For more details, refer to the Role Permissions and API Key Generation help pages.

3. Authenticate Using an X-Risk-token Header: All API requests must be made over HTTPS; calls made over plain HTTP will fail. Authentication is required for all requests, and you must include an X-Risk-Token header with the value set to your API token. For example, in a curl request, use the flag:

   --header 'X-Risk-Token: SoL310X108mps'
   

   In ReadMe, you can add the API key in the Authentication section on the right side. This will automatically populate the API examples when using the "Try It!" button.

   For setting environment variables:

   • In bash or zsh shells, use single quotes, for example:

     export KENNA_API_KEY='7apikey-with2dashes-and0a1period'
     

   • In Windows DOS, use:

     set KENNA_API_KEY=7apikey-with2dashes-and0a1period
     

Create and Configure the Connector

After you have completed the prerequisites, follow these steps to create and configure your Balbix connector for Cisco Vulnerability Management.

API Reference Documentation

To learn more about the Cisco Vulnerability Management API, see the references listed below:

• Role Permissions - Kenna FAQ

• Kenna API Docs