- Category: SecureTrack
When connecting a Check Point Security Management Server to SecureTrack, there are two possibilities to gather the topology:
Check Point Security Management Server only
In this case, Secure Internal Communication is set up to have a secure connection between the SecureTrack Server and the Check Point Management.
The Topology for SecureTrack is read from the Interface information defined in the Check Point Firewall and Cluster, respectively. Anti-Spoofing information is also read to get as much information as possible about the Topology.
Check Point OS Monitoring
In this case, the Topology is read from the monitored devices directly using SNMP. Other information isn't gathered - information from the object defined in the Security Mangagement Server is ignored.
If Check Point OS monitoring is activated and the SecureTrack Server has no possibility to read information using SNMP (161/udp), no information about the Topology is imported and therefore this device isn't shown in the SecureTrack Topology. Allowing SNMPv3 between the SecureTrack Server and the firewall device helps to avoit this potential problem.
- Category: SecureChange
If there is a distributed installation with a SecureTrack Server and a SecureChange Server, communication is needed between these two servers.
Necessary communication: HTTPS (443/tcp) in both directions.
SecureChange Server needs information from SecureTrack, e.g. about Topology and Rule Bases of the firewalls. The SecureChange Designer needs also the opposite direction connecting from the SecureTrack Server to the SecureChange Server. If this doesn't work, the designer will result in an error.
To configure the SecureTrack Server in SecureChange, go to Menu > Settings > SecureTrack
To configure the name of the SecureChange Server used e.g. in E-Mails, select Menu > Settings > Miscellaneous
The name or IP address listed here represents the SecureChange Server and will also be used for the communication between SecureTrack and SecureChange. If a wrong name or IP address is configured here, SecureTrack won't be able to communicate with SecureChange since only this name/address will be contacted from SecureTrack.
For sure, the name needs to be resolvable for users too, since they will find this name in their E-Mail regarding e.g. a new task.
- Category: TufinOS
Please update your TufinOS
Google Security has found a vulnerability in glibc, a commonly used library:
A remote attacker could create a specially crafted DNS response which could cause libresolv to crash or, potentially, execute code with the permissions of the user running the library.
Tufin points out, that a patch is needed for TufinOS 2.10:
- TufinOS 1.x isn't vulnerable
- TufinOS 2.x is vulnerablle
Tufin has published a patch for TufinOS 2.10:
Please install this patch. If necessary, carry out an update before so the patch can be installed.
- Category: Admin Management
Welcome to blog.tufin.club
We are glad that you found this blog about solutions by Tufin Technologies. Their product is the Tufin Orchestration Suite which consists currently of the parts SecureTrack, SecureChange, and SecureApp.
This blog is operated by AERAsec Network Services and Security GmbH in Hohenbrunn/Germany. AERAsec is Gold Partner of Tufin and also selling all Tufin Solutions. Besides sales, AERAsec also delivers support for all Tufin Solutions even if direct support is provided by Tufin Technologies. Esp. german speaking customers often like first and second level support in German.
The main author of this blog is Matthias Leu. He started with Tufin products in 2006 and is the only german speaking "official" TCSE Trainer.
Please feel free to contact AERAsec by E-Mail via info at aerasec.de
Page 11 of 11