808bits

FortiGate-200B [1], FortiGate-310B [2] and FortiGate-620B [3]

FIPS 140-2 certificate #1834 · Fortinet, Inc. · data as of 2026-09-12

FortiGate-200B [1], FortiGate-310B [2] and FortiGate-620B [3], from Fortinet, Inc., holds FIPS 140-2 certificate #1834 at overall level 2. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its validation history, algorithm certificates and security policy, drawn from the NIST CMVP entry.

Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and with the tamper evident seals installed as indicated in the Security Policy

Certificate

Certificate number1834
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorFortinet, Inc. · website
Hardware versionsC4CD24 [1], C4ZF35 [2] and C4AK26 [3] with Tamper Evident Seal Kit: FIPS-SEAL-BLUE
Firmware versionsFortiOS 4.0, build8892, 111128

Module description

Quoted from the NIST CMVP entry for this certificate.

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 (6)

AlgorithmCAVP certificates
AES1408, 1899, 1900
HMAC829, 1139, 1140
RNG996
RSA685, 973
SHS1278, 1668, 1669
Triple-DES961, 1234, 1235

Other algorithms

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

Validation history

DateTypeLab
2012-11-08InitialDXC Technology

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: 2012-11-08

Source documents