- Category: SecureTrack
When using one or more TOP Plugin other devices than fully supported devices can be monitored. Even if the documentation is very basic, some use cases are there.
Uninstalling a TOP Plugin using the "Red X" in Menu > Settings > Monitoring > TOP Plugins might not be possible in some versions.
If you run into this problem, do an upgrade to TOS R16.1 HF3. This version allows to uninstall a TOP Plugin (again).
- Category: Basics
For administration of Tufin SecureTrack and Tufin SecureChange you need at least one administrative account. This account must not be lost and the password must not be forgotten.
If it is forgotten, there is a way to reset the admin account if CLI access is possible as root.
SecureChange / SecureApp
Resetting the admin account here is quite easy. Just type
# scw help
scw: Usage: scw help|info|version|reset-admin
and you see the solution. Resetting the account by
# scw reset-admin
will deliver the password admin which needs to be changed at the next login.
The procedure shown for SecureChange doesn't work for SecureTrack. But there is a command that will allow you to define a new (administrative) user.
This command starts a routine to define a new user. You will be asked questions about username, password, Mail-Address and -configuration as well as real name adn date format.
After this procedure this user can be taken for a login and for modifying the "old" admin user. If needed, this new user can be deleted after having the password for the other admin account resetted.
- Category: SecureTrack
How to connect a Check Point Security Management Server (SMS, aka SmartCenter) R77.x to SecureTrack:
Prepare the Check Point SMS
It's recommended to define a Permission Profile for Tufin's access to the SMS and the logs. If there is only SecureTrack and no provisioning by SecureChange is wanted, a Read-Only Profile is sufficient. To define it, go in the SmartDashboard Menu to Manage > Permission Profiles and define a Read-Only profile.
Next, an object of the type Host Node is needed representing the System Tufin SecureTrack is running on. This is necessary because the IP address is needed later when the OPSEC Application is defined. To define it, go to Manage > Network Objects > New > Host Node.
To initiate the Secure Internal Communication (SIC), defining an OPSEC Application is necessary. To do so, open Manage > Servers and OPSEC Applications and define a new one. Necessary protocols are LEA (Log Export API) to have access to logs as well as CPMI (Check Point Management Interface) to have access to the objects and rules.
It's necessary to configure the permissions of Tufin SecureTrack within Check Point. For CPMI as well as for LEA the Permission Profile defined earlier should be selected. You are free to allow further access, but it's not necessary if the use of only SecureTrack is planned.
After these steps, the SIC should be initiated by setting an Activation Key. This is a One-Time Password for authenticating Tufin SecureTrack at the SMS. When this authentication is successful, a newly generated certificate is transferred to SecureTrack. From then on, authentication is based on this certificate. The communication is encrypted as it is between the Check Point components like e.g. SMS and Firewall Module.
When the password is typed twice, the button Initialize finishes this part of the configuration.
Please don't forget to make this newly generated certificate available by installing the Database. This is done by Menu > Policy > Install Database. If you forget to install the database on the SMS, the connection to SecureTrack won't work.
Prepare the Check Point Rulebase
If there is a Firewall between Tufin SecureTrack and Check Point SMS, a rule must allow the necessary access. Besides the access using LEA and CPMI furhter connections are needed, e.g. for Certificate Management:
Connection to SMS for authenticating using the one-time password and for retrieving the certificate
Connnection needed to access the CRL running on the SMS to check if the certificate presented by SMS is valid
Connection from SecureTrack to SMS / Logserver to retrieve log data (statistics) and Audit log data (recognition of actions done by administrators)
Connection from SecureTrack to SMS with a CPMI client to retrieve the latest revision
So a rule needs to be configured. This is necessary if any firewall is between SecureTrack and SMS. When a Check Point Firewall is in between, the rule could look like this:
Configure Check Point SMS in Tufin SecureTrack
The Check Point SMS needs to be defined in SecureTrack so the configuration can be monitored. To do so, some steps are necessary. First of all, connect with administrative rights to Tufin SecureTrack using a web browser using HTTPS (443/tcp). In the default configuration doesn't redirect a HTTP request from port 80/tcp to the correct port.
In the Menu go to Settings > Monitoring > Manage Devices. On the left pane all monitored devices are listed. On the right side a new device can be definded. Here, select Check Point SmartCenter.
After this selection a wizard starts, asking for several configuration options in five steps.
The Device Type can't be changed here since this option has been selected before. The other options are:
- Name for Display
Name shown in SecureTrack for this device
If SecureTrack is configured to use Domains, the corresponding Domain can be selected there. Please be aware that using this option clearly separates all data.
- Get revisions from <IP> or <Offline File>
If the SMS is monitored live, the IP Address of the SMS is provided here. If there is no direct access, configuration data can be imported. Please be aware that this option requires a license also - even if there is no monitoring of the changes.
- Usage Analysis
Here it's selected which data are collected. Esp. when "Rule and Object Usage" reports are required, the first two options need to be selected. Besides this, it's recommended to select the enablement of the Topology. In this case, all information that require Topology is available (e.g. Policy Analysis, Zones, Compliance Rules...).
The next step is to authenticate using the One-Time Password and to retrieve the certificate used from then on to authenticate.
It's necessary to provide the name of the OPSEC Application configured in Check Point SmartDashboard. The Activation Key is the One-Time Password provided during configuration in Check Point SMS.
In many cases the next windows can be kept using "default" for the OPSEC settings.
If there were changes configured in $CPDIR/conf/sic_policy.conf they can be considered here. It's all about authentication used for LEA and CPMI. All relevant Check Point options can be selected, so a successful authenticated connection from Tufin SecureTrack to Check Point SMS is possible.
In some cases the configuration for the timing of monitoring needs to be adjusted.
As in many cases, the default setting is useful when the global configured timing is sufficient.
Finally, the configured connection should be tested. If this is ok, the button Save finalizes the configuration.
Monitoring the Check Point SMS
The status of monitoring the SMS can be checked using Menu > Settings > Administration > Status. Depending on the connection and the load on the Check Point SMS the status will remain some time in "Starting" and "Yellow". When it has changed to "Green" the SMS is shown under Menu > Compare also in green and after a short time the first revision will show up.
- Category: SecureTrack
Let's imgine following situation:
Tufin SecureTrack is licensed for 2 Firewall Clusters which are centrally managed by one Check Point Security Management Server (resulting in a single SecureTrack ID).
Reports for e.g. Rule and Object Usage deliver results for one Firewall Cluster only. Reports on the second Cluster don't contain any data.
This behavior isn't as expected since it cannot be the connectivity between the Log Server and SecureTrack. Besides this, logs for this cluster are there and shown in the tools by Check Point. So Log data are there but SecureTrack doesn't deliver any report.
This behaviour can be reasoned by a missing license! In our case only one FW-license was attached to the Firewall Cluster, but not the second one. So the Firewall Cluster not delivering reports wasn't licensed full and therefore no reports were generated. After (re-)attaching the license reports deliver results for both Firewall Clusters - as expected.
- Category: Version update
Tufin delivers new versions quite often. If you are working with TOS and all your requirements are fulfilled - fine. But sometimes an upgrade is recommended, e.g. if there are new features you want or support is needed. It's quite sure that Tufin Support will recommend an upgrade if you have a problem with a version which is very old.
Upgrades can't always be done inplace. Esp. when upgrading TufinOS from version 1.x to 2.x a fresh install of the OS is needed.
We do upgrades mostly running in virtualized environments. Using Snapshots it's easy to restore the older version if something went wrong.
The upgrade path
Example: Starting with TufinOS 1.1x and TSS 6.1
To upgrade from version 6.x to R16-1 these steps are recommended
- Upgrade to version R12-6
- Upgrade to TufinOS 1.17 (if not done before)
- Upgrade to version R13-3 GA
- Upgrade to version R14-1 GA
- Upgrade to version R14-3 GA
- Install TufinOS 2.11 and R14-3 GA. Then migrate the configuration to this version using backup/restore.
If an upgrade of TufinOS isn't possible, upgrade to PSQL version 9.
- Upgrade to R15-1 GA
- Upgrade to TufinOS 1.21 - only needed if still TufinOS 1.x is used
- Upgrade to R15-3 GA (direct upgrade to R16-1 is possible)
- Upgrade to R15-4 GA
- Upgrade to R16-1 GA
This procedure has been proven and should work in many situations.
- Category: Uncategorised
Tufin has published their new User Center and Partner Center. A new design and a new structure of content gives an excellent overview and much information. Be sure to visit https://portal.tufin.com - a new password might be required.
A new information provided is e.g. Tufin Products Life Cycle Policy.
https://portal.tufin.com/aspx/ProductsLifeCyclePolicy (Authentication required)
Supported Versions including New Hotfix Support and Patches:
16-1, 15-4, 15-3, and 15-2
All other versions are EOL and don't get any more support
Supported Version including New Critical Security Updates Support:
2.11 and 1.21
All other versions are EOL and don't get any more support
Regarding Appliances: All current Appliances (T510, T1100, T1100XL) are fully supported. Older models as T80, T500, T1000, and T1000XL cannot be ordered any more. The five years of Advanced Replacement Program are guaranteed - but no extent for more years is possible.
Page 13 of 14