Configuring the Tenable.io Scanner Connector

As an administrator, you can configure different types of scanners to scan security risks and vulnerabilities across your IT infrastructure. BMC Helix Automation Console currently supports Tenable.io as a Scanner Connector and other scanners will eventually be integrated with the Automation Console.

Tenable.io is a comprehensive vulnerability management solution that provides complete visibility of the security risks across your IT infrastructure. With this integration, you can retrieve the vulnerability scan results from multiple Tenable.io instances and process the vulnerabilities to map the remediation content. You can then create operations to remediate vulnerabilities. 

After you configure and run this connector, the scan files that contains the Tenable.io assets and vulnerabilities are automatically imported into Automation Console.

Before you begin

Make sure that the following prerequisites are met:

• One or more configured Tenable.io instances are running in your environment.

• The API keys are generated for your user account in Tenable.io. The connector uses these keys to authenticate Tenable.io APIs. For more information, see Generate API keys.

• Install and run the connector on Windows or Linux operating systems based on the following criteria:

  • Port requirements:

    Port	Protocol	From	To	Inbound / Outbound
    443 OR <Customer configured port>	HTTPS	Connector	Tenable.io Server	Outbound
    443	HTTPS	Tenable.io Server	Connector	Inbound

Configuring the connector

After you install TrueSight Automation Console, the Tenable.io connector is available for configuration in the Scanner Connectors widget. 

1. From the TrueSight Automation Console, login as an administrative user. 
2. From Briefcase , click Connectors.
3. On the Manage Connectors page, click the  option against the Scanner Connector widget and click Edit > Add Configuration.
   
4. On the Add configuration page, provide the following details:
   1. Select the required vendor from the dropdown menu.
   2. In the Connector details section, specify a unique name and an optional description.

   3. (Optional) In the Admin Security Group field, specify one or more admin security groups (comma separated list) that can access the scan results.
      If no security group is specified, all the admin security groups can access the scan files imported from Tenable.io.

      Important

      If you have both TrueSight Server Automation and TrueSight Network Automation endpoints, specify the name of the appropriate security group. If you specify a non-admin security group, Automation Console does not fetch any data from Tenable.io.

   4. In the Connector Configuration section, perform the following steps:
      1. In the Endpoint URL field, specify the URL to connect to Tenable.io.

      2. In the Fetch Data From field, specify the number of days for which you want to fetch the scan results.

         Important

         Automation Console retrieves the vulnerability data for the specified days during the first import. If you do not specify any value, Automation Console retrieves all the reported vulnerabilities from the Tenable.io instances.

         For all the imports during the next schedules, Automation Console fetches only those vulnerabilities and assets that were scanned and available in Tenable.io after the last sync date.

   5. In the Authentication Details section, specify the access and secret keys to authenticate with the Tenable.io API.
   6. In the Filters section and provide values to fetch specific scanned data:
      1. Select the required Severity levels.
      2. To fetch more precise data, enter the Network IP/Hostname/CIDR as comma separated values.
      3. Specify additional filters to fetch further detailed scanned data.
   7. In the Auto-close vulnerabilities section, select the Enable Auto-close check box to enable the system to automatically close vulnerabilities that were fixed in the previous scan and are no longer present in the subsequent scan.
5. Click Save.
   The newly added configuration is listed in the Configurations table.
6. If you have multiple Tenable scanners in your environment, repeat steps 2 to 5 for each scanner.
7. In the Configuration Schedule section, specify a frequency at which you want to run the connector, and save the schedule.
8. Click Continue and download the connector zip file on a local host. 

9. On the server where the connector file is downloaded and extracted, go to the connector location, and run the following command to install and start the connector: 

   • Windows: run.bat
   • Linux: run.sh

   The connector starts running successfully. You can view the connector status on the Connectors page.

Vulnerability scan files are created with the specified configuration names. Automation Console processes each configuration sequentially.

Updating the connector

1. On the Manage Connectors page, click the  option against the Scanner Connector widget, and click Disable.
2. Click Edit.
   The available configurations are displayed. To quickly locate the required configuration, search or sort the configurations by the various columns, such as Status and Vendor.
3. Click Save.
   
   

Enabling debug mode

1. Press CTRL+C twice to stop the connector, if its already running.

2. Go to <ConnectorLocation>/config, open the application.properties file, add the following parameter, and set it to debug.

   #
   #Logging related Properties
   logging.level.com.bmc.truesight.scannerconnector=debug
3. Save the file.
4. Restart the connector.

Troubleshooting

If you encounter any issues while fetching data from Tenable.io, the Connector tile on the Manage Connectors page displays the name of the configuration with error messages and the related exceptions are logged in the log file. For troubleshooting issues, see Working-with-logs and Troubleshooting-connectors.