Skip to main content

Tenable Source

icon

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

note

This source is available in the Fed deployment.

Data collected

Polling IntervalData
5 minExport API
5 minAudit logs
5 minExports assets

Setup

note

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

Vendor configuration

You need to have a Tenable account to generate Access Key and Secret Key. Follow the instruction in the Tenable documentation to generate Access Key and Secret Key.

Source configuration

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 Sumo Logic, navigate to** Manage Data > Collection** and open the Collection tab.
  2. On the Collectors page, click Add Source next to a Hosted Collector.
  3. Select for and select Tenable.
  4. Enter a Name for the source. The description is optional.
  5. (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.
  6. Forward to SIEM. Check the checkbox to forward your data to Cloud SIEM.
  7. (Optional) Fields. Click the +Add Field link to 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 in the Fields table schema.
    • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist in the Fields table schema. In this case, an option to automatically add 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 it is ignored, known as dropped.
  8. Provide the Access Key and Secret Key to authenticate requests.
  9. (Optional) Include unlicensed objects. Select the checkbox if you want to collect unlicensed objects.
  10. Supported APIs to collect. Select one or more of the available APIs: Vulnerability Data, Audit Logs, and Asset Data.
  11. Processing Rules. Configure any desired filters, such as allowlist, denylist, hash, or mask, as described in Create a Processing Rule.
  12. When you are finished configuring the Source, click Submit.

Metadata fields

FieldValueDescription
_siemVendorTenableSet when Forward To SIEM is checked.
_siemProductCloud APISet when Forward To SIEM is checked.
_siemFormatJSONSet when Forward To SIEM is checked.
_siemEventIDVulnerabilities: vulnerability, Audits: {action}, or Assets (Inventory): assetsSet when Forward To SIEM is checked and specific to the API collected.
_siemDataTypeInventoryOnly with Assets (Inventory) data.

Base URL

Internally, the source will use the following base URL depending on the respective environment:

BASE URLValue
Non-Fed Env.https://cloud.tenable.com
Fed Env.https://fedcloud.tenable.com

JSON schema

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. 

ParameterTypeValueRequiredDescription
schemaRefJSON Object{"type":"Tenable"}YesDefine the specific schema type.
sourceTypeString"Universal"YesType of source.
configJSON ObjectConfiguration objectYesSource type specific values.

Configuration Object

ParameterTypeRequiredDefaultDescriptionExample
nameStringYesnullType a desired name of the source. The name must be unique per Collector. This value is assigned to the metadata field _source."mySource"
descriptionStringNonullType a description of the source."Testing source"
categoryStringNonullType a category of the source. This value is assigned to the metadata field _sourceCategory. See best practices for details."mySource/test"
fieldsJSON ObjectNonullJSON map of key-value fields (metadata) to apply to the Collector or Source. Use the boolean field _siemForward to enable forwarding to SIEM.{"_siemForward": false, "fieldA": "valueA"}
access_keyStringYesnullThe Tenable access key you want to use to authenticate collection requests.
secret_keyStringYesnullThe Tenable secret key you want to use to authenticate collection requests.
fed_cloudBooleanNoFalseSet to true if tenable.io uses FedRAMP environment.
include_unlicensed_assetsBooleanNoFalseSet to true if you want to collect unlicensed objects.
supported_apisArray of stringsNoVulnerability DataDefine 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"]

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"
}
}

Download example

Terraform example

resource "sumologic_cloud_to_cloud_source" "tenable_source" {
collector_id = sumologic_collector.collector.id
schema_ref = {
type = "Tenable"
}
config = jsonencode({
"name": "Tenable",
"description": "East field",
"access_key": "********",
"secret_key": "********",
"supported_apis": ["Vulnerability Data","Audit Logs","Asset Data"],
"fields": {
"_siemForward": false
},
"category": "eastTeamF"
})
}
resource "sumologic_collector" "collector" {
name = "my-collector"
description = "Just testing this"
}

Download example

FAQ

info

Click here for more information about Cloud-to-Cloud sources.

Legal
Privacy Statement
Terms of Use

Copyright © 2024 by Sumo Logic, Inc.