808bits

FortiGate-3016B, FortiGate-3600A and FortiGate-3810A-E4

FIPS 140-2 certificate #1098 · Fortinet, Inc. · data as of 2026-10-21

FortiGate-3016B, FortiGate-3600A and FortiGate-3810A-E4, from Fortinet, Inc., holds FIPS 140-2 certificate #1098 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

Certificate

Certificate number1098
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorFortinet, Inc. · website
Hardware versionsC4XA14, V3BU94 and C3GV75
Firmware versionsFortiOS 3.00, build8785, 080605

Module description

Quoted from the NIST CMVP entry for this certificate.

FortiGate Multi-Threat Security Solutions are dedicated, hardware-based devices that deliver complete content protection against blended threats at the network perimeter or within the internal network.

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
AES612, 613, 614
HMAC315, 316, 317
RNG345
RSA284, 285
SHS660, 661, 662
Triple-DES582, 583, 584

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 method provides 112 bits of encryption strength); DES; MD5; HMAC-MD5

Validation history

DateTypeLab
2009-03-10InitialDOMUS

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: 2009-03-10

Source documents