Fortisandbox v3.2.3 Release Notes
Fortisandbox v3.2.3 Release Notes
Version 3.2.3
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
NSE INSTITUTE
https://training.fortinet.com
FORTIGUARD CENTER
https://www.fortiguard.com
FEEDBACK
Email: [email protected]
Change Log 4
Introduction 5
Supported models 5
New features and enhancements 6
Upgrade Information 7
Before and after any firmware upgrade 7
Upgrade path 7
Firmware image checksums 8
Upgrading cluster environments 8
Upgrade procedure 8
Downgrading to previous firmware versions 9
FortiSandbox VM firmware 9
Product Integration and Support 10
Resolved Issues 12
Fabric Integration 12
GUI 12
Scan 12
System & Security 12
Log & Report 13
Known Issues 14
Scan 14
System & Security 14
This document provides the following information for FortiSandbox version 3.2.3 build 0255.
l Supported models
l New features and enhancements
l Upgrade Information
l Product Integration and Support
l Resolved Issues
l Known Issues
For more information on upgrading your FortiSandbox device, see the FortiSandbox 3.2.3 Administration Guide and
FortiSandbox 3.2.3 VM Install Guide.
Supported models
FortiSandbox version 3.2.3 supports the FSA-500F, FSA-1000D, FSA-1000F, FSA-2000E, FSA-3000D, FSA-3500D,
FSA-3000E, and FSA-VM (AWS, Azure, Hyper-V, KVM, and VMware ESXi) models.
Before any firmware upgrade, save a copy of your FortiSandbox configuration by going to Dashboard > System
Configuration > Backup.
After any firmware upgrade, if you are using the web UI, clear the browser cache before logging into FortiSandbox so
that web UI screens display properly.
Upgrade path
3.2.0–3.2.2 3.2.3
3.1.4 3.2.0
3.0.6–3.1.3 3.1.4
2.5.2–3.0.5 3.0.6
2.4.1–2.5.1 2.5.2
2.4.0 2.4.1
If you are using KVM or Hyper-V, the upgrade path must be 3.1.3 > 3.2.0 > 3.2.3.
As with all VM upgrades, take a snapshot or make a checkpoint before upgrading.
After upgrading, FortiSandbox might stop processing files until the latest rating engine is
installed either by FDN update or manually. The rating engine is large so schedule time for the
download.
Every time FortiSandbox boots up, it checks FDN for the latest rating engine.
If the rating engine is not available or out-of-date, you get these notifications:
l A warning message informs you that you must have an updated rating engine.
l The Dashboard System Information widget displays a red blinking No Rating Engine message besides Unit Type.
If necessary, you can manually download an engine package from Fortinet Customer Service & Support.
If the rating engine is not available or out-of-date, FortiSandbox functions in the following ways:
l FortiSandbox still accepts on-demand, network share, and RPC submissions, but all jobs are pending.
l FortiSandbox does not accept new devices or FortiClients.
l FortiSandbox does not accept new submissions from Sniffer, Device, FortiClient, or Adapter.
The MD5 checksums for all Fortinet software and firmware releases are available at the Fortinet Customer Service &
Support portal located at https://support.fortinet.com. After logging in select Download > Firmware Image Checksums,
enter the image file name including the extension, and select Get Checksum Code.
Before upgrading, it is highly recommended that you set up a cluster IP set so the failover between primary (master) and
secondary (primary slave) can occur smoothly.
In a cluster environment, use this upgrade order:
1. Upgrade the workers (regular slaves) and install the new rating engine. Then wait until the devices fully boot up.
2. Upgrade the secondary (primary slave) and install the new rating engine. Then wait until the device fully boots up.
3. Upgrade the primary (master). This causes HA failover.
4. Install the new rating engine on the old primary (master) node. This node might take over as primary (master) node.
Upgrade procedure
When upgrading from 3.1.0 or later and the new firmware is ready, you will see a blinking New
firmware available link on the dashboard. Click the link and you will be redirected to a page
where you can either choose to download and install an available firmware or manually upload
a new firmware.
4. Microsoft Windows Sandbox VMs must be activated against the Microsoft activation server if they have not been
already. This is done automatically after a system reboot. To ensure the activation is successful, port3 of the system
must be able to access the Internet and the DNS servers should be able to resolve the Microsoft activation servers.
FortiSandbox VM firmware
Fortinet provides FortiSandbox VM firmware images for VMware ESXi, Hyper-V, Nutanix, and Kernel Virtual Machine
(KVM) virtualization environments.
For more information, see the VM Installation Guide in the Fortinet Document Library.
The following table lists FortiSandbox 3.2.3 product integration and support information.
Other web browsers may function correctly but are not supported by Fortinet.
FortiOS/FortiOS Carrier l 7.0.0
l 6.4.0 and later
l 6.2.0 and later
l 6.0.0 and later
l 5.6.0 and later
FortiAnalyzer l 7.0.0
l 6.4.0 and later
l 6.2.0 and later
l 6.0.0 and later
l 5.6.0 and later
l 5.4.0 and later
FortiManager l 7.0.0
l 6.4.0 and later
l 6.2.1 and later
l 6.0.0 and later
l 5.6.0 and later
l 5.4.0 and later
FortiClient l 7.0.0
l 6.4.0 and later
l 6.2.0 and later
l 6.0.1 and later
l 5.6.0 and later
FortiEMS l 7.0.0
l 6.4.0 and later
l 6.2.0 and later
l 6.0.5 and later
FortiMail l 7.0.0
FortiWeb l 6.4.0
l 6.3.5 and later
l 6.3.2 and later
l 6.2.0 and later
l 6.0.0 and later
l 5.8.0 and later
l 5.6.0 and later
AV engine l 00006.00263
Virtualization environment l VMware ESXi: 5.1, 5.5, 6.0, 6.5, 6.7, and 7.0.1.
l KVM: Linux version 4.15.0 qemu-img v2.5.0
l Microsoft Hyper-V: Windows server 2016 and 2019
The following issues have been fixed in FortiSandbox 3.2.3. For inquiries about a particular bug, contact Customer
Service & Support.
Fabric Integration
Bug ID Description
689623 Fixed connectivity issues with FortiClient that randomly gets stalled.
GUI
Bug ID Description
687401 Fixed wrong CPU data on the System Resource Usage widget.
690948 Fixed logon to the Web GUI with RADIUS two-factor authentication.
Scan
Bug ID Description
687843 Fixed a race condition when processing results from cluster nodes.
Bug ID Description
Log & Report
Bug ID Description
690564 Fixed syslog format to include host_id after timestamp to conform to RFC.
The following issues have been identified in FortiSandbox 3.2.3. For inquiries about a particular bug or to report a bug,
contact Customer Service & Support.
Scan
Bug ID Description
672997 Sniffer mode fails to extract user-defined file type eml from the traffic.
682154 Missing job details info due to retention policy discrepancies caused by heavy load.
Fixed in 4.0.0.
Bug ID Description