808bits

AirFortress® Wireless Security Gateway

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

AirFortress® Wireless Security Gateway, from Fortress™ Technologies, Inc., holds FIPS 140-2 certificate #794 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. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode

Certificate

Certificate number794
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorFortress™ Technologies, Inc. · website
Hardware versionsAF2100
Firmware versions2.5.6

Module description

Quoted from the NIST CMVP entry for this certificate.

The AirFortress® Wireless Security Gateway is an electronic encryption module that enforces network access rights and encrypts and decrypts communication across a WLAN. Installed by the vendor onto a production-quality hardware platform and deployable on any LAN or WAN, the AirFortress® Wireless Security Gateway provides encryption, data integrity checking, authentication, access control, and data compression.

Approved algorithms (4)

AlgorithmCAVP certificates
AES14
HMAC62
SHS316
Triple-DES107

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 56 bits of encryption strength; non-compliant); MD5; DES; RSA (non-compliant); ANSI X9.31 RNG (non-compliant); non-Approved RNG

Validation history

DateTypeLab
2007-07-02InitialCOACT INC CAFE LAB
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-07-02, 2010-03-26, 2013-05-17

Source documents