808bits

Meru Networks Security Gateway SG1000 Cryptographic Module

FIPS 140-2 certificate #1164 · Meru Networks · data as of 2026-10-09

Meru Networks Security Gateway SG1000 Cryptographic Module, from Meru Networks, holds FIPS 140-2 certificate #1164 at overall level 3. 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: None

Certificate

Certificate number1164
StandardFIPS 140-2
Statushistorical
Overall level3
Module typeHardware
EmbodimentMulti-chip embedded
VendorMeru Networks · website
Hardware versionsP/N MN-SG1000
Firmware versions1.0-27

Module description

Quoted from the NIST CMVP entry for this certificate.

The Meru Networks Security Gateway SG1000 Cryptographic Module is a high performance purpose built security solution for Wireless LAN deployments. The Meru Networks Security Gateway SG1000 Cryptographic Module provides a FIPS 140-2 Level 3 security solution conforming to the IEEE 802.11i security standards. The Meru Networks Security Gateway SG1000 Cryptographic Module is installed in a slot in the Meru Networks Security Gateway SG1000 appliance.

Approved algorithms (7)

AlgorithmCAVP certificates
AES903, 904
HMAC493
KASvendor affirmed
RNG518
RSA440
SHS894
Triple-DES720

Other algorithms

MD5; AES (Cert. #903, key wrapping; key establishment methodology provides 128 bits of encryption strength); RSA (key wrapping; key establishment methodology provides 80 bits of encryption strength; non-compliant);

Validation history

DateTypeLab
2009-08-18InitialUL Verification Services, Inc.

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: 2009-08-18

Source documents