Tenable.sc

The configuration required for Tenable Security Center is minimal.

  • Each severity and pluginType must be listed.

  • Provide the host address and port of the local TenableSC instance.

There is no need to set the interval more frequently than the frequency Tenable.SC is scanning the network.

If the interval_hours is set to 0, the integration will attempt to download additional content each time the Corelight-update service runs. See Global configuration and policy settings

Once downloaded, this data will be used to create an Input Framework file that can be used by a Zeek script to generate new logs, or enrich existing logs, such as the suricata_corelight.log.

The input file will be published with any other input files from other integrations (if there are any). If “input” in enabled in the “push_content” settings, the file will automatically get pushed to the Fleet Manager policy and/or all sensors in the policy. See Push content settings for more details.

Attention

The Nessus (Tenable Security Center) user you’re using to provide an access_key and secret_key must have Security Management rights. Do not use an admin user.

Settings

tenable_sc:
  enabled:                          false
  interval_hours:                   24
  access_key:
  secret_key:
  severity:                         "4,3,2,1"
  pluginType:                       "Active,Passive,Event"
  address:
  port:                             443
  request_limit:                    50000

Input file

The following is a sample input file created by this integration, using tab-separated values.

#fields  ip     hostname  cve_list
192.168.2.186   mbp       CVE-2021-1234,CVE-2021-4321
192.168.2.133   mbp       CVE-2021-1234,CVE-2021-4321
3.19.25.148     f5        CVE-2020-5902

Important

To use this file, an additional Zeek package is required on the sensor.