808bits

3e-525A, 3e-525N and 3e-519 Wireless Gateway

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

3e-525A, 3e-525N and 3e-519 Wireless Gateway, from 3e Technologies International, Inc., holds FIPS 140-2 certificate #502 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 number502
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
Vendor3e Technologies International, Inc. · website

Module description

Quoted from the NIST CMVP entry for this certificate.

A problem of increasing concern in the deployment of Wireless LANs throughout enterprise environments is security. 3e Technologies International meets this need by providing a secure, accessible, highperformance WLAN end-to-end solution, through its family of Secure Wireless Gateway/Access Points and Secure Client solutions. The 3e family of Secure Wireless Gateways implements a cryptographic suite including AES, 3DES, SHA-1, HMAC SHA-1, Diffie-Hellman, and HTTPS/TLS. These algorithms are used in combination to protect the main Gateway services of bridging from wired uplink LAN to the wire.

Approved algorithms (5)

AlgorithmCAVP certificates
AES200
HMAC13
RNG22
SHS278
Triple-DES292

Other algorithms

Diffie-Hellman (key agreement); RSA (PKCS#1; non-compliant); MD5; RC4; DES; AES (non-compliant)

Validation history

DateTypeLab
2005-01-18InitialSAIC-VA
2005-10-31Update

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: 2005-01-18, 2005-10-31

Source documents