808bits

3e-523-F2 and 3e-523-3 Secure Multi-function Wireless Data Points

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

3e-523-F2 and 3e-523-3 Secure Multi-function Wireless Data Points, from 3e Technologies International, Inc., holds FIPS 140-2 certificate #1253 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: When operated in FIPS mode

Certificate

Certificate number1253
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
Vendor3e Technologies International, Inc. · website
Hardware versions1.0, 1.1, 1.2 (3e-523-F2) and 2.0 (3e-523-3)
Firmware versions4.3.2

Module description

Quoted from the NIST CMVP entry for this certificate.

The 3e-523-F2 and 3e-523-3 operate as either a gateway connecting a local area network to wide area network (WAN), an access point within a wireless local area network (WLAN), a client within a WLAN, or a wireless bridging device. 3eTI software provides the following major services in FIPS mode: Wireless 802.11a/b/g Access Point functionality; Wireless 802.11a/b/g Client functionality; Wireless 802.11a/b/g Bridge functionality; Wireless 802.11a/b/g Mesh functionality (auto-forming, self-healing wireless capability); IEEE 802.11i.

Approved algorithms (6)

AlgorithmCAVP certificates
AES1021, 1022
HMAC570, 571
RNG583
RSA490
SHS975, 976
Triple-DES782, 783

Other algorithms

Diffie-Hellman; RSA (key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant); MD5; RC4; DES; AES CFB (non-compliant)

Validation history

DateTypeLab
2010-01-28InitialSAIC-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: 2010-01-28

Source documents