808bits

Model 650 SafeNet Encryptor

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

Model 650 SafeNet Encryptor, from SafeNet, Inc., holds FIPS 140-2 certificate #2178 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. 186-2 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number2178
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip standalone
VendorSafeNet, Inc. · website
Hardware versions904-000028-001, 904-000029-001, 904-000036-001, 904-53260-007, 904-53260-207, 943-53270-007, 943-53270-207, 904-53261-007, 904-53361-201, 943-53271-007 and 943-53371-201
Firmware versions4.3

Module description

Quoted from the NIST CMVP entry for this certificate.

The SafeNet Encryptor provides data privacy and access control for connections between vulnerable public and private SONET/SDH networks or 10G Ethernet 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 or 10G Ethernet network.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (7)

AlgorithmCAVP certificates
AES2616
CVL101
DRBG400
HMAC1620
RSA1337
SHS2196
Triple-DES1574

Other algorithms

RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less then 112 bits of encryption); Diffie-Hellman (non-compliant); NDRNG

Validation history

DateTypeLab
2014-06-18InitialCGI Information Systems & Management Consultants Inc
2017-01-10UpdateCGI Information Systems & Management Consultants 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: 2014-06-18, 2017-01-10

Source documents