808bits

3e-636S-1 Accelerated Crypto Module

FIPS 140-2 certificate #1218 · 3e Technologies International, Inc. · data as of 2026-10-21

3e-636S-1 Accelerated Crypto Module, from 3e Technologies International, Inc., holds FIPS 140-2 certificate #1218 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 number1218
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip embedded
Vendor3e Technologies International, Inc. · website
Hardware versions1.0(A)
Firmware versions4.3.1

Module description

Quoted from the NIST CMVP entry for this certificate.

3eTI's 3e-636S-1 Accelerated Crypto Module provides AES and Triple-DES data encryption, SHS secure hashing, and HMAC keyed hashing at very high levels of sustained bandwidth. The 3e-636S-1 leverages built-in hardware-based cryptography to greatly accelerate device performance. The 3e-636S-1 is a robust, stand-alone inline encryptor which can straightforwardly be inserted into a network where FIPS 140-2 Validation is required. The 3e-636S-1 helps customers meet Federal Cryptography requirements at extremely high levels of performance, where traditional software-based algorithm implementation

Approved algorithms (6)

AlgorithmCAVP certificates
AES1022, 1023
HMAC571, 572
RNG583
RSA490
SHS976, 977
Triple-DES783, 784

Other algorithms

RSA (key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant); MD5

Validation history

DateTypeLab
2009-10-22InitialSAIC-VA

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-10-22

Source documents