808bits

Datacryptor® Gig Ethernet v1.0 and v1.1

FIPS 140-2 certificate #1187 · Thales e-Security Inc. · data as of 2026-09-08

Datacryptor® Gig Ethernet v1.0 and v1.1, from Thales e-Security Inc., holds FIPS 140-2 certificate #1187 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. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: None

Certificate

Certificate number1187
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorThales e-Security Inc. · website
Hardware versions1600X409 v1.00
Firmware versionsv1.0 and v1.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The Datacryptor® Gig Ethernet v1.0 and v1.1 are multi-chip standalone cryptographic modules. They secure communications using signed Diffie-Hellman key exchange and AES-256 encryption over Gigabit Ethernet networks. They provide data encryption over 1000baseX (802.3z) with supported media types of 1000BaseSX (short-haul fiber), 1000BaseLX (long-haul fiber) or 1000BaseCX (single twisted-pair copper). The units also provide integrated secure unit management capability employing the same techniques used for traffic encryption.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • EMI/EMC: Level 3

Approved algorithms (4)

AlgorithmCAVP certificates
AES454
DSA184
RNG239
SHS517

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant)

Validation history

DateTypeLab
2009-09-21InitialCYGNACOM 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: 2009-09-21

Source documents