808bits

3e-523 and 3e-523-F1 WLAN Products

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

3e-523 and 3e-523-F1 WLAN Products, from 3e Technologies International, Inc., holds FIPS 140-2 certificate #694 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 number694
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
Vendor3e Technologies International, Inc. · website
Hardware versions3e-523 V1.0, 3e-523-F1 V1.0
Firmware versions3.4, Build 5

Module description

Quoted from the NIST CMVP entry for this certificate.

The 3e-523 and 3e-523-F1 WLAN products provide wired connections for Ethernet and Serial devices. This connection can be over an Ethernet 10/100 baseT RJ-45 and/or via RS-232/422/485 interface. The 3e-523 and 3e-523-F1 wireless connection can be configured to use IEEE 802.11a/b/g with Layer 2 AES or TDES encryption. The wireless connectivity is a wireless bridging function to, for example, another 523, a 3e-525A-3 Wireless Access Point, or similar device. The 3e-523 and 3e-523-F1 are ideal for connecting RFID readers, sensors, and other data devices (printers, terminals, etc.) into a secur

Security level exceptions

  • EMI/EMC: Level 3

Approved algorithms (5)

AlgorithmCAVP certificates
AES200
HMAC13
RNG22
SHS278
Triple-DES292

Other algorithms

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

Validation history

DateTypeLab
2006-07-21InitialSAIC-VA
2006-08-01Update

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-07-21, 2006-08-01

Source documents