Tenable-io v1.2.0

About the connector

Tenable.io Vulnerability Management provides the most accurate information about dynamic assets and vulnerabilities in ever-changing environments.

This document provides information about the Tenable.io connector, which facilitates automated interactions, with a Tenable.io server using FortiSOAR™ playbooks. Add the Tenable.io connector as a step in FortiSOAR™ playbooks and perform automated operations, such as retrieving a list along with details of all the completed scans for a specified time duration, retrieving information about asset(s) that are associated with a specified scan, and retrieving information about the vulnerabilities associated with a particular asset.

Version information

Connector Version: 1.2.0

Authored By: Community

Certified: No

Release Notes for version 1.2.0

Following enhancements have been made to the Tenable.io connector in version 1.2.0:

• A new field called "useragent" has been added to the Rest API headers. The User-Agent string enables tenable to recognize the source of the request, which helps tenable in consolidation and analysis.

Installing the connector

From FortiSOAR™ 5.0.0 onwards, use the Connector Store to install the connector. For the detailed procedure to install a connector, click here.
You can also use the following yum command as a root user to install connectors from an SSH session:

yum install cyops-connector-tenable-io

Prerequisites to configuring the connector

• You must have the URL of Tenable.io server to which you will connect and perform the automated operations and credentials to access that server.
• You must have the access key and secret key that is configured for your account to access the Tenable.io server to which you will connect and perform the automated operations.
• The FortiSOAR™ server should have outbound connectivity to port 443 on the Tenable.io server.

Configuring the connector

For the procedure to configure a connector, click here.

Configuration parameters

In FortiSOAR™, on the Connectors page, click the Tenable.io connector row (if you are in the Grid view on the Connectors page) and in the Configurations tab enter the required configuration details:

Actions supported by the connector

The following automated operations can be included in playbooks, and you can also use the annotations to access operations from FortiSOAR™ release 4.10.0 onwards:

operation: List Scans

Input parameters

Output

The JSON output contains a list along with the details of all the completed scans retrieved from Tenable.io, based on the time duration you have specified.

The output contains the following populated JSON schema:
{
"starttime": "",
"uuid": "",
"enabled": "",
"legacy": "",
"read": "",
"owner": "",
"control": "",
"schedule_uuid": "",
"permissions": "",
"id": "",
"status": "",
"user_permissions": "",
"name": "",
"rrules": "",
"type": "",
"creation_date": "",
"last_modification_date": "",
"timezone": "",
"shared": ""
}

operation: Trigger Scan

Input parameters

Output

The JSON output contains the status of the trigger scan operation. The JSON output returns a Success message if the scan is triggered successfully or an Error message containing the reason for failure. The JSON output also contains the UUID of the triggered scan.

The output contains the following populated JSON schema:
{
"scan_uuid": ""
}

operation: List Scan's Assets

Input parameters

Output

The JSON output contains information about the asset(s) associated with a specific scan retrieved from Tenable.io, based on the scan ID you have specified.

The output contains the following populated JSON schema:
{
"uuid": "",
"mac": [],
"ip": [],
"time_start": "",
"fqdn": [],
"os": [],
"time_end": ""
}

operation: List Asset's Vulnerabilities

Input parameters

Output

The JSON output contains information about the vulnerabilities associated with a specific asset retrieved from Tenable.io, based on the asset UUID you have specified.

The output contains the following populated JSON schema:
{
"plugin_id": "",
"plugin_family": "",
"counts_by_severity": [
{
"value": "",
"count": ""
}
],
"count": "",
"severity": "",
"vulnerability_state": "",
"plugin_name": "",
"accepted_count": "",
"recasted_count": ""
}

operation: Get Vulnerability Information

Input parameters

Output

The JSON output contains information about the vulnerabilities associated with a specific plugin retrieved from Tenable.io, based on the plugin ID you have specified.

The output contains the following populated JSON schema:
{
"see_also": [],
"count": "",
"reference_information": [],
"severity": "",
"synopsis": "",
"discovery": {
"seen_last": "",
"seen_first": ""
},
"risk_information": {
"cvss_vector": "",
"cvss3_temporal_score": "",
"stig_severity": "",
"cvss3_base_score": "",
"cvss3_temporal_vector": "",
"risk_factor": "",
"cvss_temporal_vector": "",
"cvss_base_score": "",
"cvss_temporal_score": "",
"cvss3_vector": ""
},
"plugin_details": {
"modification_date": "",
"name": "",
"type": "",
"publication_date": "",
"family": "",
"severity": "",
"version": ""
},
"description": ""
}

operation: Get Plugin Information

Input parameters

Output

The JSON output contains information about the specific plugin retrieved from Tenable.io, based on the plugin ID you have specified.

The output contains the following populated JSON schema:
{
"id": "",
"family_name": "",
"name": "",
"attributes": [
{
"attribute_name": "",
"attribute_value": ""
}
]
}

operation: Export Vulnerabilities

Input parameters

Output

The output contains the following populated JSON schema:
{
"severity": "",
"first_found": "",
"output": "",
"port": {
"protocol": "",
"port": ""
},
"last_found": "",
"severity_id": "",
"plugin": {
"version": "",
"risk_factor": "",
"publication_date": "",
"solution": "",
"family_id": "",
"id": "",
"modification_date": "",
"name": "",
"synopsis": "",
"type": "",
"has_patch": "",
"description": "",
"family": ""
},
"scan": {
"uuid": "",
"schedule_uuid": "",
"started_at": "",
"completed_at": ""
},
"asset": {
"uuid": "",
"last_authenticated_results": "",
"operating_system": [],
"agent_uuid": "",
"netbios_name": "",
"network_id": "",
"fqdn": "",
"mac_address": "",
"ipv4": "",
"hostname": "",
"tracked": "",
"device_type": "",
"bios_uuid": ""
},
"severity_default_id": "",
"state": "",
"severity_modification_type": ""
}

operation: Export Assets

Input parameters

Output

The output contains the following populated JSON schema:
{
"azure_resource_id": "",
"aws_ec2_instance_id": "",
"agent_uuid": "",
"first_scan_time": "",
"aws_ec2_instance_type": "",
"azure_vm_id": "",
"aws_ec2_instance_ami_id": "",
"netbios_names": [],
"last_authenticated_scan_date": "",
"aws_region": "",
"fqdns": [],
"last_licensed_scan_date": "",
"terminated_at": "",
"gcp_zone": "",
"agent_names": [],
"ipv6s": [],
"deleted_by": "",
"id": "",
"aws_ec2_instance_group_name": "",
"aws_availability_zone": "",
"first_seen": "",
"aws_ec2_name": "",
"has_agent": "",
"aws_vpc_id": "",
"terminated_by": "",
"operating_systems": [],
"last_seen": "",
"tags": [],
"qualys_asset_ids": [],
"network_id": "",
"mcafee_epo_agent_guid": "",
"servicenow_sysid": "",
"qualys_host_ids": [],
"deleted_at": "",
"bios_uuid": "",
"system_types": [],
"gcp_instance_id": "",
"network_name": "",
"manufacturer_tpm_ids": [],
"hostnames": [],
"mcafee_epo_guid": "",
"last_scan_time": "",
"mac_addresses": [],
"sources": [
{
"first_seen": "",
"last_seen": "",
"name": ""
}
],
"ipv4s": [],
"aws_ec2_instance_state_name": "",
"gcp_project_id": "",
"network_interfaces": [
{
"aliased": "",
"name": "",
"ipv6s": [],
"mac_addresses": [],
"ipv4s": [],
"virtual": "",
"fqdns": []
}
],
"installed_software": [],
"has_plugin_results": "",
"aws_ec2_product_code": "",
"aws_owner_id": "",
"symantec_ep_hardware_keys": [],
"aws_subnet_id": "",
"ssh_fingerprints": [],
"updated_at": "",
"created_at": ""
}

Included playbooks

The Sample - Tenable.io - 1.2.0 playbook collection comes bundled with the Tenable.io connector. This playbook contains steps using which you can perform all supported actions. You can see the bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Tenable.io connector.

• Export Assets
• Export Vulnerabilities
• Get Plugin Information
• Get Vulnerability Information
• List Asset’s Vulnerabilities
• List Scans
• List Scan’s Assets
• Trigger Scan

Note: If you are planning to use any of the sample playbooks in your environment, ensure that you clone those playbooks and move them to a different collection since the sample playbook collection gets deleted during connector upgrade and delete.