808bits

3e-010F-A-2 Cryptomodule and 3e-010F-C-2 Cryptomodule

FIPS 140-2 certificate #663 · 3e Technologies International, Inc. · data as of 2026-08-28
Historical. RNG SP800-131A Revision 1 Transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number663
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
Vendor3e Technologies International, Inc. · website
Software versions3e-010F-A-2 Version 2.0, Build 18; 3e-010F-C-2 Version 2.0, Build 15; and 3e-010F-C-2 Version 2.0, Build 15, Revision 1

Module description

The 3e-010F-A-2 and 3e-010F-C-2 Crypto Clients provide standard 802.11a/b/g wireless access along with enhanced protection through a variety of cryptographic features, providing a high level of security for wireless environments. In FIPS 140-2 mode (highly secure), encryption can be set for None, Static AES, Static 3DES, Dynamic Key Exchange and WPA2 Enterprise and Personal (AES-CCM). In non-FIPS mode, one can select None, Static AES, Static 3DES, Dynamic Key Exchange, Static WEP, WPA-Enterprise and Personal (TKIP or AES-CCM) and WPA2-Enterprise and Personal (TKIP or AES-CCM).

Security level exceptions

  • EMI/EMC: Level 3

Approved algorithms

AlgorithmCAVP certificate
AES225, 287, 288
CCM5, 6
HMAC32
RNG67
RSA112
SHS306
Triple-DES316

Other algorithms

RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength; non-compliant less than 112 bits of encryption strength)

Tested configurations

  • Microsoft Windows 2000 Professional with SP4 and Microsoft Windows XP with SP2 (single-user mode)

Validation history

DateTypeLab
2006-04-26InitialSAIC-VA
2006-08-01Update
2007-08-29Update

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: 2006-04-26, 2006-08-01, 2007-08-29

Source documents