808bits

CGX Cryptographic Module

FIPS 140-2 certificate #644 · SafeNet, Inc. · data as of 2026-09-15

CGX Cryptographic Module, from SafeNet, Inc., holds FIPS 140-2 certificate #644 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. 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 number644
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorSafeNet, Inc. · website
Software versions3.21.1

Module description

Quoted from the NIST CMVP entry for this certificate.

Based on SafeNet's 20 years of security expertise and the most widely deployed VPN software in the industry, the CGX Cryptographic Library provides a high-level software interface to SafeNet SafeXcel™ VPN acceleration chips, cards, and EmbeddedIP™ intellectual property. The CGX library can be used as an API to hardware accelerators or for compiling software implementations of the latest industry standard algorithms.

Security level exceptions

  • EMI/EMC: Level 3
  • Design Assurance: Level 3

Approved algorithms (5)

AlgorithmCAVP certificates
AES329
HMAC148
RNG49
SHS403
Triple-DES393

Other algorithms

DES; MD5; MD2; RSA (non-compliant); RC5; RIPEMD-128; RIPEMD-160; Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 80-bits of encryption strength)

Tested configurations

  • Linux 2.4.18-3 and Solaris 8.2/02

Validation history

DateTypeLab
2006-04-03InitialCOACT INC CAFE LAB

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: 2006-04-03

Source documents