Skip to main content
Skip table of contents

Tenable

Actions for Tenable Vulnerability Management

  • Send to Tenable Vulnerability Management Assets. Sends a custom set of Lucidum data to Tenable Vulnerability Management to import as assets.

  • Launch Tenable Vulnerability Management Scan. Launches a scan in Tenable Vulnerability Management with a specified list of assets.

  • Add to Tenable Vulnerability Management Target Group. Adds a list of assets to a target group in Tenable Vulnerability Management. A target group includes a list of targets to scan.

Use Cases

Below are the possible use cases for this action:

  • If you want to run Lucidum “headless”, you can send relevant data to Tenable Vulnerability Management on a regular schedule.

  • You can send data to Table to be indexed, searched, and analyzed.

Prerequisites

Before you can execute actions on Tenable Vulnerability Management, you must first create an account on Tenable Vulnerability Management and retrieve the following:

  • API Key ID

  • API Key Secret (value of the key)

https://docs.tenable.com/vulnerability-management/Content/Settings/my-account/GenerateAPIKey.htm

Workflows

Tenable Vulnerability Management Configuration

  • Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.

  • Host. The hostname of the Tenable server. For Tenable Vulnerability Management, the default value is https://cloud.tenable.com.

  • Access Key. Enter the value for the API Key that you generated in the previous section.

  • Access Secret. Enter the value for the API Secret that you generated in the previous section.

  • Max # of Records per Payload. The maximum number of records to send to Tenable Vulnerability Management in each action. The default value is “50”.

  • Verify SSL. For future use. The default value is “False”.

Create or Edit an Action

You can create the following types of Actions for Tenable Vulnerability Management:

  • Send to Tenable Vulnerability Management Index. Sends a custom set of Lucidum data to Tenable Vulnerability Management.

To create an action for Tenable Vulnerability Management:

  1. Go to the Create a New Action page.

  2. In the General step, enter values in these fields:

    • Action Type. Select from the pulldown options. Choices are:

      • Send to Tenable Vulnerability Management Assets. Sends a custom set of Lucidum data to Tenable Vulnerability Management to import as assets.

      • Launch Tenable Vulnerability Management Scan. Launches a scan in Tenable Vulnerability Management with a specified list of assets.

      • Add to Tenable Vulnerability Management Target Group. Adds a list of assets to a target group in Tenable Vulnerability Management. A target group includes a list of targets to scan.

    • Configuration Name. Select an action configuration from the pulldown options.

    • Action Name. Identifier for the action. This name will appear in the Lucidum Action Center.

    • Description. Description of the action.

  3. Click the Next (>) icon.

  4. In the Filters page, click Configure Filters.

  5. The Build a Query page appears.

    build_query1_updated.png

  6. In the Build a Query page, you define the query for the assets or users that the action will act upon.

  7. Click Next.

  8. In the Build a Current Query page, enter the fields, operators, and values for the query. For existing actions, the query is already loaded in this page.

    build_query2_updated.png

  9. For details on creating and editing queries in Lucidum, see the section on Building Queries.

    NOTE: To optimize performance, the default time range is Current. If you need to access historical data, contact Lucidum Custom Success for help on using historical data without affecting performance.

  10. Click the Apply (page and pencil) icon.

  11. Click the Next (>) icon.

  12. The Schedule page appears.

  13. In the Schedule page, enter: 

    • Schedule Type. Define the schedule for the action. Choices are:

      • Recurrence. Specify a frequency for the recurring schedule.

      • After Data Ingestion. The action is executed after data ingestion, which happens at least once every 24 hours and can also be triggered manually.

    • Do not trigger the action unless. Specify the number of results from Filters as a prerequisite for executing the action.

  14. Click the Next (>) icon.

  15. The Details step appears. The fields in this page differ depending upon the Tenable action you selected in the General step.

  16. In the Details page, enter the following:

    • Output Fields. For the records selected with the Filters field, specify the columns to display. When creating or editing the query in the Filters field, you can select these fields in the Query Results page > Edit Column button.

    • Action-specific field. This field differs depending on the action you selected in the General step.

      • Tenable Vulnerability Management Target Source Identifier. If you selected the Action Type “Send to Tenable Vulnerability Management Assets”, supply a source identifier. The data sent to Tenable will be labeled with this identifier. For example “lucidum_assets”.

      • Tenable Vulnerability Management Scan Name. If you selected the Action Type “Launch Tenable Vulnerability Management Scan”, specify the name of the scan (already configured in Tenable Vulnerability Management)

      • Tenable Vulnerability Management Target Group Name. If you selected the Action Type “Add to Tenable Vulnerability Management Target Group”, specify the name of the target group (already configured in Tenable Vulnerability Management)

    • De-dupe Previous Jobs. In this field, you specify whether you want duplicates of asset IDs (if your query is for assets) or user IDs (if your query is for users). You can specify integers between 0 and the number specified in Settings > Data Settings > Action Result Retention in Days. This setting specifies the number of days that Lucidum stores action results.

      • If you specify “0” (zero), Lucidum includes all the records from the query in each delivery to AWS S3.

      • If you specify “1” (one), Lucidum examines the previous webhook payload and excludes records for asset IDs or user IDs that were sent in the delivery to AWS S3.

      • If you specify “2” (two), Lucidum examines the last two webhook payloads and excludes records for asset IDs or user IDs that were sent in the previous two deliveries to AWS S3.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.