808bits

Fortress Controller -X (FC-X)

FIPS 140-2 certificate #1251 · 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 number1251
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorFortress™ Technologies, Inc. · website
Hardware versionsFC-250, FC-250SB, FC500, FC500SB, FC-1500 and FC1500SB
Firmware versions5.1.2, 5.1.2.5100CAJ and 5.1.2.5100CAP

Module description

The Fortress Controller -X (FC-X) secures wireless devices, users and network infrastructure. It implements Fortress's Mobile Security Protocol (MSP) to provide network authentication, key exchange, and data encryption and integrity checking at layer 2 of the OSI networking model.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Design Assurance: Level 3

Approved algorithms

AlgorithmCAVP certificate
AES852, 853, 389
HMAC469, 569, 371
RNG487, 488, 189
RSA488
SHS845, 846, 721, 722, 715
Triple-DES703

Other algorithms

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 192 bits of encryption strength); MD5; Hardware RNG

Validation history

DateTypeLab
2010-01-06InitialCOACT INC CAFE LAB
2010-01-28Update
2010-03-26Update
2010-08-02Update
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: 2010-01-06, 2010-01-28, 2010-03-26, 2010-08-02, 2013-05-17

Source documents