808bits

Thales Datacryptor Gigabit

FIPS 140-2 certificate #495 · Thales e-Security Inc. · data as of 2026-10-21

Thales Datacryptor Gigabit, from Thales e-Security Inc., holds FIPS 140-2 certificate #495 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 number495
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorThales e-Security Inc. · website
Hardware versionsC
Firmware versions2.2

Module description

Quoted from the NIST CMVP entry for this certificate.

The Datacryptor Gigabit is a high performance, integrated security appliance that offers Gigabit Ethernet IPSec encryption. Housed in a tamper evident chassis, the Datacryptor Gigabit has two Gigabit Ethernet ports. Traffic on the local port is received in the clear, while traffic on the remote port has security processing applied to it. Fully compatible with existing IP networks, the Datacryptor Gigabit can be seamlessly deployed into Gigabit Ethernet environments, including IP siteto-site VPNs and storage over IP networks. Its high-speed AES and 3DES IPSec processing eliminates bottlenecks while providing data authentication, confidentiality, and integrity.

Approved algorithms (5)

AlgorithmCAVP certificates
AES156
HMAC-SHA-1vendor affirmed
RSAvendor affirmed
SHA-1117
Triple-DES258

Other algorithms

DES (Cert. #260); Diffie-Hellman (key agreement); MD5; HMAC-MD5

Validation history

DateTypeLab
2005-01-07InitialDOMUS
2005-10-13Update

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: 2005-01-07, 2005-10-13

Source documents