WEB APPLICATION FIREWALL

FortiWeb Release Notes

VERSION 5.6
FORTINET DOCUMENT LIBRARY
http://docs.fortinet.com

FORTINET VIDEO GUIDE
http://video.fortinet.com

FORTINET BLOG
https://blog.fortinet.com

CUSTOMER SERVICE & SUPPORT
https://support.fortinet.com 

http://cookbook.fortinet.com/how-to-work-with-fortinet-support/
FORTIGATE COOKBOOK
http://cookbook.fortinet.com

FORTINET TRAINING SERVICES
http://www.fortinet.com/training

FORTIGUARD CENTER
http://www.fortiguard.com

END USER LICENSE AGREEMENT

http://www.fortinet.com/doc/legal/EULA.pdf

FEEDBACK
Email: [email protected]

September 23, 2016

FortiWeb 5.6 Release Notes

1st Edition
TABLE OF CONTENTS

Introduction 4
What’s new 5
Disk partitioning requirement 5
New and enhanced features 5
Change and performance notices 7
HTTP content routing policies that match X509 certificate content 7
Log feature after upgrade 7
Software support for FortiWeb 400B and 1000B 7
Order of web UI Log&Report menu items 7
Traffic logs 7
Time required to display data analytics reports 7
Data analytics data set limitations 8
Rebuilding the log aggregation database 8
Upgrade instructions 9
Hardware & VM support 9
Repartitioning the hard disk 9
Image checksums 31
Upgrading from previous releases 32
To upgrade from FortiWeb 5.5.x 33
To upgrade from FortiWeb 5.3.x 33
To upgrade from a version previous to FortiWeb 5.3 33
Upgrading an HA cluster 34
Downgrading to a previous release 34
FortiWeb-VM license validation after upgrade from pre-5.4 version 34
Resolved issues 35
Known issues 37
Introduction

Introduction

This document provides installation instructions and caveats, resolved issues, and known issues for FortiWeb™
5.6, build 0856.

FortiWeb provides web application security in a single platform enabling the protection, load balancing and
acceleration of web applications and the data exchanged between them and clients.

For additional documentation, please visit:

http://docs.fortinet.com/fortiweb/

FortiWeb 5.6 Release Notes 4

Fortinet Technologies Inc.
 What’s new Disk partitioning requirement

What’s new

Disk partitioning requirement

To support the latest features and enhancements, your FortiWeb needs to be re-partitioned when you upgrade
from any platform previous to FortiWeb 5.5.

For detailed instructions, see Repartitioning the hard disk on page 9.

New and enhanced features

l Enhanced cookie security — The cookie poisoning settings are now part of the new cookie security policy, which
allows you to configure additional ways to prevent cookie-based attacks. For example, you can encrypt the cookies
issued by a back-end server or add security attributes to them.
l Logging
l Log filter — You now search logs in the Web UI by adding a filter that matches messages found in the
most recent 100,000 messages in the attack, event, or traffic log. You can specify one or more values
to match, including the action, severity level, or message. (When searching by date and time, all
messages with the selected date are displayed.)
l Log file size — The log file no longer has a maximum size. Each log file can contain approximately
50,000 log records.
l Improved hard disk log storage — Logging enhancements have improved performance when
FortiWeb logs messages to the local hard disk. Recording traffic and event log messages in the local
random access memory (RAM) of the FortiWeb appliance is no longer supported.
l Site Publishing
l Multiple authentication servers — Site publishing rules now authenticate clients using a member of
a pool of authentication servers. The pool can contain LDAP servers, RADIUS servers, or both.
l User lock out — You can define an account lockout policy to prevent account cracking by locking an
account out after several failures logging into FortiWeb.
l Integrated stateful firewall — The new system firewall settings allow you to add basic stateful firewall
functionality to your FortiWeb appliance.
l FortiWeb Manager administrative access — You now configure access to a FortiWeb appliance from FortiWeb
Manager using a specific FortiWeb Manager administrative access setting. (Access by FortiWeb Manager via
HTTPS administrative access is no longer supported.)
l Data capture using DPDK — For models 3000E, 3010E and 4000E, when the operation mode is offline
protection, the network interfaces assigned as data capture ports now use Data Plane Development Kit (DPDK) for
packet processing.
l Optional compression for alert emails — You are allowed to determine whether to apply compression to an
alert email policy or not. With the compression function being enabled, event logs and alerts will be attached to the
emails in ZIP format, otherwise they will be attached in TXT format.
l Enhanced data compression performance — Compression performance of FortiWeb's file compression
function is highly improved by introducing the SLZ (Stateless ZIP library).

FortiWeb 5.6 Release Notes 5

Fortinet Technologies Inc.
New and enhanced features What’s new

l FortiWeb 600D — A new mid-range model.

l FortiWeb-VM
l Microsoft Azure integration — FortiWeb-VM deployed on Azure can be integrated with Azure
Security Center by sending FortiWeb's log messages, security and health alerts to Azure Event
Hubs.

For more information, see the FortiWeb-VM for Azure Install Guide.

l KVM ttyS0 console support — You can now configure a FortiWeb-VM instance you deploy on
KVM with the console “/dev/ttyS0” in addition to the console “/dev/console”.

For more information, see the FortiWeb-VM Install Guide.

6 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
 Change and performance notices HTTP content routing policies that match X509 certificate content

Change and performance notices

HTTP content routing policies that match X509 certificate content

In 5.5 Patch 4, the HTTP content routing policy settings that match X509 certificate content were enhanced to
allow you to match values found in either in the client certificate's subject field or extension field. When you
upgrade from an earlier release, the upgrade process deletes any HTTP content routing policies that match X509
Certificate content. You can re-create these policies using the enhanced settings.

Log feature after upgrade

The logging feature does not work after you downgrade your FortiWeb 5.5 or later appliance to an earlier version
and then upgrade back to the original version.

Software support for FortiWeb 400B and 1000B

FortiWeb 5.4 and higher software is not supported on models 400B and 1000B. Fortinet will continue to provide
bug fixes to these models with 5.3.x patch releases.

Order of web UI Log&Report menu items

In 5.4, under System > Config, the order of Operation, HA-Config, and Config-Sync was changed to reflect
the way that they are most commonly used.

In 5.3 Patch 4, the items under Log&Report in the navigation menu were re-ordered to reflect the way that they
are most commonly used.

Traffic logs

Due to abnormal disk wear-and-tear and performance decreases caused by very frequent disk writing, Fortinet
recommends enabling traffic logs only while debugging problems. Disable traffic logs once FortiWeb is operating
normally. Failure to disable traffic logging during normal use may cause premature hard disk failure.

Time required to display data analytics reports

Depending on how much data must be analyzed for your query, data analytics queries can take some time.
Fortinet recommends that you filter your query to include data from short periods of time.

FortiWeb 5.6 Release Notes 7

Fortinet Technologies Inc.
 Data analytics data set limitations Change and performance notices

Data analytics data set limitations

Due to the large amount of data that can be stored in the data analytics database, for performance reasons, a
data analytics query currently will only search up to 1,000,000 records at a time. This will be enhanced in the
future.

Rebuilding the log aggregation database

In some cases, if the log aggregation database is damaged, the web UI does not display logs correctly on the
Aggregated Attacks page. For example, duplicate logs are displayed or logs are missing.
To correct this problem, use the following command to rebuild the database:
execute db rebuild

This operation does not delete any logs.

8 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
 Upgrade instructions Hardware & VM support

Upgrade instructions

Hardware & VM support

FortiWeb™ 5.6 supports:

l FortiWeb 100D
l FortiWeb 400C
l FortiWeb 400D
l FortiWeb 600D
l FortiWeb 1000C
l FortiWeb 1000D
l FortiWeb 3000C/3000CFsx
l FortiWeb 3000D/3000DFsx
l FortiWeb 3000E
l FortiWeb 3010E
l FortiWeb 4000C
l FortiWeb 4000D
l FortiWeb 4000E
l FortiWeb-VM

Repartitioning the hard disk

To upgrade from a version of FortiWeb previous to 5.5, you must first resize your FortiWeb operating system's
disk.

For all hardware models and some FortiWeb-VM versions, you perform the required resizing task by installing a
special firmware image. See To use the special firmware image to repartition your FortiWeb hard disk .

Repartitioning affects the operating system’s disk (USB/flash disk), not the hard disk.
Existing data such as reports and event, traffic, and attack logs, which are on the hard
disk, are not affected.

You can use this image to upgrade an HA cluster by following the same procedure you
use for a regular firmware upgrade. For more information, see "Updating firmware on
an HA pair" in the FortiWeb Administration Guide.

For the following FortiWeb-VM versions, you cannot use the special firmware image to repartition the hard disk:

l Citrix XenServer
l open source Xen Project

FortiWeb 5.6 Release Notes 9

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

l Microsoft Hyper-V
l KVM
For these platforms, you upgrade by deploying a new virtual machine and restoring configuration and log data
you backed up earlier. See To create hard disk partitions for FortiWeb 5.5 or later without the special firmware
image.

To use the special firmware image to repartition your FortiWeb hard disk

1. Perform a complete backup of your FortiWeb configuration.

Although the repartitioning firmware image automatically saves your FortiWeb configuration, Fortinet
recommends that you also manually back it up.

2. Go to the Fortinet Customer Service & Support web site to download the special repartitioning firmware
image from the FTP site:

https://support.fortinet.com
Ensure that you download the correct image for your FortiWeb platform.

3. Use one of the following interface items to install the special firmware image. Follow the same procedure that
you use to install or upgrade firmware using a standard image.

l On the Status dashboard, beside the Firmware Version information (in the System Information widget) click
Update
l System > Maintenance > Backup & Restore
l In the CLI, the execute restore config command
FortiWeb backs up the current configuration, resizes the hard drive partitions, and boots the system.

4. Continue with the instructions in Upgrading from previous releases on page 32.

To create hard disk partitions for FortiWeb 5.5 or later without the special firmware image

On some hypervisor platforms, you cannot re-size the FortiWeb hard disk partitions using the special firmware
image. For these FortiWeb-VM appliances, you instead create a new virtual machine and restore a backed-up
configuration and log data to it.

1. Perform a complete back up of your FortiWeb configuration.

2. Use the instructions for your hypervisor platform to detach the log disk from the VM:
l To detach the log disk from a Citrix XenServer VM
l To detach the log disk from a Microsoft Hyper-V VM
l To detach the log disk from a KVM VM
3. Deploy a new FortiWeb 5.5 or later virtual machine on the same platform.
4. Use the instructions for your hypervisor platform to attach the log disk you detached earlier to the new VM:
l To attach the log disk to a Citrix XenServer VM
l To attach the log disk to a Microsoft Hyper-V VM
l To attach the log disk to a KVM VM
5. Restore the configuration you backed up earlier to the new VM.

10 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Repartitioning the hard disk

6. When you are sure that the new VM is working properly with the required configuration and log data, delete
the old VM.

To detach the log disk from a Citrix XenServer VM

1. In Citrix XenCenter, connect to the VM.

2. In the settings for the VM, on the Storage tab, select Hard disk 2, and then click Properties.

3. For Description, enter a new description, and then click OK.

FortiWeb 5.6 Release Notes 11

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

12 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Repartitioning the hard disk

4. Select Hard disk 2 again, and then click Detach.

5. Click Yes to confirm the detach task.

To detach the log disk from a Microsoft Hyper-V VM

1. In the Hyper-V Manager, select the FortiWeb-VM in the list of machines, and then, under Actions, click
Settings.

FortiWeb 5.6 Release Notes 13

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

2. Select Hard Drive (data.vhd), and then click Remove.

14 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Repartitioning the hard disk

3. Click Apply.

To detach the log disk from a KVM VM

1. In Virtual Machine Manager, double-click the FortiWeb-VM in the list of machines.

FortiWeb 5.6 Release Notes 15

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

16 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Repartitioning the hard disk

2. Click Show virtual hardware details (the "i" button).

FortiWeb 5.6 Release Notes 17

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

3. Click VirtIO Disk 2, and then click Remove.

To attach the log disk to a Citrix XenServer VM

1. In Citrix XenCenter, connect to the VM.

2. In the settings for the new, FortiWeb 5.5 or later VM, on the Storage tab, select Hard disk 2, and then click
Delete.

18 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Repartitioning the hard disk

3. Click Yes to confirm the deletion.

4. On the Storage tab, click Attach Disk, and then navigate to the hard disk you detached from the old VM to
attach it.

FortiWeb 5.6 Release Notes 19

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

5. Start your new virtual machine.

To attach the log disk to a Microsoft Hyper-V VM

1. In the Hyper-V Manager, select the new, FortiWeb 5.5 or later virtual machine in the list of machines, and
then, under Actions, click Settings.

20 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Repartitioning the hard disk

FortiWeb 5.6 Release Notes 21

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

2. Select Hard Drive (log.vhd), and then click Browse.

3. Browse to the hard drive you detached from the old virtual machine to select it.

22 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Repartitioning the hard disk

4. Click Apply.

5. Start the new virtual machine.

To attach the log disk to a KVM VM

For KVM deployments, you remove an existing virtual disk from the new VM before you attach the disk detached
from the original VM.

FortiWeb 5.6 Release Notes 23

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

1. In Virtual Machine Manager, double-click the new, FortiWeb 5.5 or later VM in the list of machines.

24 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Repartitioning the hard disk

2. Click Show virtual hardware details (the "i" button).

FortiWeb 5.6 Release Notes 25

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

3. Click VirtIO Disk 2, and then click Remove.

26 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Repartitioning the hard disk

4. Click Add Hardware.

FortiWeb 5.6 Release Notes 27

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

5. Click Storage, select Select managed or other existing storage, and then click Browse.

28 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Repartitioning the hard disk

6. Click Browse Local.

FortiWeb 5.6 Release Notes 29

Fortinet Technologies Inc.
Repartitioning the hard disk Upgrade instructions

7. Navigate to the log disk file for the original machine to select it, and then click Open.

30 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Upgrade instructions Image checksums

8. For Device type, select Virtio disk, for Storage format, select qcow2, and then click Finish.

9. Start the new virtual machine.

Image checksums

To verify the integrity of the firmware file, use a checksum tool to compute the firmware file’s MD5 checksum.
Compare it with the checksum indicated by Fortinet. If the checksums match, the file is intact.

MD5 checksums for software releases are available from Fortinet Customer Service & Support:

https://support.fortinet.com

FortiWeb 5.6 Release Notes 31

Fortinet Technologies Inc.
Upgrading from previous releases Upgrade instructions

Customer Service & Support image checksum tool

After logging in to the web site, in the menus at the top of the page, click Download, and then click Firmware
Image Checksums.
Alternatively, near the bottom of the page, click the Firmware Image Checksums button. (The button appears
only if one or more of your devices has a current support contract.) In the File Name field, enter the firmware
image file name including its extension, then click Get Checksum Code.

Upgrading from previous releases

l If you upgrade from a version of FortiWeb previous to 5.5.4, the upgrade process deletes any HTTP content routing
policies that match X509 certificate content. You can re-create these policies using the new, enhanced X509
certificate settings.
l To upgrade from a version of FortiWeb previous to 5.5, you must first resize your FortiWeb hard disk partitions. See
Repartitioning the hard disk on page 9.

32 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
 Upgrade instructions Upgrading from previous releases

l If you upgrade from a version of FortiWeb previous to 5.3.4 and your server policy configuration includes settings
that customize an attack blocking or server unavailable error page, the upgrade deletes these server-based
settings. The functionality is replaced by the global, default FortiWeb pages.
l If you upgrade from a version of FortiWeb previous to 5.3.6, the upgrade process deletes any V-zone IP addresses,
which are no longer required. This operation has no impact on routing or connectivity after the upgrade.
Note: To upgrade from 4.0 MR4, Patch x or earlier, please contact Fortinet Technical Support.

To upgrade from FortiWeb 5.5.x

Upgrade to FortiWeb 5.6 directly.

To upgrade from FortiWeb 5.3.x

Upgrade to FortiWeb 5.6 directly after completing the hard disk repartitioning process.

If you are upgrading FortiWeb-VM on a hypervisor other than VMware vSphere, see FortiWeb-VM license
validation after upgrade from pre-5.4 version on page 34.

To upgrade from a version previous to FortiWeb 5.3

FWB5.3.exe is a Microsoft Windows executable script that automatically migrates your FortiWeb 5.2.x
configuration settings to a 5.3.x configuration.

1. If your version is 5.0.x or 5.1.x, upgrade to FortiWeb 5.2.x.

2. Use System > Maintenance > Backup & Restore to back up your FortiWeb configuration. Fortinet
recommends that you use the Backup entire configuration option.

Note: If you forget to back up the configuration before you upgrade to FortiWeb 5.3, you can use the Boot into
alternate firmware option to downgrade to the previous version, and then backup its configuration. For more
information, see online help or the FortiWeb Administration Guide.
3. To obtain the upgrade script, log in to https://support.fortinet.com. In the menus at the top of the page, click
Download, and then click Firmware Images.
4. For product, select FortiWeb. Then, on the Download tab, navigate to the following folder:

/FortiWeb/v5.00/5.3/Upgrade_script/

5. Download the .zip compressed archive (for example, FWB5.3Upgrade_v1.9.zip) to a location you can
access from your Windows PC.
6. In Windows, extract the .zip archive's contents, and then use a command line interface to execute the upgrade
script.

For example, in the directory where the file FWB5.3Upgrade.exe and your backup configuration file are
located, execute the following command:

FWB5.3Upgrade.exe -i YOUR_CONFIG_NAME.conf –o 5.3_new.conf

The script removes the Domain Server, Physical Server, Server Farm, Content Routing policy configurations and
generates a new configuration file named 5.3_new.conf.
7. Resize your FortiWeb hard disk partitions. See Repartitioning the hard disk on page 9.

FortiWeb 5.6 Release Notes 33

Fortinet Technologies Inc.
 Upgrading an HA cluster Upgrade instructions

8. Upgrade to FortiWeb™ 5.6.

9. Use System > Maintenance > Backup & Restore to restore the configuration file you created using the script
(for example, 5.3_new.conf).

If you upgrade from a previous version of FortiWeb and your server policy configuration includes settings that
customize an attack blocking or server unavailable error page, the upgrade deletes these server-based settings.
The functionality is replaced by the global, default FortiWeb pages.

Upgrading an HA cluster

If the HA cluster is running FortiWeb 4.0 MR4 or later, the HA cluster upgrade is streamlined. When you upgrade
the active appliance, it automatically upgrades the standby appliance too. No manual intervention is required to
upgrade the other appliance. (This includes upgrading using the special hard disk repartitioning firmware image
for upgrading to 5.5 or later from earlier releases.)

If the HA cluster is running FortiWeb 4.0 MR3 Patch x or earlier, contact Fortinet Technical Support for
assistance.

Downgrading to a previous release

When you downgrade your FortiWeb™ 5.6 to version 5.1 or 5.0, the basic configuration for your appliance's
connections to the network (for example, IP address and route configuration) is preserved.

FortiWeb-VM license validation after upgrade from pre-5.4 version

On some virtual machine deployments, upgrading FortiWeb-VM from a version previous to 5.4 changes the
virtual machine's universal unique identifier (UUID). Because of this change, the first time you upload your
existing FortiWeb-VM license, the FortiGuard Distribution Network (FDN) server reports that it is invalid.

To solve this problem, after you have uploaded the license, wait 90 minutes, and then upload the license again.

This issue does not affect FortiWeb-VM deployed on a VMware vSphere hypervisor.

34 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Resolved issues

Resolved issues

The resolved issues listed below do not list every bug that has been corrected with this release. For inquires about
a particular bug, please contact Fortinet Customer Service & Support:

https://support.fortinet.com

Resolved issues

Bug ID Description

299744 Packet header in traffic log messages is incomplete when service is HTTPS.

Health check SSL version should be the same as the SSL version configured for back-end
357460
server.

377883 User tracking fails when Expect request-header field value is '100-continue'.

379598 Forwarding a HTTP request containing lots of form data by adding it a X-Forwarded-For
379214 header causes system failed to add X-Forwarded-For to subsequent HTTP requests.

380197 FortiWeb-VM for Azure is installed with admin account with blank password.

380236 In true transparent proxy mode, FortiWeb reboots when testing SYN flood protection.

380268 FortiWeb does not forward some HTTPS traffic even though the policy is configured not to
parse traffic.

The web UI shows Auto Learn Profile server policy option as disabled when no Web
380955
Protection Profile is selected, but the auto learn profile still runs in the background.

383306 System rebooting losses FortiWeb the installed certificates.

Message "<http_modify.c:2305> no memory pool allocated for op data,policy : pol_i-

383340
bank,module_num 777" continually appears on console.

384110 In offline mode, FortiWeb drops a connection when it detects two of the same SYN packet.

385048 Memory leak occurs in FortiWeb's SNMP V3.

385250 In reverse proxy mode, daemon proxyd might go crashed when content routing processes a
HTTP request containing a very long string in the Host request-header field.

The URL rewrite function outputs a rewritten URL without processing the '+' characters
387941
within the URL.

388149 CPU soft lockup is detected on FortiWeb.

FortiWeb 5.6 Release Notes 35

Fortinet Technologies Inc.
 Resolved issues

Bug ID Description

It would fail to restore a configuration file (from System > Maintenance > Backup & Restore
388681
on Web UI) if the encryption password in the configuration contains a blank character.

388683 FortiWeb has worse performance of responding the SNMP queries using SNMPWALK.

36 FortiWeb 5.6 Release Notes

Fortinet Technologies Inc.
Known issues

Known issues

This section lists the known issues of this release, but is not a complete list. For inquires about a particular bug,
please contact Fortinet Customer Service & Support:

https://support.fortinet.com

Known issues

Bug ID Description

305076 It fails to upgrade image for FortiWeb-VM via PowerCLI, and an error message "The guest OS for
the virtual machine is unknown" appears.

305069 A timeout error appears when using cmdlet Invoke-VMScript to config FortiWeb-VM via PowerCLI.

369655 It is unable to change Reserve Management Port for Cluster Member option via web UI.

FortiWeb 5.6 Release Notes 37

Fortinet Technologies Inc.
Copyright© 2016 Fortinet, Inc. All rights reserved. Fortinet®, FortiGate®, FortiCare® and FortiGuard®, and certain other marks are registered trademarks of Fortinet,
Inc., in the U.S. and other jurisdictions, and other Fortinet names herein may also be registered and/or common law trademarks of Fortinet. All other product or company
names may be trademarks of their respective owners. Performance and other metrics contained herein were attained in internal lab tests under ideal conditions, and
actual performance and other results may vary. Network variables, different network environments and other conditions may affect performance results. Nothing herein
represents any binding commitment by Fortinet, and Fortinet disclaims all warranties, whether express or implied, except to the extent Fortinet enters a binding written
contract, signed by Fortinet’s General Counsel, with a purchaser that expressly warrants that the identified product will perform according to certain expressly-identified
performance metrics and, in such event, only the specific performance metrics expressly identified in such binding written contract shall be binding on Fortinet. For
absolute clarity, any such warranty will be limited to performance in the same ideal conditions as in Fortinet’s internal lab tests. In no event does Fortinet make any
commitment related to future deliverables, features, or development, and circumstances may change such that any forward-looking statements herein are not accurate.
Fortinet disclaims in full any covenants, representations,and guarantees pursuant hereto, whether express or implied. Fortinet reserves the right to change, modify,
transfer, or otherwise revise this publication without notice, and the most current version of the publication shall be applicable.