SafeNet Encryptor, Model 600
SafeNet Encryptor, Model 600, from SafeNet, Inc., holds FIPS 140-2 certificate #1513 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.
Caveat: When operated in FIPS mode. Refer to the cryptographic module's security policy for the details on the letter i, p and x designations.
Certificate
| Certificate number | 1513 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 3 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | SafeNet, Inc. · website |
| Hardware versions | 904-10001-00x, 904-10002-00x, 904-10003-00x, 904-10014-00x, 904-10112-00x, 904-10113-00x, 904-20001-00x, 904-20002-00x, 904-20003-00x, 904-25005-00x, 904-30013-00x, 904-511i0-00p, 904-511i1-00p, 943-511i0-00p and 943-511i1-00p |
| Firmware versions | 4.0.2 and 4.0.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 or Ethernet networks. It employs FIPS approved AES and Triple-DES algorithms and, with the flexibility to choose the desired interface module, can be deployed in SONET 155 MB (OC-3), 622 MB (OC-12), 1.0 GB, and 2.4 GB (OC-48) networks.
Approved algorithms (6)
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
| Date | Type | Lab |
|---|---|---|
| 2011-03-04 | Initial | CYGNACOM SOLUTIONS INC |
| 2011-06-21 | Update | CYGNACOM 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: 2011-03-04, 2011-06-21