808bits

Fortress Secure Client Bridge

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

Fortress Secure Client Bridge, from Fortress™ Technologies, Inc., holds FIPS 140-2 certificate #886 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. 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 number886
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-chip standalone
VendorFortress™ Technologies, Inc. · website
Hardware versions1.0
Firmware versions2.1.1

Module description

Quoted from the NIST CMVP entry for this certificate.

The Fortress Secure Client Bridge is a hardware module designed to deliver security on wireless and wired devices that cannot run the Fortress Secure Client software. A plug-and-play solution, the Secure Client Bridge encrypts and decrypts communication across the WLAN and LAN and protects the device against attacks without user intervention.

Approved algorithms (5)

AlgorithmCAVP certificates
AES545
HMAC286
RNG312
SHS609
Triple-DES541

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); DSA (non-compliant); RSA (non-compliant); MD2; MD5; Blowfish; CAST; IDEA; RC2; RC4; RC5

Validation history

DateTypeLab
2008-01-07InitialCOACT 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: 2008-01-07, 2010-03-26, 2013-05-17

Source documents