808bits

SafeEnterprise™ Encryptor, Model 600

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

SafeEnterprise™ Encryptor, Model 600, from SafeNet, Inc., holds FIPS 140-2 certificate #686 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: None

Certificate

Certificate number686
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip standalone
VendorSafeNet, Inc. · website
Hardware versions904-10001-00x, 904-10002-00x, 904-10003-00x, 904-10112-00x, 904-20001-00x, 904-20002-00x, 904-20003-00x, 904-30013-00x, 904-10014-00x, 904-10014-00x, 904-10113-00x, 904-25005-00x, 904-25005-00x, 904-25005-00x
Firmware versions3.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The SafeEnterprise™ Encryptor, Model 600 provides data privacy and access control for connections between vulnerable public and private networks. It employs FIPS approved AES and Triple-DES algorithms and, with the flexibility to choose the desired interface module, can be deployed in 155Mbps (OC-3), 622Mbps (OC-12), 1.0Gbps, and 2.4Gbps (OC-48) networks.

Approved algorithms (6)

AlgorithmCAVP certificates
AES262, 240
HMAC48
RNG18, 76
RSA15
SHS251, 319
Triple-DES268

Other algorithms

Diffie-Hellman (key agreement, key establishment methodology provides 80 bits of encryption strength; non-compliant); RSA (key wrapping, key establishment methodology provides 80 bits of encryption strength; non-compliant)

Validation history

DateTypeLab
2006-07-11InitialCYGNACOM SOLUTIONS INC
2007-04-09Update
2007-04-26Update
2007-12-07Update
2008-03-07Update

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-07-11, 2007-04-09, 2007-04-26, 2007-12-07, 2008-03-07

Source documents