Fortress Controller -X (FC-X)
Fortress Controller -X (FC-X), from Fortress™ Technologies, Inc., holds FIPS 140-2 certificate #1251 at overall level 2. 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.
Certificate
| Certificate number | 1251 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Fortress™ Technologies, Inc. · website |
| Hardware versions | FC-250, FC-250SB, FC500, FC500SB, FC-1500 and FC1500SB |
| Firmware versions | 5.1.2, 5.1.2.5100CAJ and 5.1.2.5100CAP |
Module description
Quoted from the NIST CMVP entry for this certificate.
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 (6)
| Algorithm | CAVP certificates |
|---|---|
| AES | 852, 853, 389 |
| HMAC | 469, 569, 371 |
| RNG | 487, 488, 189 |
| RSA | 488 |
| SHS | 845, 846, 721, 722, 715 |
| Triple-DES | 703 |
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
| Date | Type | Lab |
|---|---|---|
| 2010-01-06 | Initial | COACT INC CAFE LAB |
| 2010-01-28 | Update | |
| 2010-03-26 | Update | |
| 2010-08-02 | Update | |
| 2013-05-17 | Update | Leidos 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