808bits

Datacryptor® 100M Ethernet

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

Datacryptor® 100M Ethernet, from Thales e-Security Inc., holds FIPS 140-2 certificate #3042 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. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When configured as indicated in Section 1 of the Security Policy with the Point-Point license

Certificate

Certificate number3042
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorThales e-Security Inc. · website
Hardware versions1600x439, Rev. 01 and 1600x439, Rev. 02
Firmware versions5.0 and 5.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The Datacryptor® 100 Mbps Ethernet Layer 2 is rack-mountable multi-chip standalone cryptographic modules which facilitate secure data transmission across public Ethernet Layer 2 networks. The Datacryptor® uses 100BaseT ports to connect the host and public sides of the network. The Datacryptor® offers user verification services via ECDSA enabled X.509 v.3 certificates, key management based on a Elliptic Curve Diffie-Hellman key agreement scheme, and AES encryption of data passing over public networks. Management of the Datacryptor® is performed via a remote management interface.

Security level exceptions

  • Mitigation of Other Attacks: N/A

Approved algorithms (6)

AlgorithmCAVP certificates
AES2014, 2030, 2062
DRBG188
ECDSA289, 304
KAS34
KBKDF1
SHS1764, 1808

Allowed algorithms

NDRNG

Tested configurations

  • N/A

Validation history

DateTypeLab
2017-10-11InitialCOACT 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: 2017-10-11

Source documents