808bits

Fortress Secure Wireless Access Bridge ES520

FIPS 140-2 certificate #756 · Fortress™ Technologies, Inc. · data as of 2026-10-21

Fortress Secure Wireless Access Bridge ES520, from Fortress™ Technologies, Inc., holds FIPS 140-2 certificate #756 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 number756
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorFortress™ Technologies, Inc. · website
Hardware versionsES520
Firmware versions2.6.1, 2.6.3 and 2.6.4

Module description

Quoted from the NIST CMVP entry for this certificate.

The Fortress Secure Wireless Access Bridge is an all-in-one network access device housed in a rugged compact chassis, with the most stringent security available today built in. It can serve as a wireless bridge, a WLAN access point, and an eight-port LAN switch, while performing all the functions of a Fortress controller device: encrypting wireless traffic and providing Multi-factor Authentication for devices on the network it protects.

Approved algorithms (4)

AlgorithmCAVP certificates
AES423
HMAC198
RNG218
SHS494

Other algorithms

Diffie-Hellman (non-compliant key agreement; key establishment methodology provides 56 bits of encryption strength; non-compliant); RSA (non-compliant); Blowfish; DES; RC2; RC4; RC5; Safer; Skipjack; DSA (non-compliant); MD2; MD4; MD5; GUAVA; IDEA; Triple-DES

Validation history

DateTypeLab
2007-04-11InitialCOACT INC CAFE LAB
2007-05-22Update
2007-12-07Update
2010-03-26Update
2013-05-17UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab

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: 2007-04-11, 2007-05-22, 2007-12-07, 2010-03-26, 2013-05-17

Source documents