808bits

SafeNet HighAssurance 500/1000 Gateway Cryptographic Module

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

SafeNet HighAssurance 500/1000 Gateway Cryptographic Module, from SafeNet, Inc., holds FIPS 140-2 certificate #385 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number385
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorSafeNet, Inc. · website
Hardware versionsSE-HA500-01 and SE-HA1000-01
Firmware versions5.01 and 7.0.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The SafeNet HA500/1000 Gateway is a high-performance, standards-based hardware Virtual Private Network (VPN) and firewall. Providing a high speed, low cost solution, it features the strongest cryptography available and complete manageability. SafeNet custom designed a state-of-the-art Application Specific Integrated Circuits (ASIC) for the HA500/1000 that allows encryption using either AES, DES, or triple-DES as nIeeded by client applications.

Security level exceptions

  • EMI/EMC: Level 3

Approved algorithms (5)

AlgorithmCAVP certificates
AES96
HMAC-SHA-1vendor affirmed
RSAvendor affirmed
SHA-1187
Triple-DES210

Other algorithms

DES (Cert. #233); HMAC-MD5, Diffie-Hellman (key agreement); DSA (non-compliant)

Validation history

DateTypeLab
2004-02-19InitialCOACT INC CAFE LAB
2004-10-19Update
2005-06-06Update

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: 2004-02-19, 2004-10-19, 2005-06-06

Source documents