808bits

ProtectServer Gold

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

ProtectServer Gold, from SafeNet, Inc., holds FIPS 140-2 certificate #739 at overall level 3. 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 number739
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip embedded
VendorSafeNet, Inc. · website
Hardware versionsRevisions B2, B3 and B4
Firmware versions2.03.00

Module description

Quoted from the NIST CMVP entry for this certificate.

The SafeNet PSG Adapter is a high-end intelligent PCI adapter card that provides a wide range of cryptographic functions using firmware and dedicated hardware processors. Access to the PSG is provided via a comprehensive PKCS#11 API, allowing extremely flexible use of the module in a multitude of applications.

Approved algorithms (9)

AlgorithmCAVP certificates
AES382
DSA166
ECDSA26
HMAC171
RNG184
RSA134
SHS457
Triple-DES426
Triple-DES MACvendor affirmed

Other algorithms

DES; DES MAC; AES MAC (non-compliant); CAST 128; CAST MAC; IDEA; IDEA MAC; RC2; RC2 MAC; SEED; SEED MAC; MD2; MD5; HMAC MD5; RC4; RIPEMD-128; RIPEMD-160; HMAC RMD128; HMAC RMD160; Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant); RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Validation history

DateTypeLab
2007-03-01InitialSAIC-VA
2007-03-20Update
2007-04-26Update
2009-01-26Update

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: 2007-03-01, 2007-03-20, 2007-04-26, 2009-01-26

Source documents