Fortisandbox v4.2.4 Release Notes
Fortisandbox v4.2.4 Release Notes
FortiSandbox 4.2.4
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
Fabric integration 6
Special Notices 7
Scan Profile 7
Upgrade path 7
Upgrade Information 8
Before and after any firmware upgrade 8
Tracer and Rating Engines 8
Upgrade path 9
Firmware image checksums 9
Upgrading cluster environments 10
Upgrade procedure 10
Downgrading to previous firmware versions 10
FortiSandbox VM firmware 11
Product Integration and Support 12
Resolved Issues 14
GUI 14
Scan 14
System & Security 14
Known Issues 15
Fabric Integration 15
Logging & Reporting 15
Scan 15
System & Security 15
This document provides the following information for FortiSandbox version 4.2.4 build 0261.
l Supported models
l New features and enhancements
l Special Notices
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 4.2.4 Administration Guide and
FortiSandbox 4.2.4 VM Install Guide.
Supported models
The following is summary of new features and enhancements in version 4.2.4. For details, see the FortiSandbox4.2.4
Administration Guide in the Fortinet Document Library.
Fabric integration
Scan Profile
After upgrading to 4.2.4 the VM Association in the Scan Profile changes the CSV extension category from User defined
extension to Office Documents as intended. When a CSV file is scanned by the VM, the CSV file type is displayed as
userdefined in the Job Detail.
Upgrade path
A feature that was introduced in FortiSandbox v4.2.0 causes a critical bug that only affects FSA-1000F, FSA-500F and
VM after upgrading to v4.2.1. We strongly recommend that customers who have upgraded to v4.2.1 upgrade to v4.2.4.
Customers upgrading from v4.2.0 should upgrade to 4.2.4.
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.
The tracer and rating engines are automatically downloaded by the FortiSandbox from FortiGuard. For air-gapped
mode, the engines are available for download from our Support site.
To download the latest engine:
1. Log in to FortiCloud.
2. In the banner, click Support > Service Updates.
3. On the FortiGuard Updates page, click FortiSandbox and select the OS version.
Upgrade path
3.2.3 4.0.2
3.1.4 3.2.0
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, then follow the
upgrade table.
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 and tracer engine. Then wait until the devices fully
boot up.
2. Upgrade the secondary (primary slave) and install the new rating and tracer engine. Then wait until the device fully
boots up.
3. Upgrade the primary (master). This causes HA failover.
4. Install the new rating and tracer 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.
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 4.2.4 product integration and support information.
Other web browsers may function correctly but are not supported by Fortinet.
FortiClient l 7.2.0
l 7.0.0 and later
l 6.4.0 and laster
l 6.2.0 and later
l 6.0.1 and later
l 5.6.0 and later
FortiEMS l 7.2.0
l 7.0.0 and later
l 6.4.0 and later
l 6.2.0 and later
l 6.0.5 and later
FortiADC l 7.2.0
l 7.1.0 and 7.1.1
l 7.0.0 and 7.0.3
l 6.2.0 and later
l 6.1.0 and later
l 6.0.0 and later
l 5.4.0 and later
l 5.3.0 and later
l 5.0.1 and later
FortiWeb l 7.2.0
l 7.0.0 and later
l 6.4.0 and later
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
FortiIsolator l 2.4.2
AV engine l 00006.00285
The following issues have been fixed in FortiSandbox 4.2.4. For inquiries about a particular bug, contact Customer
Service & Support.
GUI
Bug ID Description
871484 Fixed a few counter issues on the Security Fabric device page for FortiGate.
877216 Fixed file download feature on job detail page due to invalid characters.
Scan
Bug ID Description
868205 Enhanced return code for Inline Block deployment to support drop files for unsupported file
format.
876901 Fixed a legacy duplicate response on Malware package that impacts FortiSandbox
performance.
882869 Fixed a legacy behavior that impacts FortiSandbox performance when FortiGate queries
unexisting file.
Bug ID Description
857120 Fixed DNS traffic flow issue for VM traffic to correctly traverse on port3.
The following issues have been identified in FortiSandbox 4.2.4. For inquiries about a particular bug or to report a bug,
contact Customer Service & Support.
Fabric Integration
Bug ID Description
810164 ICAP Adapter issue with McAfee Web Gateway responding with 'No Content'
Bug ID Description
785274 Wrong filename and service info on the Job details when conserve mode enabled in sniffer
setting.
Scan
Bug ID Description
822024 Unsupported ISO file in UDF 2.5 format not extracted and launched.
Bug ID Description
Copyright© 2023 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet, Inc., and other Fortinet names herein
may also be registered and/or common law trademarks of Fortinet. All other product or company names may be trademarks of their respective owners. Performance and other metrics contained herein were
attained in internal lab tests under ideal conditions, and actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance
results. Nothing herein represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written contract,
signed by Fortinet’s General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified performance metrics and, in such event, only
the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For absolute clarity, any such warranty will be limited to performance in the same ideal
conditions as in Fortinet’s internal lab tests. Fortinet disclaims in full any covenants, representations, and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change,
modify, transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.