808bits

Datacryptor® 100M Ethernet

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

Datacryptor® 100M Ethernet, from Thales e-Security Inc., holds FIPS 140-2 certificate #2054 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. Moved to historical list in accordance with SP800-131A Revision 1 Transition (AES/TDES key wrapping). Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When configured with the Multi-Point license as indicated in the Security Policy

Certificate

Certificate number2054
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip standalone
VendorThales e-Security Inc. · website
Hardware versions1600x439, Rev. 01 and 1600x439, Rev. 02
Firmware versions5.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The Datacryptor® 100 Mbps Ethernet Layer 2 is a rack-mountable multi-chip standalone cryptographic module designed to secure data in transmissions across public Ethernet Layer 2 networks. The Datacryptor® uses 100BaseT ports to connect the host and public sides of the network. The Datacryptor® employs an automatic key generation and exchange mechanism using X.509 v3 certificates and the Elliptic Curve Diffie-Hellman key agreement scheme. The algorithm used for securing data transmission is AES-256 GCM. Management of the Datacryptor® is performed via a remote management interface.

Approved algorithms (5)

AlgorithmCAVP certificates
AES2014, 2030, 2065
DRBG188
ECDSA289, 304
KAS34
SHS1764, 1808

Other algorithms

AES (Cert. #2014, key wrapping); HWRBG

Validation history

DateTypeLab
2013-12-05InitialCOACT INC CAFE LAB

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: 2013-12-05

Source documents