Clean Install of TOS Aurora on GCP

For additional help, refer to the official documentation Create and start a VM instance.

1. In the Google Cloud console, navigate to Compute Engine > VM instances

2. Click CREATE INSTANCE.

3. Configure:

   • Name:

   • Region/Zone: As appropriate

   • Machine family: GENERAL-PURPOSE

   • Series: E2

   • Machine type: Custom

   • Cores / Memory: According to the load-model parameter value received from your account team.

4. Under Boot Disk, click CHANGE.

5. Configure the boot disk.

   • Make sure tab Public Images is selected.

   • Operating system: Red Hat Enterprise Linux or Rocky Linux

   • Version:

     • Red Hat Enterprise Linux 8.6, 8.8, or 8.9

     • Rocky Linux 8.6, 8.8, or 8.9

   • Boot disk type, SSD persistent disk

   • Size, The value received from your account team.

6. Click Select. The boot disk settings will be saved.

7. Select Advanced options.

8. Select Networking.

9. Configure Networking:

   • Network tags: default-allow-ssh allow-nginx-ingress

   • Hostname: Optional

10. (Optional) Host name: Type a host name or use the default device value.

11. Click CREATE.

Create a firewall rule to allow traffic to nginx nodeport and health checking

Leave default values for all parameters not mentioned.

1. Navigate to VPC Network > Firewall

2. Click CREATE FIREWALL RULE

3. Configure:

   • Name: allow-nginx-ingress

   • Network: default

   • Direction: Ingress

   • Action: Allow

   • Targets: Specified target tags

   • Target tags: allow-nginx-ingress

   • Source filter: IPv4 ranges

   • Source IPv4 ranges: 0.0.0.0/0

   • Second sourced filter: None

   • Protocols and ports: Specified ports and protocols - TCP 31443

4. Click CREATE.

For more information about managing instance groups, see the vendor documentation Group unmanaged VMs together.

Leave default values for all parameters not mentioned.

1. Navigate to Compute Engine > Instance groups

2. Click CREATE INSTANCE GROUP.

3. Select New unmanaged instance group (not the stateless or stateful options).

   

4. Configure:

   • Name:

   • Location: As defined for your VM

   • Network / Subnetwork: Same network used by the instance or Default

   • VM Instances: Select the new VM created previously

   

5. Under Port mapping, click ADD PORT

6. Enter port details

   • Name: https

   • Number: 31443

7. Add additional TCP ports, by repeating the previous two steps, depending on the features you intend to use from the list below.

   • OPM devices -31099

   • TCP syslogs - 31514

   

8. Click CREATE. The instance group will be created.

Leave default values for all parameters not mentioned.

1. Navigate to Health checks.

2. Click CREATE HEALTH CHECK.

3. Select/Enter values:

   • Name

   • Protocol: TCP

   • Port: 31443

4. Leave default values for health criteria, or change according to your requirements.

5. Click CREATE.

After launching the instance, you need to create a separate load balancer for each of the ports you are going to need. These ports are listed in the Target column in the table below. Some ports are only needed if you are deploying a remote collector.

Protocol	Source	Target	Purpose	Cluster Type (Central Cluster/Remote Collectors)
TCP	443	31443	Mandatory. UI connectivity.	Central cluster
TCP	9099	31099	OPM devices	Central cluster
TCP	6514	31514	TCP syslogs	Central cluster/ Remote collector
TCP	8422	31422	Event streaming	Remote collector
TCP	9090	31090	Allows central cluster to receive data from remote collector cluster	Remote collector
TCP	31843	8443	RC sync - Revisions and control	Remote collector
TCP	61617	31617	JMS - configuration metrics and device statuses	Remote collector
TCP	8443	31843	SecureTrack client	Central cluster (only if deploying remote collector)

Repeat this step for each port in the table that you are going to need.

For more information, see the vendor documentation Set up the load balancer.

Leave default values for all parameters not mentioned.

1. Navigate to Network Services - Load balancing.

2. Click CREATE LOAD BALANCER

3. Under TCP load balancing, click START CONFIGURATION.

4. Select/Enter values:

   • Internet facing or internal only: From Internet to my VMs.

   • Multiple regions or single region: Multiple regions.
5. Click Continue.
6. Enter a name for the load balancer.

7. Click Backend configuration:

8. Enter values:

   • Backend type: Instance group

   • Protocol: TCP

   • Named port: https-ingress

   • Timeout: 30

9. Enter/select values:

   • Instance group: The instance group created previously

   • Port numbers: 31443

   • Health check: The health check created previously

10. Click DONE

11. Click Frontend configuration

12. Click ADD FRONTEND IP AND PORT

13. Enter values:

    • New frontend IP and port - Name: https-ingress

    • Protocol: TCP

    • IP version: IPv4

    • IP address: Ephemeral

    • Port: 443

14. Click DONE

15. Click CREATE

For more information, see the vendor documentation Create a new firewall rule.

1. Navigate to VPC Network > Firewall

2. Click CREATE FIREWALL RULE

3. Configure:

   • Name

   • Logs: Off

   • Network: Default

   • Priority: 1000

   • Direction of traffic: Ingress

   • Action on match: Allow

   • Targets: Specified target tags

   • Target tags: (example) syslog-ingress

   • Source filter: IPv4 ranges

   • Source IPv4 ranges: 0.0.0.0/0

   • Second source filter: None

   • Protocols and ports: Specified protocols and ports - UDP 30514

4. Click CREATE.

5. Navigate to VM instances and select the VM created previously

6. Click EDIT

7. Go to Network Tags and add the target tag specified above

For more information, see the vendor documentation Set up the load balancer.

Leave default values for all parameters not mentioned.

1. Navigate to Load balancing - Network services.

2. Click CREATE LOAD BALANCER

3. Under UDP load balancing, click START CONFIGURATION.

4. Select/Enter values:

   • Internet facing or internal only: From Internet to my VMs.

   • Backend type: Target Pool or Target Instance
5. Click Continue.
6. Enter a name for the load balancer.
7. Select same region defined for your VM.

8. Click Backend configuration:

9. Enter values:

   • Backends: SELECT EXISTING INSTANCES

   • VM instances: Your VM name

10. Click Frontend configuration

11. Click ADD FRONTEND IP AND PORT

12. Enter values:

    • New frontend IP and port - Name: 

    • Protocol: UDP

    • Network service Tier: Premium

    • IP address: Ephemeral

    • Port: 30514

13. Click DONE.

14. Click CREATE.

To connect via ssh you can add an existing ssh key to GCP via UI or use the gcloud utilily to generate key and add it.

To generate a key using gcloud:

1. Download gcloud to your workstation.

2. Run gcloud auth login command to login to your account. Variable <PROJECT_ID> can be set once globally to avoid entering it each time.

   gcloud config set project "<PROJECT_ID>"

   gcloud config set project "<PROJECT_ID>"

   gcloud compute ssh --zone "<ZONE>" "<VM_INSTANCE_NAME>" 

   gcloud compute ssh --zone "<ZONE>" "<VM_INSTANCE_NAME>"

If not done already, set up partitions according to the Prerequisites.

1. If you are not currently logged in as user root, do so now.

   [<ADMIN> ~]$ su -

   su -

2. If you want to change the host name or IP of the machine, do so now. Once TOS Aurora has been installed, changing the host name or IP address will require reinstalling - see Changing IP Address/Host Names. To change the host name, use the command below, replacing <mynode> with your preferred name.

   [<ADMIN> ~]# hostnamectl set-hostname <mynode>

   hostnamectl set-hostname <mynode>

3. Modify the environment path to run TOS CLI commands without specifying the full path (/usr/local/bin/tos).

   [<ADMIN> ~]# echo 'export PATH="${PATH}:/usr/local/bin"' | sudo tee -a /root/.bashrc > /dev/null

   echo 'export PATH="${PATH}:/usr/local/bin"' | sudo tee -a /root/.bashrc > /dev/null

4. Synchronize your machine time with a trusted NTP server. Follow the steps in Configuring NTP Using Chrony.

5. Configure the server timezone.

   [<ADMIN> ~]# timedatectl set-timezone <timezone>

   timedatectl set-timezone <timezone>

   where <timezone> is in the format Area/Location. Examples: America/Jamaica, Hongkong, GMT, Europe/Prague. List the time-zone formats that can be used in the command.

   [<ADMIN> ~]# timedatectl list-timezones

   timedatectl list-timezones

6. Upgrade the kernel:

   [<ADMIN> ~]# dnf upgrade

   dnf upgrade

7. Disable SELinux:

   • If file /etc/selinux/config exists, edit and change the value of SELINUX to disabled:

     SELINUX=disabled

   • If the file doesn't exist or SELINUX is already set to disabled, do nothing.
8. Reboot the machine and log in.
9. Install Wireguard. This is needed to encrypt communication between nodes (machines) within the cluster. See Install Wireguard and follow the steps for your Linux distribution.
10. Reboot the machine and log in.

11. Install tmux and rsync:

    [<ADMIN> ~]# dnf install -y rsync tmux

    dnf install -y rsync tmux

12. Disable the firewall:

    [<ADMIN> ~]# systemctl stop firewalld

    systemctl stop firewalld

    [<ADMIN> ~]# systemctl disable firewalld

    systemctl disable firewalld

13. Create the TOS Aurora load module configuration file /etc/modules-load.d/tufin.conf. Example using vi:

    [<ADMIN> ~]# vi /etc/modules-load.d/tufin.conf

    vi /etc/modules-load.d/tufin.conf

14. Specify the modules to be loaded by adding the following lines to the configuration file created in the previous step. The modules will then be loaded automatically on boot.

    br_netfilter
    wireguard
    overlay
    ebtables
    ebtable_filter

    br_netfilter wireguard overlay ebtables ebtable_filter

15. Load the above modules now:

    [<ADMIN> ~]# cat /etc/modules-load.d/tufin.conf |xargs modprobe -a 

    cat /etc/modules-load.d/tufin.conf |xargs modprobe -a

    Look carefully at the output to confirm all modules loaded correctly; an error message will be issued for any modules that failed to load.

16. Check that Wireguard has loaded correctly.

    [<ADMIN> ~]# lsmod |grep wireguard

    lsmod |grep wireguard

    The output will appear something like this:

    wireguard              201106  0
    ip6_udp_tunnel         12755  1 wireguard
    udp_tunnel             14423  1 wireguard
    

    If Wireguard is not listed in the output, contact support.

17. Create the TOS Aurora kernel configuration file /etc/sysctl.d/tufin.conf. Example using vi:

    [<ADMIN> ~]# vi /etc/sysctl.d/tufin.conf

    vi /etc/sysctl.d/tufin.conf

18. Specify the kernel settings to be made by adding the following lines to the configuration file created in the previous step. The settings will then be applied on boot.

    net.bridge.bridge-nf-call-iptables = 1
    fs.inotify.max_user_watches = 1048576
    fs.inotify.max_user_instances = 10000
    net.ipv4.ip_forward = 1

    net.bridge.bridge-nf-call-iptables = 1 fs.inotify.max_user_watches = 1048576 fs.inotify.max_user_instances = 10000 net.ipv4.ip_forward = 1

19. Apply the above kernel settings now:

    [<ADMIN> ~]# sysctl --system

    sysctl --system

Deploy the Install File

1. On the target machine, create the directory /opt/misc/, if it does not exist already.

2. Transfer the run file (already downloaded and extracted) to the /opt/misc/ directory.

3. Verify the integrity of the TOS installation packages by entering the following commands and comparing the output with the checksum information.

[<ADMIN> ~]$ sha256sum tos-xxxx-xxxxxxxx-final-xxxx.run.tgz

sha256sum tos-xxxx-xxxxxxxx-final-xxxx.run.tgz

[<ADMIN> ~]$ sha1sum tos-xxxx-xxxxxxxx-final-xxxx.run.tgz

sha1sum tos-xxxx-xxxxxxxx-final-xxxx.run.tgz

4. Extract the TOS run file from its archive.

   [<ADMIN> ~]$ tar -xvzf tos-xxxx-xxxxxxxx-final-xxxx.run.tgz

   tar -xvzf tos-xxxx-xxxxxxxx-final-xxxx.run.tgz

5. Run the TOS Aurora run file.

   [<ADMIN> ~]$ sudo cd /opt

   sudo cd /opt

   [<ADMIN> ~]$ sudo sh <runfile>

   sudo cd /opt sudo sh <runfile>

6. You must have permissions to execute TOS CLI commands. Grant permissions as shown below or allow use of sudo command.

   [<ADMIN> ~]# chmod +x /usr/local/bin/tos

   chmod +x /usr/local/bin/tos

Start the Install

1. Run the screen command:

   [<ADMIN> ~]$ sudo tmux new-session -S install

   sudo tmux new-session -S install

2. Run the install command, replacing the parameters:

   • <SERVICE-CIDR> with the CIDR you want TOS Aurora to use for the Kubernetes service network, as described in Prerequisites

   • <MODULE-TYPE> with one of the following values:

     • ST for SecureTrack only
     • ST, SC for both SecureTrack and SecureChange
   • <LOAD> with the load-model parameter value received from your account team as described in Prerequisites.

   [<ADMIN> ~]$ sudo tos install --modules=<MODULE-TYPE> --primary-vip=external --services-network=<SERVICE-CIDR> --load-model=<LOAD> -d

   sudo tos install --modules=<MODULE-TYPE> --primary-vip=external --services-network=<SERVICE-CIDR> --load-model=<LOAD> -d

   Example:

   # sudo tos install --modules=ST,SC --primary-vip=external --services-network=10.10.10.0/24 --load-model=medium -d
   

3. The EULA is displayed. After reading, enter 'q' to exit the document and then enter 'y' to accept the EULA and continue until the command completes.

   

4. You can now safely exit the CLI screen session:

   [<ADMIN> ~]$ sudo exit

   exit

5. Go to the TOS Aurora login page by going to the URL of the load balancer DNS in your browser.

6. Log in with user=admin, password=admin. If a warning message is shown regarding the site security certificate, 'accept the risk' and continue to the site. You will be prompted to set a new password.

Post-Install Configuration

Professional Services

If you are a PS (Tufin Professional Services) customer,

1. Restart the PS web service

   [<ADMIN> ~]$ sudo systemctl start tufin-ps-web

   sudo systemctl start tufin-ps-web

2. Enable the PS cron job

   Edit the cron file

   [<ADMIN> ~]# crontab -e

   crontab -e

   Delete the # character from the beginning of the PS-scripts line

   # 1 * * * * cat /opt/tufin/securitysuite/ps/PS-Scripts

SSL Certificates

Secured connections to TOS Aurora require a valid SSL certificate. Such a certificate is generated during the installation. It is automatically renewed when it expires and also when upgrading to later versions of TOS Aurora. When connecting for the first time after certificate renewal, you will be prompted to accept the new certificate. You can also use your own CA signed certificate, but such certificates will not be renewed automatically.

SAN Certificates

If you have FortiManager devices in SecureTrack, add a SAN signed certificate to each device.

License Activation

Relevant only for central clusters, skip for remote collectors.

Follow the instructions in Activate license

Reactivate your license. In some cases, particularly when hardware is changed, license validity gets lost in the upgrade process. If activation is lost, this will not limit the functionality of TOS Aurora but future upgrades will not be possible until the license is reactivated.

• Check the status - go to Admin > Licenses. The License window appears.

• If the status shown in the window is anything other than Activated, follow the instructions in Activate License.

Restoring Tufin Extensions (formerly Tufin Marketplace) Applications and Data

If you had Tufin Extensions (formerly Tufin Marketplace) applications installed on TOS Classic:

1. Download the applications from the Tufin Marketplace.

2. Reinstall the applications.

3. For STRE, copy the backed up folder saved previously to /opt/tufin/data/volumes/ps/reportpack.

4. For other Tufin Extensions (formerly Tufin Marketplace) apps, follow the instructions for each app, as described in Prerequisites.

Using Syslog for Accountability and More

You can use syslog to send accountability and other information from your devices to SecureTrack - see Sending Additional Information via Syslog. If you want to use this feature and you have installed TOS on-premise, you must also set up a Syslog VIP Address.

Adding Worker Nodes to Your Cluster

TOS Aurora is now deployed as a single node Kubernetes cluster. See Multi-Node Cluster for more information about adding additional nodes.

Setting up External Backups

We recommend setting up backups on external storage.

Setting up Scheduled Backups

We recommend creating a backup policy as soon as possible.

DR (Disaster Recovery)

If you want to use the DR feature to setup TOS redundancy across sites, see Disaster Recovery.

TOS Monitoring

TOS Monitoring lets you monitor the status of the TOS cluster and its nodes by generating a notification whenever a change in status occurs, such as a node failing, or a usage threshold reached, such as CPU or disk usage. We recommend that you set up TOS notifications in TOS Monitoring (see TOS Monitoring).

Additional Configuration

A number of additional parameters can be set now or later e.g. session timeout and SNMP - see Configuring TOS.

SecureChange Settings

Relevant only for central clusters; skip for remote collectors.

If you have SecureChange:

1. If you are not already logged in to SecureTrack, log in now.

2. Create a new SecureTrack administrator user that SecureChange and SecureApp will use to get SecureTrack information. If you have already configured multi-domain management, make this user either a super administrator or multi-domain administrator, depending on whether you want to restrict the administrator to selected domains.

3. Sign into SecureTrack.

   • Using SSO: From R22-1, TOS uses Single Sign-On (SSO) authentication method by default.

     1. Log into TOS.

     2. For your first login session, you must change your password:

     3. You are automatically logged into SecureTrack. To log into SecureChange, type https://<IP>/securechangeworkflow or https://<IP>/tufinapps/securechange in the browser URL, where <IP> is the cluster VIP or external load-balancer IP.

   • Not using SSO:

     1. For your first login session, you must change your password. SecureChange users are separate from SecureTrack users; there is no connection between a SecureTrack user and SecureChange user with the same name.

     2. In this prompt window, you can also enter an email address for administrative email notifications. We recommend using the address of an email list so you can easily edit the list of recipients.

     3. Login to SecureChange at https://<IP>/securechangeworkflow or https://<IP>/tufinapps/securechange where <IP> is the cluster VIP or external load-balancer IP, with your admin credentials.

4. Go to Settings > Miscellaneous.

   

Enter a value for Server DNS name - the DNS server to use for links in email notifications. This can be an IP address in the format 11.22.33.44 or a FQDN in the format https://mydomain.com. The SecureChange DNS name is published by SecureChange so it can be accessed from external sources. For example, it is embedded in notification mails sent by SecureChange, which include a link to a ticket, such as an email notifying a handler assigned with a task, or informing a requester that the ticket has been successfully resolved.

5. Go to Settings > SecureTrack:

   

   1. Enter the SecureTrack administrator username, created previously.

   2. If you want a link from SecureChange to SecureTrack and from SecureTrack to SecureChange, select Show link to SecureTrack. These two links will appear in the applications icon menu in both systems:

      

      

   3. If you want to change how often SecureChange tests its connectivity to SecureTrack, change the value of Connection check interval.

   4. Click Test connection to verify that SecureChange has a connection to SecureTrack.

   5. Click Refresh license status so that SecureTrack and SecureChange share the highest level of connectivity.

   6. Click Save.

6. Additional setup can be done now or later:

   • Mail server connection
   • (optional) LDAP directory connection to use LDAP user accounts
   • Local users and user roles
   • Subsequent password changes can be made from the command line , see SecureChange Command Line Reference.