808bits

SafeEnterpriseTM Encryptor, Model 650

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

SafeEnterpriseTM Encryptor, Model 650, from SafeNet, Inc., holds FIPS 140-2 certificate #1225 at overall level 2. 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 number1225
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorSafeNet, Inc. · website
Hardware versions904-23160-007
Firmware versions3.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The SafeEnterpriseTM SONET Encryptor provides data privacy and access control for connections between vulnerable public and private SONET/SDH networks. It employs federally endorsed AES and Triple-DES algorithms and, with the flexibility to choose the desired interface module, can be deployed in a SONET OC-192 network.

Security level exceptions

  • Cryptographic Module Ports and Interfaces: Level 3
  • Roles, Services, and Authentication: Level 3
  • Design Assurance: Level 3

Approved algorithms (6)

AlgorithmCAVP certificates
AES391, 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
2009-11-24InitialCYGNACOM SOLUTIONS 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: 2009-11-24

Source documents