Fortinet FortiClient EMS Lab Guide For FortiClient EMS 7.0
Fortinet FortiClient EMS Lab Guide For FortiClient EMS 7.0
© FORTINET
FortiClient EMS
Lab Guide
for FortiClient EMS 7.0
DO NOT REPRINT
© FORTINET
Fortinet Training
https://training.fortinet.com
https://docs.fortinet.com
https://kb.fortinet.com
https://fusecommunity.fortinet.com/home
Fortinet Forums
https://forum.fortinet.com
Fortinet Support
https://support.fortinet.com
FortiGuard Labs
https://www.fortiguard.com
https://training.fortinet.com/local/staticpage/view.php?page=certifications
https://home.pearsonvue.com/fortinet
Feedback
Email: [email protected]
9/21/2021
DO NOT REPRINT
© FORTINET
TABLE OF CONTENTS
Network Topology 5
Lab 1: Introduction 6
Lab 2: FortiClient EMS and FortiClient Installation 7
Exercise 1: Installing FortiClient EMS 8
Install FortiClient EMS Using an Installation File 8
Access the FortiClient EMS GUI and Install the License 10
Exercise 2: Installing FortiClient 13
Install FortiClient Using a Custom Installer File From FortiClient EMS 13
Lab 3: FortiClient EMS Configuration 17
Exercise 1: Accessing the GUI and Creating a FortiClient EMS Administrator 18
Access the FortiClient EMS GUI 18
Create a New FortiClient EMS Administrator 20
Exercise 2: Configuring FortiClient EMS System Settings 22
Configure Server Settings 22
Configure Log Settings 23
Configure Login Banner Settings 23
Exercise 3: Creating an Endpoint Group and a Group Assignment Rule, and
Running Scans 25
Create an Endpoint Group for a Windows Workgroup 25
Create a Group Assignment Rule for Windows Endpoints 26
Run Antivirus and Vulnerability Scans on a Registered Endpoint 27
Exercise 4: Enabling the Security Fabric to Trigger Automatic Quarantine 32
Verify FortiClient Log Settings 32
Enable the Security Fabric on the Root FortiGate 33
Lab 4: FortiClient Deployment Using FortiClient EMS 44
Exercise 1: Creating an Installer for Deployment 45
Create a FortiClient Installer for Deployment 45
Exercise 2: Adding Endpoints to FortiClient EMS 48
Add Endpoints Using an AD Domain Server 48
Exercise 3: Creating a Deployment Package to Install FortiClient 50
Create a Deployment Package to Install FortiClient 50
Lab 5: FortiClient Provisioning Using FortiClient EMS 52
Exercise 1: Creating and Assigning an Endpoint Profile for Deployment 53
DO NOT REPRINT
© FORTINET
Create an Endpoint Profile on FortiClient EMS 53
Create a Profile to Deploy FortiClient 53
Enable the Web Filter Feature in the Endpoint Profile 53
Provision a VPN in the Endpoint Profile 56
Create an Endpoint Policy to Assign the Endpoint Profile 57
Exercise 2: Testing the FortiGuard Web Filter 60
Verify FortiGuard Connectivity 60
Identify Web Filter Categories 60
Review a FortiGuard Category-Based Web Filter 63
Test the Web Filter 65
Verify a Web Filter Exclusion List 66
Test the Web Exclusion List 67
Exercise 3: Understanding Antivirus Protection and Vulnerability Scans 68
Verify AntiVirus Protection Settings 68
Test the Antivirus Real-Time Configuration 69
Run an On-Demand Vulnerability Scan 70
Lab 6: Zero Trust Network Access 72
Exercise 1: Configuring ZTNA Tags, Tagging Rules, and Features 74
Verify the Connection Between FortiClient, FortiClient EMS, and FortiGate 74
Configure FortiClient EMS ZTNA Tagging Rules 76
Enable the ZTNA Feature and Verify That ZTNA Tags Are Synced 80
Exercise 2: Configuring a Basic HTTPS Access Proxy With SSL Certificate-
Based Authentication 81
Configure a Basic HTTPS Access Proxy With Certificate-Based Authentication 81
Test Remote Access to the HTTPS Access Proxy 85
Understand the Behavior of the set empty-cert-action Option 89
Exercise 3: Configuring an HTTPS Access Proxy With User Authentication
and ZTNA Tags 91
Configure an Authentication Rule 92
Apply the User Group and ZTNA Tag to a ZTNA Rule 93
Test Remote Access to the HTTPS Access Proxy With User Authentication 94
Verify the Behavior When the Security Posture Changes on the Endpoint 97
Exercise 4: Configuring and Testing Compliance Rules to Create Dynamic
Groups and Policies 99
Create a Firewall Policy 99
Test Endpoint Access Using the IP/MAC Filtering ZTNA Firewall Policy 100
Lab 7: Diagnostics and Troubleshooting 104
Exercise 1: Running Diagnostic Tools 105
Run the FortiClient Diagnostic Tool 105
Run the FortiClient EMS Diagnostic Tool 108
DO Network
NOTTopology
REPRINT
© FORTINET
Network Topology
In this lab, you will examine FortiClient EMS and FortiClient installation.
Objectives
l Install FortiClient EMS on a Windows AD server
l Apply a FortiClient EMS license
l Install FortiClient on a Windows endpoint
Time to Complete
Estimated: 25 minutes
Prerequisites
Before beginning this lab, you must make sure that the installer file from the EMS deployment package is available
on the desktop of the FortiClient-Laptop VM, in the Resources folder.
For this exercise, we have provided a FortiClient EMS installation file and license. In a
real environment, you should not install FortiClient EMS on a Windows server that is
hosting AD or any other services.
4. Accept the license agreement, and then click Install to start the installation.
© FORTINET
The setup wizard installs FortiClient on the host machine. By default, the FortiClient EMS files are installed in
the C:\Program Files\Fortinet\FortiClient folder.
© FORTINET
Access the FortiClient EMS GUI and Install the License
You will access the FortiClient EMS GUI, create an administrator password, and install the license.
2. Click Sign in, and then log in to the FortiClient EMS GUI with the username admin and no password.
© FORTINET
3. Type Password123 in the New Password and Confirm Password fields to meet the password requirement, and
then click Submit to save the password.
4. In the License Source field, click File Upload, and then click Browse to select the license file in the Desktop >
Resources > Installation Files folder.
© FORTINET
6. On the FortiClient EMS GUI, click Dashboard > Status to see the license information.
From version 6.2.0 or later, FortiClient must be used with FortiClient EMS. FortiClient
must connect to FortiClient EMS to activate its license and become provisioned by the
endpoint profile that the administrator configured in FortiClient EMS. For this exercise,
we have provided a deployment package file from FortiClient EMS. You cannot use
FortiClient features until FortiClient is connected to FortiClient EMS and licensed.
After installation, FortiClient will be managed by FortiClient EMS, and all security
profiles have been configured to perform lab tasks.
You will install FortiClient using an installer file from FortiClient EMS.
3. Accept the license agreement, and then click Next to start the installation.
© FORTINET
By default, the FortiClient files are installed in the C:\Program Files\Fortinet\FortiClient\ folder.
5. Click Install.
© FORTINET
© FORTINET
FortiClient downloads all the signature databases to get up-to-date. It may take some time before the
download completes and FortiClient is available for you to configure other options. However, you can
continue with the lab steps as the download process runs in the background.
7. On the FortiClient-Laptop VM, in the system tray, right-click the FortiClient icon.
8. Click Open FortiClient Console to open the FortiClient GUI.
Allow some time for FortiClient to get all of its configuration from FortiClient EMS.
Objectives
l Access the FortiClient EMS GUI
l Explore the dashboard and view system information
l Create an administrator
l Configure system settings
l Create an endpoint group
l Run a vulnerability scan on an endpoint
Time to Complete
Estimated: 65 minutes
Prerequisites
Before beginning this lab, you must finish the previous lab.
In this exercise, you will access the FortiClient EMS GUI, and then create a new administrator account.
You will access the FortiClient EMS GUI, by either launching the application or using a browser.
© FORTINET
4. Log in to the FortiClient EMS GUI with the username admin and password Password123.
5. Click Dashboard > Status to confirm the FortiClient EMS serial number.
6. Locate the License Information widget, and then write down the serial number that appears in the Serial Number
field.
You can also access the FortiClient EMS GUI using the server host name
https://<server_name>.
Tip: You can get the <server_name> by running ipconfig /all on the server.
The Host Name appears under Windows IP Configuration. If you cannot
access the FortiClient EMS remotely, make sure that you can ping <server_name>,
by adding it to the DNS entry or the Windows host file.
7. Navigate to Endpoint Policy & Components, and then you will see CA Certificates.
Here, you can upload and manage certificates that can be used for EMS HTTPS access.
© FORTINET
Create a New FortiClient EMS Administrator
To log in to FortiClient EMS, you require a user administrator account. You will create both a super administrator
and a limited access account.
3. In the Add user window, in the User source section, select Create a new user, and then click Next.
Field Value
User EPadmin
5. Click Next.
6. In the Password and Confirm Password fields, type Fortinet123.
© FORTINET
8. Click the admin icon on the right side of the EMS GUI, and then select Sign out.
When you log in with the username EPadmin, why do you see only View Profiles under Endpoint
Profiles?
This user account has limited permissions and is not allowed to access endpoint profile management. The
Endpoint Administrator role that this user account is assigned to allows only read-only permissions to the
Settings Permissions category. This is the category that allows access to Endpoint Profiles.
In this exercise, you will configure the following FortiClient EMS system settings:
l Server settings
l Log settings
l Login banner settings
In EMS Settings, you can configure settings, such as the host name, the FQDN, and remote access. You will
configure the FQDN to access the FortiClient EMS server, using the configured FQDN.
© FORTINET
Configure Log Settings
In Log Settings, you can configure the log level, and the number of days that you want to keep logs, events, and
alerts before they are cleared. You will change the Log level setting.
In EMS Settings, you will configure a disclaimer message that appears before a user logs in to FortiClient EMS.
© FORTINET
In this exercise, you will create an endpoint group and a group assignment rule, and run antivirus and vulnerability
scans on endpoints. Endpoint management enables FortiClient EMS to perform various actions and run scans.
You will create individual groups for Windows workgroup endpoints on FortiClient EMS.
2. Click All Groups > Other Endpoints to view the registered endpoints.
3. In the Workgroups drop-down list, right-click All Groups, and then click Create group.
© FORTINET
FortiClient EMS can use group assignment rules to automatically place endpoints into custom groups, based on
the installer ID, IP address, OS, or AD group of the endpoints. You will create a group assignment rule based on
OS.
Field Value
Type OS
5. On the pane on the right, click Run Rules Now to add Windows endpoints to the new group.
© FORTINET
FortiClient EMS automatically places endpoints that do not apply to a group
assignment rule into the Other Endpoints group.
FortiClient EMS endpoint management can run scans on managed clients. Before you can run an AV scan, you
must change the endpoint profile on FortiClient EMS.
© FORTINET
After the Default profile is synced, on the FortiClient-Laptop VM, MALWARE PROTECTION appears on the
FortiClient GUI.
The Default endpoint profile doesn't have the malware protection feature enabled by default. To enable AV,
click the AntiVirus Protection button.
2. Beside the registered client, select the checkbox to highlight the registered client.
The following options appear: Scan, Patch, Move to, and Action.
© FORTINET
The scan starts, and it will finish after the endpoint resyncs or sends the next keepalive packet.
© FORTINET
© FORTINET
You can also click > to see more details about the applications.
In this exercise, you will enable the Fortinet Security Fabric to trigger automatic quarantine, based on indicators of
compromise (IOC) on FortiAnalyzer.
To identify compromised hosts, FortiClient must send logs to FortiAnalyzer. You will verify the FortiClient log
settings.
© FORTINET
If you are using a browser to access FortiClient EMS, you must enable Advanced view
settings on the FortiClient EMS Endpoint Profiles page.
You will configure the Security Fabric and enable telemetry on the FortiGate internal interface.
To configure the Security Fabric and enable telemetry on the root FortiGate
1. On the AD Server VM, open Firefox, type the FortiGate IP address 10.0.1.254, and log in with the username
admin and password password.
2. On the FortiGate GUI, click Security Fabric > Fabric Connecters.
3. Select Security Fabric Setup, and then click Edit.
4. In the Security Fabric Settings section, click Enabled.
Field Value
IP address 10.0.1.250
© FORTINET
8. Click OK.
9. When the Verify FortiAnalyzer Serial Number warning appears, click Accept.
10. When the FortiAnalyzer status warning appears, click Close because you will configure this in a later step.
11. Configure the following settings:
Field Value
port3
© FORTINET
17. Select the HQ-FortiGate device, click Authorize, and then click OK to complete the authorization.
18. On the HQ-FortiGate GUI, click Security Fabric > Fabric Connectors.
19. Click FortiAnalyzer Logging, and then click Edit.
In the FortiAnalyzer Status section, the Connection status is Connected.
3. In the New Fabric Connector window, select FortiClient EMS, and then configure the following settings:
© FORTINET
Field Value
Name EMSServer
4. Click OK, and then click Accept to accept the certificate and save the settings.
© FORTINET
5. On the FortiClient EMS GUI, click Administration > Fabric Devices.
6. On the right side, select FortiGate, and then click Authorize.
7. On the AD Server desktop, click PuTTY, double-click HQ-FortiGate, and then log in with the username admin and
password password.
8. Run the execute fctems verify EMSServer CLI command.
9. On the FortiClient EMS GUI, on the Administration > Fabric Devices page, select FortiGate again, and then click
Edit.
10. In the edit window, select the Share tag info from all FortiClients checkbox, and then click Save to apply the
changes.
For this lab, the FortiClient EMS certificate is already trusted by FortiGate. When you
configure a new connection, you must install the FortiClient EMS CA certificate on
FortiGate before you authorize. Otherwise, you will see the following status:
© FORTINET
The stitch, trigger, and action are enabled for an IOC compromised host.
Field Value
Name IOC_Policy
Source FortiClient-Laptop
Destination all
Schedule always
Service ALL
© FORTINET
Field Value
Action ACCEPT
NAT <enable>
3. Click OK.
4. Drag and drop the IOC_Policy policy above the Full_Access policy.
© FORTINET
Reason for using console access is that when FortiClient is quarantined, you may not be able to access
FortiClient-Laptop using RDP.
If lab menu shows any other VM, then use the Go back option in the lab menu to return
to the lists of VMs and then select FortiClient-Laptop from the list.
© FORTINET
2. Click the Ctrl+Alt+Delete button on the upper-right conrner, so you can enter a password.
3. Enter the password password to log in to Windows using the console connection.
4. On the FortiClient-Laptop VM, open Firefox, and then type the URL www.google.com.
5. Open a new browser tab, and then type http://195.22.28.198.
This IP address is blocked by the FortiClient malicious websites category.
6. Continuing on the AD Server VM, on the FortiAnalyzer GUI, click SOC > FortiView > Compromised Hosts.
The endpoint appears in the window.
© FORTINET
The result on your FortiGate may not match the lab example above.
10. Click Log & Report > Events > System Events to view the logs. You may need to change log source from
FortiAnalyzer to local disk in the upper-right corner.
11. FortiClient will show the quarantine screen. FortiClient is blocking all communication, except to the EMS.
© FORTINET
To remove the client from the compromised hosts list, on the FortiAnalyzer GUI, click
SOC > Fortiview. To clear the host, click Threats > Compromised Hosts, click ACK
to acknowledge the host, and then write some text. This will also clear the host from
FortiGate.
12. On the AD Server VM, log in to the FortiClient EMS GUI, and then select Endpoints > All Endpoints.
13. In the right pane, select FortiClient-Laptop, click Action, and then click Unquarantine to allow internet
access to the endpoint.
In this lab, you will learn about the deployment of FortiClient on endpoints, using FortiClient EMS.
Objectives
l Create a FortiClient installer
l Add endpoints to FortiClient EMS from Windows AD
l Create and manage a deployment package
Time to Complete
Estimated: 20 minutes
Prerequisites
Before beginning this lab, you must finish the previous lab.
To create an installer
1. On the AD Server VM, log in to the FortiClient EMS GUI.
2. In the pane on the left, click Deployment & Installers > FortiClient Installer, and then click +Add to open a new
window.
3. In the Version tab, keep the default settings for Installer Type and Release, in the Patch field, select 7.0.1, and
then click Next.
4. In the General tab, in the Name field, type FortiClient-Version-7.0, and then click Next.
5. In the Features tab, under Basic Security Features, select the Secure Access Architecture Components and
Vulnerability Scan checkboxes, and then under Additional Security Features, select the Malware, Web
Filtering, and Application Firewall checkboxes.
© FORTINET
6. Click Next.
7. In the Advanced tab, select the Enable desktop shortcut and Enable start menu shortcut checkboxes, and
then keep the default values for the other settings.
© FORTINET
8. Click Next.
9. In the Telemetry tab, notice that it shows that FortiClient will be managed by <EMS hostname and FQDN
address>.
10. Click Finish to add the deployment package to FortiClient EMS.
The installer appears on the Deployment & Installers > FortiClient Installer pane.
You will manually import endpoints from an AD server. You will import and synchronize information about
computer accounts with an LDAP or LDAPS service. You will also add endpoints by identifying the endpoints that
are part of an AD domain server.
Field Value
Username ADadmin
Password password
© FORTINET
You can add the entire domain or an organizational unit (OU) from the domain. After
you import endpoints from an AD server, you can edit the endpoints. These changes
are not synchronized back to the AD server.
In this exercise, you will create a deployment package to install FortiClient on AD endpoints.
You must add a FortiClient installer to the FortiClient EMS deployment package to install FortiClient. You will
select the installer that you created in exercise 1.
© FORTINET
7. Enable Start at a Scheduled Time, and then specify the installation start time, which should be five minutes from
the current time.
8. Disable Reboot when no users are logged in, and then keep the default values for all other settings.
9. In the Username field, type Administrator, and then in the Password field, type password.
10. Enable Enable the Deployment.
11. Click Save.
The deployment package appears on the Deployment & Installers > Manage Deployment page.
This deployment installs FortiClient on the AD Server VM. After this exercise, wait until
FortiClient installs, updates signatures, and then connects to the EMS server.
In this lab, you will learn about using FortiClient EMS to provision FortiClient on endpoints.
Objectives
l Create an endpoint profile
l Enable the web filter and antivirus features
l Configure a VPN tunnel
l Create a policy to assign a new endpoint profile to an AD domain or workgroup endpoints
Time to Complete
Estimated: 35 minutes
Prerequisites
Before beginning this lab, you must finish the previous lab.
In this exercise, you will create an endpoint profile and assign the profile to endpoints. You will also configure a
security profile and provision a VPN. After you complete provisioning, the configuration is pushed to FortiClient
endpoints by FortiClient EMS.
To push the configuration to FortiClient endpoints, you must create an endpoint profile. The endpoint profile has
profile references that enable and disable FortiClient features and deployment.
You must add a FortiClient installer to the FortiClient EMS before you can select an endpoint profile. You will
select the installer that you created in Lab 4—Exercise 1.
You can enable and disable security features, such as web filter, malware (antivirus), and application firewall in
endpoint profiles.
© FORTINET
2. On the Web Filter tab, in the General section, enable Web Filter, and then keep Enable WebFiltering on
FortiClient set to Always On.
3. In the Site Categories section, beside Bandwidth Consuming, click + to expand the list.
4. In the list, beside Streaming Media and Download, select Block.
6. In the Exclusion List section, change the action to Allow, type www.mp3.com, and then leave the other settings
at the default values.
© FORTINET
7. Click Save.
© FORTINET
Provision a VPN in the Endpoint Profile
You will provision the VPN settings. The VPN profile is applied to FortiClient when the profile installs on the
endpoint.
3. On the VPN Tunnels tab, click Add Tunnel, keep the VPN type set to Manual (default selection) , and then click
Next.
4. In the next window, configure the following settings:
Field Value
Port 10443
© FORTINET
5. Click Add Tunnel to save the VPN profile.
6. Click Save.
After creating the profile, you must create an endpoint policy to assign the profile to domains or workgroups. When
you create an endpoint policy to assign the profile to domains or workgroups, the profile settings are automatically
pushed to the endpoints in the domain or workgroup.
If you do not assign a profile to a specific domain or workgroup, the default profile is automatically applied to the
domain or workgroup.
© FORTINET
5. Click Add Rule, and then click Save to add the on-fabric detection rule.
6. On the Endpoint Policy & Components menu, select Manage Policies > Add.
7. In the Endpoint Policy window, in the Endpoint Policy Name field, type Training.
8. In the Endpoint Groups field, click Edit, select trainingAD.training.lab and All Groups, and then click Save.
9. In the Profile field, select Fortinet-Training in the profiles list.
10. In the Profile (Off-Fabric) field, select Default in the profiles list.
This profile applies when the endpoint is off-fabric. You cannot select the same endpoint profile for the on-
fabric and off-fabric status.
11. In the On-Fabric Detection Rules field, select On-Fabric in the drop-down list.
12. Ensure that Enable the Policy is enabled.
13. Keep the other settings at the default values, and then click Save to add the endpoint policy.
The endpoint policy should have the following settings:
© FORTINET
The endpoint profile is assigned to the endpoint policy. After FortiClient is deployed on the endpoints and the
endpoints are connected to FortiClient EMS, you can update the endpoints by editing the associated profiles.
14. On the FortiClient-Laptop VM, in the system tray, right-click the FortiClient icon.
15. Click Open FortiClient Console to show the VPN profile.
16. Verify that FortiClient is connected to EMS and all configurations are enabled on the endpoint.
In this exercise, you will test the configuration (WF profile) that you defined in the previous exercise. You will
examine the FortiClient web filter, based on FortiGuard categories, by making sure that FortiClient can contact the
FortiGuard servers.
Then, you will review a category-based web filter security profile on FortiClient and inspect the HTTP traffic.
Finally, you will test different actions taken by FortiClient, according to website categories that you configured in
the previous exercise.
You will verify connectivity to FortiGuard Distribution Servers (FDS) from the FortiClient host machine. FDS is
required because it handles URL categorization. FortiClient takes action to allow or block websites based on
category.
To understand how websites are categorized on FortiGuard, you must first identify how specific websites are
categorized by the FortiGuard service.
© FORTINET
2. Use the Web Filter Lookup tool to search for the following URL:
www.youtube.com
3. Use the Web Filter Lookup tool again to find the web filter categories for the following websites:
© FORTINET
l www.viber.com
l www.ask.com
l www.bing.com
© FORTINET
You will also test your web filter using these websites.
The following table shows the category assigned to each URL, as well as the action to take, which is
configured on FortiClient based on your web filter settings:
You will review the web filter profile and configuration of the FortiGuard category-based filter. These are the web
filter settings that you configured in the previous exercise on endpoint profiles, which were then pushed by EMS.
© FORTINET
4. On the Web Filter tab, in the upper-right corner, click the settings icon .
5. Review the configured actions for the following categories:
Category Action
Adult/Mature Content Allow: Sports Hunting and War Games, Sex Education, and Lingerie
and Swimsuit
Unrated Allow
© FORTINET
7. Verify that Streaming Media and Download is set to Block, and Internet Telephony is set to Warn.
For the purposes of this lab, you will test the web filter security profile that is configured for each category.
© FORTINET
You will verify that the URL www.mp3.com is included in the exclusion list.
2. On the Web Filter tab, in the upper-right corner, click the settings icon .
3. Click the + sign to expand Exclusion List.
© FORTINET
Test the Web Exclusion List
You will test the web exclusion list you reviewed in the previous procedure.
In this exercise, you will test the FortiClient malware protection features that you configured in Exercise 1. You will
test antivirus protection to understand how FortiClient performs real-time protection. You will also learn how a
vulnerability scan helps detect and patch application vulnerabilities that can be exploited by known and unknown
threats.
You will verify antivirus settings on FortiClient, which you configured in the EMS endpoint profile, and were then
pushed to FortiClient.
2. You can also click the settings icon , and then verify that the Scan files as they are downloaded or copied
to my system checkbox is selected.
© FORTINET
Test the Antivirus Real-Time Configuration
You will download the EICAR test file to your FortiClient-Laptop VM. The EICAR test file is an industry-standard
virus that is used to test antivirus detection without causing damage.
2. On the EICAR website, in the upper-right corner of the page, click DOWNLOAD ANTI MALWARE TESTFILE.
3. On the left side of the page, click the Download link.
4. In the Download area using the secure, SSL enabled protocol HTTPS section, download the sample file
named eicar_com.zip.
FortiClient should quarantine the download attempt and insert a replacement message similar to the following
example:
FortiClient shows the HTTP/HTTPS virus message when it blocks or quarantines infected files.
© FORTINET
5. Click Close to close the alert window.
6. In the download window, click OK to save the file.
7. Change the download location to Desktop, and then click Save.
You should see that the file you downloaded on the desktop shows the download error in the Firefox
downloads dialog.
Because the file is quarantined, an EMS administrator must add it to the allowlist it and restore it to view the
content.
You will test an on-demand vulnerability scan that you configured on the EMS endpoint profile in the first exercise,
which was then pushed to FortiClient. Vulnerability scans help detect and patch application vulnerabilities that can
be exploited.
© FORTINET
3. After the scan is finished, you will see the scan results under Vulnerabilities Detected.
4. To review the vulnerability details, click CRITICAL, and then expand 3rd Party App.
In this case, FortiClient cannot automatically install the software patch because the recommended action is
Manual Install. You can manually download and install the latest version of vulnerable software to fix the
vulnerability.
In the real environment, you should install the patch on affected applications.
In this lab, you will learn about the use of a zero trust network access (ZTNA) proxy for remote access to specific
applications. You will configure the required components, from the FortiClient EMS, to FortiGate and FortiClient.
You will also review key ZTNA concepts.
Objectives
l Verify the FortiGate and FortiClient EMS connection
l Configure EMS ZTNA tagging rules
l Enable the ZTNA feature on FortiGate and verify ZTNA tags
l Configure a basic HTTPS access proxy with SSL certificate-based authentication
l Configure an HTTPS access proxy with basic user authentication and ZTNA tags
l Configure basic ZTNA IP/MAC filtering
Time to Complete
Estimated: 55 minutes
Prerequisites
Before you start this lab, you must connect the Remote-Client endpoint to FortiClient EMS. FortiClient is already
installed on the endpoint and must establish a connection to FortiClient EMS.
© FORTINET
4. Click Connect.
After a few minutes, the status changes to connect, and FortiClient has all the configuration pushed by
FortiClient EMS.
In this exercise, you will verify the connection between FortiClient, FortiClient EMS, and FortiGate. You will also
configure ZTNA tags and tagging rules, and then verify if the tags are synced on FortiClient and FortiGate. These
tags will be used in the next exercises to authorize user traffic based on ZTNA tagging rules configured on
FortiClient EMS.
Establishing device identity and device trust between FortiClient, FortiClient EMS, and FortiGate is integral to
ZTNA setup. All of these devices must have a stable connection in order to exchange information required for
ZTNA tagging to work properly.
3. In the ZERO TRUST TELEMETRY section, ensure that the status of Centrally Managed by EMS is Connected.
© FORTINET
If the status is shown as Not reachable, you must reconnect the endpoint.
In this exercise, FortiGate is configured with a VIP and a firewall policy that allows
inbound connections to FortiClient EMS so that the remote endpoint can connect.
© FORTINET
You can also verify the status by running the following CLI command on FortiGate:
diagnose endpoint fctems test-connectivity <EMS name>
FortiClient EMS uses zero-trust tagging rules to tag endpoints based on the information that it has on each
endpoint. The tags are shared with FortiGate, which are then used to assign authorization to user traffic. You will
configure ZTNA tagging rules on the FortiClient EMS server.
To configure the FortiClient EMS ZTNA tagging rule for detecting a file
1. On the AD Server VM, click the FortiClient EMS icon to launch the application.
2. Log in to the FortiClient EMS GUI with the username admin and password Password123.
3. In the left menu, click Zero Trust Tags > Zero Trust Tagging Rules.
4. In the upper-right, click Add.
5. In the Name field, type Malicious-File-Detected.
6. In the Tag Endpoint As field, type Malicious-File-Detected, and then press Enter.
7. In the Rules section, click Add Rule, and then select Windows OS.
8. In the Rule Type field, select File.
© FORTINET
9. In the File field, type C:\virus.txt, and then click Save.
10. Click Save to save this zero-trust tagging rule.
To configure the FortiClient EMS ZTNA tagging rule for detecting remote endpoints
1. Continuing on Zero Trust Tags > Zero Trust Tagging Rules.
2. In the upper-right, click Add.
3. In the Name field, type Remote-Endpoints.
4. In the Tag Endpoint As field, type Remote-Endpoints, and then press Enter.
5. In the Rules section, click Add Rule, and then select Windows OS.
6. In the Rule Type field, select IP Range.
7. In the IP Range field, type 10.0.2.0/24, and then click Save.
8. Click Save to save this zero-trust tagging rule.
© FORTINET
© FORTINET
To configure the ZTNA tag to display on FortiClient
1. Continuing on the FortiClient EMS GUI, click Endpoint Profiles > Manage Profiles.
2. Select the Default profile, and then click Edit.
3. On the System Settings tab, under UI, enable Show Host Tag on FortiClient GUI.
© FORTINET
Enable the ZTNA Feature and Verify That ZTNA Tags Are Synced
You will enable the ZTNA feature on FortiGate, and then verify that the tags are synced between FortiClient EMS
and FortiGate.
To enable the ZTNA feature and verify that ZTNA tags are synced on FortiGate
1. On the AD server VM, on the FortiGate GUI, click System > Feature Visibility, and then enable Zero Trust
Network Access.
2. Click Policy & Objects > ZTNA, and then on the right side, click the ZTNA Tags tab.
ZTNA tags should be displayed on the page.
3. Hover over the Remote-Endpoints tag to see the IP address of the endpoint.
In this exercise, you will configure a basic HTTPS proxy access with SSL certificate-based authentication. A client
certificate is obtained when an endpoint registers with FortiClient EMS. FortiClient automatically submits a CSR
request and FortiClient EMS signs and returns the client certificate. The endpoint information is synchronized
between FortiGate and FortiClient EMS.
You will also locate the certificate on the endpoint and match it on FortiClient EMS and FortiGate. Finally, you will
see the behavior of the FortiGate set client-cert and set empty-cert-action options on the access-
proxy object.
The HTTPS access proxy setup requires a ZTNA server, real server, ZTNA rule, and firewall policy on FortiGate.
Field Value
Name ZTNA-webserver
External IP 100.64.1.10
© FORTINET
© FORTINET
3. In the Name field, type ZTNA-Allow-All.
4. Leave the Source field set to all.
5. In the ZTNA Server field, select ZTNA-webserver.
6. In the Action field, select ACCEPT.
7. In the Logging Options section, ensure that the Log Allowed Traffic field is set to All Sessions.
8. Ensure that Enable this policy is enabled.
Field Value
Name ZTNA-WAN
© FORTINET
Field Value
Source all
Schedule always
Service ALL
Action ACCEPT
NAT <disable>
© FORTINET
Test Remote Access to the HTTPS Access Proxy
Now that you configured FortiGate, you will test the HTTPS access proxy remote connection.
The actual ping will not be successful—you just want to be sure that the DNS resolves.
Access to the web server should be allowed. We're using the FortiAnalyzer login page to demonstrate the
web page.
© FORTINET
By default, client certificate authentication is enabled on the access proxy, so when the
HTTPS request is received, the FortiGate WAD process challenges the client to
identify itself with its certificate.
To locate the certificate on the endpoint and match it on FortiClient EMS and FortiGate
1. Continuing on the Remote-Client VM, open a Windows search, and then look for user certificates.
© FORTINET
2. In the user certificate store, open the Personal > Certificates folders.
3. Choose the FCTEMS issued certificate, and then double-click the certificate to view the properties.
4. Click the Details tab, and then find the Serial number of the certificate.
© FORTINET
Your certificate might not match what is shown in this example.
5. On the desktop, open PuTTY, and then double-click HQ-FortiGate from the saved session to open FortiGate CLI
access.
6. Enter the username admin and password password to log in, and then enter the following CLI command to view
the endpoint serial number (SN) and other information:
diagnose endpoint record list
7. On the AD server tab, open the FortiClient EMS GUI, and then click Endpoints > All Endpoints.
8. In the list, click Remote-Client, and then in the Configuration section, check the FortiClient ID and ZTNA Serial
Number fields to match the information.
© FORTINET
Your FortiClient ID and certificate serial number might not match what is shown in this example.
By default, client certificate authentication is enabled on the access proxy, so when the HTTPS request is
received, the FortiGate WAD process challenges the client to identify itself with its certificate. FortiGate also has a
configuration to accept or block an empty client certificate.
If a user clicks cancel during the certificate challenge, one of the following actions
occurs:
4. Click Cancel.
FortiGate blocks access.
© FORTINET
In this exercise, you will extend the solution to include user authentication with local users and security posture
checks with ZTNA tags. You will configure local user authentication and ZTNA rules to apply security posture
checks using ZTNA tags.
You can also use LDAP, RADIUS, and TACACS+ users for authentication.
© FORTINET
6. In the Method field, select Basic.
7. Leave the User database field set to Local.
An authentication rule specifies which proxy sources and destinations require authentication and which
authentication scheme to apply. You will use active authentication through the basic HTTP prompt and apply it to
all sources.
© FORTINET
Apply the User Group and ZTNA Tag to a ZTNA Rule
You must apply a user or user group to one or more ZTNA rules that you want to use to control user access. The
authenticated user from the authentication scheme and rule must match the user or user group in the ZTNA rule.
To apply a user group and add a ZTNA tag to the ZTNA allow rule
1. Continuing on the HQ-FortiGate GUI, click Policy & Objects > ZTNA.
2. Click ZTNA Rules, select ZTNA-Allow-All, and then click Edit.
3. In the Source field, click + to add a new entry.
4. In the window, select User, and then choose ZTNAaccess_group.
5. In the ZTNA Tag field, click +, and then add the Remote-Endpoints IP tag.
Field Value
Name ZTNA-Deny-Malicious
User: ZTNAaccess_group
Action Deny
© FORTINET
Test Remote Access to the HTTPS Access Proxy With User Authentication
You will test the HTTPS access proxy connection for authorized and unauthorized users.
© FORTINET
7. Select ZTNAuser, and then click Deauthenticate to remove the user from FortiGate.
© FORTINET
2. Choose the EMS signed certificate, and then click OK.
3. When prompted for sign-in, type the Username student and Password fortinet, and then click Sign in to
access the page.
Access is denied because the user is not authorized to access the resource.
4. On the HQ-FortiGate GUI, click Log & Report > Forward Traffic to check the deny logs for the student user.
© FORTINET
You may need to filter the Source IP address to 100.64.2.253 to see the related logs.
Verify the Behavior When the Security Posture Changes on the Endpoint
You will test a scenario where the endpoint security posture changed because of a malicious file. You will create a
test virus file to trigger the ZTNA tag detection that you created in the previous exercise.
4. On the desktop, open the Chrome browser, and then type https://webserver.ztnademo.com:9443 to
access the web page.
© FORTINET
In this exercise, you will create and test a firewall policy using ZTNA IP/MAC filtering. You will use an existing
ZTNA tag to block endpoint access when a malicious file exists on the endpoint. ZTNA IP/MAC filtering mode
enhances security when endpoints are physically on the corporate network, whereas full ZTNA mode focuses on
access for remote users.
To enforce compliance for local endpoints, you can select a ZTNA IP/MAC filtering option and apply a ZTNA tag to
a firewall policy.
Field Value
Name Block-Malicious
Source all
Destination all
Schedule always
Service ALL
Action DENY
© FORTINET
4. Move the Block-Malicious policy above the IOC_Policy policy at the top.
Test Endpoint Access Using the IP/MAC Filtering ZTNA Firewall Policy
To test endpoint access using the IP/MAC filtering ZTNA firewall policy
1. On the FortiClient-Laptop VM, ping IP 8.8.8.8 -t continuously to check connectivity to the internet.
It must be allowed.
2. On the FortiClient EMS GUI, click Zero Trust Tags > Zero Trust Tag Monitor.
There should not be any endpoints with the Malicious-File-Detected tag.
© FORTINET
3. On the FortiClient-Laptop VM, open Notepad, and then create a file with dummy text.
4. On the C: drive, save the file as virus.
5. Open the FortiClient console, and then click the avatar to view the detected tag.
It may take a minute to see the updated tag.
6. On the FortiClient EMS GUI, click Zero Trust Tags > Zero Trust Tag Monitor.
An endpoint appears on the Malicious-File-Detected tag.
© FORTINET
The endpoint IP address is shown. The ping should have stopped because the endpoint is tagged with a
malicious file detection tag.
© FORTINET
9. On the FortiClient-Laptop VM, on the C: drive, delete the virus file.
After some time, a ping should start.
10. On the AD Server VM, on the FortiClient EMS GUI, click Zero Trust Tags > Zero Trust Tag Monitor. There is no
Malicious-File-Detected tag.
11. On the FortiGate GUI, click Policy & Objects > ZTNA.
12. Click ZTNA Tags, and then hover over the Malicious-File-Detected tag.
There is no IP address.
In this lab, you will examine the files that are created by running the diagnostic tools of FortiClient and FortiClient
EMS.
Objectives
l Run FortiClient and FortiClient EMS diagnostic tools
Time to Complete
Estimated: 20 minutes
Prerequisites
Before beginning this lab, you must finish the previous lab.
In this exercise, you will run FortiClient and FortiClient EMS diagnostic tools on the FortiClient-Laptop VM and AD
Server VM.
You will run the diagnostic tool on FortiClient endpoints to gather system information.
Before you run the diagnostic tool, you must change the FortiClient log level to
Debug. On the FortiClient EMS GUI, click Endpoint Profiles > Fortinet-Training,
click Edit on the System Settings tab, and then under Log, change the log level to
Debug.
© FORTINET
A command line window opens and the diagnostic tool runs tasks to collect system data.
© FORTINET
If Windows cannot extract or unzip the folder, you may need to use 7-Zip software to
unzip a file. 7-Zip is installed on the VM.
8. To review the file content, click these files. When you click a file, a window opens and extracts the file to a
destination. Select Desktop for the destination.
Log files are compressed, so to read them, you must extract the files.
© FORTINET
The tool starts to run in the background. The file should be available after three keepalive cycles. The default
is 60 seconds for each cycle.
4. Continuing on the FortiClient EMS GUI, click Action, and then select Download Available Diagnostics Results
to download the results file.
5. Click Save again to download the file to the FortiClient EMS server download folder.
You will run the FortiClient EMS diagnostic tool on the AD server to gather information. Before you run the tool,
you must change the FortiClient EMS log level to DEBUG.
A command line window opens and the diagnostic tool runs tasks to collect system data.
© FORTINET
3. After all tasks are completed, the tool opens the C:\Users\Administrator\AppData\Local\Temp\1 link to
show the forticlientems_diagnostic.zip file.
4. Extract or unzip the forticlientems_7.0.1.0103_diagnostic_<xxxxxx-xxx-xxxx-xxxx-
xxxxxxxxx-xxxxxxx>.zip file, and then search for the SystemInfo.txt, events, and debug_xx-xx-
xxxx files.
5. To review the file content, click these files. When you click a file, a window opens and extracts the file to a
destination. Select Desktop for the destination.
Log files are compressed, so to read them, you must extract the files.
No part of this publication may be reproduced in any form or by any means or used to make any
derivative such as translation, transformation, or adaptation without permission from Fortinet Inc.,
as stipulated by the United States Copyright Act of 1976.
Copyright© 2021 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet,
Inc., in the U.S. and other jurisdictions, and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or company
names may be trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and
actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance results. Nothing herein
represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written
contract, signed by Fortinet’s General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified
performance metrics and, in such event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For
absolute clarity, any such warranty will be limited to performance in the same ideal conditions as in Fortinet’s internal lab tests. In no event does Fortinet make any
commitment related to future deliverables, features, or development, and circumstances may change such that any forward-looking statements herein are not accurate.
Fortinet disclaims in full any covenants, representations,and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify,
transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.