TCSE Fundamentals R19-1 Exercise Book
TCSE Fundamentals R19-1 Exercise Book
Preface .......................................................................................................... 3
Chapter 1: Visibility and Monitoring .......................................................... 4
Exercise 1: Getting to know Tufin’s virtual lab................................................................................ 5
Exercise 2: Logging into SecureTrack ........................................................................................... 7
Exercise 3: Configuring Personal Settings ................................................................................... 10
Exercise 4: Adding Users and Administrators .............................................................................. 11
Exercise 5: Adding a New Device ................................................................................................ 14
Exercise 6: Device Groups........................................................................................................... 18
Exercise 7: Filtering Revisions ..................................................................................................... 20
Exercise 8: Viewing and Comparing Policy Revisions ................................................................. 21
Exercise 9: Comparing Cloud Policy Revisions ........................................................................... 23
Exercise 10: Using Tufin’s Interactive Map .................................................................................. 24
Preface
Welcome to the Tufin Certified Security Expert (TCSE) Fundamentals course. This course guide
contains exercises geared to your personal environment in the Tufin Training Lab.
Thank you for your interest in the Tufin Orchestration Suite (TOS). Tufin uses a policy-based
approach to identify, orchestrate and automate changes to some of the largest, most complex
networks in the world. Tufin does this in m inutes instead of days, all from a single pane-of-glass.
Multi-Domain management
Policy Browser
Policy optimization
Cleanup measures
Network Mapping
Access Requests
Rule Recertification
Rule Decommission
Server Decommission
For full Tufin Orchestration Suite documentation, visit Tufin’s knowledge center at:
https://forum.tufin.com/support/kc/latest/
Connecting to Tufin:
There are two options to connect to the Tufin Training Lab
• Option 1: Register for a virtual lab, found at the bottom of the course page within Tufin Academy
(https://portal.tufin.com/aspx/TrainingHome).
• Option 2 (for classroom courses): Login via the email link received from your instructor.
In this exercise, we will verify the Tufin Orchestration suite version and then log into SecureTrack.
1) Either use the built-in console or login using an SSH client, such as MobaXterm or Putty.
Built-in console
SSH Client
Copy/Paste External Address found under the Tufin VM into your client
Type the following credentials to log in: username: tcse, password: tufin123
Type [tcse@TufinOS ~]$ sudo tos ver to verify which version of TOS is installed on your
virtual machine.
2) Complete the information below:
Tufin Orchestration Suite Version: ____________
Build: __________
TufinOS Release: __________
TufinOS Build: _____________
3) To log into the Tufin web interface, click on the Tufin UI tab.
5) Go to Settings > Administration > Licenses, check license status and expiry date.
Note: If needed, please download the Tufin Evaluation License from the TCSE Courses Menu
located on the left of the Tufin Academy screen (https://portal.tufin.com/aspx/TrainingHome).
In this exercise, we will explore the steps required to define personal user settings.
Go to Settings > My Settings, configure the settings as shown in the image below
Verify the following settings:
Set the Start Page to Compare
Show modified objects only
Default Graphical View
Recent Revisions Timeframe value: Custom and 1000000 hours (one million)
Save the configuration
In this exercise, we will add users and administrators to SecureTrack and discover what each user
type is permitted to do.
1) Go to Settings > Configuration > Users:
3) Click Save.
4) Click +New to add new users, with the following credentials, using tufin123 for the local
authentication password. There is no need to configure a TACACS+ server, in this training
environment.
Note: Usernames are case sensitive – Please enter usernames exactly as written below
a) Make sure that Sarah.Jones’s user’s permissions are limited to viewing only the Palo
Alto devices under the HQ- California domain.
5) To change users, click on user’s icon and then select Log out
User view
Note that according to the user settings (you defined as Admin), you can only see Palo Alto devices.
In this exercise we will add a new device to be monitored. The device is a Check Point Security
Management Server VM.
1) Login to SecureTrack as: John.Smith
2) Go to Settings > Monitoring > Manage Devices.
3) Under Start monitoring a new device, select Checkpoint > SmartCenter.
Note: Usage Analysis traffic collection and Topology are enabled by default.
5) Click Next.
8) Click Next.
a) Click Custom to review the available SIC authentication combinations, before clicking NEXT.
9) Click Next.
10) Enter the following Management API connection details:
User Name: api
Password: tufin123
In this exercise, we will create a new device group and add devices to the group.
Later, we will examine the differences between a Group’s Risk Score and Overall Score.
4) For the name of the group, enter TCSE and click Save.
5) In the group tree on the left, select the TCSE group and add the RTR1 and RTR2 devices.
6) Click Save.
Note: Make sure ONLY the newly added TCSE group is selected in the device tree. You can use
the search engine (magnifying glass) to look up the required devices.
Tip: When you create device groups, the groups are shown in the device tree for the Dashboard and
the Risk, Cleanup and Change browsers
In this exercise, we will filter the revision list to view only revisions installed by a specific administrator.
1) In Compare view, select the CMA-R80 device.
In the middle strip, click Filter.
By Show revisions in this time frame, select Show All.
Configure the filter to show Installed Policy events by administrator aa
2) Click Apply filter.
In this exercise, we will view & compare two policy revisions on the SMC-Docklands and Palo Alto
devices. We will also create and review a Comparison Report.
7) In Compare view, select the R80-Training device.
8) In the Revision history pane (right hand side), select a revision.
9) In the middle strip, click View Policy
10) Mouse-over the group object below and review the tooltip:
11) Click one of the object groups and review its content in the newly opened window. Then close the
window.
12) Export the policy to PDF and save it to your Desktop:
13) In the Revision table, select CMA-R80 device revisions #18 and #20, and, in the middle strip,
click Compare.
Tip: Show all revisions.
14) In the Objects tab, review the changes made to the network objects.
In this exercise, we will examine how devices are monitored in the cloud.
3) Click on Generate Report, compare your findings with your previous answer.
4) Select the OpenStack Data Center Migration device and click View Policy.
5) Select the NSX device, select a revision and click on View Policy.
6) Select the NSX-Distributed Firewall device, show revisions and click Compare.
Tip: Selecting compare, will automatically select the last two revisions.
5) Search for the R80-Training device using the search function (top right of screen).
6) Enter the details of the device interfaces. Right-click on the device and select Show interfaces.
11) Right-click the R80-Training device and select Show matching rules:
In this exercise, we will import USP Zones using a CSV file (TCSE Zones.csv) prepared in advance.
Note: Please download the TCSE Materials zip file, found within the 'File repository area' at the
bottom right of the Tufin Academy course page.
4. Select TCSE Zones.csv file (downloaded in the previous exercise) and click OK to import.
5. To view the zones subnet details, tick the relevant zones checkboxes from the ‘Zone List’ on the
left. Make sure ‘Include subnets of child zones’ is checked.
Tufin’s Unified Security Policy™ allows you defining the controls to govern the traffic between the
security zones of your environment that you defined in Network > Zones (previous step).
The controls can define:
In this exercise, we will prepare the USP Matrix CSV file (TCSE Compliance Policy.csv) for import.
The policy will allow only tcp 587 access from the PCI Data zone to the Hosting zone.
Note: The TCSE Compliance Policy.csv file can be found within the TCSE Materials zip file, found
within the 'File repository area' at the bottom right of the Tufin Academy course page.
4. Click Save.
5. Click on the name of the new policy to enter it and press the Import button on the right corner of
the screen
6. Select the TCSE Compliance Policy.csv file (downloaded in the previous exercise) and click OK
to import.
Instead of waiting for a new revision, we will sync the topology. Go to Network > Interactive Map,
click Synchronize (top right of screen) to sync topology
Tip: This maps the device interfaces to the SecureTrack Zones imported.
Let’s view the results in the Policy Browser
1) Go to Home > Policy Browser
2) Create a Search for violations: TCSE USP
Tip: One option at this stage, would be to update the firewall policy, so that it is in compliant with the
USP e.g. allow HTTPS traffic on rule #7.
Another option is to create an USP exception, to allow only https traffic.
Example: Posting the ‘Create an exception’ REST API, would have the following effect:
USP Exceptions definition
We are now going to identify permissive rules that need to be replaced with less permissive rules
1) Go to Home > Policy Browser
2) Search for Permissiveness Level: High
3) Select the CMA-R80 device and view the highly permissive rules
4) Select the Rule #6 and click Edit Metadata in the top right corner of the window.
Tip: User metadata can be added to each rule in the most recent policy revision for each device.
Tip: Through the Policy Browser you can also run a search on any metadata added, for example all
rules that have Legacy rule checked
Click Next (lower right corner of screen) to proceed to New job stage 2
In New job stage 2 window you can select the log source to perform the APG analysis.
File - Analysis is based on Syslog file collected in the past (hit the Browse button to upload)
Device - Analysis is based on a log file according to selected duration (in the following example below,
we have prepared a Syslog file due to time constraints)
9) Type a job name
10) Set the Log source to File
11) Browse to the Checkpoint.apg file located in the TCSE Materials folder.
12) Click Save (lower right corner of screen) to continue.
You will be directed to the main screen where you can view the job list.
14) Click on the graph points and observe how the permissiveness & number of rules are changing
accordingly.
Your objective is to find a point of low permissiveness with a reasonable number of rules.
In our example, we selected a point which yields permissiveness level of 42 achieved with 45
rules. This new rule base will replace Rule #6 with permissiveness level of 42.
15) Click OK once you are satisfied with the point selection.
The following table represents the generated rules which will replace the original rule:
• The grey-out rules represent the original permissive rules
• The black-text rules represent the newly generated rules by the APG.
By expanding (+) or collapsing (-) rule sets, the permissiveness level will adopt automatically
A few guidelines:
• Aim to a low permissiveness value
• When expanding a rule, it becomes grey and new strict rules show up
• A rule with one source host, one destination host and one service has the smallest value of 1
• A rule with Source ANY, Destination ANY and Protocol ANY has the highest value of 100
Tip: You can always go back to the Balance Graph to set the desired permissiveness using the
points on the graph:
13) If you made any changes and are satisfied with the results, click on Save Rule Set.
We are now going to complete the flow by creating a SecureChange Access request to implement the
new rules in the firewall.
CSV Administration
The APG CSV file needs to be formatted in a format accepted by SecureChange. To do the format, all
wording and the Name, Port, Hits and Permissive columns need to be removed and an action column
i.e. ‘accept’ column needs to be added along with TCP and UDP ports, according to service type.
The below screenshot is taken from the Secure Change Access Request, Advanced options dialog
and explains how to format the APG CSV file to a format accepted by SecureChange.
1) In this exercise, we will use the prepared SecureChange APG Format.csv file TCSE Materials
folder.
Before After
4) Click Create.
5) Click on Advanced Options.
6) Select Paste from Excel and paste the formatted excel into the window:
As we do not have this particular Checkpoint device in the lab, we will conclude the exercise here.
We can see that there are three objects for same IP.
4) Now go to Analyze > Object Lookup
5) Search by Text, IP, 192.168.3.105
In our case, we can see a naming convention was implemented, but the two objects below were not
deleted, resulting in a bloated and inefficient firewall policy.
Create a Rule Decommission workflow, to disable or delete rules, which are no longer required.
Select rules for decommission, add these rules to the workflow created and provision changes.
The workflow should be based on a template and contain the following steps:
Rules to Remove/Disable => Business Approval => Technical Design and Implementation
Good Luck!
3) Verify that John Smith has the necessary permissions to create a change requests -
requestor Role and Create change requests and view ‘My Requests’ tab Permissions
Note: When selecting a rule in the Policy Browser, the following perquisites are needed, in order for
the ‘Add to ticket’ button to be active:
3) Click OK.
1) In Step#1 Properties tab, make sure the step name is: Rules to Disable/Remove
2) In the Fields tab, add the Rule Decommission field with the following:
3) Click OK
4) Add a text area field named Business Justification in the opening step.
6) Click Save
3) Add an Approve / Reject field and name it: Rule Decommission Approval
5) Click Save
1) Create a third and final step and name it: Design and Implementation
2) In the Fields tab, add the Rule Decommission field and select the Designer (Allow all) and
Verifier tools.
5) Click Save.
Note: If you were logged in to SecureTrack, when creating the Rule Decommission workflow, you
will have to logout and login again, to refresh SecureTrack with the new workflow created.
2) In the Policy Browser, search all devices for rules with a last hit of greater than 180 days.
4) Add this rule to a ticket, by clicking on the Add to ticket button at the top right of the screen.
5) Click on the eye icon at the top right of the screen, to view selected rules
3) Click Submit
1) Go to Tasks tab
4) Click Done
5) Select the pending task once more. You should now be in Step#3
6) Accept the task and click on Designer to see the recommended changes.
9) Click Continue.
NOTE: You might have to wait a few minutes for the policy to save on the firewall
10) Close the Designer window and click on Verifier to verify the change was successfully
implemented i.e. disabled.
In SecureTrack, open the Policy Browser and view the disabled rule and its associated ticket.
You have successfully disabled a rule using the Rule Decommission workflow!
Create a Rule Recertification workflow, to recertify rules or flag them for decommission.
Select rules for recertification/decertification, add these rules to the workflow created and provision
changes.
Good Luck!
Prerequisites
4) Click OK.
1) In Step#1 Properties tab, make sure the step name is: Rules to Recertify/Decertify
2) In the Fields tab, add the Rule Recertification field with the following:
3) Click OK
5) Click Save
3) Add an Approve / Reject field and name it: Rule Decommission Approval
5) Click Save
1) Create a third and final step and name it: Rule Recertification
2) In the Fields tab, add the Rule Recertification field and select the Update Metadata option.
Deselect the Read-only option.
3) Click Save
Note: If you were logged in to SecureTrack, when creating the Rule Recertification workflow, you
will have to logout and login again, to refresh SecureTrack with the new workflow created.
3) In the Policy Browser, search all devices for rules that are not certified (have no certification
date)
5) Add these rules to a ticket, by clicking on the Add to ticket button at the top right of the screen
6) Click on the eye icon at the top right of the screen, to view selected rules
2) Click Submit
1) Go to Tasks tab
3) Accept the handling the task step and approve recertifying the rule
a. Provide a reason
4) Click Done
5) Select the pending task once more. You should now be in Step#3
6) Accept the task, select Rule 2 and Rule 9 and certify them for 180 days.
7) Click OK
9) Click OK
You have successfully recertified and decertified rules using the Rule Recertification feature!
At his stage the rule can be added to a new Rule Decommission ticket (which we covered in
the previous exercise).
Password: tufin123
2) Go to Workflows
3) Click New Workflow
4) Choose the Server Decommission Type.
7) Create a 4-step workflow (with the Server Decommission field in all 3 steps):
NOTE: Do not forget adding the Server Decommission field in each step with its relevant tool. Assign
steps 2-4 to John Smith.
9) Go to My Requests tab
20) Close the Designer dialog and note the Designer indication in green
25) Once the update is complete, Commit the change direct to the firewall
In this exercise, we will modify a group from a device by adding an object. The object will be added
from the same target device.
Note: You can only add objects from the same device that the group is configured on.
a. Go to Workflow properties
b. Modify workflow name: My Group Modification
5) In step #2, edit the Modify the Modify group field, to allow design and update only.
6) In step #3, edit the Modify the Modify group field, to allow commit only.
a. In the assignment tabs of steps 2 and 3, select Self Assigned and assign FW Operation
as the handler
b. In the Device field, search for: R80-Training and then click Add
c. Click OK.
a. Click on the menu icon on the top right of the editing table
c. Search for:
Type: Network
Name: LAN
Click Search and Click: Add
a. Search for:
Type: Host
Name: CP-R80.10-Gateway
Click Search and Click: Add
2) Step#2: Accept the task, run the Designer and Update the firewall policy
3) Close the Designer dialog, select Approve (insert a reason) and click Done
4) In Step#3, open the Designer tool and commit the changes to the firewall.
Appendix I
Command Line Reference
The SecureTrack processes can be managed from the command line with these commands:
st_add_user
Adds a SecureTrack Administrator. This command is useful if the Administrator's SecureTrack
password has been forgotten. The command initiates a series of prompts, for username, password,
full name, and options for the new Administrator.
st info
The st info command line collects SecureTrack logs and additional information, and places it in a file
named st_info.tgz.
st info does not collect any part of the security policy (rules, objects, etc) or your organization's
security configuration.
st restart [IP]
Stops and restarts all running connections to all devices. To restart a specific connection, specify the
device IP address as an additional parameter. SecureTrack's web interface has an equivalent action.
st stop [IP]
Stops all running connections to the devices.
To stop a specific connection, add the device IP address.
SecureTrack's web interface has an equivalent action.
st version
Displays the product version and build number. This information is also displayed in st stat.
tos conf
Displays status of Tufin Orchestration Suite products, and prompts to change these settings.
tos version
Displays TufinOS and TOS versions currently installed.
<backup_file> - the name of the backup file. The file is compressed in TGZ format.
By default, the backup operation is performed while SecureTrack monitoring processes are active. A
database locking mechanism ensures database integrity.
When the Tufin databases take up most of the hard drive's disk space, this command may fail if the
backup is made to a local (non-NFS) file.
The target restore server must have the same TOS version and the same amount of installed RAM
as the source backup server.
Appendix II
Patents and Trademarks
PATENTS
https://www.tufin.com/patents/
TRADEMARKS
Tufin, SecureChange, SecureTrack, Automatic Policy Generator, and the Tufin logo are trademarks of Tufin Software
Technologies Ltd.
All other product names mentioned herein are trademarks or registered trademarks of their respective owners.
Some TOP plugins include software developed by Terrapin Communications, Inc. and its contributors for RANCID.