808bits

FortiGate-6301F/6501F

FIPS 140-2 certificate #3654 · Fortinet, Inc. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. 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 and entropy token installed as indicated in the Security Policy. No assurance of the minimum strength of generated keys

Certificate

Certificate number3654
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorFortinet, Inc. · website
Hardware versionsC1AG85, C1AG83 with Tamper Evident Seal Kits: FIPS-SEAL-RED
Firmware versionsFortiOS 5.6, build4265,190820

Module description

The FortiGate-6301F and FortiGate-6501F 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
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AESC531, C599, C644
CVLC531, C599, C644
DRBGC613
ECDSAC531, C599, C644
HMACC531, C599, C644
KTS
KTS
RSAC531, C644
SHSC531, C599, C644

Allowed algorithms

Diffie-Hellman (CVL Certs. #C599 and #C644, key agreement; key establishment methodology provides between 112 and 196 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #C644, key agreement; key establishment methodology provides between 128 and 256 bits of encryption strength); MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 or 128 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2020-05-19InitialLightship 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: 2020-05-19

Source documents