Create an Input

After you complete the configuration for your Tenable Add-On for Splunk, you must create the input. The following process outlines input creation if you have a deployment with Tenable Add-On for Splunk orTenable App for Splunk,.

To create an input:

  1. In the left navigation bar, click Tenable Add-On for Splunk, Tenable App for Splunk,.

  2. Click the Inputs tab.

  3. Click Create New Input.

    A new configuration window appears.

  4. Provide the following information.

    Note: If you don't use the default index, you must update the Tenable Macro.

    Tenable Vulnerability Management

    Input Parameters Description Required
    Name The unique name for each Tenable data input.

    Yes

    Interval The interval parameter specifies when the input restarts to perform the task again. This supports seconds (between 3600 and 86400) or a cron schedule.

    Yes

    Index The index in which to store Tenable Vulnerability Management data.

    Yes

    Global Account Splunk pulls data from this Tenable account.

    Yes

    Sync Plugin Details If selected, the related tags in Tenable assets include plugin details.

    Yes

    Host Vulnerability   Start Time   The date and time to start collecting host data. If you leave this field blank, the integration collects all historical data. (Enter in this format - YYYY-MM-DD hh:mm:ss.)  

    No

    Lowest Severity Score The lowest level of severity stored.

    No

    Historical Fixed Vulnerability Allows the import of host vulnerabilities fixed before the current day.

    No

    Tags Limits host vulnerabilities pulled to host assets that have tags selected.

    No

    Tenable Security Center Vulnerability

    Input Parameters Description Required
    Name The unique name for each Tenable data input.

    Yes

    Interval

    The interval parameter specifies when the input restarts to perform the task again. This supports seconds (between 300 and 86400) or a cron schedule.

    Note: Restricting the input to collect data during inactive scan periods with a cron schedule is recommended, especially for large Security Center deployments. For smaller deployments, a minimum interval of one hour (3600) can be used.

    Yes

    Index The index in which to store Tenable Security Center data.

    Yes

    Global Account Splunk pulls data from this Tenable account.

    Yes

    Start Time

    The date and time to start collecting data. If you leave this field blank, the integration collects all historical data.

    Note: Uses the YYYY-MM-DD hh:mm:ss format.

    No

    Sync Plugin Details If selected, the related tags in Tenable assets include plugin details.

    Yes

    Historical Fixed Vulnerability Allows the import of vulnerabilities fixed before the current day.

    No

    Query Name

    A name for Tenable Security Center vulnerability filter.

    Note: The interval must be query type Vulnerability Detail List.

    No

    Tenable Security Center Mobile

    Input Parameters Description Required
    Name The unique name for each Tenable data input.

    Yes

    Interval The interval parameter specifies when the input restarts to perform the task again (in seconds).

    Yes

    Index The index in which to store Tenable Security Center data.

    Yes

    Global Account Splunk pulls data from this Tenable account.

    Yes

    Query Name

    A name for Tenable Security Center vulnerability filter.

    Note: The interval must be query type - Vulnerability Detail List.

    No

  5. Click Add to create the input.
  1. Run the All Time saved search.
  2. Schedule an All Time saved search.

Note: Tenable recommends running the saved search every 24 hours. However, you can adjust as needed.

Note: Asset and vulnerabilities in Splunk might differ from individual scan results since the Splunk integration synchronizes cumulative vulnerability and asset data from the Tenable API endpoints.