808bits

FortiGate-201E/301E/401E/501E/601E

FIPS 140-2 certificate #3927 · Fortinet, Inc. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition - replaced by certificate #4609. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and installed, initialized and configured as specified in the FIPS 140-2 Compliant Operation Section of the Security Policy with the tamper evident seals installed as indicated in the Security Policy. Authentication at level 3 is only applicable when identity-based authentication is enforced for the User role.

Certificate

Certificate number3927
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorFortinet, Inc. · website
Hardware versionsFortiGate-201E (C1AE64), FortiGate-301E (C1AG46), FortiGate-401E (C1AH76), FortiGate-501E (C1AG44) and FortiGate-601E (C1AH71) with Tamper Evident Seal Kit: FIPS-SEAL-RED
Firmware versionsFortiOS 6.0 build 5445 and FortiOS 6.2 build 5548

Module description

The FortiGate-201E/301E/401E/501E/601E are multiple chip, standalone cryptographic modules consisting of production grade components contained in a physically protected enclosure in accordance with FIPS 140-2 Level 2 requirements.

Security level exceptions

  • Roles, Services, and Authentication: Level 3

Approved algorithms

Allowed algorithms

Diffie-Hellman (CVL Certs. #C1572, #C1574, #C1575 and #C1576, key agreement; key establishment methodology provides between 112 and 196 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #C1572, #C1574, #C1575 and #C1576, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2021-05-17InitialLightship Security, 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: 2021-05-17

Source documents