808bits

FortiGate-30D/60D/92D, FortiWiFi-60D and FortiGateRugged-60D

FIPS 140-2 certificate #2784 · 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 with the tamper evident seals installed as indicated in the Security Policy and configured according to the Entropy Token Section of the Security Policy. The module generates cryptographic keys whose strengths are modified by available entropy. There is no assurance of the minimum strength of generated keys

Certificate

Certificate number2784
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorFortinet, Inc. · website
Hardware versionsC1AA93, C1AB28, C1AC34, C1AB32, and C1AB57 with Tamper Evident Seal Kits: FIPS-SEAL-RED
Firmware versions5.2.7, build0718,160328

Module description

The FortiGate product family spans the full range of network environments, from SOHO to service provider, offering cost effective systems for any size of application. FortiGate appliances detect and eliminate the most damaging, content-based threats from email and Web traffic such as viruses, worms, intrusions, inappropriate Web content and more in real time - without degrading network performance.

Security level exceptions

  • Cryptographic Module Ports and Interfaces: Level 3
  • Roles, Services, and Authentication: Level 3
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AES3963, 3964, 3965
CVL794, 795
DRBG1161
HMAC2581, 2582, 2583
RSA2024, 2025
SHS3267, 3268, 3269
Triple-DES2172, 2173

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); AES-CCM (non-compliant); DES; HMAC-MD5; MD5

Tested configurations

  • N/A

Validation history

DateTypeLab
2016-10-31InitialCGI 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: 2016-10-31

Source documents