808bits

Riverbed XD Series Wi-Fi Products

FIPS 140-2 certificate #3507 · Riverbed Technology, Inc. · data as of 2026-10-21

Riverbed XD Series Wi-Fi Products, from Riverbed Technology, Inc., holds FIPS 140-2 certificate #3507 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. SP 800-56Arev3 transition. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode and with the tamper evident seals installed as indicated in Sections 9 and 10 of the Security Policy

Certificate

Certificate number3507
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorRiverbed Technology, Inc. · website
Hardware versionsP/Ns XD2-240-FIPS, XD4-240-FIPS, XA4-240-FIPS, XD2-230-FIPS and XH2-240-FIPS with XE-6000-TBAR (Enclosure Form Factor) and with SKU XE-LABEL-FIPS (Tamper-Evident Seals)
Firmware versionsAOS-8.6

Module description

Quoted from the NIST CMVP entry for this certificate.

Wireless LAN Access Points

Security level exceptions

  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (8)

AlgorithmCAVP certificates
AES5946, 5947
CVL2176, 2177
DRBG2496
HMAC3919
KBKDF248
KTS
RSA3122
SHS4698

Allowed algorithms

Diffie-Hellman (CVL Certs. #2176 and #2177, key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #2176, key agreement; key establishment methodology provides 128 bits of encryption strength); MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2019-08-08InitialUL 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: 2019-08-08

Source documents