808bits

AirFortress™ Wireless Security Gateway Cryptographic Module

FIPS 140-2 certificate #386 · Fortress™ Technologies, Inc. · data as of 2026-09-15

AirFortress™ Wireless Security Gateway Cryptographic Module, from Fortress™ Technologies, Inc., holds FIPS 140-2 certificate #386 at overall level 1. 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 number386
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeFirmware
EmbodimentMulti-chip standalone
VendorFortress™ Technologies, Inc. · website
Firmware versions2.4

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 AF Gateway provides encryption, data integrity checking, authentication, access control, and data compression.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • EMI/EMC: Level 3
  • Design Assurance: Level 3
  • Tested: Fortress interface and Shell (FISH) Version 2.4

Approved algorithms (4)

AlgorithmCAVP certificates
AES14
HMAC-SHA-1vendor affirmed
SHA-134
Triple-DES19

Other algorithms

DES (Cert. #23); Diffie-Hellman (key agreement)

Validation history

DateTypeLab
2004-02-19InitialCOACT INC CAFE LAB
2004-04-29Update
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: 2004-02-19, 2004-04-29, 2010-03-26, 2013-05-17

Source documents