Fortress Mesh Points
Fortress Mesh Points, from Fortress™ Technologies, Inc., holds FIPS 140-2 certificate #1606 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 | 1606 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 2 |
| Module type | Hardware |
| Embodiment | Multi-chip standalone |
| Vendor | Fortress™ Technologies, Inc. · website |
| Hardware versions | ES210, ES300, ES440, ES520v1, ES520v2 and ES820 |
| Firmware versions | 5.3.1 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Fortress Mesh Point is an all-in-one network access device housed in a rugged compact chassis, with the most stringent security available today built in. It can serve as a wireless bridge, a WLAN access point, and an eight-port LAN switch, while performing all the functions of a Fortress controller device: encrypting wireless traffic and providing Multi-factor Authentication for devices on the network it protects.
Security level exceptions
- Roles, Services, and Authentication: Level 3
- Design Assurance: Level 3
Approved algorithms (7)
| Algorithm | CAVP certificates |
|---|---|
| AES | 688, 694, 1519 |
| DRBG | 66 |
| HMAC | 367, 371, 889 |
| KAS | 10 |
| RNG | 402, 406 |
| RSA | 439 |
| SHS | 717, 721, 1357 |
Other algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 bits security strength; non-compliant less than 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides 192 bits security strength); MD5
Validation history
| Date | Type | Lab |
|---|---|---|
| 2011-09-26 | Initial | SAIC-VA |
| 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: 2011-09-26, 2013-05-17