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:

  • AdoptOpenJDK Runtime Environment 17 is installed on the connector host.

  • Port requirements:

    Port	Protocol	From	To	Notes
    443	HTTPS	Connector	HAC SaaS and Internet	Outbound
    443 OR <Customer configured port>	HTTPS	Connector	Tenable.io Server	Outbound
    443	HTTPS	Tenable.io Server	Connector	Inbound

    • Connector's Outbound port 443 should be opened for ifm url mentioned in creds.json available in <connectorDirectory>/config/ folder. e.g.

      "endpoints": {        "ifm": "https://<url>"
          }

     

To configure the Tenable.io connector

1. In BMC Helix Automation Console, click Configuration and then click Connectors.
2. On the Manage Connectors page, click Add Connector.
3. On the Add Connector page, from the list of available Connector types, select Scanner Connector.
4. Click Add Configuration.
5. On the Add configuration page, provide the following details:
   1. In the Vendor field, select Tenable.io from the list.
   2. In the Connector details section, provide the following information:
      1. In the Configuration Name field, specify a unique name that is assigned to the scan files imported into Automation Console.
      2. (Optional) In the Configuration Description field, provide a description of the connector.

      3. In the Admin Security Group field, specify one or more admin security groups (comma-separated list) that can access the scan results.
         If you do not specify a security group, all the admin security groups can access the scan files that are imported from Tenable.io.
         

         Important

         For TrueSight Server Automation and Helix endpoints, specify the name of the appropriate security group. If you do not specify a security group, all the admin security groups for both endpoints can access the scan files that are imported from Tenable.io.

   3. 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 schedule, Automation Console fetches only those vulnerabilities and assets that were scanned and available in Tenable.io after the last sync date.

   4. In the Authentication Details section, perform the following steps:
      1. Enter the User Name set for your account with Tenable.io.
      2. Enter the Password set for your account with Tenable.io.
   5. In the Filters section, provide values to fetch the specific scanned data:
      1. Select the required Severity levels.
      2. To fetch more precise data, enter the Network IP in CIDR format.
      3. Specify additional filters to fetch further detailed scanned data.
   6. 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.
6. Click Save.
   The newly added configuration is listed in the Configurations table.
7. If you have multiple Tenable scanners in your environment, repeat steps 4to 6for each scanner.
8. On the Add Connectors page, in the Configuration Schedule section, specify a frequency at which you want to run the connector, and save the schedule.
9. Click Continue and download the connector zip file on a local host. 

10. From the connector location on the server where the connector file is downloaded and extracted, run the following command to install and start the connector: 

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

    You can view the connector status on the Connectors page.

11. (Optional) To configure the Scanner connector as a service, perform the following steps:
    1. Make sure the scanner-connector.xml file is available in a folder where the connector zip file is unzipped.
    2. Run the scanner-connector.exe install command. 
    3. A new service with the name BMC Scanner Connector is created on the host and can be used as any other available service.

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

To update the connector

1. On the Manage Connectors page, click Action against the Scanner connector and then click Disable.
2. Click Action against the Scanner connector and then click Edit.
3. 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.
4. Edit the information according to your requirements and click Update. 

To enable 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 Troubleshooting-connectors.