808bits

SafeNet Ethernet Encryptor, Branch Office

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

SafeNet Ethernet Encryptor, Branch Office, from SafeNet, Inc., holds FIPS 140-2 certificate #1594 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. Refer to the cryptographic module's security policy for the details on the letter v designations.

Certificate

Certificate number1594
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip standalone
VendorSafeNet, Inc. · website
Hardware versions943-5020v-004 [1] [2] and 943-50211-001 [2]
Firmware versions1.0.6.4 [1] and 2.0.2 [2]

Module description

Quoted from the NIST CMVP entry for this certificate.

The SafeNet Ethernet Encryptor Branch Office provides data privacy and access control for connections between vulnerable public and private networks. It employs a FIPS-approved AES algorithm and can be deployed in 10 Megabit Ethernet networks. The encryptor can be centrally controlled or managed across multiple remote stations using SafeNet's Security Management Center (SMC), a SNMPv3-based security management system.

Approved algorithms (6)

AlgorithmCAVP certificates
AES1243
HMAC740
RNG690
RSA596
SHS1142
Triple-DES890

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); Camellia; SEED

Validation history

DateTypeLab
2011-09-27InitialCYGNACOM 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-09-27

Source documents