Está en la página 1de 7

4/16/2017 Sandboxing with FortiSandbox and FortiClient ­ Fortinet Cookbook

FORTICLIENT / FORTICLIENT 5.4 / FORTICLOUD / FORTIGATE / FORTIOS 5.4.0 / FORTISANDBOX / FORTISANDBOX


2.1 / SECURITY

Sandboxing with FortiSandbox and FortiClient
Posted on December 22, 2015 by Victoria Martin

Share this post:

In this recipe, you will set up sandboxing to send suspicious ៜ�les to a FortiSandbox Appliance for
further inspection. The FortiSandbox scans for threats that can get past other detection methods,
using Windows virtual machines (VMs) to test suspicious ៜ�les in isolation from your network.

http://cookbook.fortinet.com/sandboxing­fortisandbox­forticlient­54/ 1/7
4/16/2017 Sandboxing with FortiSandbox and FortiClient ­ Fortinet Cookbook

You will also conៜ�gure your FortiGate to automatically receive signature updates from FortiSandbox
and add the originating URL of any malicious ៜ�le to a blocked URL list. Finally, you will conៜ�gure
FortiClient to use extended scanning that includes FortiSandbox.

 Watch the video

1. Connecting the FortiSandbox

Connect the FortiSandbox to your FortiGate as shown in the diagram, so that port
1 and port 3 on the FortiSandbox are on different subnets.

FortiSandbox port 3 is used for outgoing communication triggered by the execution of the ៜ�les
under analysis. It is recommended to connect this port to a dedicated interface on your FortiGate
(in the example, port 15), to protect the rest of the network from threats currently being
investigated by the FortiSandbox.

FortiSandbox port 3 must be able to connect to the Internet. On the FortiGate, go


to Policy & Objects > IPv4 Policy and create a policy allowing connections from
the FortiSandbox to the Internet (using the isolated interface on the FortiGate
mentioned above).

On the FortiSandbox, go to System > Network > Static Routing and add static
routes for both port 1 and port 3. 

The static route for port 3 must have the Destination/IP Mask 0.0.0.0/0.0.0.0,


while port 1 is assigned the Destination/IP Mask for trafៜ�c in the local network.

Once the FortiSandbox has access to the Internet through port 3, it will begin to
activate its VM licenses.

Before continuing with this recipe, wait until a green arrow shows up beside
Windows VM in the FortiSandbox’s System Information widget, found at System
> Status. This indicates that the VM activation process is complete.

2. Enabling Sandbox Inspection

On the FortiGate, go to System > External Security Devices. Select Enable

http://cookbook.fortinet.com/sandboxing­fortisandbox­forticlient­54/ 2/7
4/16/2017 Sandboxing with FortiSandbox and FortiClient ­ Fortinet Cookbook

Sandbox Inspection and select FortiSandbox Appliance.

Set the IP Address (in the example, 172.20.121.128) and enter a Notiៜ�er Email,


where notiៜ�cations and reports will be sent.

If you select Test Connectivity, the Status shows as Service is not conៜ�gured
because the FortiGate has not been authorized to connect to the FortiSandbox.

On the FortiSandbox, go to File-based Detection > File Input > Device. Edit the
entry for the FortiGate.

Under Permissions, enable Authorized.

On the FortiGate, go to System > External Security Devices and for FortiSandbox
select Test Connectivity. The Status now shows that Service is online.

3. Configuring sandboxing in the default AntiVirus profile

Go to Security Proៜ�les > AntiVirus and edit the default proៜ�le.

Under Inspection Options, enable both Send Files to FortiSandbox Appliance for
Inspection and Use FortiSandbox Database.

If FortiSandbox discovers a threat, it creates a signature for that ៜ�le that is added
to the FortiGate’s AntiVirus signature database.

4. Configuring sandboxing in the default Web Filter profile

Go to Security Proៜ�les > Web Filter and edit the default proៜ�le.

Under Static URL Filter, enable Block malicious URLS discovered by


FortiSandbox.

If the FortiSandbox discovers a threat, the URL that threat came from will be
added to the list of URLs that will be blocked by the FortiGate.

http://cookbook.fortinet.com/sandboxing­fortisandbox­forticlient­54/ 3/7
4/16/2017 Sandboxing with FortiSandbox and FortiClient ­ Fortinet Cookbook

5. Configuring sandboxing in the default FortiClient profile

Go to Security Proៜ�les > FortiClient Proៜ�les and edit the default proៜ�le.

Under AntiVirus, enable Realtime Protection, then enable Scan Downloads,


followed by Scan with FortiSandbox. Enter the IP of the FortiSandbox.

Decide if you want to wait for FortiSandbox results before sending ៜ�les to the PC
running FortiClient, or if you want downloaded ៜ�les to be sent at the same time as
they are being scanned by FortiSandbox.

Enable Use FortiSandbox signatures to make sure new virus signatures and
blocked URLs from the FortiSandbox are added to FortiClient’s databases.

This proៜ�le will be pushed to any device running FortiClient that is registered to your FortiGate.
These settings can also be conៜ�gured from within FortiClient’s AntiVirus settings.

6. Applying AntiVirus and Web Filter scanning to network
traffic

Go to Policy & Objects > IPv4 Policy and view the policy list. If a policy has
AntiVirus and web ៜ�ltering scanning applied, the proៜ�les will be listed in the
Security Proៜ�les column.

If scanning needs to be added to any security policy (excluding the Implicit Deny
policy) select the + button in the Security Proៜ�les column for that policy, then
select the default AntiVirus Proៜ�le, the default Web Filter Proៜ�le, the
appropriate Proxy Options, and the deep-inspection proៜ�le for SSL Inspection
Options (to ensure that encrypted trafៜ�c is inspected). Then select OK.

7. Results 

If your FortiGate discovers a suspicious ៜ�le, it will now be sent to the


FortiSandbox. To view information about the ៜ�les that have been sent on the
FortiGate, go to FortiView > FortiSandbox to see a list of ៜ�le names and current
status.

http://cookbook.fortinet.com/sandboxing­fortisandbox­forticlient­54/ 4/7
4/16/2017 Sandboxing with FortiSandbox and FortiClient ­ Fortinet Cookbook

You can also view results on the FortiSandbox by going to System > Status and
viewing the Scanning Statistics widget.

Open FortiClient using a Windows PC on the internal network. Make sure it is


registered to your FortiGate.

Go to AntiVirus > Realtime Protection Enabled and edit the settings. You will see
that the Realtime Protection settings match the FortiClient Proៜ�le conៜ�gured on
the FortiGate. These settings cannot be changed using FortiClient.

On the FortiGate, go to Monitor > FortiClient Monitor. Select the FortiClient


device, then select Quarantine.

The PC is now quarantined by FortiClient and cannot connect to the Internet or


other network devices.

A message appears in FortiClient, telling the user to contact the system


administrator.

FortiClient cannot be shutdown on the PC. It can also not be uninstalled or


unregistered from the FortiGate.

If a FortiClient device attempts to download a ៜ�le that FortiSandbox discovers is malicious, the
FortiSandbox notiៜ�es the FortiGate. The administrator can take action to quarantine the device.
When a quarantine is in effect, FortiClient cuts off other network trafៜ�c from the device directly,
preventing it from infecting or scanning the local network. When a device is under quarantine,
FortiClient cannot be shutdown or uninstalled. A user is also unable to unregister from the
FortiGate that quarantined them, or register to another FortiGate unit. A quarantine can only be
lifted by the administrator of the FortiGate where the FortiClient device is registered.

About   Latest Posts

Victoria Martin
Technical Writer & Head Cookbook Chef at Fortinet

Victoria Martin works in Ottawa as part of the FortiOS technical documentation team. She
graduated with a Bachelor's degree from Mount Allison University, after which she
attended Humber College's book publishing program, followed by the more practical
technical writing program at Algonquin College. She does need glasses but also likes
wearing them, since glasses make you look smarter.

http://cookbook.fortinet.com/sandboxing­fortisandbox­forticlient­54/ 5/7
4/16/2017 Sandboxing with FortiSandbox and FortiClient ­ Fortinet Cookbook

Was this helpful?  Yes      No

 AntiVirus, FortiClient, FortiCloud, FortiSandbox, web ៜ�ltering, Windows

Leave a Reply

2 Comments on "Sandboxing with FortiSandbox and FortiClient"

Connect with:

Powered by OneAll Social Login

Notify of new follow-up comments Email ›

Join the discussion

Carlos Basulto

Good Afternoo, when i try to realize those steps, i can´t put the static route
0.0.0.0/0 on port 3. In GUI the interface port 3 can´t select because doesn´t
appear. I try to put default gateway on CLI and show this: Gateway may not be set
to port3. I need help!!!

 REPLY  July 21, 2016 12:41 pm

Victoria Martin

Hello Carlos,

This recipe was written using an earlier version of FortiSandbox’s ៜ�rmware.


In the 2.2 ៜ�rmware, the static route for port 3 is part of the default
conៜ�guration, so you no longer need to create it manually.

I hope that helps.

http://cookbook.fortinet.com/sandboxing­fortisandbox­forticlient­54/ 6/7
4/16/2017 Sandboxing with FortiSandbox and FortiClient ­ Fortinet Cookbook

 REPLY  July 25, 2016 10:44 am

CONTACT |  DOCUMENTATION LIBRARY |  CLI PORTAL  |  FUSE |  VIDEOS |  SUPPORT |  CORPORATE |  LEGAL

© 2017 Fortinet

http://cookbook.fortinet.com/sandboxing­fortisandbox­forticlient­54/ 7/7