808bits

FortiGate-VM Virtual Appliance

FIPS 140-2 certificate #2887 · Fortinet, Inc. · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. There is no assurance of the minimum strength of generated keys

Certificate

Certificate number2887
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorFortinet, Inc. · website
Software versionsFortiGate-VM64 v5.2.7,build0718,160328

Module description

The FortiGate-VM appliances are software modules designed to execute on a General Purpose Computer (GPC) hardware platform running the VMware hypervisor and FortiOS 5.2. The FortiOS provides integrated firewall, VPN, antivirus, antispam, intrusion prevention, content filtering and traffic shaping and HA capabilities.

Security level exceptions

  • Cryptographic Module Ports and Interfaces: Level 3
  • Roles, Services, and Authentication: Level 3
  • Physical Security: N/A
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AES4021, 4022
CVL850, 851
DRBG1199
HMAC2623, 2624
RSA2191
SHS3317, 3318
Triple-DES2201, 2202

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 201 bits of encryption strength; non-compliant less than 112 bits of encryption strength); RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength; non-compliant less than 112 bits of encryption strength); DES; HMAC-MD5; MD5

Tested configurations

  • FortiGate-VM on VMware ESXi 5.5 (single-user mode) running on Dell PowerEdge R720 with Intel Xeon E5-2620 processor with the Fortinet entropy token (part number FTR-ENT-1)

Validation history

DateTypeLab
2017-04-21InitialCGI Information Systems & Management Consultants Inc

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2017-04-21

Source documents