808bits

FortiClient 5.0 VPN Client

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

FortiClient 5.0 VPN Client, from Fortinet, Inc., holds FIPS 140-2 certificate #2542 at overall level 1. 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and configured according to the Entropy Token Section of the Security Policy. The module generates cryptographic keys whose strengths are modified by available entropy. There is no assurance of the minimum strength of generated keys

Certificate

Certificate number2542
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorFortinet, Inc. · website
Software versionsFortiClient 5.0, build0367, 151201

Module description

Quoted from the NIST CMVP entry for this certificate.

The FortiClient VPN client provides a FIPS 140-2 validated, IPSec and SSL VPN client for Windows platforms.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
AES2912, 2924
CVL329
DRBG538
HMAC1842, 1851
PBKDFvendor affirmed
RSA1533
SHS2451, 2460
Triple-DES1728, 1737

Other algorithms

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 or 144 bits of encryption strength; non-compliant less than 112 bits of encryption strength); NDRNG

Tested configurations

  • Windows 7 Enterprise Edition running on a Dell Optiplex 755 with the Fortinet entropy token (part number FTR-ENT-1) (single-user mode)

Validation history

DateTypeLab
2016-01-26InitialDXC 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: 2016-01-26

Source documents