fortianalyzer-v7.4.5-release-notes
fortianalyzer-v7.4.5-release-notes
FortiAnalyzer 7.4.5
FORTINET DOCUMENT LIBRARY
https://docs.fortinet.com
FORTINET BLOG
https://blog.fortinet.com
FORTIGUARD LABS
https://www.fortiguard.com
FEEDBACK
Email: [email protected]
Change Log 6
FortiAnalyzer 7.4.5 Release 7
Supported models 7
FortiAnalyzer VM subscription license 7
Management extension applications 8
Supported models for MEA 8
Minimum system requirements 8
Special Notices 10
Upgrading from 7.4.3 to 7.4.5 with FIPS mode enabled 10
Field name when log forwarding to CEF 10
Shell access has been removed 10
Events and Incidents FortiView monitors removed 10
Alert notifications generated by FortiAnalyzer and sent by syslog 11
Additional configuration required for SSO users 11
FortiAnalyzer 7.2.3 and later firmware on FortiGuard 11
Configuration backup requires a password 11
FortiAnalyzer-3500E support 12
PostgreSQL database upgrade 12
Serial console has changed for FortiAnalyzer deployments on Xen 13
OpenXen in PV mode is not supported in FortiAnalyzer 7.4.1 13
Default GUI theme changed 13
Management Extensions visibility in the GUI 13
FortiManager Features removed 13
Setup wizard requires FortiCare registration 14
Hyperscale firewall mode 14
Modifying the interface status with the CLI 14
Citrix XenServer default limits and upgrade 14
FortiAnalyzer VM upgrade requires more memory 15
Maximum ADOM limits for FortiAnalyzer 15
Port 8443 reserved 15
Hyper-V FortiAnalyzer-VM running on an AMD CPU 15
SSLv3 on FortiAnalyzer-VM64-AWS 16
Upgrade Information 17
Downgrading to previous firmware versions 17
Firmware image checksums 17
FortiAnalyzer VM firmware 17
SNMP MIB files 19
Product Integration and Support 20
Supported software 20
Web browsers 21
FortiOS and FortiOS Carrier 21
2024-10-18 Updated Resolved issues on page 51 and Known issues on page 52.
This document provides information about FortiAnalyzer version 7.4.5 build 2553.
The recommended minimum screen resolution for the FortiAnalyzer GUI is 1920 x 1080.
Please adjust the screen resolution accordingly. Otherwise, the GUI may not display properly.
Supported models
FAZ-300F supports the subscription license for the SOC service. However performance may
be impacted because FAZ-300F has fewer resources and a smaller CPU than other
FortiAnalyzer models that support the SOC service.
The FortiAnalyzer VM subscription license supports FortiAnalyzer version 6.4.1 and later. For information about
supported firmware, see FortiAnalyzer VM firmware on page 17.
See also Appendix A - Default and maximum number of ADOMs supported on page 54.
You can use the FortiAnalyzer VM subscription license with new FAZ-VM installations.
For existing FAZ-VM installations, you can migrate to a FortiAnalyzer VM subscription license,
starting with FortiAnalyzer 7.0.1. See the FortiAnalyzer 7.0.1 VM License Migration Guide.
The following section describes supported models and minimum system requirements for management extension
applications (MEA) in FortiAnalyzer 7.4.5.
FortiAnalyzer uses port TCP/443 or TCP/4443 to connect to the Fortinet registry and
download MEAs. Ensure that the port is also open on any upstream FortiGates. For more
information about incoming and outgoing ports, see the FortiAnalyzer 7.0 Ports Guide.
As of FortiAnalyzer 7.4.0, the Management Extensions pane is only visible in the GUI when docker status is enabled and
at least one MEA is enabled and downloaded. For more information about enabling and using the MEAs, see the
Management Extensions documentation in the FortiAnalyzer Documents Library.
You can use any of the following FortiAnalyzer models as a host for management extension applications:
Some MEAs have minimum system requirements that require you to increase system resources. The following table
identifies the minimum requirements for each MEA as well as the recommended system resources to function well in a
production environment.
MEA minimum system requirements apply only to the individual MEA and do not take into consideration any system
requirements for resource-sensitive FortiAnalyzer features or multiple, enabled MEAs.
*The numbers in the Recommended system resources for production column are a combination of the default system
resource settings for FortiAnalyzer plus the recommended system requirements for the MEA.
This section highlights some of the operational changes that administrators should be aware of in FortiAnalyzer version
7.4.5.
When FIPS mode is enabled, upgrading from 7.4.3 to 7.4.5 might fail due to the following error message: "FIPS firmware
signature verification failed". The following steps should be taken as workaround:
1. Backup FortiAnalyzer-v7.4.3-fips-cc mode DB.
2. Disable FortiAnalyzer-v7.4.3-fips mode to normal mode.
3. Upgrade FortiAnalyzer-v7.4.3 normal mode to v7.4.5.
4. FortiAnalyzer-v7.4.5 enable fips-cc mode.
5. Restore FortiAnalyzer-v7.4.3-fips DB on FortiAnalyzer-v7.4.5-fips.
The field names no longer include the "ad." prefix when log forwarding to a CEF server.
The following CLI command has been removed, which was previously used to access shell when enabled:
execute shell
In FortiAnalyzer 7.4.3, the following FortiView monitors are removed from the GUI:
Beginning in 7.4.3, alert notifications generated by FortiAnalyzer and sent by syslog will use the RFC-5424 format.
Beginning in 7.4.3, additional configuration is needed for FortiAnalyzer Users declared as wildcard SSO users.
When configuring Administrators as wildcard SSO users, the ext-auth-accprofile-override and/or ext-auth-
adom-override features, under Advanced Options, should be enabled if the intent is to obtain the ADOMs list and/or
permission profile from the SAML IdP.
Starting in FortiAnalyzer 7.2.1, a setup wizard executes to prompt the user for various configuration steps and
registration with FortiCare. During the execution, the FortiAnalyzer unit attempts to communicate with FortiGuard for a
list of FortiAnalyzer firmware images currently available on FortiGuard – older and newer.
In the case of FortiAnalyzer 7.2.2, a bug in the GUI prevents the wizard from completing and prevents the user from
accessing the FortiAnalyzer unit. The issue has been fixed in 7.2.3 and later and a CLI command has been added to
bypass the setup wizard at login time.
config system admin setting
set firmware-upgrade-check disable
end
Fortinet has not uploaded FortiAnalyzer 7.2.3 and later firmware to FortiGuard in order to work around the GUI bug,
however, the firmware is available for download from the Fortinet Support website.
As of FortiAnalyzer 7.4.2, configuration backup files are automatically encrypted and require you to set a password. The
password is required for scheduled backups as well.
In previous versions, the encryption and password were optional.
For more information, see the FortiAnalyzer Administration Guide.
FortiAnalyzer-3500E support
FortiAnalyzer 7.4.2 and later does not support the FortiAnalyzer-3500E device.
FortiAnalyzer 7.4.2 introduces an upgrade of the OpenSSL library to address known vulnerabilities in the library. As a
result, the SSL connection that is setup between the FortiAnalyzer-3500E device and the Google Map server hosted by
Fortinet uses a SHA2 (2048) public key length. The certificate stored on the BIOS that is used during the setup of the
SSL connection contains a SHA1 public key length, which causes the connection setup to fail. Running the following
command shows the key length.
FAZ3500E # config system certificate local
(local)# ed Fortinet_Local
(Fortinet_Local)# get
name : Fortinet_Local
password : *
comment : Default local certificate
private-key :
certificate :
Subject: C = US, ST = California, L = Sunnyvale, O = Fortinet, OU = FortiAnalyzer,
CN = FL3K5E3M15000074, emailAddress = [email protected]
Issuer: C = US, ST = California, L = Sunnyvale, O = Fortinet, OU = Certificate
Authority, CN = support, emailAddress = [email protected]
Valid from: 2015-03-06 16:22:10 GMT
Valid to: 2038-01-19 03:14:07 GMT
Fingerprint: FC:D0:0C:8D:DC:57:B6:16:58:DF:90:22:77:6F:2C:1B
Public key: rsaEncryption (1024 bits)
Signature: sha1WithRSAEncryption
Root CA: No
Version: 3
Serial Num:
1e:07:7a
Extension 1: X509v3 Basic Constraints:
CA:FALSE
...
(Fortinet_Local)#
FortiAnalyzer 7.4.1 includes an upgrade of the PostgreSQL database. Upon upgrading to FortiAnalyzer 7.4.1, by default
analytical features, such as Log View, FortiView, Reports, and Event Management are unavailable until the PostgreSQL
database finishes upgrading. During this time, FortiAnalyzer will continue to receive new logs, but they will not be
inserted into the PostgreSQL database. PostgreSQL database upgrade times depend on the number of ADOM
configured and the analytical log volume. Some sample upgrade times are shown below.
For customers who prefer to not wait for accessing the analytical features, such as Log View, FortiView, Reports, and
Event Management, for new logs, they can execute a SQL. This command can take a long time to complete depending
on the amount of data.
FAZVM64 # exec sql-local rebuild-db
Rebuild the entire log SQL database has been requested.
This operation will remove the log SQL database and rebuild from log data.
This operation will reboot the device.
Do you want to continue? (y/n)
In FortiAnalyzer 7.4.1, the serial console for Xen deployments has changed from hvc0 (Xen specific) to ttyS0 (standard).
As of FortiAnalyzer 7.4.1, kernel and rootfs are encrypted. OpenXen in PV mode tries to unzip the kernel and rootfs, but
it will fail. Therefore, OpenXen in PV mode cannot be used when deploying or upgrading to FortiAnalyzer 7.4.1. Only
HVM (hardware virtual machine) mode is supported for OpenXen in FortiAnalyzer 7.4.1.
As of FortiAnalyzer 7.4.1, the default GUI theme is Jade. The default theme can be changed from System Settings >
Settings.
As of FortiAnalyzer 7.4.0, the Management Extensions pane is only visible in the GUI when docker status is enabled and
at least one management extension application (MEA) is enabled and downloaded. For more information about enabling
and using the MEAs, see the Management Extensions documentation in the FortiAnalyzer Documents Library.
FortiAnalyzer 7.2.1 and later no longer supports FortiManager Features. If you have FortiManager Features enabled
before upgrading to FortiAnalyzer 7.2.1, FortiManager Features will be permanently disabled after upgrading to
FortiAnalyzer 7.2.1.
Starting in FortiAnalyzer 7.2.1, the FortiAnalyzer Setup wizard requires you to complete the Register with FortiCare step
before you can access the FortiAnalyzer appliance or VM. Previously the step was optional.
For FortiAnalyzer units operating in a closed environment, contact customer service to receive an entitlement file, and
then load the entitlement file to FortiAnalyzer by using the CLI.
When FortiManager is managing FortiAnalyzer in a closed environment, FortiManager contains the FortiAnalyzer
contract information, and you can point FortiAnalyzer to FortiManager.
FortiAnalyzer does not support logs from the following models when they have hyperscale firewall mode and netflow
enabled:
l FortiGate-1800F
l FortiGate-1801F
l FortiGate-2600F
l FortiGate-2601F
l FortiGate-4200F
l FortiGate-4201F
l FortiGate-4400F
l FortiGate-4401F
FortiAnalyzer only supports logs when the normal firewall mode with standard FortiGate logging are enabled.
Starting in verion 7.0.1, the CLI to modify the interface status has been changed from up/down to enable/disable.
For example:
config system interface
edit port2
set status <enable/disable>
next
end
Citrix XenServer limits ramdisk to 128M by default. However the FAZ-VM64-XEN image is larger than 128M. Before
updating to FortiAnalyzer 6.4, increase the size of the ramdisk setting on Citrix XenServer.
When upgrading FortiAnalyzer VM units from a previous version to FortiAnalyzer 7.2.2 or higher, the upgrade may fail
because of memory allocation. As of FortiAnalyzer 7.2.2, FortiAnalyzer VM requires 16 GB of RAM and 4 CPU.
Workaround: Before upgrading FortiAnalyzer VM to FortiAnalyzer 7.2.2, change the memory allocation to 16 GB of
RAM.
FortiAnalyzer hardware devices and VMs display a warning when the maximum number of ADOMs is reached or
exceeded. The platform does not enforce the limit; however, adding more ADOMs may affect the performance of the
unit. For more details, see Appendix A - Default and maximum number of ADOMs supported on page 54.
Port 8443 is reserved for https-logging from FortiClient EMS for Chromebooks. See also FortiAnalyzer 7.0 Ports
Reference on the Docs Library.
A Hyper-V FAZ-VM running on a PC with an AMD CPU may experience a kernel panic. Fortinet recommends running
VMs on an Intel-based PC.
SSLv3 on FortiAnalyzer-VM64-AWS
Due to known vulnerabilities in the SSLv3 protocol, FortiAnalyzer-VM64-AWS only enables TLSv1 by default. All other
models enable both TLSv1 and SSLv3. If you wish to disable SSLv3 support, please run:
config system global
set ssl-protocol t1sv1
end
Prior to upgrading your FortiAnalyzer, please review the FortiAnalyzer Upgrade Guide in detail
as it includes all of the necessary steps and associated details required to upgrade your
FortiAnalyzer device or VM, including recommended upgrade paths.
See the FortiAnalyzer Upgrade Guide in the Fortinet Document Library.
FortiAnalyzer does not provide a full downgrade path. You can downgrade to a previous firmware release by using the
GUI or CLI, but doing so results in configuration loss. A system reset is required after the firmware downgrade process
has completed. To reset the system, use the following CLI commands via a console port connection:
execute reset {all-settings | all-except-ip}
execute format {disk | disk-ext4 | disk-ext3}
The MD5 checksums for all Fortinet software and firmware releases are available at the Customer Service & Support
portal, https://support.fortinet.com. After logging in, go to Download > Firmware Image Checksums, enter the image file
name including the extension, and select Get Checksum Code.
FortiAnalyzer VM firmware
Fortinet provides FortiAnalyzer VM firmware images for Amazon AWS, Amazon AWSOnDemand, Citrix and Open
Source XenServer, Linux KVM, Microsoft Hyper-V Server, and VMware ESX/ESXi virtualization environments.
l The 64-bit Amazon Machine Image (AMI) is available on the AWS marketplace.
l .out: Download the 64-bit firmware image to upgrade your existing FortiAnalyzer VM installation.
l .out.OpenXen.zip: Download the 64-bit package for a new FortiAnalyzer VM installation. This package contains
the QCOW2 file for the Open Source Xen Server.
l .out.CitrixXen.zip: Download the 64-bit package for a new FortiAnalyzer VM installation. This package
contains the Citrix XenServer Virtual Appliance (XVA), Virtual Hard Disk (VHD), and OVF files.
l .out: Download the 64-bit firmware image to upgrade your existing FortiAnalyzer VM installation.
l .out.gcp.zip: Download the 64-bit package for a new FortiAnalyzer VM installation.
Linux KVM
l .out: Download the 64-bit firmware image to upgrade your existing FortiAnalyzer VM installation.
l .out.kvm.zip: Download the 64-bit package for a new FortiAnalyzer VM installation. This package contains
QCOW2 that can be used by qemu.
Microsoft Azure
The files for Microsoft Azure have AZURE in the filenames, for example <product>_VM64_AZURE-v<number>-
build<number>-FORTINET.out.hyperv.zip.
l .out: Download the firmware image to upgrade your existing FortiAnalyzer VM installation.
The files for Microsoft Hyper-V Server have HV in the filenames, for example, <product>_VM64_HV-v<number>-
build<number>-FORTINET.out.hyperv.zip.
l .out: Download the firmware image to upgrade your existing FortiAnalyzer VM installation.
l .hyperv.zip: Download the package for a new FortiAnalyzer VM installation. This package contains a Virtual
Hard Disk (VHD) file for Microsoft Hyper-V Server.
l .out: Download the 64-bit firmware image to upgrade your existing FortiAnalyzer VM installation.
l .out.opc.zip: Download the 64-bit package for a new FortiAnalyzer VM installation.
VMware ESX/ESXi
l .out: Download the 64-bit firmware image to upgrade your existing VM installation.
l .ovf.zip: Download either the 64-bit package for a new VM installation. This package contains an Open
Virtualization Format (OVF) file for VMware and two Virtual Machine Disk Format (VMDK) files used by the OVF file
during deployment.
For more information, see the FortiAnalyzer Data Sheet available on the Fortinet web site. VM
installation guides are available in the Fortinet Document Library.
You can download the FORTINET-FORTIMANAGER-FORTIANALYZER.mib MIB file in the firmware image file folder.
The Fortinet Core MIB file is located in the main FortiAnalyzer version 5.00 file folder.
This section lists FortiAnalyzer 7.4.5 support of other Fortinet products. It also identifies what FortiAnalyzer features are
supported for managed platforms and what languages FortiAnalyzer supports. It also lists which Fortinet models can be
managed by FortiAnalyzer.
The section contains the following topics:
l Supported software on page 20
l Feature support on page 26
l Language support on page 27
l Supported models on page 28
Supported software
To confirm that a device model or firmware version is supported by the current firmware
version running on FortiAnalyzer, run the following CLI command:
diagnose dvm supported-platforms list
Always review the Release Notes of the supported platform firmware version before upgrading
your device.
Web browsers
The FortiAnalyzer Release Notes communicate support for FortiOS versions that are
available at the time of the FortiAnalyzer 7.4.5 release. For additional information about other
supported FortiOS versions, please refer to the FortiAnalyzer compatibility chart in the Fortinet
Document Library.
See FortiAnalyzer compatibility with FortiOS.
FortiAnalyzer 7.4.5 supports the following versions of FortiOS and FortiOS Carrier:
l 7.4.0 to 7.4.5
l 7.2.0 to 7.2.10
l 7.0.0 to 7.0.17
l 6.4.0 to 6.4.15
l 6.2.0 to 6.2.16
l 6.0.0 to 6.0.18
FortiADC
FortiAnalyzer
FortiAuthenticator
FortiCache
FortiCASB
FortiClient
FortiDDoS
FortiDeceptor
FortiIsolator
FortiMail
FortiManager
FortiNAC
FortiNDR
FortiPAM
FortiProxy
FortiSandbox
FortiSASE
For more information about compatibility, see the FortiSASE Release Notes.
FortiSOAR
FortiSwitch ATCA
FortiToken
FortiWeb
Virtualization
Public Cloud
Private Cloud
Feature support
The following table lists FortiAnalyzer feature support for log devices.
FortiGate ✓ ✓ ✓ ✓
FortiCarrier ✓ ✓ ✓ ✓
FortiADC ✓ ✓ ✓
FortiAnalyzer ✓ ✓
FortiAuthenticator ✓
FortiCache ✓ ✓ ✓
FortiClient registered ✓ ✓ ✓
to FortiGate
FortiClient registered ✓ ✓ ✓
to FortiClient EMS
FortiDDoS ✓ ✓ ✓ ✓
FortiDeceptor ✓
FortiFirewall ✓ ✓ ✓ ✓
FortiMail ✓ ✓ ✓
FortiManager ✓ ✓
FortiNAC ✓
FortiNDR ✓ ✓ ✓ ✓
FortiPAM ✓ ✓ ✓
FortiProxy ✓ ✓ ✓ ✓
FortiSandbox ✓ ✓ ✓
FortiSOAR ✓ ✓ ✓
FortiWeb ✓ ✓ ✓
Syslog ✓ ✓ ✓
Language support
English ✓ ✓
Chinese (Simplified) ✓ ✓
Chinese (Traditional) ✓ ✓
French ✓ ✓
Hebrew ✓
Hungarian ✓
Japanese ✓ ✓
Korean ✓ ✓
Portuguese ✓
Russian ✓
Spanish ✓
To change the FortiAnalyzer language setting, go to System Settings > Admin > Admin Settings, in Administrative
Settings > Language select the desired language on the drop-down menu. The default value is Auto Detect.
Russian, Hebrew, and Hungarian are not included in the default report languages. You can create your own language
translation files for these languages by exporting a predefined language from FortiAnalyzer, modifying the text to a
different language, saving the file as a different language name, and then importing the file into FortiAnalyzer. For more
information, see the FortiAnalyzer Administration Guide.
Supported models
The following tables list which FortiGate, FortiCarrier, FortiDDoS, FortiAnalyzer, FortiMail, FortiSandbox, FortiSwitch
ATCA, FortiWeb, FortiCache, FortiProxy, and FortiAuthenticator models and firmware versions that can be managed by
a FortiManager or send logs to a FortiManager running version 7.4.5.
Software license activated LENC devices are supported, if their platforms are in the
supported models list. For example, support of FG-3200D indicates support of FG-
3200D-LENC.
FortiGate models
The following FortiGate models are released with FortiOS firmware. For information about supported FortiGate models
on special branch releases of FortiOS firmware, see FortiGate special branch models on page 35.
The following FortiGate models are released on special branches of FortiOS. FortiAnalyzer version 7.4.5 supports these
models on the identified FortiOS version and build number.
For information about supported FortiGate models released with FortiOS firmware, see FortiGate models on page 29.
FortiOS 7.2
FortiOS 7.0
FortiOS 6.4
FortiOS 6.2
FortiOS 6.0
FortiCarrier models
The following FortiCarrier models are released on special branches of FortiOS Carrier. FortiAnalyzer version 7.4.5
supports these models on the identified FortiOS Carrier version and build number.
For information about supported FortiCarrier models released with FortiOS Carrier firmware, see FortiCarrier models on
page 38.
FortiCarrier 7.0
FortiCarrier 6.4
FortiCarrier 6.2
FortiCarrier 6.0
FortiADC models
FortiAnalyzer models
FortiAuthenticator models
FortiCache models
FortiDDoS models
FortiDeceptor models
FortiFirewall models
Some of the following FortiFirewall models are released on special branches of FortiFirewall firmware. FortiAnalyzer
version 7.4.5 supports these models on the identified FortiFirewall firmware version and build number.
FortiFirewall 7.4
FortiFirewall 7.2
FortiFirewall 7.0
FortiFirewallCarrier models
Some of the following FortiFirewallCarrier models are released on special branches of FortiFirewallCarrier firmware.
FortiAnalyzer version 7.4.5 supports these models on the identified FortiFirewallCarrier firmware version and build
number.
FortiIsolator models
FortiMail models
FortiMail: FE-200F, FE-400F, FE-900F, FE-2000E, FE-2000F, FE-3000E, FE-3000F, FE- 7.4
3200E
FortiMail VM: FML-VM, FortiMail Cloud
FortiMail: FE-60D, FE-200D, FE-200E, FE-200F, FE-400E, FE-400F, FE-900F, FE-2000E, 7.2
FE-2000F, FE-3000E, FE-3000F, FE-3200E
FortiMail VM: FML-VM, FortiMail Cloud
FortiMail: FE-60D, FE-200D, FE-200E, FE-200F, FE-400E, FE-400F, FE-900F, FE-1000D, 7.0
FE-2000E, FE-2000F, FE-3000D, FE-3000E, FE-3000F, FE-3200E
FortiMail VM: FML-VM, FortiMail Cloud
FortiNAC models
FortiNDR models
FortiPAM models
FortiProxy models
FortiSandbox models
FortiSOAR models
FortiWeb models
The following issues have been fixed in 7.4.5. To inquire about a particular bug, please contact Customer Service &
Support.
The following issues have been identified in a previous version of FortiAnalyzer and remain in FortiAnalyzer 7.4.5.
Device Manager
Bug ID Description
1106056 Deleting a model device may result in the removal of the Logs folder under Storage. This
issue occurs only if the model device never comes online and does not match a FortiGate.
Fabric View
Bug ID Description
918006 An issue with the EMS Asset Inventory has been identified. When running the playbook, no
assets or inventory are displayed on FortiAnalyzer, and the Fabric View lists remain empty.
1078817 The "FortiClient EMS Cloud" Fabric Connector (existing/newly added) may not function
properly, causing FortiAnalyzer to potentially fail in establishing a successful connection with
the "FortiClient EMS Cloud" due to this issue.
FortiView
Bug ID Description
922053 Mismatched Username Detected for the Same IP Address in IOC Compromised Hosts.
954542 When the time range is extensive, FortiAnalyzer may experience limitations in handling data
points, resulting in potential omissions of data entries in the final results for FortiView SD-
WAN Monitors widgets.
1050052 In some cases, the compromised host entry may display different FSSO users and source IPs
than the actual users and source IPs on the drill-down page.
Reports
Bug ID Description
895106 Top destination by bandwidth dataset does not exclude long-live session.
System Settings
Bug ID Description
1058282 Remote administrators may be unable to review the Event Logs, as the GUI might display the
following message: "Web Server Error 500."
1063040 Unable to import a local certificate into FortiAnalyzer. This issue may occur if the certificate is
encrypted with a newer OpenSSL version that FortiAnalyzer does not yet support.
Workaround:
Convert the latest certificate to the legacy format before uploading it to FortiAnalyzer.
This section identifies the supported number of ADOMs for FortiAnalyzer hardware models and virtual machines.
See also the FortiAnalyzer Data Sheet.
Hardware models
Desktop models 1 1
150G Series 3 3
Virtual Machines
Five (5) ADOMs are included with FortiAnalyzer VM subscription licenses. Additional ADOMs can be purchased with an
ADOM subscription license.
Copyright© 2025 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 Chief Legal Officer, 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.