www.tufin.club

The message "checker failure" might occur when checking the status of the Tufin Orchestration Suite. 

When looking at Tufin's knowledge base, this message is mentioned as "known bug" that is fixed in R24-1 PHF4.1.0 and R24-2 PHF1.0.0, respectively. If you cannot upgrade or get still the message, this procedure might help: 

• Find as root the pod that is responsible for this message by using the command
  # kubectl get pods -owide | grep node-exporter
  tos-prometheus-node-exporter-zddqg                    2/2     Running     0 …
  
  
• Check this pod, e.g. if it's running (can be skipped)
  # kubectl describe pod tos-prometheus-node-exporter-zddqg
  ...
• Restarting the pod helps to return to a normal status
  # kubectl delete pod tos-prometheus-node-exporter-zddqg

You can check the status of this pod by using the first command shown above. Please give the pod to start (and to show a status "ok") about two minutes. Checking "tos status" before will still deliver "checker failure" because the pod is still not running well. 

Tufin has released TOS R24-2, the second version of the Tufin Orchestration Suite of 2024. 
TOS R24-2 is available as GA and can be downloaded from the Tufin Portal (authentication required).
Some improvements of TOS R24-2:

Deployment

• Upgrade
  The upgrade process has been optimized and is shown in a more transparent way. This increases visibility and helps troubleshooting during upgrades.

Change Monitoring, Automation, and Orchestration

• SecureChange
  SLA can be set for tickets. Starting with this version, business hours and non-working days can be considered by configuration.
• SecureChange
  The page showing the tickets has been improved esp. regarding search tickets and manage saved queries. 
  
  
• SecureTrack
  OPM devices are integrated better now. Supported is e.g. automatic mapping of zones to interfaces, matching rules in the Topology Map, etc. So they are also found by SecureChange as possible installation targets.
• SecureTrack
  The Topology Map now supports both IPv4 and IPv6 routes. So it can be used in mixed environments also.
• SecureTrack
  The Device Viewer includes the feature "Revision History" for all devices now. This is useful esp. for GCP, Cisco Meraki and OPM devices because they don't have the option for comparing revisions.

Devices and Platforms

• Azure NSG
  SecureChange Designer now provides suggested changes for access across Azure NSGs and Azure firewall devices. 
• Azure NSG
  SecureTrack Rule Viewer can interpret the configuration of NSGs, so e.g. "cleanup" as well as "unused objects" can be used.
• Azure Firewall
  Azure firewalls in a Virtual WAN- Secured Hub deployment when routing is configured in the Azure Hub are supported. So based on the Topology, also USP violations as well as Designer / Verifier are supported. 
  
  
• Cisco
  For Cisco FMC devices generic NAT is supported, so it can be used in Topology.
  
  
• Fortinet
  UserID Automation for FortiManager is supported now, delivering improved visibility for the LDAP groups that are part of the User Groups and FSSO objects. This includes topology support as well as automation tools of SecureChange.
• Fortinet
  For path analysis FQDN objects or DNS can be used.
• Fortinet
  The support of enhanced VPN across Fortinet devices is improved (Dial-Up/dynamic VPN). The modelling of SD-WAN is improved.
  
  
• Google
  GCP VPC firewalls can be used in Access Request workflows, they are automatically recognized based on information from the Topology. So also the Verifier can be used for these devices.
  
  
• VMware
  NSX-T is supported by the Rule Viewer, last hit information for NSX-T Distributed firewall rules is available now.
• VMware
  NSX-T VRFs can be imported as logical routers and be used in Topology.
• VMware
  IPv6 is now supported for VMware NSX-T in the Interactive Map: Interfaces and Routes. So in SecureChange Designer, Provisioning and Verifier are supported.

Further improvements, as well as corrections, are included in R24-2.
The latest version of the Tufin Orchestration Suite can be found at the Tufin Portal: https://portal.tufin.com

In earlier times, when using TufinOS 3.x (based on CentOS) it has been possible to check which ciphers are going to be used in SSL and TLS, respectivly. After upgrading to TufinOS 4.x (based on Rocky Linux) this is no more possible. 

Tufin Support states that this is "as designed" and "it's secure": 

Tufin routinely carries security tests for each supported version. If an issue is detected by public commercial tools or with customized penetration testing - it is handled immediately. As far as we can tell, based on tests by Tufin and many of our customers, there are no vulnerable ciphers loaded and available to use in TOS. 

When having users on a TufinOS, each user has an ID that can be checked in /etc/passwd, e.g.

# cat /etc/passwd | grep tufin-admin
tufin-admin:x:1000:1000::/home/tufin-admin:/bin/bash
#

If a user is added, ID1001 might be the ID for this new user. 
Checking system activity (e.g. with ps aux) might show this user quite active, even if not logged in. 

The reason for this effect is that TOS is running some processes with ID1001 - independently of "real usage" of this ID in /etc/passwd or not.
Processes using this ID are e.g. Java, MongoDB, Kafka, ... 

So don't wonder about users not logged in to CLI but using some resources, it's not an attack, but TOS working as designed by Tufin.

Just a short reminder

As known by the most, TufinOS 4.x is available and should be deployed. Since July, 1st, TufinOS 3.x is no more supported since it's based on CentOS 7 which has been depreciated. So for this Linux, no more development or even security patches are available.

There are different ways to upgrade from TufinOS 3.x to TufinOS 4.x. All of them are documented in the Tufin Portal (authentication required)

• Upgrade of VMWare ESXi
• Upgrade of Tufin Appliances

Please be aware that a backup is required before upgrading. Additionally, TufinOS 4.x is based on Rocky Linux, so some configuration details are different to TufinOS 3.x