Actions for Cisco Vulnerability Management #
- Send Data to Cisco Vulnerability Management. Sends a custom set of Lucidum data to Cisco Vulnerability Management.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to Cisco Vulnerability Management on a regular schedule.
- You can send normalized, enriched Lucidum data to Cisco Vulnerability Management to be indexed, searched, and analyzed.
Prerequisites #
To execute Cisco Vulnerability Management actions, you must configure a Cisco Vulnerability Management API connection beforehand. For details, see https://apidocs.kennasecurity.com/reference/api-authentication.
NOTE. The specified account should have read and write permissions.
Workflows #
- Creating a new Configuration and a new Action
- Cloning an Existing Action
- Creating a new Action from the Location Results page
- Editing a Configuration
- Editing an Action
- Viewing Information about an Action
Cisco Vulnerability Management Configuration #
To create a configuration for Cisco Vulnerability Management? actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
- URL. URL of the host for the API. For example api.ciscovm.com. To determine where the host is, look at the format of the subdomain for your subscription or see Settings > API Keys.
-
API Key. API Key that allows read and write access to the APIs for Cisco Vulnerability Management. For details, see https://help.kennasecurity.com/hc/en-us/articles/360029111331-API-Key-Generation-and-Permissions.
-
Max # of Records per Payload. The maximum number of records to send to Cisco Vulnerability Management in each action. The default value is “50”.
Create a New Action #
To create an action for Cisco Vulnerability Management, contact Lucidum customer care.