808bits

Fortress Secure Client

FIPS 140-2 certificate #831 · Fortress™ Technologies, Inc. · data as of 2026-08-28
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 number831
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorFortress™ Technologies, Inc. · website
Software versions4.0

Module description

The Fortress Secure Client identifies network devices and encrypts and decrypts traffic transmitted to and from those devices. A plug-and-play solution, the Client encrypts and decrypts communication across the network and protects the device against attacks without user intervention.

Approved algorithms

AlgorithmCAVP certificate
AES427, 437
HMAC201, 205, 256
RNG221, 227
SHS498, 505, 573
Triple-DES457, 463

Other algorithms

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

Tested configurations

  • Microsoft Windows XP, Microsoft Windows 2000 (single user mode)

Validation history

DateTypeLab
2007-09-05InitialCOACT 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-09-05, 2010-03-26, 2013-05-17

Source documents