www.tufin.club
How to remove EOL message in SecureTrack
- Details
- Category: SecureTrack
If you use Tufin TOS Classic R21-3 you surely have seen the EOL message on the login screen.
There might be one or another situation not allowing this message, e.g. if auditors complain about why this message is shown (and you currently cannot upgrade to TOS Aurora because SecureTrack and SecureChange need to run on different systems due to security reasons).
It is possible to remove this EOL message by a script. Just go to the CLI and call this script with root permissions:
[root]# /opt/tufin/securitysuite/scripts/eol_message_disable.sh
From then on, this message isn't shown anymore.
But - please don't forget that TOS Classic still has its EOL at the end of the year 2022 (!)
If you need this message to be shown again, access to the database is necessary. As always, never ever do anything with the database without a current backup!
To turn the message on again, issue this command to alter the field within the corresponding table:
[root]# psql -Upostgres keycloak-db -c "update custom_properties set value='false' where id='eol_message_disabled'"
(this command needs to be typed using one line only)
After having issued this command, the EOL message is turned on again.
How to determine the Management ID in SecureTrack
- Details
- Category: SecureTrack
Before doing anything with a device, e.g. adding an Interface or restarting the device via CLI, it is necessary to know the SecureTrack Management ID of the device.
If this device is a simple unmanaged Firewall, finding the Management ID is quite easy by navigating to the Device List shown in Menu > Compare (in TOS Aurora: Menu > Reports > Compare Revisions).
A click into this list on the left side and pressing "t" shows the number.
When having a Firewall Management (e.g. Check Point, FortiManager, Panorama...) this list shows the Management only, not the relevant Firewalls.
In this case, the information can be retrieved by going to Menu > Settings > Administration > Licenses (in TOS Aurora: Menu > Settings > Licenses). Scrolling down to the window "Devices", click into the field, and pressing "t" delivers the Management ID of the firewall itself.
In this example, the Management has the ID 285 and the Firewalls have 286 and 287, respectively.
Generic Routes to improve SecureTrack Topology
- Details
- Category: SecureTrack
Building the SecureTrack Topology (Interactive Map) so it represents the network reality sometimes is a challenge.
Some improvements can be done manually, e.g. to define a Generic Device. There might be situations, SecureTrack doesn't recognize all routes configured on a monitored device. In this case, one or more routes need to be added manually to SecureTrack Topology by defining Generic Routes.
Today's versions allow to add them in the Interactive Map directly, but also using the CLI is a way to configure Generic Routes. Once integrated into SecureTrack, Generic Routes will be persistent until they are removed manually. So let's have a look at
- Configuration of Generic Routes in the Interactive Map
- Configuration of Generic Routes using the CLI
- Listing and removing Generic Routes from Topology
Configuration of Generic Routes using the Interactive Map
Using one of the recent versions of SecureTrack, a Generic Route can be added directly in the Interactive Map.
To do so, login to SecureTrack with administrative rights and go to
Menu > Network > Interactive Map (TOS Aurora: Menu > Map)
Then, find the device you want to provide with an additional, generic route. In this example, the Check Point Firewall will get an additional route. To show all routes stored in SecureTrack for this device, right-click and select "show routes".
A new window opens, showing all routes configured for this device.
To add a route, click on the "+" at the top right corner. A new window opens that allows defining a new (generic) route. Here information needs to be provided:
- Destination
IP-Address and Prefix - Interface
optional - Virtual R&F
optional - Next Hop Type
IP or VR - Next Hop
e.g. IP address of the next hop / router
By pressing "Add" the configuration is taken into the window shown below.
In this phase, the route can be deleted by clicking on the dustbin on the right side. The configuration is finished by pressing "Save".
The newly configured route is shown and active in the interactive map after synchronizing the Topology
Please be aware that this Generic Route cannot be deleted via WebUI. To delete a Generic Route access to the CLI is necessary, shown here.
Configuration of Generic Routes using the CLI
(TOS Classic only)
Some administrators prefer using the CLI. If an elder version of SecureTrack is used, the configuration of Generic Routes is possible using the CLI only.
Doing so, the Management ID of the device needs to be known (also called Device ID).
To configure it, a CSV file needs to be prepared. It has to have the following content:
- Destination
IP-Address - Mask
Dotted decimal subnet mask - Interface
name of the Interface to be used - Next Hop
IP address of the next hop / router - Next Hop Type
IP or VR - VRF
optional
Here is an example of the content:
# cat /home/tufin-admin/route.csv
10.1.2.0,255.255.255.0,eth1,10.1.1.254,IP,
10.1.3.0,255.255.255.0,eth1,10.1.1.254,IP,
It needs to be considered that the number of fields needs to be always the same. So if a VRF isn't configured, the "," still needs to be in the file.
Besides this, it needs to be known that an import of the file replaces all Generic Routes configured before. So each Generic Route that needs to be configured on the device needs to be included in this file.
The next step is to import the file. This is done by the commands
- cd /usr/local/st
- ./topology_generic_routes -m <DeviceID> -i <file.csv>, e.g.
./topology_generic_routes -m 286 -i /home/tufin-admin/routes.csv
The next step is to synchronize SecureTrack Topology. This can be done using the WebUI (see above) or via CLI by the commands
- cd /usr/local/st
- ./topology_graph_builder
After this procedure, the content of the CSV files is shown in the Topology.
Listing and removing Generic Routes from Topology
(TOS Classic only)
If one or more Generic Routes are configured, they can be displayed in the WebUI - but there is no option to remove or alter these routes. To do so, using the CLI is necessary. One option is to use "regular commands", the other is to "hack the database". The second option is not really recommended by Tufin.
To check Generic Routes the easiest way is to check the routing table of the device in the Interactive Map. Here it needs to be considered that there is no difference shown between a regular and a generic route. Checking the Generic Routes via CLI requires knowing the Management ID of the device (the example below refers to 286 and the configuration above).
It is a command to query the database of SecureTrack:
# psql -Upostgres securetrack -c "select * from topology_generic_routes where mgmt_id='286'"
id | mgmt_id | destination | mask | interface_name | next_hop | next_hop_type | vrf
----+---------+-------------+---------------+----------------+------------+---------------+-----
26 | 286 | 10.1.2.0 | 255.255.255.0 | eth1 | 10.1.1.254 | IP |
27 | 286 | 10.1.3.0 | 255.255.255.0 | eth1 | 10.1.1.254 | IP |
(2 rows)
The output shows two Generic Routes that have been added to the device with Management ID 286.
If one or more Generic Routes need to be removed from SecureTrack Topology, this should be done with a CSV file as shown above. An import of a CSV file with Generic Routes always replaces all of them. So if an empty file is imported, all Generic Routes are removed after Topology Sync.
Tufin Orchestration Suite 21-3
- Details
- Category: Version update
Tufin has released TOS R21-3, the third and final version of the Tufin Orchestration Suite of 2021.
TOS 21-3 is available as GA and can be downloaded from the Tufin Portal (login required) in its variants for TOS Classic and TOS Aurora.
TOS 21-3 is the last version for TOS Classic. It will be supported until the end of 2022.
This version delivers improvements, e.g.
Change Automation and Orchestration
- Enhancements for Access Decommission
This is supported now for Check Point R80 and Panorama.
A new tab "Manage Related Rules" has been introduced
as well as the option to disable and not only to remove rules. - Enhancements for Server Decommission and Server Cloning
Decommission of subnets as well as IP address ranges is possible now.
Cloning allows this kind of network objects also, including a move e.g. from a subnet to a host
Application Driven Automation
- SecureApp supports now User Identity
- Application Identity is shown in Connection Status
Devices and Platforms
- Microsoft Azure
New supported management and firewall devices in Microsoft Azure:- Check Point CloudGuard Multi-Domain Server, Check Point Security Management, Check Point Gateway
- Palo Alto Panorama and PanOS
- Fortinet FortiManager and FortiGate
- Fortinet
FortiManager with Central NAT policies is supported by SecureTrack now - Intelligent Provisioning
for Check Point R80 and Juniper SRX - New versions supported:
- Cisco ACI 5.1
- Cisco FMC 6.7
- VMWare NSX-V 6.4.9
- Forcepoint SMC 6.9 with API 6.8
- Fortinet FortiManager 6.4.6
REST API
- SecureTrack
- Microsoft Azure Resouces can be imported
- Support of "get license status"
- SecureChange
- Auditing of some actions is possible, e.g. LDAP or RADIUS server changes as well as changes in roles
- Output of a list of active workflows, including name, description, and type
Further improvements, as well as corrections, are included.
The latest version of the Tufin Orchestration Suite can be found at the Tufin Portal: https://portal.tufin.com
TufinOS 3.81 available
- Details
- Category: TufinOS
Tufin has published TufinOS 3.81. An upgrade to this version is recommended since it fixes a potential vulnerability (authentication required) in NSS during certificate verification.
When upgrading please consider the supported upgrade path as well as the minimum requirements regarding the TOS version.
Vulnerabilities in Apache Log4J
- Details
- Category: Basics
After the first vulnerability in Apache Log4j has been found and is discussed on the Internet, some more have been identified. All together, until now three vulnerabilities have been found. They are described in CVE-2021-44288 (resolved in Log4j 2.15), CVE-2021-45046 (resolved in Log4j 2.16), and CVE-2021-45105 (resolved in Log4j 2.17).
Tufin has checked whether Tufin Orchestration Suite is vulnerable or not.
The latest status can be found here: https://forum.tufin.com/support/kc/latest/Content/Suite/CVE-2021-44228.htm?cshid=CVE-2021-44228.
Some official patches are available, i.e. for RTOS 19.3 and above. If you are currently using R19-2 or earlier, please upgrade to a supported version of TOS.
It is recommended to check the latest status (Tufin Portal > Security Advisories) and to subscribe to Tufin's mailing list.
Please check also the Tufin Portal also for additional information.
Page 5 of 22