808bits

FortiProxy-400E/2000E/4000E

FIPS 140-2 certificate #3628 · 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 with the tamper evident seals installed as indicated in the Security Policy.

Certificate

Certificate number3628
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorFortinet, Inc. · website
Hardware versionsC1AG57, C1AD93 and C1AG58 with Tamper Evident Seal Kit: FIPS-SEAL-RED
Firmware versionsFortiProxy 1.0, b0066, 190423

Module description

FortiProxy is a secure web/application proxy that protects users against internet-borne attacks by incorporating multiple detection techniques such as web filtering, DNS filtering, data loss prevention, antivirus, intrusion prevention and advanced threat protection. It helps enterprises enforce internet compliance using granular application control.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AESC655, C702, C703, C787, C806, C813, C832
CVLC702, C703, C806, C813, C832
DRBGC658, C799
ECDSAC702, C703, C806, C813, C832
HMACC702, C703, C806, C813, C832
KTS
KTS
RSAC702, C806, C813
SHSC702, C703, C806, C813, C832

Allowed algorithms

Diffie-Hellman (CVL Certs. #C702, #C703, #C806 and #C832, key agreement; key establishment methodology provides between 112 and 196 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #C702 and #C806, key agreement; key establishment methodology provides 128 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2020-03-04InitialLightship 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-03-04

Source documents