Skip to main content
Sumo Logic

Tenable Source

The Tenable Source provides a secure endpoint to ingest audit-log events, vulnerability, and asset data from the APIs. It securely stores the required authentication, scheduling, and state tracking information.


A Tenable Source tracks errors, reports its health, and start-up progress. You’re informed, in real-time, if the Source is having trouble connecting, if there's an error requiring user action, or if it is healthy and collecting by utilizing Health Events.

A Tenable Source goes through the following states when created:

  1. Pending: Once the Source is submitted it is validated, stored, and placed in a Pending state.
  2. Started: A collection task is created on the Hosted Collector.
  3. Initialized: The task configuration is complete in Sumo Logic.
  4. Authenticated: The Source successfully authenticated with Tenable.
  5. Collecting: The Source is actively collecting data from Tenable.

If the Source has any issues during any one of these states it is placed in an Error state.

When you delete the Source it is placed in a Stopping state, when it has successfully stopped it is deleted from your Hosted Collector.

On the Collection page, the Health and Status for Sources is displayed. Use Health Events to investigate issues with collection.

Tenable error.png

Hover your mouse over the status icon to view a tooltip with details on the detected issue.

health error generic.png


The Tenable Source is configured with a Tenable IO Access and Secret Key. Your account must have ADMINISTRATOR [64] user permissions.

Create a Tenable Source

When you create a Tenable Source, you add it to a Hosted Collector. Before creating the Source, identify the Hosted Collector you want to use or create a new Hosted Collector. For instructions, see Configure a Hosted Collector.

To configure A Tenable Source:

  1. In the Sumo Logic web app, navigate to Manage Data > Collection and open the Collection tab.
  1. On the Collectors page, click Add Source next to a Hosted Collector.
  1. Select Tenable.
    Tenable icon.png
  1. Enter a Name for the Source. The description is optional.
  1. (Optional) For Source Category, enter any string to tag the output collected from the Source. Category metadata is stored in a searchable field called _sourceCategory.
  2. Forward to SIEM. Check the checkbox to forward your data to Cloud SIEM Enterprise. When configured with the Forward to SIEM option the following metadata fields are set:
    Field Name Value
    _siemVendor Tenable
    _siemProduct Cloud
    _siemFormat JSON

    Set to the type of data ingested. 

    Vulnerabilities: vulnerability
    Audits: {action}

    Assets (Inventory): assets

    _siemDataType (Only with Assets (Inventory) data) Inventory
  3. (Optional) Fields. Click the +Add link to add custom log metadata Fields.
    • Define the fields you want to associate, each field needs a name (key) and value. 
      • green check circle.png A green circle with a check mark is shown when the field exists and is enabled in the Fields table schema.
      • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist, or is disabled, in the Fields table schema. In this case, an option to automatically add or enable the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema or is disabled it is ignored, known as dropped. 
  4. Provide the Access Key and Secret Key to authenticate requests.

  5. (Optional) Include unlicensed objects. Select the checkbox if you want to collect unlicensed objects.

  6. Supported APIs to collect. Select one or more of the available APIs: Vulnerability Data, Audit Logs, and Asset Data.

  7. Processing Rules. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in Create a Processing Rule.
  8. When you are finished configuring the Source click Submit.

Error types

When Sumo Logic detects an issue it is tracked by Health Events. The following table shows the three possible error types, the reason the error would occur, if the Source attempts to retry, and the name of the event log in the Health Event Index.

Type Reason Retries Retry Behavior Health Event Name
ThirdPartyConfig Normally due to an invalid configuration. You'll need to review your Source configuration and make an update. Yes The Source will retry for up to 90 minutes, after which retries will be attempted every 60 minutes. ThirdPartyConfigError
ThirdPartyGeneric Normally due to an error communicating with the third party service APIs. Yes The Source will retry for up to 90 minutes, after which retries will be attempted every 60 minutes. ThirdPartyGenericError
FirstPartyGeneric Normally due to an error communicating with the internal Sumo Logic APIs. Yes The Source will retry for up to 90 minutes, after which retries will be attempted every 60 minutes. FirstPartyGenericError

JSON configuration

Sources can be configured using UTF-8 encoded JSON files with the Collector Management API. See how to use JSON to configure Sources for details. 

Parameter Type Required? Description Access
config JSON Object Yes Contains the configuration parameters for the Source.  
schemaRef JSON Object Yes Use {"type":"Tenable"} for a Tenable Source. not modifiable
sourceType String Yes Use Universal for a Tenable Source. not modifiable

The following table shows the config parameters for a Tenable Source.

Parameter Type Required Default Description Access
name String Yes   Type a desired name of the Source. The name must be unique per Collector. This value is assigned to the metadata field _source. modifiable
description String No null Type a description of the Source. modifiable
category String No null Type a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details. modifiable
fields JSON
No   JSON map of key-value fields (metadata) to apply to the Collector or Source.

Use the boolean field _siemForward to enable forwarding to SIEM.
access_key String Yes   The Tenable access key you want to use to authenticate collection requests. modifiable
secret_key String Yes   The Tenable secret key you want to use to authenticate collection requests. modifiable
include_unlicensed_assets Boolean No False Set to true if you want to collect unlicensed objects. Modifiable
supported_apis Array of strings No Vulnerability Data Define one or more of the available APIs to collect: Vulnerability Data, Audit Logs, and Asset Data.

For example, for both you'd use:
["Vulnerability Data","Audit Logs","Asset Data"]

See how to create processing rules using JSON.

Tenable Source JSON example:

    "api.version": "v1",
    "source": {
        "schemaRef": {
            "type": "Tenable"
        "config": {
            "name": "Tenable",
            "description": "East field",
            "access_key": "********",
            "secret_key": "********",
            "supported_apis": ["Vulnerability Data","Audit Logs","Asset Data"],
            "fields": {
                "_siemForward": false
            "category": "eastTeamF"
        "sourceType": "Universal"