Академический Документы
Профессиональный Документы
Культура Документы
ie
w
Fo
rR
ev
Course 201
www.fortinet.com
nl
y
Copyright 2013 Fortinet, Inc. All rights reserved. No part of this publication including text, examples,
diagrams, or illustrations may be reproduced, transmitted, or translated in any form or by any means,
electronic, mechanical, manual, optical, or otherwise, for any purpose, without prior written permission of
Fortinet, Inc.
Fo
rR
ev
ie
w
Trademarks
Dynamic Threat Prevention System (DTPS), APSecure, FortiASIC, FortiBIOS, FortiBridge, FortiClient,
FortiGate, FortiGate Unified Threat Management System, FortiGuard, FortiGuard-Antispam, FortiGuardAntivirus, FortiGuard-Intrusion, FortiGuard-Web, FortiLog, FortiAnalyzer, FortiManager, Fortinet, FortiOS,
FortiPartner, FortiProtect, FortiReporter, FortiResponse, FortiShield, FortiVoIP, and FortiWiFi are
trademarks of Fortinet, Inc. in the United States and/or other countries. The names of actual companies
and products mentioned herein may be the trademarks of their respective owners.
MODULE 1:
nl
y
MODULE 2:
ie
w
MODULE 3:
ev
MODULE 4:
MODULE 5:
rR
Fo
MODULE 6:
MODULE 7:
Antivirus ............................................................................................................................................................ 82
MODULE 8:
Email Filtering .................................................................................................................................................. 93
01-50000-0201-20130215-C
MODULE 9:
Web Filtering .................................................................................................................................................. 105
MODULE 10:
Fo
rR
ev
ie
w
nl
y
01-50000-0201-20130215-C
ii
Introduction
nl
y
2013 Fortinet Training Services. This training may not be recorded in any medium, disclosed, copied, reproduced or
distributed to anyone without prior written consent of an authorized representative of Fortinet. Rev. 20130215-C
Fo
rR
ev
ie
w
Module 1
Module Objectives
By the end of this module, participants will be able to:
Identify the major features of the FortiGate Unified Threat Management appliance
Access and use the FortiGate units administration interfaces
Create administrators
Work with configuration files
01-50000-0201-20130215-C
Introduction
nl
y
VPN
Intrusion Prevention
Application Control
Web Filtering
WAN Optimization
Antispam
Antivirus
Firewall
ev
ie
w
Fo
rR
Fortinet Solution
VPN
Intrusion Prevention
Application Control
Web Filtering
WAN Optimization
Antispam
Antivirus
Firewall
and more
01-50000-0201-20130215-C
Introduction
Fortinet Solution
Firewall
Web
Filter
AV
FortiOS
IPS
nl
y
ie
w
Hardware
ev
Security
Automated
and network-level
update
service
services
Specialized
operating
system
Purpose-driven
hardware
Fo
rR
1
1
1
1
Application
control
WAN
Intrusion
Data
Antivirus
optimization
leak
prevention
prevention
Secure
VPN
Email
filtering
High
availability
Firewall
Endpoint
compliance
Dynamic
routing
Wireless
Logging
Authentication
and
reporting
Traffic
shaping
Virtual
Web
filtering
domains
01-50000-0201-20130215-C
Introduction
Fortinet Appliances
FortiWifi
FortiVoice
FortiCarrier
FortiAnalyzer
FortiMail
FortiBridge
FortiGate-ONE
FortiManager
FortiWeb
FortiSwitch
FortiClient
FortiScan
FortiDB
ev
ie
w
nl
y
FortiAP
Fo
rR
01-50000-0201-20130215-C
Introduction
nl
y
password: (blank)
ev
ie
w
Fo
rR
Device Administration
Web GUI
CLI
10
01-50000-0201-20130215-C
Introduction
ev
ie
w
nl
y
Admin Profiles
Fo
rR
11
Admin Profiles
Read
System Configuration
Network Configuration
Firewall Configuration
UTM Configuration
VPN Configuration
etc.
Read-Write
Admin
Profile
12
01-50000-0201-20130215-C
Introduction
Full access
custom
profile
prof_admin
profile
ev
super_admin
profile
ie
w
Custom access
nl
y
Administrators
Fo
rR
13
14
01-50000-0201-20130215-C
Introduction
nl
y
Administrator Authentication
ev
ie
w
Fo
rR
15
Administrator Authentication
16
01-50000-0201-20130215-C
Introduction
nl
y
Device Configuration
ev
ie
w
Fo
rR
17
18
01-50000-0201-20130215-C
Introduction
Interface IPs
Every used interface on the unit must have an IP assigned (in NAT
mode) using one of three methods:
ev
ie
w
nl
y
Fo
rR
19
Static Gateway
There must be at least one default gateway
If an interface is DHCP or PPPoE, then a gateway can be added
to the routing dynamically
20
01-50000-0201-20130215-C
10
Introduction
nl
y
ie
w
IP and DNS
Configuration
ev
Fo
rR
21
22
01-50000-0201-20130215-C
11
Introduction
ev
ie
w
nl
y
DHCP Activity
Fo
rR
23
24
01-50000-0201-20130215-C
12
Introduction
nl
y
ie
w
ev
Fo
rR
25
Step 1: Backup and store old configuration (Full config backup from CLI)
Step 2: Have copy of old firmware available
Step 3: Have disaster recovery option on standby (especially if remote)
Step 4: READ THE RELEASE NOTES (upgrade path, bug information)
Step 5: Double check everything
Step 6: Upgrade
26
01-50000-0201-20130215-C
13
Introduction
ie
w
ev
nl
y
Fo
rR
27
Labs
(OPTIONAL)
Lab 2: Administrative Access
Ex 1: Profiles and Administrators
Ex 2: Restricting Administrator Access
28
01-50000-0201-20130215-C
14
Introduction
ev
ie
w
nl
y
Fo
rR
29
01-50000-0201-20130215-C
15
ie
w
ev
rR
Fo
nl
y
2013 Fortinet Training Services. This training may not be recorded in any medium, disclosed, copied, reproduced or
distributed to anyone without prior written consent of an authorized representative of Fortinet. Rev. 20130215-C
Fo
rR
ev
ie
w
Module 2
nl
y
Module Objectives
By the end of this module participants will be able to:
Define the storage location for log information
Enable logging for different FortiGate unit events
View and search logs
Monitor log activity
Understand RAW log output
Customize widgets on the dashboard
01-50000-0201-20130215-C
16
nl
y
ie
w
ev
Establish baselines
Fo
rR
01-50000-0201-20130215-C
17
Memory and
Hard drive
nl
y
SNMP
ie
w
Syslog
ev
Local logging
Remote logging
Fo
rR
Event Log
System (System related events)
Router, VPN, User, WanOpt & Cache, Wifi
01-50000-0201-20130215-C
18
nl
y
utm-incident-traffic-log
config sys global
ie
w
If log allowed traffic is disabled on the policy, then a UTM event enabled traffic
logging for that session
Behavior is not configurable and only on, pre 5.0
ev
Fo
rR
Log Traffic
UTM Function
Extended-utm
utm-incidenttraffic-log
Enabled
N/A
N/A
Enabled
Disabled
Either
Disabled
Disabled
Enabled
Disabled
Disabled
Disabled
Disabled
Enabled
Enabled
Behavior
Traffic log generated by kernel (like
today). All new UTM fields empty.
01-50000-0201-20130215-C
19
ev
ie
w
nl
y
Fo
rR
10
01-50000-0201-20130215-C
20
nl
y
ev
ie
w
Fo
rR
11
12
01-50000-0201-20130215-C
21
nl
y
Log body
ie
w
ev
Fo
rR
13
14
01-50000-0201-20130215-C
22
ie
w
nl
y
ev
Fo
rR
15
Alert Email
01-50000-0201-20130215-C
23
SNMP
SNMP agent
nl
y
Fortinet MIB
Managed device
SNMP manager
ev
ie
w
Fo
rR
17
Event Logging
18
01-50000-0201-20130215-C
24
ev
ie
w
nl
y
Event Log
Fo
rR
19
Monitor
20
01-50000-0201-20130215-C
25
Monitor
ev
ie
w
nl
y
Fo
rR
21
Monitor
AV Monitor
Recent and top virus activity
Web Monitor
Top blocked FortiGuard categories
Application Monitor
Most used applications
22
01-50000-0201-20130215-C
26
ev
ie
w
nl
y
The same widget can be added multiple times to the same dashboard showing
different information
Fo
rR
23
Labs
(OPTIONAL)
Lab 2: Remote Monitoring
Ex 1: Remote Syslog and SNMP Monitoring
24
01-50000-0201-20130215-C
27
ev
ie
w
nl
y
Fo
rR
25
01-50000-0201-20130215-C
28
ie
w
ev
rR
Fo
nl
y
Firewall Policies
nl
y
Firewall Policies
2013 Fortinet Training Services. This training may not be recorded in any medium, disclosed, copied, reproduced or
distributed to anyone without prior written consent of an authorized representative of Fortinet. Rev. 20130215-C
Fo
rR
ev
ie
w
Module 3
Module Objectives
By the end of this module participants will be able to:
Identify the components used in a firewall policy
Create firewall objects
Create Address and Device Identity policies and manage the order of their
processing
Monitor traffic through policies
01-50000-0201-20130215-C
29
Firewall Policies
Firewall Policies
Incoming and outgoing interfaces
Source and destination IP addresses
Schedules
Action = ACCEPT
Logging
ev
Traffic
Shaping
ie
w
Authentication
Threat
Management
nl
y
Services
Fo
rR
Types of Policies
Address
Policy match based on IPs
User Identity
Policy match based on authentication information (user)
Device Identity
Policy match based on OS
01-50000-0201-20130215-C
30
Firewall Policies
Firewall Actions
Policy Action
Deny
Accept
nl
y
ie
w
ev
Deny
Fo
rR
01-50000-0201-20130215-C
31
Firewall Policies
ev
ie
w
nl
y
Fo
rR
01-50000-0201-20130215-C
32
Firewall Policies
nl
y
edit "port1"
end
ev
ie
w
Fo
rR
end
10
01-50000-0201-20130215-C
33
Firewall Policies
ev
ie
w
nl
y
Fo
rR
11
12
01-50000-0201-20130215-C
34
Firewall Policies
ev
ie
w
nl
y
Fo
rR
13
14
01-50000-0201-20130215-C
35
Firewall Policies
ev
ie
w
nl
y
Fo
rR
15
16
01-50000-0201-20130215-C
36
Firewall Policies
nl
y
ev
ie
w
Fo
rR
17
Firewall Interfaces
Incoming
Interface
Outgoing
Interface
18
01-50000-0201-20130215-C
37
Firewall Policies
ie
w
FortiGate unit uses Services to determine the types of communication accepted or denied
Default of ALL services available
Select a Service from predefined list on FortiGate unit or create a custom service
Web Proxy Service also available if Incoming Interface is set to web-proxy
Group Services and Web Proxy Service Group to simplify administration
ev
Firewall Policy
Packet
nl
y
Fo
rR
19
Traffic Logging
Accept
Deny
20
01-50000-0201-20130215-C
38
Firewall Policies
11.12.13.14
wan1
200.200.200.200
nl
y
Firewall policy
with NAT enabled
wan1 IP address: 200.200.200.200
Source IP address:
200.200.200.200
Source port: 30912
internal
10.10.10.1
ie
w
Source IP address:
10.10.10.1
Source port: 1025
Destination IP address:
11.12.13.14
Destination Port: 80
ev
Destination IP address:
11.12.13.14
Destination Port: 80
Fo
rR
21
Firewall policy
with NAT + IP pool enabled
wan1 IP pool: 200.200.200.2-200.200.200.10
11.12.13.14
wan1
200.200.200.200
internal
10.10.10.1
Source IP address:
10.10.10.1
Source port: 1025
Source IP address:
200.200.200.?
Source port: 30957
Destination IP address:
11.12.13.14
Destination Port: 80
Destination IP address:
11.12.13.14
Destination Port: 80
22
01-50000-0201-20130215-C
39
Firewall Policies
ev
ie
w
nl
y
Fo
rR
23
24
01-50000-0201-20130215-C
40
Firewall Policies
ev
ie
w
HTTP
FTP
IM
nl
y
Traffic Shaping
Fo
rR
25
26
01-50000-0201-20130215-C
41
Firewall Policies
wan1
200.200.200.200
Source IP address:
200.200.200.201
Source port: 1025
internal
10.10.10.1
11.12.13.14
nl
y
Firewall policy
with NAT + IP pool enabled + fixed port (CLI only)
wan1 IP pool: 200.200.200.201
Destination IP address:
11.12.13.14
Destination Port: 80
ie
w
Source IP address:
10.10.10.1
Source port: 1025
ev
Destination IP address:
11.12.13.14
Destination Port: 80
Fo
rR
27
Firewall policy
with destination address virtual IP + Static NAT
wan1 IP address: 200.200.200.200
11.12.13.14
wan1
internal
10.10.10.10
Source IP address:
11.12.13.14
Destination IP address:
200.200.200.222
Destination Port: 80
28
01-50000-0201-20130215-C
42
Firewall Policies
Firewall policy
with destination address virtual IP + Static NAT
wan1 IP address: 200.200.200.200
nl
y
wan1
11.12.13.14
internal
ev
ie
w
10.10.10.10
Fo
rR
29
30
01-50000-0201-20130215-C
43
Firewall Policies
ev
ie
w
nl
y
Threat Management
Fo
rR
31
32
01-50000-0201-20130215-C
44
Firewall Policies
nl
y
Enable UTM
ev
ie
w
Fo
rR
33
Traffic Shapers
Shared Traffic Shaper
Guaranteed Bandwidth
Maximum Bandwidth
Guaranteed Bandwidth
Maximum Bandwidth
Guaranteed Bandwidth
Maximum Bandwidth
Guaranteed Bandwidth
Maximum Bandwidth
34
01-50000-0201-20130215-C
45
Firewall Policies
Traffic Shapers
Shared Traffic Shaper
Guaranteed Bandwidth
Maximum Bandwidth
nl
y
Guaranteed Bandwidth
Maximum Bandwidth
ie
w
ev
Bandwidth
Values applied toGuaranteed
each IP
address affected by the
Maximum Bandwidth
policy
Fo
rR
35
DoS Policies
DoS Policy
Firewall Policy
36
01-50000-0201-20130215-C
46
Firewall Policies
nl
y
Endpoint Control
ie
w
Up to date ?
ev
Disallowed software
installed ?
Fo
rR
37
38
01-50000-0201-20130215-C
47
Firewall Policies
Object Tagging
Simplifies firewall policy object management
Useful for administering multiple VDOMs
Easier to find and access specific firewall policies within specific VDOMs
ev
ie
w
nl
y
Fo
rR
39
Monitor
40
01-50000-0201-20130215-C
48
Firewall Policies
Labs
(OPTIONAL)
Lab 2: Traffic Log
ev
ie
w
nl
y
Fo
rR
41
42
01-50000-0201-20130215-C
49
ie
w
ev
rR
Fo
nl
y
nl
y
2013 Fortinet Training Services. This training may not be recorded in any medium, disclosed, copied, reproduced or
distributed to anyone without prior written consent of an authorized representative of Fortinet. Rev. 20130215-C
Fo
rR
ev
ie
w
Module 4
Module Objectives
By the end of this module participants will be able to:
Describe the authentication mechanisms available through the FortiGate device
Create local users and user groups
Create identity-based policies to enable local user authentication
Monitor active users
Check authentication Log entries
01-50000-0201-20130215-C
50
ev
ie
w
nl
y
Authentication
Fo
rR
01-50000-0201-20130215-C
51
nl
y
ev
ie
w
Fo
rR
RADIUS
LDAP
Digital
certificates
Directory
Services
TACACS+
Remote Users
6
01-50000-0201-20130215-C
52
User Groups
Active
Directory
Visitors
Firewall
User Group
Directory Service
User Group
nl
y
Paris
ev
ie
w
User groups are assigned one of four group types: Firewall, Fortinet Single Sign on
(FSSO), Guest and Radius Single Sign on (RSSO)
Firewall user groups provide access to firewall policies that require authentication
Directory Service user groups used to allow single sign on for Active Directory or Novell
eDirectory users
Fo
rR
Identity-Based Policies
Policy
Enable Identity Based Policy
Authentication Rule
User/Group
Services
Schedules
Logging
Threat management
Traffic Shaping
01-50000-0201-20130215-C
53
Disclaimers
Policy
nl
y
Enable Disclaimer
ev
ie
w
Fo
rR
Authentication Timeout
10
01-50000-0201-20130215-C
54
Password Policy
8 to 64 characters
Must Contain:
Uppercase letters
Lowercase letters
Numerical digits
Non-alphanumeric characters
Password Expiration:
X days
Apply to:
Administrators
IPSec Preshared Key
ie
w
nl
y
Minimum Length:
ev
Set a password policy to enforce higher standards for both the length and complexity
of passwords
Policies can be applied to administrator password and IPSec VPN preshared keys
Fo
rR
11
Two-Factor Authentication
A one-time password can be delivered to the user through various
methods:
FortiToken: Every 60 seconds, the token generates a 6-digit code based on a
unique serial number, seed and GMT time
Email: The one-time password is sent to users configured email address after
successful password authentication
SMS phone message: The one-time password sent through email to the users
SMS provider. The email address pattern varies by provider.
12
01-50000-0201-20130215-C
55
ev
ie
w
nl
y
Two-Factor Authentication
Fo
rR
13
Policy Configuration
14
01-50000-0201-20130215-C
56
nl
y
User Monitor
ie
w
ev
Fo
rR
15
Labs
16
01-50000-0201-20130215-C
57
ev
ie
w
nl
y
Fo
rR
17
01-50000-0201-20130215-C
58
ie
w
ev
rR
Fo
nl
y
SSL VPN
nl
y
SSL VPN
2013 Fortinet Training Services. This training may not be recorded in any medium, disclosed, copied, reproduced or
distributed to anyone without prior written consent of an authorized representative of Fortinet. Rev. 20130215-C
Fo
rR
ev
ie
w
Module 5
Module Objectives
By the end of this module participants will be able to:
Identify the VPN technologies available on the FortiGate device
Configure the SSL VPN operating modes
Define user restrictions
Setup SSL VPN portals
Configure firewall policies and authentication rules for SSL VPNs
01-50000-0201-20130215-C
59
SSL VPN
ev
ie
w
nl
y
Fo
rR
FortiGate VPN
SSL VPN
IPSec VPN
VPN
01-50000-0201-20130215-C
60
SSL VPN
ev
ie
w
nl
y
Fo
rR
01-50000-0201-20130215-C
61
SSL VPN
User Groups
nl
y
Web mode and tunnel mode both require a firewall policy for
authentication
Tunnel mode requires additional policies to allow internal network
access
Mode(s) user has access to is determined by authentication policy
ev
ie
w
Fo
rR
Authentication
01-50000-0201-20130215-C
62
SSL VPN
ie
w
nl
y
ev
Fo
rR
10
01-50000-0201-20130215-C
63
SSL VPN
ev
ie
w
https://<FortiGate IP address>
nl
y
Fo
rR
11
12
01-50000-0201-20130215-C
64
SSL VPN
ev
ie
w
nl
y
Only traffic destined for the tunnel IP range network will be routed over
the SSL VPN
If access to another inside network is desired, the client will need to
create a static route pointing to their own SSL VPN interface
Fo
rR
13
14
01-50000-0201-20130215-C
65
SSL VPN
nl
y
ie
w
Fo
rR
15
ev
The web portal page will display the status of the SSL VPN client
ActiveX control
The portal web page must remain open for the tunnel to function
16
01-50000-0201-20130215-C
66
SSL VPN
nl
y
RDPNative: for Microsoft Windows native RDP client over port forward
ev
ie
w
etc.
Fo
rR
17
18
01-50000-0201-20130215-C
67
SSL VPN
No client software
required (web browser
only)
Uses FortiGate-specific
client downloaded to PC
(ActiveX or Java applet)
Requires admin/root
privilege to install layer3 tunnel adaptor
Web Mode
nl
y
Tunnel Mode
ie
w
Downloaded to client PC
and installed without
admin/root privileges
ev
Fo
rR
19
Configuration
20
01-50000-0201-20130215-C
68
SSL VPN
ev
ie
w
nl
y
Configuration
Fo
rR
21
Labs
22
01-50000-0201-20130215-C
69
SSL VPN
ev
ie
w
nl
y
Fo
rR
23
01-50000-0201-20130215-C
70
IPSec VPN
nl
y
IPSec VPN
2013 Fortinet Training Services. This training may not be recorded in any medium, disclosed, copied, reproduced or
distributed to anyone without prior written consent of an authorized representative of Fortinet. Rev. 20130215-C
Fo
rR
ev
ie
w
Module 6
Module Objectives
By the end of this module participants will be able to:
Define the architectural components of IPSec VPN
Define the protocols used as part of an IPSec VPN
Identify the phases of Internet Key Exchange (IKE)
Identify the FortiGate unit IPSec VPN modes
Configure IPSec VPN on the FortiGate unit
01-50000-0201-20130215-C
71
IPSec VPN
IPSec VPN
Data has
integrity
ie
w
Data
confidential
nl
y
Private network
ev
Sender
authenticated
Fo
rR
IPSec VPN
01-50000-0201-20130215-C
72
IPSec VPN
IPSec VPN
IPSec VPN operates at the network layer (layer 3)
Encryption occurs transparently to the upper layers
Applications do not need to be designed to use IPSec
nl
y
IPSec VPN can protect upper layer protocols (such as TCP) but
the complexity and overhead of the exchange is increased
ev
ie
w
Fo
rR
01-50000-0201-20130215-C
73
IPSec VPN
Phase 1
IKE Phase 1 performs the following:
Authenticates and protects the parties involved in the IPSec transaction
Can use pre-exchanged keys or digital certificates
nl
y
ev
ie
w
Fo
rR
KB IDs:
11657
13574
01-50000-0201-20130215-C
74
IPSec VPN
Phase 2
IKE Phase 2 performs the following:
Negotiates IPSec SA parameters
Protected by existing IKE SA
nl
y
ev
ie
w
Fo
rR
10
01-50000-0201-20130215-C
75
IPSec VPN
Interface Mode
Creates a virtual IPSec network interface that applies encryption
or decryption as needed to any traffic that it carries
Also known as Route-Based
ev
ie
w
nl
y
Create two firewall policies between the virtual IPSec interface and
the interface that connects to the private network
The firewall policy action is ACCEPT
Needs static routes over VPN tunnels
Required if dynamic routing, GRE over IPSec or altering of
incoming subnet is needed
Fo
rR
11
Tunnel Mode
12
01-50000-0201-20130215-C
76
IPSec VPN
Interface
Mode
ev
ie
w
nl
y
Tunnel
Mode
Fo
rR
13
Overlapping Subnets
Site-to-site route-based VPN configurations sometimes experience a
problem where private subnet addresses at each end of the
connection are the same
After a tunnel is established, hosts on each side can communicate with
hosts on other side using the mapped IP addresses
Use NAT with IP Pool
Interface mode can NAT both the incoming and outgoing traffic
Tunnel mode can only NAT outgoing traffic
14
01-50000-0201-20130215-C
77
IPSec VPN
nl
y
Headquarters
Site-to-site
ev
ie
w
Branch office
Fo
rR
15
16
01-50000-0201-20130215-C
78
IPSec VPN
ev
ie
w
nl
y
Fo
rR
17
Configuration
18
01-50000-0201-20130215-C
79
IPSec VPN
ev
ie
w
nl
y
Configuration
Fo
rR
19
Labs
20
01-50000-0201-20130215-C
80
IPSec VPN
ev
ie
w
nl
y
Fo
rR
21
01-50000-0201-20130215-C
81
ie
w
ev
rR
Fo
nl
y
Antivirus
nl
y
Antivirus
2013 Fortinet Training Services. This training may not be recorded in any medium, disclosed, copied, reproduced or
distributed to anyone without prior written consent of an authorized representative of Fortinet. Rev. 20130215-C
Fo
rR
ev
ie
w
Module 7
Module Objectives
By the end of this module participants will be able to:
Describe conserve mode conditions and AV system behavior
Define the virus scanning techniques used on the FortiGate unit
Identify the differences between file-based and flow-based virus scanning
Configure quarantine options
Define firewall policies using antivirus profiles
Update FortiGuard Services
01-50000-0201-20130215-C
82
Antivirus
Conserve Mode
What is conserve mode?
System self protection measure when facing local resource exhaustion
nl
y
When entering conserve mode the FortiGate unit activates protection measures in
order to recover memory space
Once enough memory is recovered, the system leaves the conserve mode state
and releases the protection measures
ev
ie
w
Fo
rR
Conserve Mode
Regular conserve mode is depletion of shared memory
Used mainly by proxies (to store the buffered data) but also by buffers (logging,
quarantining)
Impact (configurable)
Established sessions remain unchanged
New sessions are not inspected
Fail-open action applies to stream and proxy-based inspection
01-50000-0201-20130215-C
83
Antivirus
AV Fail-Open
There are currently two conditions that can cause the FortiGate unit to
operate in AV fail-open mode:
The system is low on memory and has entered conserve mode
nl
y
The individual proxy pool is full (no free connections are available)
ev
ie
w
With the first condition, low memory, the av-failopen setting will be
applied
Fo
rR
AV Fail-Open
01-50000-0201-20130215-C
84
Antivirus
AV Fail-Open
The second condition occurs when the individual proxy pool
is full (default disable)
The action will depend on the av-failopen-session settings
nl
y
ev
ie
w
Fo
rR
Antivirus
Antivirus
01-50000-0201-20130215-C
85
Antivirus
.jpg
Virus
scan
File
type
Grayware
Heuristics
nl
y
File
Name
pattern
ev
ie
w
File
size
Fo
rR
Proxy-Based Scanning
10
01-50000-0201-20130215-C
86
Antivirus
File is scanned on a
packet-by-packet basis as
it passes through the
FortiGate unit
Faster scanning, but lower
accuracy rate
nl
y
Flow-Based Scanning
ev
ie
w
Fo
rR
11
Virus Scanning
Regular
Extended
Extreme
Flow-based
12
01-50000-0201-20130215-C
87
Antivirus
Unknown Viruses
Sometimes a virus may go undetected because
it is not in the signature database
ev
ie
w
nl
y
Fo
rR
13
Known Virus
14
01-50000-0201-20130215-C
88
Antivirus
Heuristics Scanning
Virus-like attribute
+ Virus-like attribute
nl
y
+ Virus-like attribute
> Heuristic threshold
Suspicious
ie
w
ev
Fo
rR
15
Antivirus Profiles
16
01-50000-0201-20130215-C
89
Antivirus
ev
ie
w
nl
y
Fo
rR
17
Quarantine
Infected, blocked or
suspicious files can be
quarantined to the hard
drive on the FortiGate
unit or to the
FortiAnalyzer device
Files quarantined based
on their protocol
Information regarding
quarantined files is
displayed in the logs
FortiAnalyzer
18
01-50000-0201-20130215-C
90
Antivirus
ev
ie
w
nl
y
Logs
Fo
rR
19
Labs
20
01-50000-0201-20130215-C
91
Antivirus
ev
ie
w
nl
y
Fo
rR
21
01-50000-0201-20130215-C
92
ie
w
ev
rR
Fo
nl
y
Email Filtering
nl
y
Email Filtering
2013 Fortinet Training Services. This training may not be recorded in any medium, disclosed, copied, reproduced or
distributed to anyone without prior written consent of an authorized representative of Fortinet. Rev. 20130215-C
Fo
rR
ev
ie
w
Module 8
Module Objectives
By the end of this module participants will be able to:
Identify the email filtering methods used on the FortiGate device
Configure banned word, IP address and email address filters
Define firewall policies using email filter profiles
Identify the differences between the email filtering capabilities of the FortiGate and
FortiMail units
01-50000-0201-20130215-C
93
Email Filtering
Email Filtering
nl
y
ev
ie
w
SPAM?
Fo
rR
Spam Actions
Tag
Discard
01-50000-0201-20130215-C
94
Email Filtering
nl
y
Heuristic check
ev
ie
w
Fo
rR
IP BWL Check
MIME Header
Email BWL
Banned word
(on Body)
IP BWL Check
(Receive Header)
Banned word
(on Subject)
01-50000-0201-20130215-C
95
Email Filtering
MIME Header
Email BWL
IP BWL Check
nl
y
Banned Word
(on Subject)
Banned word
(on Body)
ev
ie
w
Fo
rR
01-50000-0201-20130215-C
96
Email Filtering
ie
w
nl
y
ev
Fo
rR
Our online
pharmacy offers
great prices on
all your
prescription
medications.
hash
10
01-50000-0201-20130215-C
97
Email Filtering
nl
y
An administrator can add to or edit the IP addresses and configure the action
to take
Spam (use spam action)
Clear (consider Not Spam)
ev
ie
w
Fo
rR
11
From: bsmith@acme.com
Mark as Spam
Mark as Clear
12
01-50000-0201-20130215-C
98
Email Filtering
ev
ie
w
nl
y
Fo
rR
13
14
01-50000-0201-20130215-C
99
Email Filtering
ev
ie
w
nl
y
Fo
rR
15
Drugs
Score=10
Pharmacy
Score=5
Prescription
Score=5
Threshold=18
10 +5 +5 =20
16
01-50000-0201-20130215-C
100
Email Filtering
ev
ie
w
nl
y
Fo
rR
17
18
01-50000-0201-20130215-C
101
Email Filtering
ev
ie
w
nl
y
Fo
rR
19
Caching reduces
FortiGuard requests;
can improve
performance
Small % of system
memory dedicated to
cache
Query results cached
until TTL setting is
reached
Alternate port 8888 for
access to FortiGuard
servers
IP address:
10.10.10.1
URL:
www.acme.com
Message
checksum:
x65Fsd34c
20
01-50000-0201-20130215-C
102
Email Filtering
ev
ie
w
nl
y
Fo
rR
21
Labs
22
01-50000-0201-20130215-C
103
Email Filtering
ev
ie
w
nl
y
Fo
rR
23
01-50000-0201-20130215-C
104
Web Filtering
nl
y
Web Filtering
2013 Fortinet Training Services. This training may not be recorded in any medium, disclosed, copied, reproduced or
distributed to anyone without prior written consent of an authorized representative of Fortinet. Rev. 20130215-C
Fo
rR
ev
ie
w
Module 9
Module Objectives
By the end of this module participants will be able to:
Identify the web filtering mechanisms used on the FortiGate device
Create web content and URL filters
Configure FortiGuard Web Filtering
Configure FortiGuard Web Filtering exemptions and rating overrides
Define firewall policies using web filter profiles
01-50000-0201-20130215-C
105
Web Filtering
Web Filtering
Means of controlling the web content that a user is able to view
ev
ie
w
nl
y
Fo
rR
01-50000-0201-20130215-C
106
Web Filtering
ev
ie
w
nl
y
Fo
rR
01-50000-0201-20130215-C
107
Web Filtering
ev
ie
w
nl
y
Fo
rR
01-50000-0201-20130215-C
108
Web Filtering
ev
ie
w
nl
y
Fo
rR
DNS Request
DNS Response
HTTP GET
HTTP 200
10
01-50000-0201-20130215-C
109
Web Filtering
URL
Block
Web URL
Filter
FortiGuard
Filter
nl
y
Allow
Block
Allow
Block Page
Block Page
Allow
Advanced
Filter
Block
Content
Filter
Block
ie
w
Allow
Block Page
Allow
Block
Virus Scan
Display Page
ev
Block Page
Fo
rR
11
Flow-Based
High throughput
No caching
Not as secure
DNS-Based
Very lightweight
Hostname filtering only
No advanced options, URL and FortiGuard only
12
01-50000-0201-20130215-C
110
Web Filtering
Pharmacy
Score=5
nl
y
Prescription
Score=5
10 +5 +5 =20
Block or Exempt
ie
w
Threshold=18
www.acme.com
ev
If pattern appears
multiple times on web
page, score is only
counted once
Score=10
Fo
rR
13
14
01-50000-0201-20130215-C
111
Web Filtering
www.example.com
www.abc.com
URL: www.mypage.com/index.html
nl
y
www.mypage.com/index.html
ev
www.mypage.com
ie
w
Block
Allow
Monitor
Exempt
Fo
rR
15
16
01-50000-0201-20130215-C
112
Web Filtering
Categories
URL: www.mypage.com
ev
www.mypage.com
ie
w
nl
y
Allow
Block
Monitor
Warning
Authenticate
Fo
rR
17
18
01-50000-0201-20130215-C
113
Web Filtering
nl
y
ev
ie
w
Fo
rR
19
FortiGuard Caching
Most web sites are visited over and over again
FortiGate unit can remember what the response was
01-50000-0201-20130215-C
114
Web Filtering
Category:
Games
nl
y
Games Quota
Games Quota
ie
w
ev
Games Quota
Fo
rR
21
Rating Submissions
Requests for rating of a web site, or to have a web sites rating
re-evaluated can be submitted by accessing:
http://www.fortiguard.com/ip_rep.php
22
01-50000-0201-20130215-C
115
Web Filtering
Rating Override
Rating override
www.acme.com
ie
w
nl
y
Category:
General Organizations
ev
Fo
rR
23
Rating Override
Can override the rating applied to a hostname by FortiGuard
Subscription Services
Hostname reassigned to a completely different category and uses that action
Hostnames only
google.com
www.google.com
www.google.com/index.html
24
01-50000-0201-20130215-C
116
Web Filtering
nl
y
Local Categories
ev
ie
w
Fo
rR
25
Warning Action
Action = Warning (right click in the GUI)
26
01-50000-0201-20130215-C
117
Web Filtering
Authenticate Action
ev
www.hackthissite.org
ie
w
nl
y
Marketing
Fo
rR
27
28
01-50000-0201-20130215-C
118
Web Filtering
Labs
Lab 1: Web Filtering
ev
ie
w
nl
y
Fo
rR
29
30
01-50000-0201-20130215-C
119
ie
w
ev
rR
Fo
nl
y
Application Control
Application Control
2013 Fortinet Training Services. This training may not be recorded in any medium, disclosed, copied, reproduced or
distributed to anyone without prior written consent of an authorized representative of Fortinet. Rev. 20130215-C
Fo
rR
ev
ie
w
Module 10
nl
y
Module Objectives
By the end of this module participants will be able to:
Define application control lists
Define firewall policies using application control lists
01-50000-0201-20130215-C
120
Application Control
Application Control
Application control is used to detect and take actions on network traffic
based on the application generating the traffic
nl
y
ev
ie
w
Fo
rR
01-50000-0201-20130215-C
121
Application Control
ev
ie
w
nl
y
http://www.fortiguard.com/applicationcontrol/appform.html
Fo
rR
01-50000-0201-20130215-C
122
Application Control
ev
ie
w
nl
y
Fo
rR
01-50000-0201-20130215-C
123
Application Control
nl
y
Order of Operations
ev
ie
w
Fo
rR
Implicit Rules
10
01-50000-0201-20130215-C
124
Application Control
ev
ie
w
nl
y
Fo
rR
11
Categories
Update if using
Signatures change and update
12
01-50000-0201-20130215-C
125
Application Control
ev
ie
w
nl
y
Proper Identification
Fo
rR
13
? ?
14
01-50000-0201-20130215-C
126
Application Control
nl
y
ie
w
ev
Fo
rR
15
Peer-to-Peer Detection
16
01-50000-0201-20130215-C
127
Application Control
Peer-to-Peer Detection
Peer-to-peer transfer
nl
y
1 Client
ev
ie
w
N Servers
Fo
rR
17
Peer-to-Peer Detection
18
01-50000-0201-20130215-C
128
Application Control
Labs
Lab 1: Application Identification
ev
ie
w
nl
y
Fo
rR
19
20
01-50000-0201-20130215-C
129
nl
y
ie
w
Fo
rR
ev
Course 201
www.fortinet.com
nl
y
Copyright 2013 Fortinet, Inc. All rights reserved. No part of this publication including text, examples,
diagrams, or illustrations may be reproduced, transmitted, or translated in any form or by any means,
electronic, mechanical, manual, optical, or otherwise, for any purpose, without prior written permission of
Fortinet, Inc.
Fo
rR
ev
ie
w
Trademarks
Dynamic Threat Prevention System (DTPS), APSecure, FortiASIC, FortiBIOS, FortiBridge, FortiClient,
FortiGate, FortiGate Unified Threat Management System, FortiGuard, FortiGuard-Antispam, FortiGuardAntivirus, FortiGuard-Intrusion, FortiGuard-Web, FortiLog, FortiAnalyzer, FortiManager, Fortinet, FortiOS,
FortiPartner, FortiProtect, FortiReporter, FortiResponse, FortiShield, FortiVoIP, and FortiWiFi are
trademarks of Fortinet, Inc. in the United States and/or other countries. The names of actual companies
and products mentioned herein may be the trademarks of their respective owners.
Table of Contents
nl
y
ie
w
MODULE 1 ............................................................................................................................... 9
ev
rR
Fo
MODULE 2 ............................................................................................................................. 21
Lab 1: Status Monitor and Event Log ................................................................................................................................. 21
Exercise 1 Exploring the GUI Status Monitor ............................................................................................................................... 21
Exercise 2 Event Log and Logging Options ................................................................................................................................... 23
Lab 2: Remote Monitoring ..................................................................................................................................................... 25
Exercise 1 Remote Syslog Logging and SNMP Monitoring ..................................................................................................... 25
MODULE 3 ............................................................................................................................. 28
Lab 1: Firewall Policy .............................................................................................................................................................. 28
Exercise 1 Creating Firewall Objects and Rules .......................................................................................................................... 28
Exercise 2 Policy Action ......................................................................................................................................................................... 30
Exercise 3 Configuring Virtual IP Access ........................................................................................................................................ 31
Exercise 4 Configuring IP Pools .......................................................................................................................................................... 34
Lab 2: Traffic Log ...................................................................................................................................................................... 36
Exercise 1 Enabling Traffic Logging ................................................................................................................................................. 36
Exercise 2 Device Policies ..................................................................................................................................................................... 37
Page |1
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
Table of Contents
MODULE 4 ............................................................................................................................. 42
Lab 1: User Authentication .................................................................................................................................................... 42
Exercise 1 Identity-based Firewall Policy ...................................................................................................................................... 42
nl
y
MODULE 5 ............................................................................................................................. 44
MODULE 6 ............................................................................................................................. 51
ie
w
ev
MODULE 7 ............................................................................................................................. 54
rR
MODULE 8 ............................................................................................................................. 57
Fo
MODULE 9 ............................................................................................................................. 59
Lab 1: Web Filtering................................................................................................................................................................. 59
Exercise 1 FortiGuard Web Filtering................................................................................................................................................ 59
MODULE 10 ........................................................................................................................... 63
Lab 1: Application Identification ........................................................................................................................................ 63
Exercise 1 Creating an Application Control List .......................................................................................................................... 63
Page |2
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
This section provides details of the virtual lab environment that will be used for the hands-on labs in
this course. Steps are included for connecting to the virtual environment along with troubleshooting
tips to help students easily navigate the lab configuration.
ev
ie
w
Alert: The following section is only applicable to the Fortinet hosted virtual lab
environment. Please ignore this section if you are using an alternate classroom lab
environment unless otherwise directed by your trainer. If you are uncertain, consult your
trainer to find out which lab setup documentation you must follow.
Fo
rR
The network diagram below shows the configuration of the virtual environment that students will use
in the course.
Page |3
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
1. Run the TrueLab System Checker to verify the compatibility of your computer with the virtual
lab environment.
nl
y
http://truelab.hatsize.com/syscheck/frankfurt/
APAC:
ie
w
http://truelab.hatsize.com/syscheck/singapore/
Click Run if a security warning window appears.
Fo
rR
ev
The TrueLab System Checker will determine whether a connection can be established from
the PC to the TrueLab environment. It can also help troubleshoot connectivity problems
related to the Java Virtual Machine, company firewall, or proxy server.
If the PC is successfully able to connect to the TrueLab virtual lab environment a Success
message will be displayed.
Page |4
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
If a status of Failed is displayed, verify the on-screen messages to identify potential problem
areas or click the Troubleshooter link to help diagnose any problems that were encountered.
For assistance with troubleshooting speak to your instructor.
2. If a status of SUCCESS is displayed, log in to the virtual lab portal by browsing to the
following URL:
nl
y
Americas:
rR
ev
ie
w
http://remotelabs.training.fortinet.com/
EMEA:
Fo
http://virtual.mclabs.com/
Enter the username and password provided by the instructor and click LOGIN.
3. Select the time zone for your location from the drop-down menu and click UPDATE.
By selecting the proper time zone you ensure that the class schedule is accurate.
Page |5
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
4. The virtual lab Java applet is launched. Select a resolution for the applet and click Open to
access the Windows 2003 Server device in the virtual lab environment. This will serve as the
primary student machine for the classroom exercises.
Note: If for any reason the connection to the virtual Windows 2003 Server is lost, regain
access by selecting Operations > Disconnect and then Operations > Connect to Primary from
the menu.
Fo
rR
ev
ie
w
nl
y
The instructor will provide a description of each of the virtual systems available to you in the
virtual lab environment.
Page |6
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
Troubleshooting Tips
It is not recommended to connect to the virtual lab environment using a wireless (Wi-Fi)
connection or a VPN tunnel. For optimal performance, connect to the lab environment
through a dedicated LAN connection.
nl
y
Ensure that the company network or firewall policies are not blocking Java applets.
Students should ensure that the following settings are configured on their computer:
Screen savers should be disabled on the computer
ie
w
In the Java Control Panel (located in the Windows Control Panel) ensure that Java
console is set to Show console. It is recommended that the Java console be left open
as it often provides useful logs for troubleshooting.
ev
If you get disconnected unexpectedly from any of the virtual machines (or from the virtual
lab portal) please reattempt a connection. If unable to reconnect repeatedly after multiple
attempts, please notify the instructor.
rR
If during the labs, particularly when reloading configuration files, you see a message
similar to the one shown below, go to the console and enter the following CLI command:
Fo
execute update-now
This message indicates that the FGT VM is waiting for a response from the authentication
server. The command execute update-now will resend the request and force a response.
Page |7
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
rR
ev
ie
w
nl
y
The following diagram illustrates the classroom network configuration that will be used for the labs in
this course. Each student has an identical lab environment and has full control of their lab devices.
Fo
Page |8
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
ie
w
nl
y
This first lab will provide an initial orientation to the CLI and administrative GUI and will guide the
student through the basic setup of the FortiGate unit. This lab will demonstrate how to properly
backup and restore a configuration file, as well as manipulate administrative access to a FortiGate
unit.
rR
ev
Fo
Page |9
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The steps below only need to be performed if your virtual lab set-up has been started from a blank
FortiGate image. Before proceeding, please check with your instructor to confirm if these steps are
required for your particular classroom lab configuration.
1. Connect to the console of the Student FortiGate device (in the virtual lab applet, go to
Operations > Connect to Secondary > Student) and at the login screen, enter the default
username of admin (all lowercase) and leave the password blank.
ie
w
2. To access the Student FortiGate device using the GUI, you must first modify the port3
interface settings by executing the following CLI commands:
conf system interface
edit port3
ev
set ip 10.0.1.254/24
set allowaccess http
rR
end
You have now configured the port3 interface with a proper IP address and device access
settings.
Fo
4. Open a web browser and enter the following URL to access the GUI for the Student
FortiGate device:
http://10.0.1.254
Accept the FortiGate units self-signed certificate or security exemption if a security warning
appears.
HTTPS is the recommended protocol for administrative access to the FortiGate unit. Other
available protocols include SSH, PING, SNMP, HTTP and Telnet.
Note: To access the FortiGate GUI using a standard web browser, cookies and JavaScript
must be enabled for proper rendering and display of the graphical user interface.
P a g e | 10
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
The login page of the Student FortiGate device should now be displayed. Please do not log
in at this point. You will have the opportunity to explore the FortiGate units GUI in a later
exercise.
If you are not presented with a login page, check with your Instructor before proceeding.
nl
y
5. Connect to the console of the Remote FortiGate device (in the virtual lab applet, go to
Operations > Connect to Secondary > Remote) and at the login screen, enter the default
username of admin (all lowercase) and leave the password blank.
ie
w
edit port4
6. Enter the following CLI commands to set the port4 IP address and access control settings for
your device.
set ip 10.200.3.1/24
ev
end
rR
7. You will also need to set a route to allow connections from your remote Windows Server host.
Execute the following commands to set this static route. (Routing will be explained in more
detail in a later section.)
conf route static
Fo
edit 0
P a g e | 11
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
In this exercise, students will be introduced to the FortiGate units command line interface (CLI).
nl
y
1. Connect to the console of the Student FortiGate device and at the Fortigate-VM prompt, and
at the login screen log in with the default username of admin (all lowercase) and no
password.
2. Type the following command to display status information about the FortiGate unit:
get system status
The output displays the FortiGate unit serial number, firmware build, operational mode, and
additional settings.
ie
w
Confirm that the firmware build is the correct version for this class.
3. Type the following command to see a full list of accepted objects for the get command:
get ?
ev
Fo
rR
At the --More-- prompt in the CLI, press the spacebar to continue scrolling or <enter> to
scroll one line at a time. Press <q> to exit.
Depending on objects and branches used with this command, there may be other subkeywords and additional parameters to enter.
4. Press the up arrow key to display the previous get system status command and try
some of the control key sequences that are summarized below.
Previous command
up arrow, or CTRL+P
Next command
Beginning of line
CTRL+A
End of line
CTRL+E
CTRL+B
CTRL+F
CTRL+D
CTRL+C
Clear screen
CTRL+L
CTRL+C is context sensitive and in general aborts the current command and moves up to
the previous command branch level. If already at the root branch level, CTRL+C will force a
logout of the current session and another login will be required.
P a g e | 12
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
5. Type the following command and press the <tab> key 2 or 3 times.
execute <tab>
The command displays the list of available system utility commands one at a time each time
the <tab> key is pressed.
6. Type the following command to see the entire list of execute commands:
nl
y
execute ?
7. Enter the following CLI commands and compare the available keywords for each one:
config ?
show ?
ie
w
config begins the configuration mode while show displays the configuration. The only
difference is show full-configuration. The default behavior of the show command is
to only display the differences from the factory-default configuration.
ev
8. Enter the following CLI commands to display the FortiGate units internal interface
configuration settings and compare the output for each of them:
show system interface port3
rR
Fo
Only the characters shown in bold type face need to be typed, optionally followed by <tab>,
to complete the command key word. Use this technique to reduce the number of keystrokes
to enter information. CLI commands can be entered in an abbreviated form as long as
enough characters are entered to ensure the uniqueness of the command keyword.
P a g e | 13
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
From the Windows Server, you first will need to connect to each FortiGate device and restore the
configuration files that are needed to complete the upcoming exercises.
Fo
rR
ev
ie
w
nl
y
1. From the GUI on the Student FortiGate device go to System > Dashboard > Status. Under
System Information, click Restore.
2. Browse the Desktop and navigate to the Resources > Module1 folder.
P a g e | 14
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
After restoring the configuration the FortiGate unit will automatically reboot and the following
dialog is displayed:
nl
y
The length of the boot process is affected by how complex the configuration is. The more
complicated the configuration, the longer it will take to parse it and complete the boot process.
Most configurations take less than 1 minute to complete the reboot process.
3. Reconnect to the GUI on the Student FortiGate device and verify the restored configuration.
ie
w
Go to System > Network > Interface and check your network interfaces.
Go to Router > Static > Static Route and check your default route.
ev
4. Execute the following steps to check and test the Student and Remote FortiGate device DNS
configuration. This configuration will be used to simplify access to the lab devices.
Go to System > Admin > Settings and under Display Options on GUI verify that DNS
Database is selected.
rR
Go to System > Network > DNS Server and review the student and remote DNS
zones.
Fo
In the student DNS zone, verify the IPv4 Address records and Pointer records for the
Student FortiGate device and the Windows Server (10.0.1.10).
In the Remote DNS zone, check the IPv4 Address records and Pointer records for the
Remote FortiGate device and the Windows host (10.0.2.10).
5. From a DOS command prompt on the virtual Windows Server, execute the following
commands to verify the DNS lookup functionality. DNS requests are being sent to port3, and
recursive DNS requests are allowed on this interface.
nslookup server.student.lab 10.0.1.254
nslookup fgt.student.lab 10.0.1.254
nslookup pc.remote.lab 10.0.1.254
nslookup fgt.remote.lab 10.0.1.254
P a g e | 15
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
6. In a web browser on the virtual Windows Server, connect to the following web pages to verify
that the GUI of the Student and Remote FortiGate devices can be accessed using their DNS
hostnames:
http://fgt.student.lab
nl
y
http://fgt.remote.lab
ie
w
1. Connect to the GUI on the Student FortiGate device by accessing the URL:
https://fgt.student.lab
Fo
rR
ev
2. Go to System > Dashboard > Status and under System Information, click Backup.
Select Encrypt configuration file and enter the password: fortinet. Click Backup and
save the encrypted configuration file to the Desktop with the filename student-initial-enc.conf.
Caution: When backing up the FortiGate units configuration, be sure to use a naming
convention that you understand and which identifies both the date and the device
information. Every time that you log in and make changes to your device (even if the
change seems minor or insignificant), you should ALWAYS make a backup of the
configuration file. This will always be the best form of protection against problems.
P a g e | 16
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
3. Next try restoring the encrypted configuration file. Browse the Desktop and navigate to the
file student-initial-enc.conf and click Restore.
This time you will need to enter the password fortinet as this file is encrypted.
nl
y
Using WordPad, open the file student-initial.conf. In another instance of WordPad, open the
file remote-enc.conf and compare the details in both.
Fo
rR
ev
ie
w
Note: In both the normal and encrypted configuration the top of the file acts as a
header, describing the firmware and model information this configuration belongs
to.
P a g e | 17
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The aim of this lab will be to demonstrate how to create and modify administrative access
permissions.
ie
w
Fo
rR
ev
1. From the GUI on the Student FortiGate device, go to System > Admin > Settings and select
Enable Password Policy.
Configure the password policy using the following settings:
Minimum length:
Must Contain:
Enable
1 Upper Case Letter
1 Numerical Digit
Enable
90 days
Leave all other parameters at their default settings and click Apply.
P a g e | 18
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
2. Log out of the GUI then log back in again and you will be prompted to enter a new
administrator password. Enter a new password that meets the requirements configured
above.
nl
y
3. Next, go to System > Admin > Admin Profile and create a new Admin profile called
UTM_Admin_Profile. Set UTM Security Configuration to Read-Write and set all other
permissions to Read Only.
4. Go to System > Admin > Administrators to create a new Admin user. Set Admin Profile to
the new profile you created in the previous step. By doing this, you are limiting this Admin
users access so that they will only able to modify and create UTM profiles.
ie
w
Note: Administrator names and passwords are case-sensitive. You cannot include the
< > ( ) # characters in an administrator name or password. Spaces are allowed, but
not as the first or last character. Spaces in a name or password can be confusing and
require the use of quotes to enter the name in the CLI.
To view the configuration for administrative users and profiles, type the following CLI
commands:
ev
rR
5. Log out of the GUI on the Student FortiGate device and log back in using the UTM-only
Admin user created earlier. The warning message You do not have permission to access
the requested page is displayed. Close the No Access dialog box.
Fo
6. Test this administrators access by attempting to create or modify various settings on the
Student FortiGate device.
For convenience in the labs, the admin password will not be set in the configuration files
used in the subsequent modules.
P a g e | 19
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
1. On the Remote FortiGate device, edit the admin account and enable the setting Restrict this
Admin Login from Trusted Hosts Only. Set Trusted Host #1 to the address 10.0.2.0/24.
nl
y
Now, try connecting to the GUI of the Remote FortiGate device again. What is the result this
time?
Because you are connecting from the 10.200.1.1 address (because of NAT on the
Student FortiGate device) you should notice that you are no longer able to connect to the
device since restricting the connecting source IP using Trusted Hosts.
ie
w
2. Attempt to ping the IP address 10.200.3.1. You should note that the ping no longer
responds. This type of access is also affected by the restriction on source IP which we have
configured above.
ev
3. Go to the console of the Remote FortiGate device and enter the following CLI commands to
add 10.200.0.0/16 as the second trusted IP address (Trusted Host #2) of the admin
account:
conf sys admin
rR
edit admin
set trusthost2
Fo
end
4. Test the GUI and ping access again to the IP address 10.200.3.1. You should now be
able to connect to the GUI of the Remote device and ping it as well.
5. Go to System > Dashboard > Status and under System Information, click Details for Current
Administrator.
The administrators currently logged in to the FortiGate unit are displayed.
6. By default, an administrator has a maximum of three attempts to log in to their account
before they are locked out for 60 seconds. The source IP address is taken into account by
the attempt counter.
The number of login attempts and the lockout period can be configured through the CLI. To
help improve the overall password security, the maximum number of attempts can be
decreased and the lockout timer can be increased using the following CLI commands:
config system global
set admin-lockout-threshold 2
set admin-lockout-duration 100
end
P a g e | 20
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The aim of this lab is for students to work with the event log and monitoring on a FortiGate unit.
ev
ie
w
Fo
rR
1. From the GUI of the Student FortiGate device, go to System > Dashboard > Status and
locate the System Resources widget.
2. Some widgets are not displayed on the dashboard by default. Click Widget to display the list
of widgets available to add to the dashboard. Click the Log and Archive Statistics widget from
the pop-up window to add it to the dashboard.
P a g e | 21
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
3. Hover the mouse over the title bar of the System Resources widget and click Edit to create a
custom widget.
Time Period:
ev
View Type:
ie
w
Last 60 minutes
rR
A line chart appears in a new custom System Resource History widget showing a trace of
past CPU and memory usage.
The refresh rate of this window is automatically set to 1/20 of the time period (interval)
configured.
Fo
4. The Alert Message Console widget displays recent system events, such as system restart
and firmware upgrade.
Hover the mouse over the title bar of the Alert Message Console widget and click History to
view the entire message list.
6. Next add the Top Sessions widget on your new dashboard. Click the edit icon in the title bar
of the Top Sessions widget and observe the different ways in which Top Sessions can be
reported. For example, by top destination address, top applications etc. You can also select
to display the top sessions by Source and Destination interfaces. Create your own
customized Top Sessions widget and examine the sessions that are listed.
nl
y
7. Test the functionality of the refresh, page forward, and page back icons in this window. You
may need to generate some additional traffic in order to properly test these functions.
ev
ie
w
8. Click Dashboard and select Reset Dashboards to re-display the default dashboard.
1. In this lab we will be working with local logging to the disk. On a new device you will first
need to format the hard drive.
rR
From the Student FortiGate CLI, execute the following command to check the system status.
get system status
Fo
Verify the Log hard disk status. If it is set to Available proceed to Step 2, if the status
appears as Need format, enter the following command:
execute formatlogdisk
2. Once the system has restarted, check the log disk settings by executing the following
command:
config log disk setting
get
You should observe that the status is enabled and SQL logging is enabled for all log types.
3. Repeat the previous steps on the Remote FortiGate device.
4. Return to the Student FortGate device and log out of the GUI. When logging back in, use an
incorrect password once and then use the correct password.
Log back in again with the correct password then go to Log & Report > Event Log > System
and examine the log to find the bad password event.
5. Go to Firewall Objects > Address > Address, and create a new firewall address in the
configuration. For example, set Type to FQDN and set the FQDN value to
www.fortinet.com.
P a g e | 23
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
6. Next go to Log & Report > Event Log > System and review the log entries.
rR
Click Apply.
ev
ie
w
nl
y
7. Go to Log & Report > Log Config > Log Setting and uncheck the option System activity event.
Fo
Different types of log entries fall into different categories. Only enable logging for the
activity(s) that you need to monitor. Otherwise your logs will become cluttered with
information that is of no use to you.
8. Go to Firewall Objects > Address > Address and create another firewall address entry. Go to
Log & Report > Event Log > System and review the log entries again.
Note that the entries are no longer visible for this activity. With this option deselected in the
Event Logging settings, you will no longer see entries in the log for Admin users logging
on/off or making changes to the units configuration. Other types of log entries will still appear.
9. Go to Log & Report > Log Config > Log Settings and re-enable System activity event.
P a g e | 24
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The aim of this lab is for students to set up logging to a remote device and monitoring of the
FortiGate units behavior. It can be advantageous to use remote monitoring instead of local
monitoring in order to reduce resource usage. For example, while the GUI widgets provide useful
displays of your system information, they also carry a significant resource cost and should be used
sparingly.
ev
ie
w
Fo
rR
The LINUX host in your student lab environment has been pre-configured for you to allow remote
syslog.
1. From the CLI on the Student FortiGate device enter the following commands to set up
logging to the syslog server:
conf log syslogd setting
set status enable
set facility local6
set server 10.200.1.254
end
2. To generate a few sample test log messages enter the command:
diag log test
3. Repeat the previous steps from the CLI on the Remote FortiGate device.
P a g e | 25
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
Fo
rR
ev
ie
w
nl
y
4. From the virtual Windows Server desktop launch the putty.exe application and open an SSH
session to the LINUX host (10.200.1.254).
P a g e | 26
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
Click OK.
ie
w
nl
y
8. Create a new SNMP v3 security name using the settings displayed below. Set the Auth
password to fortinet.
9. Go to System > Network > Interface and edit port1. Enable SNMP under Administrative
Access settings.
ev
10. Leave the SSH window open that is currently running the Tail command and open a new
SSH connection to the LINUX host.
rR
Fo
P a g e | 27
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The aim of this lab is for students to work with firewall policies and examine the FortiGate unit
behavior when policies are re-ordered.
ie
w
ev
Fo
rR
1. From the Windows Server, you first will need to connect to the Student FortiGate device and
restore the configuration file that is needed for this lab.
Connect to the GUI on the Student FortiGate device (10.0.1.254) and restore the following
configuration file: Resources\Module3\student-policy.conf.
The Student FortiGate device will reboot.
2. From the GUI on the Student FortiGate device, go to Firewall Objects > Address > Address
and create the following address object:
Address Name:
STUDENT_INTERNAL
Type:
Subnet
Subnet/IP Range:
10.0.1.0/255.255.255.0
Interface :
Any
P a g e | 28
3. The unrestricted port3port1 policy will need to be temporarily disabled in the policy list. To
do this, go to Policy > Policy > Policy, right-click the unrestricted port3port1 policy and
select Status > Disable.
4. Next click Create New to add a new firewall policy to provide general Internet access from
the internal network. Configure the following settings:
Firewall
Policy Subtype:
Address
Incoming Interface:
port3
Source Address:
STUDENT_INTERNAL
Outgoing Interface:
port1
Destination Address:
all
ie
w
always
Schedule:
ev
Service:
Action:
nl
y
Policy Type:
ACCEPT
Enabled
Enabled
Enabled
Comments:
Fo
rR
Enable NAT:
When creating firewall policies, keep in mind that the FortiGate device is a stateful firewall,
therefore, a firewall policy only needs to be created for the direction of the originating traffic.
5. From the virtual Windows Server desktop, open a web browser and connect to various
external web servers.
6. On the Student FortiGate device go to Policy > Policy and right-click any of the column
headings. Select Column Settings > Count to display a packet and bytes count for each rule
in the policy list display. Move this column accordingly for easier viewing.
P a g e | 29
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
7. From the CLI, enter the following command to see the source NAT action.
#get system session list
Sample Output:
STUDENT # get sys session list
SOURCE-NAT
10.200.1.1:64133
10.200.1.1:64097
10.200.1.1:64126
10.200.1.1:64124
10.200.1.1:64122
10.200.1.1:64024
10.200.1.1:64128
10.200.1.1:64095
DESTINATION
10.0.1.254:22
72.30.38.140:80
69.171.228.70:80
74.125.228.92:80
74.125.228.92:80
66.94.245.1:80
10.200.1.254:22
80.239.217.66:80
74.125.227.24:80
nl
y
SOURCE
10.0.1.10:3677
10.0.1.10:3717
10.0.1.10:3681
10.0.1.10:3710
10.0.1.10:3708
10.0.1.10:3706
10.0.1.10:3608
10.0.1.10:3712
10.0.1.10:3679
EXPIRE
3600
3587
3570
3577
3587
3587
2274
3587
3566
DESTINATION-NAT
-
ie
w
PROTO
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
rR
ev
Note that the new source address being applied is that of the destination interface
port1(10.200.1.1).
Fo
1. Use the same steps you performed earlier to create a second firewall policy. Configure the
following settings:
Policy Type:
Firewall
Policy Subtype:
Address
Incoming Interface:
port3
Source Address:
STUDENT_INTERNAL
Outgoing Interface:
port1
Destination Address:
Schedule:
always
Service:
PING
Action:
DENY
Enabled
P a g e | 30
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
2. From the Windows Server, open a DOS command prompt and ping the port1 gateway as
follows.
ping t 10.200.1.254
nl
y
Provided you have not changed the rule ordering, the ping should still work as it matches the
ACCEPT policy and not the DENY policy just created. This demonstrates the behavior of
policy ordering. The second policy was never checked because the traffic matched the first
policy.
3. From the GUI on the Student FortiGate device, go to Policy > Policy > Policy and right-click
any of the column headings. Select Column Settings > ID. Move this column accordingly for
easier viewing. By default only the sequence number of the firewall policy is displayed in the
GUI.
ie
w
4. Next, click the Seq.# for the DENY policy created previously and drag this policy upwards to
position it before the General Internet access policy.
Fo
rR
ev
5. Return to the Windows Server and examine the DOS command prompt window still running
the continuous ping. You should observe that this traffic is now blocked.
In this exercise, a virtual IP address will be configured to allow remote Internet connections to
the Windows Server located at 10.0.1.10.
1. Go to Firewall Objects > Virtual IP > Virtual IP and create a new virtual IP mapping with the
following details:
Name:
VIP_WIN2K3
External Interface:
port1
Type:
Static NAT
External IP Address/Range:
10.200.1.200
Mapped IP Address/Range:
10.0.1.10
P a g e | 31
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
2. Next, create a new firewall policy to provide access to the web server. Configure the
following settings:
Firewall
Policy Subtype:
Address
Incoming Interface:
port1
Source Address:
all
Outgoing Interface:
port3
Destination Address:
VIP_WIN2K3
nl
y
Policy Type:
always
Schedule:
ie
w
HTTP
Service:
ACCEPT
Action:
Enable NAT:
Enabled
Disabled (default)
Public access to web server
rR
Comments:
ev
Fo
3. The firewall is stateful so any existing sessions will not use this new firewall policy until they
time out or are cleared. The sessions can be cleared individually from the session widget on
the status page or from the CLI by executing the following:
diag sys session clear
4. Connect to the console of the remote Windows host. (From the virtual lab applet, go to
Operations > Connect to Secondary > WinXP to connect to the console of your WINXP host.)
On the WinXP desktop, open a web browser and access the following URL:
http://10.200.1.200
If the virtual IP operation is successful a web page is displayed.
5. From the CLI on the Student FortiGate device, check the destination NAT entries in the
session table by using the following command:
#get system session list
Sample Output:
STUDENT # get sys session list
PROTO
tcp
EXPIRE SOURCE
SOURCE-NAT
3537
10.200.3.1:62426
DESTINATION
10.200.1.200:80
DESTINATION-NAT
10.0.1.10:80
P a g e | 32
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
6. On the virtual Windows Server desktop open a web browser and connect to a few external
web sites. Now examine the session information again as follows:
#get system session list
Sample Output:
nl
y
SOURCE-NAT
DESTINATION
DESTINATION-NAT
10.200.1.200:3995 66.94.241.1:80
10.200.1.200:3977 72.30.38.140:80 10.200.1.200:3965 184.150.187.83:80 10.200.1.200:3998 74.125.228.92:80 10.200.1.200:3969 69.171.237.16:80 10.200.1.200:4001 208.91.113.80:80 10.200.1.200:3983 216.115.100.102:80 10.200.1.200:3979 216.115.100.103:80 10.200.1.200:3987 216.115.100.102:80 10.200.1.200:3981 216.115.100.103:80 10.200.1.200:3985 216.115.100.102:80 10.200.1.1:64024 10.200.1.254:22 10.200.1.200:3976 72.30.38.140:80 10.200.1.200:3996 184.150.187.99:80 10.200.1.200:3967 74.125.228.65:80 10.200.1.200:3990 216.115.100.103:80 10.200.1.200:3978 216.115.100.103:80 10.200.1.200:3980 216.115.100.103:80 -
ev
ie
w
rR
STUDENT
PROTO
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
Fo
Note that the outgoing connections from the Windows Server are now being NATed with the
VIP address as opposed to the firewall address. This is a behavior of the static NAT VIP.
That is, when SNAT is enabled on a policy, a VIP static NAT takes priority over the
destination interface IP address.
P a g e | 33
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
Currently, all traffic generated from the Windows Server through the Student FortiGate
device has a translated source IP address of 10.200.1.200 because of the static NAT
translation in the VIP.
nl
y
In this exercise, an IP address pool will be applied to a new rule which will override this
behavior.
1. From the GUI on the Student FortiGate device, go to Firewall Objects > Virtual IP > IP Pool
and create a new IP pool using the following settings:
WIN2K3_EXT_IP
External IP Range/Subnet:
10.200.1.100
ie
w
Name:
2. Go to Policy > Policy > Policy, and right-click the outgoing General Internet access policy.
Select Copy Policy then right-click the same policy again and select Paste > Above.
Policy Type:
ev
3. Select the new copy of the General Internet access policy and configure the following
settings:
Firewall
Address
Incoming Interface:
port3
Source Address:
WIN2K3
Fo
rR
Policy Subtype:
Outgoing Interface:
port1
Destination Address:
all
Schedule:
always
Service:
ALL
Action:
ACCEPT
Enabled
Enable NAT:
Enabled
WIN2K3_EXT_IP
Comments:
Click OK to save the policy and verify that you have enabled it.
4. The firewall is stateful so any existing sessions will not use this new firewall policy until they
time out or are cleared. The sessions can be cleared individually from the session widget on
the status page or from the CLI by executing the following:
diag sys session clear
P a g e | 34
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
5. Connect to a few external web sites and then examine the session table to check the source
NAT used. From the CLI on the Student FortiGate device enter the following command to
verify the source NAT IP address:
# get system session list
Sample Output:
nl
y
ie
w
STUDENT
PROTO
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
tcp
Fo
rR
ev
Observe that the source NAT address is now 10.200.1.100 as configured in the VIP pool,
therefore the order of precedence is IP Pool > Static-NAT VIP > Destination Interface.
P a g e | 35
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
ie
w
nl
y
The aim of this lab is to read traffic logs and become familiar with its contents.
rR
ev
Fo
1. Go to Policy > Policy > Policy and click the Seq.# of the DENY policy that you created
previously. Drag this policy to position it BEFORE the Window Server Source NAT Override
policy.
2. Edit the DENY policy and verify that Log Violation Traffic is enabled.
3. From the Windows Server, open a DOS command prompt and ping the port1 gateway as
follows.
ping t 10.200.1.254
Provided you have positioned the rule correctly this traffic should be blocked, and timeout.
4. From the GUI on the Student FortiGate device, go to Log & Report > Traffic Log > Forward
Traffic to examine the log entries. You should observe violation traffic entries.
5. Edit the DENY policy and change the action to ACCEPT.
From the Windows Server, you should observe that the ping now succeeds.
6. From the GUI on the Student FortiGate device, go to Log & Report > Traffic Log > Forward
Traffic.
The log entries will no longer show violation traffic, but summaries of the ping traffic that
passed.
P a g e | 36
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
In this exercise you will create a Firewall policy that uses email captive portal. Once the device is
learnt, access to a test web server should be given to the device
nl
y
1. From the Windows host, you first will need to connect to the Student FortiGate device and
restore the configuration file needed for this exercise.
Restore the following configuration file: Resources\Delta\delta-student-initial.conf.
2. Edit the outgoing port3 to port3 firewall policy using the following settings:
Firewall
Policy Subtype:
Device Identity
Incoming Interface:
Source Address:
Enable NAT:
port3
STUDENT_INTERNAL
port2
ev
Outgoing Interface:
ie
w
Policy Type:
rR
Next click Create New under Configure Authentication Rules and create the following subpolicies:
Fo
Sub-policy 1:
Destination Address:
all
Device:
Linux PC
Schedule:
always
Service:
HTTP
Action:
P a g e | 37
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
Sub-policy 2:
all
Device:
Collected Emails
Schedule:
always
Service:
Action:
ACCEPT
nl
y
Destination Address:
Click OK.
ie
w
3. Use drag-and-drop to reorder the sub-policies. The captive portal policy should be last in the
sub-policy list because this rule should only be matched if the device has not already been
identified.
In this example, the first web traffic from the client matches the email captive portal rule, the
subsequent traffic matches the collected email device object as we now have this information.
Fo
rR
ev
Note when saving this policy you will be informed that device identification will be enabled on
port3.
Click OK.
P a g e | 38
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
ie
w
5. You will now test the device policy on the Student FortiGate device. First execute the
following CLI commands to disable the email DNS check for the captive portal. (This step is
required for the purposes of this lab.)
ev
rR
end
Fo
What happens? Well if you followed the example as given, nothing should happen because
you have only allowed Linux PCs and you are connecting from the Windows PC.
From the CLI use debug flow to confirm this.
diag debug flow filter addr 10.200.1.254
diag debug flow show func en
diag debug flow show cons en
diag debug enable
diag debug flow trace start 20
The following message is displayed: Denied by forward policy check.
P a g e | 39
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
ie
w
nl
y
7. Edit the captive portal sub policy and add Windows PC as a second device type.
ev
rR
9. Go to User & Device > Device > Device Definition and check the new device.
This device is a dynamic device. These devices may update and are stored to the flash to
speed up detection.
Fo
You should observe that you are redirected to the email portal again. Accept the conditions
and enter your email address.
11. Perform a show from the CLI to confirm there are no devices in the configuration file.
show user device
12. From the GUI, go to User & Device > Device > Device Definition and edit your device from
the device list. Add an alias called myDevice. This creates a static device in the configuration
file.
Perform the following show command to confirm that the device now appears in the
configuration file.
show user device
P a g e | 40
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
13. Go to User & Device > Device > Device Group. Note that your device is already a member
of several predefined device groups.
Click Create New and add a new device group called myDevGroup. From the Members
drop-down list, select myDevice.
nl
y
Note that your device is still a member of the predefined groups and is now a member of the
custom group myDevGroup.
14. From your PC, test that you can open an FTP connection to 10.200.1.254.
Open a DOS prompt on your Windows PC. Once you have connected, close the FTP
connection.
15. Now add a sub-policy to your firewall device policy blocking FTP.
ie
w
LINUX_ETH1
Device:
myDevGroup
always
rR
Schedule:
ev
Destination:
FTP
Action:
Deny
Enable
Fo
Service:
Use drag-and-drop to reorder the sub-policies so that this policy is first in the list.
Click OK.
16. From your PC test that you can open an FTP connection to 10.200.1.254.
You should observe that the connection now fails to establish.
View the traffic logs and find the deny entry.
17. Go to one of your Dashboards and add the Device Type distribution widget. Since we only
have a single device to test in our lab environment, the graph is less effective.
P a g e | 41
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
ie
w
nl
y
The aim of this lab is to introduce students to user authentication management on the FortiGate unit.
ev
Fo
rR
1. From the Windows Server, you first will need to connect to the Student FortiGate device and
restore the configuration file that is needed for this lab.
Connect to the GUI on the Student FortiGate device (10.0.1.254) and restore the following
configuration file: Resources\Module4\student-auth.conf.
The Student FortiGate device will reboot.
2. When the device has rebooted review the user configuration for this lab.
Go to User & Device > User > User to review the local user settings
Go to User & Device > User Group > User Group to review the user group configuration.
P a g e | 42
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
3. On the virtual Windows Server desktop, open a web browser and connect to a new web site.
At the login prompt, enter the following credentials:
Username:
student
Password:
F0rtinet
nl
y
You should observe that after successful authentication, you are redirected to your
destination web site.
4. From the GUI on the Student FortiGate device go to Policy > Policy > Policy and review the
outgoing firewall policy with authentication configured.
What happens?
ie
w
5. Next, open a putty.exe session and try to ping or connect via SSH to 10.200.1.254. Log in
as root with the password: password.
ev
You should observe that this fails even though there is an accept rule for this traffic. This
highlights an important behavior of identity policies. The service becomes a permission and
not a selector, therefore, in our example the identity policy matches all outgoing traffic
regardless of service. The service is then allowed if it is set for the user.
rR
There are two ways to correct this. Either add ALL_ICMP and SSH to the identify policy rule
for the training user group, or move the regular policy before the identity policy.
Make your configuration change and retest.
Fo
6. Go to User & Device > Monitor > Firewall to view the details of the authenticated user along
with the policy used to authenticate this user.
7. Next go to Log & Report > Event Log > User and then Log & Report > Traffic Log > Forward
Traffic.
Locate the log messages for the firewall policy authentication events. The details for the entry
are displayed in the lower pane of the Event Log window.
Notice that the users name student is now included in the log messages.
8. From the CLI, view the IP addresses and users which have successfully authenticated to the
FortiGate unit with the following command:
diagnose firewall iprope authuser
Clear all authenticated sessions with the following command:
diagnose firewall iprope resetauth
P a g e | 43
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The aim of this lab for students to work with and manage user groups and portals for the SSL VPN.
ev
ie
w
Fo
rR
1. From the Windows Server, you first will need to connect to the Student FortiGate device and
restore the configuration file that is needed for this lab.
Connect to the GUI on the Student FortiGate device (10.0.1.254) and restore the following
configuration file: Resources\Module5\student-ssl.conf.
The Student FortiGate device will reboot.
2. When the device has rebooted review the SSL VPN configuration access for this lab. First
look at the firewall polices. You will find a port1port3 policy for SSL VPN. This policy also
has sub-policies. Expand this policy in order to view the sub-policies.
3. Open this SSL VPN policy and look at the objects making up this policy. Observe the Policy
Type of VPN and the Policy Subtype of SSL-VPN. Also note the Destination address and the
SSL-VPN Authentication Rules.
Open the first rule (sub-policy), and notice that this allows users in the training group to
access the web-access SSL-VPN portal.
P a g e | 44
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
4. To observe the effect of this policy you will now access the SSL VPN. On the virtual external
Windows host (WINXP) desktop, open a web browser and access the SSL VPN by browsing
to the following URL: https://10.200.1.1.
Username:
student
Password:
F0rtinet
nl
y
Accept the security warnings for the self-signed certificate and log in using the following
credentials:
You should notice that you are successfully able to log in however, the web portal is currently
in default settings. We will now configure the web-access portal which is selected in the SSL
VPN policy. Log out and return to your Windows Server host.
Category:
Type:
rR
Name:
ev
ie
w
5. Go to VPN > SSL > Portal and from the drop-down list displayed in the top right hand corner,
select web-access to edit this portal. Verify that Include Bookmarks is selected and then
create the following bookmarks in the table for the internal server.
Location:
Test
HTTP/HTTPS
HTTP/HTTPS
10.0.1.10
Fo
Click OK.
Test
Name:
RDP
Type:
RDP
Location:
10.0.1.10
Click OK. Add a Portal Message then click Apply to save the changes. Select View Portal to
review your changes.
6. Test the SSL VPN access again from the external Windows host (WINXP) by browsing to:
https://10.200.1.1
You should now observe that you have two book marks listed.
P a g e | 45
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
7. Select the HTTP/HTTPS bookmark and examine the items listed below to understand how
the web access functions.
Note the URL of the web site in the browser address bar:
https://10.200.1.1/proxy/http/10.0.1.10/
nl
y
The first part of the address is the encrypted link to the FortiGate SSL VPN gateway:
https://10.200.1.1/
The second part of the address is the instruction to use the SSL VPN HTTP
proxy: .../proxy/http...
ie
w
The final part of the address is the destination of the connection from the HTTP
proxy: .../10.0.1.10/
In this example, the connection is encrypted up to the SSL VPN gateway. The connection to
the final destination from the HTTP proxy is in clear text.
ev
8. Return to the virtual Windows Server device and from the GUI on the Student FortiGate
device, go to VPN > Monitor > SSL-VPN Monitor. Locate the details of the SSL VPN
connection.
rR
Fo
10. From the external Windows XP host, log out of the SSL VPN connection. Return to the log
and look for the SSL tunnel shutdown message.
P a g e | 46
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
11. The firewall policy is required for the SSL VPN access. Find the firewall policy for SSL VPN
access and examine its components.
Note from the policy list that this policy has a sub-policy. Edit this policy to view its contents.
VPN
Policy Subtype:
SSL-VPN
Incoming Interface:
port1
Remote Address:
all
Local Interface:
port3
WIN2K3
Disabled
ie
w
nl
y
Policy Type:
ev
The policy is incoming, that is from the external network to the internal network.
The policy subtype is SSL VPN which indicates further processing besides only accepting the
traffic.
Fo
rR
Under Configure SSL-VPN Authentication Rules, edit the first rule to view its contents.
You will notice that this rule contains many settings including User(s), Schedule, Service and
SSL-VPN Portal. Select Cancel to close the edit window for this sub-policy.
In the next exercise, we will be adding on to this policy to allow tunnel access.
P a g e | 47
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
In this exercise you will edit the current SSL policy adding a new sub-rule for a second user
configured for tunnel mode.
nl
y
1. Edit the SSL VPN policy and under Configure SSL-VPN Authentication Rules, create a new
sub-policy for a full-access portal using the following settings:
training
Schedule:
always
Service
ALL
SSL-VPN Portal:
full-access
Group(s):
ie
w
When you have added this sub-policy select OK to save the changes.
ev
2. To observe the effect of this sub-policy you will now access the SSL VPN again. From the
virtual external Windows host (WINXP) desktop, open a web browser and access the SSL
VPN by browsing to the following URL:
https://10.200.1.1
rR
When prompted, log in to the SSL VPN using the following credentials:
student
Password:
F0rtinet
Fo
Username:
P a g e | 48
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
4. In the web browser on the virtual remote Windows host, connect to the SSL VPN portal once
again at the following address:
https://10.200.1.1
Note that you may need to clear the web browsers cache if the login window is not displayed.
nl
y
student2
Password:
F0rtinet2
You should now observe that the portal established is the full-access portal.
ie
w
Note: If using the SSL VPN client available with FortiClient, you do not need to log
in via the portal.
ev
5. In the Tunnel Mode panel, click Connect. You should see a link status of UP and the bytes
sent and received incrementing.
rR
6. On the virtual remote Windows host, open a DOS command prompt and perform the
following:
ipconfig
Fo
Note the low metric routes and observe that there is a route to 10.0.1.10. Where did this
come from?
Run a continuous ping to 10.0.1.10 as follows.
ping t 10.0.1.10
P a g e | 49
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
7. From the GUI on the Student FortiGate device observe the following:
VPN > Monitor > SSL-VPN Monitor shows client connections and the IP allocated to
the tunnel connection
nl
y
8. In the firewall policy list, modify the column settings to show Count so that you can see the
packets and bytes per policy (click any of the column headings and select Column Settings >
Count). Move this column accordingly for easier viewing.
Notice that there is traffic associated with the incoming rule from the ssl.<vdom name>
interface. This rule is created automatically. This traffic is the incoming traffic from your SSL
VPN client.
ie
w
9. Go VPN > SSL > Portal to access the SSL VPN portal configuration. Edit the full-access
portal.
Within the Enable Tunnel Mode options, note the IP Pool used which refers to a firewall
address object.
ev
10. Go to Firewall Objects to look up that firewall address object. What are the values of that
object?
rR
The object defines an address range that matches your assigned address, so this is how IP
addresses are configured and assigned to SSL VPN clients.
Where does the route to 10.0.1.10 come from?
Fo
HINT: Look at the Destination address of the address of the SSL VPN policy.
You will observe that the address object values for WIN2K3 are 10.0.1.10/32, so this is
where the SSL VPN client route came from.
With this present configuration, the SSL VPN client is split tunneling. This means that only
traffic to the specific destination behind the firewall is tunneled, and all other traffic goes to
the default gateway.
What configuration change would you need to make to give the client a default route into the
tunnel?
Disable split tunneling in the full-access portal which means a default route is pushed to the
client forcing all traffic into the tunnel.
P a g e | 50
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The aim of this lab for students to configure an IPSec VPN on the FortiGate device using both
interface-based and policy-based modes.
ie
w
rR
ev
Fo
1. From the Windows Server, you first will need to connect to the Student and Remote
FortiGate devices and restore the configuration files that are needed for this lab.
Connect to the GUI on the Student FortiGate device (10.0.1.254) and restore the
following configuration file: Resources\Module6\student-ipsec.conf.
The Student FortiGate device will reboot.
Connect to the GUI on the Remote FortiGate device (10.200.3.1) and restore the
following configuration file: Resources\Module6\remote-ipsec.conf.
The Remote FortiGate device will reboot.
2. When the Student FortiGate device has rebooted, open a DOS command prompt from the
virtual Windows Server and run a continuous ping to the remote Windows XP host as
follows:
ping
-t 10.0.2.10
P a g e | 51
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
3. From the GUI on the Student FortiGate device, go to VPN > Monitor > IPsec Monitor and
examine the tunnel status.
You should observe a tunnel named remote with the destination 10.200.3.1 and the status
is currently up. This is the tunnel that is established to the Remote FortiGate device.
nl
y
4. From the Student FortiGate device review the firewall policy. Modify the column settings to
show Count so that you can see the packets and bytes per policy.
Observe that the counter is incrementing for the port3 > remote policy.
ie
w
Go to System > Network > Interface and note the blue arrow head associated with port1. If
you expand this you will be able to see the remote interface and the type for this interface
which is set to Tunnel.
5. Go to VPN > IPsec > Auto Key (IKE) and review the IPsec configuration. Note the Phase 1
and Phase 2 IKE objects.
ev
Edit the Phase1 IKE object remote. Select Advanced to view all the settings. Note that IPsec
Interface Mode is selected.
rR
The Phase1 IKE object is the IPsec interface referenced in the interface list and firewall
policy. How is the traffic getting to this policy?
Fo
Traffic arrives at the FortiGate unit on the ingress interface. For new connections, a routing
lookup is performed to select the egress interface and gateway, and then there is a lookup in
the firewall policy to find a matching rule. It is the routing lookup that selects the egress, and
therefore, the remote interface is selected in this case. So a route is driving the traffic to the
IPsec interface.
6. Go to Router > Monitor and view the current routing table. You will observe a static route to
the destination 10.0.2.0/24 pointing to the remote interface.
This is an example of the route-based VPN configuration. The alternative is the policy base
VPN which we will review next.
Generally, the route-based VPN is the preferred approach however there are a few
exceptions where you would need to use the policy-based VPN. These will be discussed
later.
7. Open a web browser on the Windows Server and connect to the GUI on the Remote
FortiGate device.
8. Go to VPN > Monitor > IPsec Monitor and examine the tunnel status from the Remote
FortiGate device. You should observe a tunnel named student with the destination
10.200.1.1 and the status is up.
This is the tunnel that is established to the Student FortiGate device.
P a g e | 52
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
9. Still on the Remote FortiGate device, go to System > Network > Interface and note there is
no tunnel sub-interface for port4.
10. Go to Route > Monitor and view the current routing table. You will observe that there is no
route to the 10.0.2.0/24 destination, there is only a default route.
How is the traffic entering the tunnel then?
nl
y
11. Review the firewall policy that exists on the Remote FortiGate device. Note that there is a
policy from port6 to port4 for address 10.0.2.0/24 to address 10.0.1.0/24 with action
IPsec.
ie
w
The policy action is IPsec, and it uses the tunnel student. It also has permissions to allow
outbound and allow inbound. We will look at these settings later.
How is the traffic matching this policy?
ev
On the Student FortiGate device, a static route was sending traffic to the IPSec interface.
Here there is no static route and the traffic is being sent to the tunnel using the policy action,
hence policy-based.
rR
The IPSec policy matches traffic from 10.0.2.0/24 to 10.0.1.0/24 and forwards it the
tunnel student.
Fo
12. From the Remote FortiGate device, go to VPN > IPsec > Auto Key (IKE) and review the
IPSec configuration. Note the Phase 1 and Phase 2 IKE objects.
13. Edit the Phase1 IKE object remote and select Advanced to view all the settings. Note that
IPSec Interface Mode is not selected.
The Phase1 IKE object is the IPSec tunnel referenced in the IPSec firewall policy. Here we
are using policy-based on the Remote FortiGate device and interface-based on the Student
FortiGate device. The type we use is of local significance therefore we can mix them, as is
the case in this example.
14. From the remote Windows host, attempt to run a continuous ping to: 10.0.1.10.
You should observe this ping fails. Identify why?
The IPsec action policy controls inbound and outbound traffic within the same policy;
however for interface-based IPsec, regular accept policies are used.
In the Student FortiGate device we have only configured the outgoing policy and this is why
the new incoming connection is dropped.
15. Return to the Student FortiGate device and add the missing rule.
P a g e | 53
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The aim of this lab is to work with both flow-based and proxy-based Antivirus scanning.
ev
ie
w
Fo
rR
1. From the Windows Server, you first will need to connect to the Student FortiGate device and
restore the configuration file that is needed for this lab.
Connect to the GUI on the Student FortiGate device (10.0.1.254) and restore the following
configuration file: Resources\Module7\student-utm.conf.
The Student FortiGate device will reboot.
2. When the FortiGate device has rebooted go to UTM Security Profiles > AntiVirus > Profile
and edit the default profile.
Configure the following details to enable AV scanning on HTTP:
Inspection Mode:
Proxy
P a g e | 54
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
3. Go to Policy > Policy > Policy and edit the port3port1 policy. Confirm that Use Standard
UTM Profiles is enabled and turn on AntiVirus. Ensure that the default antivirus profile is
selected.
4. Next go to Policy > Policy > UTM Proxy Options and examine the UTM proxy options.
nl
y
The default profile is displayed. These settings determine how FortiOS handles each
protocol. For example, which port numbers to use, whether to use client comforting, or
whether to perform deep SSL inspection and so on.
5. Go to System > Config > Replacement Message. From the top right-hand corner select
Extended View and under UTM modify the Virus Block Page.
The HTML editor that is displayed allows you to see the changes as you are making them.
Click Save shown above the editor window to apply your changes.
http://eicar.org
ie
w
6. On the virtual Windows Server desktop, launch a web browser and access the following web
site:
ev
7. On the Eicar web page, click Download Anti Malware Test File (located in the top right-hand
corner of the page) and then click the Download link that appears on the left.
rR
Download the eicar.com file from the section Download area using the standard protocol http.
Fo
The download attempt will be blocked by the FortiGate unit and a replacement message will
be displayed similar to the following (should also include any customization you made
earlier):
The Eicar file is an industry-standard used to test antivirus detection. The file contains the
following characters:
X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*
8. The HTTP virus message is shown when infected files are blocked or have been quarantined.
In the message that is displayed, click the link to the Fortinet Virus Encyclopedia to view
information about the detected virus.
P a g e | 55
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
9. From the GUI on Student FortiGate device, go to Log & Report > Traffic Log > Forward
Traffic and locate the antivirus event messages.
Alternately, go to UTM Security Profiles > Monitor > AV Monitor to view details of the log
event. If the AV monitor is not displayed in the GUI, go to System > Admin > Settings and
select UTM Monitors from the Display Options on GUI area.
nl
y
10. On the Eicar web page, click Download Anti Malware Test File and then click the Download
link that appears on the left. This time, select the eicar.com file from the Download area
using the secure, SSL enabled protocol https section.
ie
w
11. To enable inspection of SSL encrypted traffic on the Student FortiGate unit, go to Policy >
Policy > UTM Proxy Options and edit the default profile. Under SSL Inspection Options,
enable the protocol HTTPS on port 443.
12. To ensure that there are no existing sessions prior to deep scanning the communication
exchange, connect to the CLI of the Student FortiGate unit and enter the following command:
ev
rR
13. Return to the Eicar web page and attempt to download the eicar.com file from the Download
area using the secure SSL enabled protocol https section.
Fo
This time, the download will be blocked by the FortiGate unit and the replacement message
will be displayed. (If this is not the case, you may need to clear your recent browsing history
as the object may be cached.)
14. Go to UTM Security Profiles > Antivirus > Profile and change the Inspection Mode for the
default Antivirus Profile to Flow-based.
Try downloading the eicar.com file again. What happens now when the virus is detected?
Go to Log & Report > Traffic Log > Forward Traffic and examine the logs again. Ensure the
event was detected.
P a g e | 56
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The aim of this lab is for students to work with email filtering.
ie
w
Modify inspection rules to black or white list emails (using banned word, IP, email etc.)
rR
ev
Fo
1. From the Windows Server, you will first need to connect to the Student FortiGate device and
restore the configuration file that is needed for this lab. This module uses the same config as
in Module 7.
Connect to the GUI on the Student FortiGate device (10.0.1.254) and restore the following
configuration file: Resources\ Module7\student-utm.conf.
Tagged
Click Apply.
P a g e | 57
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
3. By default FortiGuard services are enabled. Go to System > Config > FortiGuard and check
the status of the service. (If you are using the hosted virtual lab environment you will need to
change the service port to UDP 8888).
4. Go to Policy > Policy > Policy and edit the port3port1 outgoing policy. Under UTM Security
Profiles, turn on Email Filter and ensure that the default email filter profile is selected.
nl
y
In the steps that follow, you will generate and send test spam emails to your Microsoft
Outlook user@internal.lab inbox. In the classroom lab environment, you will initiate the spam
generation using a script called smtpmboxgen.pl which is provided in the Resources\Module8
folder. Details for using this script will be provided in the steps that follow.
5. From the Windows server, open a command prompt and change directory to the
C:\Documents and Settings\Administrator\Desktop\Resources\Module8 folder as follows:
ie
w
ev
6. From your Microsoft Outlook mail client, check the email inbox. Review the tagged spam and
the corresponding logging events.
rR
7. Next, enable Banned Word Check in the default spam filter profile by entering the following
CLI commands:
config spamfilter profile
Fo
edit "default"
end
8. Run the following commands in the CLI to review the configured banned words.
config spam bword
show
Notice the use of both regular expression and wild cards in that list.
9. Generate a message that will be caught by the banned words configured, for example,
training. Remember that some banned words apply only to the subject line, others apply only
to the body and others apply to both.
A banned word is only scored once, for example if a banned word has a score 10 and yet the
word occurs four times in the message body, it will only still be assigned a count of 10.
10. Go to Log & Report > UTM Security Log > Email Filter and review the email filtering log
entries.
P a g e | 58
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The aim of this lab is for students to configure web filtering to block specific categories of web
content. The interaction of local categories and overrides will also be demonstrated.
ie
w
Select the most effective method for blocking or allowing a web site
rR
ev
Fo
1. From the Windows Server, you will first need to connect to the Student FortiGate device and
restore the configuration file that is needed for this lab. This module uses the same config as
in Module 7.
Connect to the GUI on the Student FortiGate device (10.0.1.254) and restore the following
configuration file: Resources\ Module7\student-utm.conf.
P a g e | 59
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
3. From the CLI on the Student FortiGate device, check the low-level status information of the
web filtering service by entering the following command:
diag debug rating
nl
y
The command diag debug rating shows the list of FDS servers for web filtering that the
FortiGate unit is using to send requests. Rating requests are only sent to the server on the
top of the list in normal operation. Each server is probed for RTT every 2 minutes.
The diag debug rating flags indicate the server status as explained below:
D indicates the server was found via the DNS lookup of the hostname. If the
hostname returns more than one IP address, all of them will be flagged with 'D' and
will be used first for INIT requests before falling back to the other servers.
I indicates the server to which the last INIT request was sent.
ie
w
F signifies the server has not responded to requests and is considered to have failed.
T signifies server is currently being timed.
ev
4. In the GUI on the Student FortiGate device, go to UTM Security Profiles > Web Filter >
Profile and review the settings of the default web filter profile. Select this profile using dropdown listed in the upper right-hand corner of the Edit Web Filter Profile window.
rR
5. Verify that the Inspection Mode is set to Proxy and enable FortiGuard Categories.
For the web categories listed below, set the Authenticate action to the training user group.
Fo
You will need to right-click each Group or Category name that is listed below in order to
make this change.
Potentially Liable
Adult/Mature Content
Security Risk
Next set the following web categories to Warning and accept the default Warning Interval
value:
Bandwidth Consuming
Unrated
Click Apply to save your changes.
6. Go to Policy > Policy > Policy and edit the outing port3port1 policy. Under UTM Security
Profile, turn on Web Filter and ensure that the default UTM profile is selected.
P a g e | 60
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
7. From a web browser on the virtual Windows Server, connect to a web site that is usually
blocked by the training policy and verify that the blocked message is displayed.
A FortiGuard replacement message should be displayed.
8. Go to System > Config > Replacement Message. Select FortiGuard Block Page and change
the text of the URL block message to customize it. Click Save to apply your changes.
nl
y
9. Revisit the same web site and ensure that the customized FortiGuard Block Page Blocked
message is displayed.
10. Next, in the web browser, attempt to connect to a web site category with an Authenticate
action. For example:
Fo
rR
ev
ie
w
A Web Page Blocked message is displayed again, this time with a Proceed button.
11. Click Proceed to view the Web Filter Block Override page. Enter the username student and
the password F0rtinet and click Continue.
The web page should now be displayed.
12. From the GUI on the Student FortiGate device, go Log & Report > Traffic Log > Forward
Traffic and locate the log messages related to the web filtering activity.
13. In the following step, you will configure an access quota for a couple of categories. Quotas
allow access to web resources for a specified length of time. Go to UTM Security Profiles >
Web Filter > Profile and edit the default web filter profile.
14. Expand Quota on Categories with Monitor, Warning and Authenticate Actions and click
Create New to create new quotas. Select the categories (same as in Step 4) to be assigned
quotas and set the quota time value to 5 minutes.
P a g e | 61
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
15. From a web browser on the Windows Server, attempt to visit a blocked category web site
again.
16. Click the Proceed link on the Web Page Blocked page. Authenticate on the Web Filter Block
Override page using the username student and the password F0rtinet and click Continue.
nl
y
Once authenticated properly, the quota timer is initiated. To view the current quota timer
value, go to UTM Security Profiles> Monitor > FortiGuard Quota. If the AV monitor is not
displayed in the GUI, go to System > Admin > Settings and select UTM Monitors from the
Display Options on GUI area.
When the daily quota value is reached the FortiGuard replacement message will be
displayed again.
ie
w
17. From the GUI on the Student FortiGate device go Log & Report > Traffic Log > Forward
Traffic and locate the log messages related to the web filtering activity.
18. Edit the default profile, expand Quota on Categories with Monitor, Warning and Authenticate
Actions and delete the quotas on the selected categories.
Fo
rR
ev
19. Still in the web filter profile and select flow-based. A notification is displayed as follows:
P a g e | 62
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The aim of this lab is for students to use the application control feature to properly identify a given
application.
ie
w
ev
Fo
rR
1. Go to UTM Security Profiles > Application Control > Application Sensor and review the
default application control sensor.(Ensure you are selecting the sensor named default.)
2. On the Edit Application Sensor page, check the settings for the following rules:
Application:
Youtube
Application:
Myspace
Check the actions for the filters. What are the expected actions of these sensors?
Traffic shaping is enabled for Youtube and these applications use a shared traffic shaper
which is capped at 1 Mbps. Connections to Myspace are blocked.
Before proceeding place both of these signatures at the top of the list.
3. Go to Policy > Policy > Policy and edit the port3port1 policy. Ensure that Application
Control is turned ON and that the default Application Control sensor is selected.
P a g e | 63
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
4. You will now test the application control configuration. From the virtual Windows Server,
open a web browser and connect to YouTube.
5. On the YouTube web site, attempt to play a few videos.
Check the traffic shaper monitor in Firewall Objects > Monitor > Traffic Shaper Monitor.
nl
y
Check the application monitor in UTM Security Profiles > Monitor > Application Monitor.
6. From the virtual Windows Server, open a web browser and connect to Myspace.
ie
w
7. Go to UTM Security Profiles > Application Control > Application Sensor and edit the default
sensor again. Click Create New to add a new application filter and select Specify
Applications.
8. In the search field shown above the Application Name column enter Facebook. A window
displays with a description of the application including popularity, and a reference link that
you can click to obtain more rating information from the FortiGuard Center.
ev
Set Action to block and ensure that this new signature is place at the top of the list.
rR
Test that this site is now blocked and view the log information (Log & Report > Traffic Log >
Forward Traffic) to confirm that this action was correctly logged. The status of the connection
should be displayed as deny.
9. Return the web browser, and attempt to access the following web site:
Fo
http://proxite.us
10. On the proxy web page, scroll down to the bottom and enter the URL of MySpace. Click Go.
You should observe this does allow some connectivity to the site. What action can be taken
to stop this?
You can create a new rule in the sensor to block the Proxy category.
P a g e | 64
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C
nl
y
The documentation web site contains all Fortinet manuals, white papers and guides for
Fortinet products.
2. Fortinet Knowledge Base: http://kb.fortinet.com
This site is useful for finding working examples and tips for Fortinet products.
ie
w
The Fortinet web site contains all hardware and product specifications.
4. FortiGuard Web Site: http://www.fortiguard.com
This site is suitable for finding information about the FortiGuard Subscription Services.
ev
rR
The FortiCare web site is used to interface with Fortinet support, register devices you have
purchased and download firmware updates.
6. Fortinet User Forums: http://support.fortinet.com/forum/
Fo
These are user-led and run forums that discuss many different topics surrounding the use of
Fortinet devices.
P a g e | 65
Course 201 Administration, Content Inspection and VPNs
01-50000-0201-20130215-C