Important Installation Information

Integrity Checks

Each TOS version comes encrypted with two SHA values. You can verify the integrity of the TOS installation package by running an integrity check before you install it on your servers. If the output is identical to the SHA values for the relevant TOS version, you can safely install the TOS package.

To verify the integrity, run the following commands:

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

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

R23-2 PHF3.2.0

R23-2 PHF3.0.0

R23-2 PHF2.0.0

R23-2 PHF1.0.0

R23-2 PGA.1.0

R23-2 PRC1.0.0

Before Installing or Upgrading

• After installing or upgrading R23-2, license usage data will be automatically collected from TOS. All TOS users will need to be able to access aus.tufin.com from the browsers on their work stations. For more information, see Send Reports Automatically.

• From R22-2 PHF2.0.0, we require that the /opt partition storage usage not exceed 70% of the available space to ensure proper TOS functionality.

• From R22-2, we improved several backup components. Backups will take longer to complete, but will be compressed and more reliable.

• After upgrading to R23-1 PRC1.0.0, you are going to have to regenerate the client certificates for any OPM device connected to TOS.

• When installing or upgrading to R23-1, all SNMP inbound queries (such as walk, get, and getNext) will be disabled by default.

  To enable SNMP v2 walk and get queries, after the installation/upgrade, run the following CLI command on the initial data node as a user with root privileges.

  tos config set -p snmp.inboundMonitoringEnabled=true -s monitor-tower

  tos config set -p snmp.inboundMonitoringEnabled=true -s monitor-tower

• If you have FortiManager devices in SecureTrack, after upgrading you are going to need to add a SAN signed certificate to each device

• If you are upgrading from R21-3 or R21-2, after the upgrade, the legacy license enforcement accuracy of management devices (such as Panorama and FortiManager) will be improved: the license status of the management devices is going to be determined according to the accumulated license statuses of their managed firewalls. As a result, if there is at least one managed firewall with the license status Expired or Unlicensed, the management device will also have the license status Expired or Unlicensed.

  To resolve this, you can:

  • Ensure that a valid license is attached to all managed firewalls.

  • Disable the unlicensed firewalls

  • Remove the unlicensed firewalls from SecureTrack monitoring.

  This does not apply to Check Point Management Devices.

Additional Information

• Starting from R23-1 PHF1.0.0, ICMP is considered both a service and an application when creating or editing the security policy of a USP zone. To differentiate:

  • ICMP = application

  • ICMP-proto = service

  This is also true when defining a specific service. For example: ICMP-proto 8.

  As a result, when importing old USP CSV files to R23-1 PHF1.0.0 and later, ICMP will be considered an application and not a service. For ICMP to be considered a service, you are going to need to change it to ICMP-proto.

• Starting from R22-2 PHF2.0.0, the Tufin Marketplace has been renamed Tufin extensions.

• Starting from R22-1 PHF2.0.0, for Cisco ASA devices, in order to prevent unnecessary ticket dependencies, Designer creates groups using the timestamp as the suffix of the group name. For example:

  • NetworkGroup_1657713531

If you want to change back to the previous naming convention, in stconf set the Designer_ASA_Index_Group_Name flag as True.

For more information, see Changing The Naming Convention of Cisco ASA Group Names Created by Designer

• Tufin Orchestration Suite enforces maximum session duration settings for SecureTrack and SecureChange, including for the REST APIs.

• To ensure that SecureChange and SecureApp have full functionality, the dedicated account used to define integration with SecureTrack (SecureChange/SecureApp > Settings > General > SecureTrack) should have Super Admin permissions configured in SecureTrack.

• For Check Point R80 devices, a new revision is automatically retrieved when you upgrade, and therefore Compare Revisions may show changes for all the existing network objects.

  Before you upgrade, make sure you have a recent (from ≤ 3 months) Check Point Jumbo Hotfix version installed on your device. See the relevant Check Point Support Center article for more information on how to verify which Jumbo Hotfix version is installed.

• SAML Login Authentication and Google Chrome browsers: Google recently introduced a change to their SameSite cookie policy that enhances browser security. As a result of this change, users will be unable to log in to SecureTrack using SAML authentication on old browsers. SAML authentication is supported only for browser versions starting from:

  • Chrome: versions 79 and 80.

  • Firefox: version 72

  We strongly recommend upgrading the browsers to these versions. For more information on the SameSite cookie policy change, see the following posts:

  • Ultimate Security Professional Blog: SameSite cookies - Everything You Need to Know

  • Medium: Why you need to care about Google’s change to the SameSite cookie attribute