808bits

Xirrus Wireless LAN Array

FIPS 140-2 certificate #895 · Xirrus, Inc. · data as of 2026-10-21

Xirrus Wireless LAN Array, from Xirrus, Inc., holds FIPS 140-2 certificate #895 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 number895
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorXirrus, Inc. · website
Hardware versionsModels: XS-3900 P/Ns 190-0001-001, 190-0001-002, 190-0001-003, 190-0001-004 Version B1; XS-3700 P/Ns 190-0005-001, 190-0005-002, 190-0005-003, 190-0005-004 Version B1; XS-3500 P/Ns 190-0004-001, 190-0004-003 Version A1; WFX-3900 P/N 190-0016-001 Version A1; WFX-3700 P/N 190-0017-001 Version A1; WFX 3500 P/N 190-0018-001 Version A; XS4 P/N 190-0092-001 Version A; XS8 P/N 190-0091-001 Version A; XS16 P/N 190-0090-001 Version A
Firmware versions3.2-0477

Module description

Quoted from the NIST CMVP entry for this certificate.

The Xirrus Wireless LAN Array represents the next generation in enterprise wireless LAN architecture - combining the functionality of a WLAN switch and Integrated Access Points (IAPs) in a single device. The WLAN Array delivers Gigabit-class Wi-Fi bandwidth to an extended coverage area simplifying the wireless LAN setup.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • EMI/EMC: Level 3

Approved algorithms (5)

AlgorithmCAVP certificates
AES470
HMAC304
RNG255
RSA290
SHS638

Other algorithms

RC4; MD5

Validation history

DateTypeLab
2008-01-10InitialUL 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: 2008-01-10

Source documents