Fortinet white logo
Fortinet white logo
2.0.0

Tor v2.0.0

About the connector

Tor Connector facilitates to query information of Tor network

This document provides information about the Tor Connector, which facilitates automated interactions, with a Tor server using FortiSOAR™ playbooks. Add the Tor Connector as a step in FortiSOAR™ playbooks and perform automated operations with Tor.

Version information

Connector Version: 2.0.0

FortiSOAR™ Version Tested on: 7.5.0-4015

Authored By: Fortinet

Certified: Yes

Release Notes for version 2.0.0

Following enhancements have been made to the Tor Connector in version 2.0.0:

  • Added Verify SSL parameter in the connector configuration.

Installing the connector

Use the Content Hub to install the connector. For the detailed procedure to install a connector, click here.

You can also use the yum command as a root user to install the connector:

yum install cyops-connector-tor

Prerequisites to configuring the connector

  • The FortiSOAR™ server should have outbound connectivity to port 443 on the Tor server.

Minimum Permissions Required

  • Not applicable

Configuring the connector

For the procedure to configure a connector, click here

Configuration parameters

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

Parameter Description
Verify SSL Specifies whether the SSL certificate for the server is to be verified.
By default, this option is selected, i.e., set to True.

Actions supported by the connector

The following automated operations can be included in playbooks and you can also use the annotations to access operations:

Function Description Annotation and Category
Check Tor Exit Node Checks if the IP address or addresses that you have specified are a Tor exit node. lookup_ip
Miscellaneous

operation: Check Tor Exit Node

Input parameters

Parameter Description
IP or list of IP's Specify an IP address to check if it is a Tor exit node. You can enter multiple IP addresses as comma-separator values. For example, xx.xx.xx.1, xx.xx.xx.2, xx.xx.xx.3.

Output

The output contains the following populated JSON schema:

[
    {
        "is_exit_node": "",
        "ip": ""
    }
]

Included playbooks

The Sample - Tor - 2.0.0 playbook collection comes bundled with the Tor connector. These playbooks contain steps using which you can perform all supported actions. You can see bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Tor connector.

  • Check Tor Exit Node

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.

Previous
Next

Tor v2.0.0

About the connector

Tor Connector facilitates to query information of Tor network

This document provides information about the Tor Connector, which facilitates automated interactions, with a Tor server using FortiSOAR™ playbooks. Add the Tor Connector as a step in FortiSOAR™ playbooks and perform automated operations with Tor.

Version information

Connector Version: 2.0.0

FortiSOAR™ Version Tested on: 7.5.0-4015

Authored By: Fortinet

Certified: Yes

Release Notes for version 2.0.0

Following enhancements have been made to the Tor Connector in version 2.0.0:

Installing the connector

Use the Content Hub to install the connector. For the detailed procedure to install a connector, click here.

You can also use the yum command as a root user to install the connector:

yum install cyops-connector-tor

Prerequisites to configuring the connector

Minimum Permissions Required

Configuring the connector

For the procedure to configure a connector, click here

Configuration parameters

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

Parameter Description
Verify SSL Specifies whether the SSL certificate for the server is to be verified.
By default, this option is selected, i.e., set to True.

Actions supported by the connector

The following automated operations can be included in playbooks and you can also use the annotations to access operations:

Function Description Annotation and Category
Check Tor Exit Node Checks if the IP address or addresses that you have specified are a Tor exit node. lookup_ip
Miscellaneous

operation: Check Tor Exit Node

Input parameters

Parameter Description
IP or list of IP's Specify an IP address to check if it is a Tor exit node. You can enter multiple IP addresses as comma-separator values. For example, xx.xx.xx.1, xx.xx.xx.2, xx.xx.xx.3.

Output

The output contains the following populated JSON schema:

[
    {
        "is_exit_node": "",
        "ip": ""
    }
]

Included playbooks

The Sample - Tor - 2.0.0 playbook collection comes bundled with the Tor connector. These playbooks contain steps using which you can perform all supported actions. You can see bundled playbooks in the Automation > Playbooks section in FortiSOAR™ after importing the Tor connector.

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.

Previous
Next