808bits

Fortress Secure Client

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

Fortress Secure Client, from Fortress™ Technologies, Inc., holds FIPS 140-2 certificate #1129 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 number1129
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorFortress™ Technologies, Inc. · website
Software versions4.1.1 Build 4278X

Module description

Quoted from the NIST CMVP entry for this certificate.

The Fortress Secure Client is a software module designed to deliver security on wireless devices such as bar scanners, handhelds, and laptops using various operating systems. A plug-and-play solution, the Client encrypts and decrypts communication across the WLAN and protects the device against attacks without user intervention.

Approved algorithms (5)

AlgorithmCAVP certificates
AES975
HMAC547
RNG552
SHS944
Triple-DES768

Other algorithms

DES; Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides 128 or 192 bits of encryption strength); MD5; RSA (non-compliant)

Tested configurations

  • Windows 2000 Professional SP 4, Windows XP Professional SP 2, Windows 2003 Server SP2, Windows Vista Ultimate Edition (single-user mode)

Validation history

DateTypeLab
2009-07-06InitialSAIC-VA
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: 2009-07-06, 2010-03-26, 2013-05-17

Source documents