808bits

Fortress Mesh Point

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

Fortress Mesh Point, from Fortress™ Technologies, Inc., holds FIPS 140-2 certificate #1301 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.

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 number1301
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorFortress™ Technologies, Inc. · website
Hardware versionsES520: Deployable Mesh Point (V1 and V2) [1,2,3,4,5,6,7], ES300: Inline Network Encryptor [1,2], ES210: Tactical Mesh Point [3,4,5,6,7], ES440: Infrastructure Mesh Point [4] and ES820: Vehicle Mesh Point [4]
Firmware versions5.1 [1], 5.1.1 [2], 5.2.1 [3], 5.3.0 [4], 5.2.1.1162 [5], 5.2.2 [6] or 5.2.2.1011[7]

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 (5)

AlgorithmCAVP certificates
AES688, 694, 698
HMAC367, 371, 372, 376
RNG402, 406, 409
RSA439
SHS715, 717, 721, 722, 726

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-04-26InitialCOACT INC CAFE LAB
2010-05-07Update
2010-05-28Update
2010-08-02Update
2010-12-21UpdateCOACT INC CAFE LAB
2011-02-24UpdateCOACT INC CAFE LAB
2011-10-04UpdateCOACT INC CAFE LAB
2012-05-10UpdateCOACT INC CAFE LAB
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-04-26, 2010-05-07, 2010-05-28, 2010-08-02, 2010-12-21, 2011-02-24, 2011-10-04, 2012-05-10, 2013-05-17

Source documents