808bits

Aruba RAP-5WN and Dell W-RAP-5WN Remote Access Points

FIPS 140-2 certificate #1815 · Aruba Networks, Inc. · data as of 2026-08-28
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 with tamper evident labels installed as indicated in the Security Policy

Certificate

Certificate number1815
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorAruba Networks, Inc. · website
Hardware versionsRAP-5WN-F1 [1] and W-RAP-5WN-F1 [2]
Firmware versionsArubaOS_6.1.2.3-FIPS [1] and Dell_PCW_6.1.2.3-FIPS [2] or ArubaOS_6.1.4.5-FIPS [1] and Dell_PCW_6.1.4.5-FIPS [2] or ArubaOS_6.1.4.7-FIPS [1] and Dell_PCW_6.1.4.7-FIPS [2]

Module description

Aruba's RAP-5WN access point aggregates wired and wireless user traffic and forwards it to an Aruba Mobility Controller through a secure IPsec tunnel, using the public Internet or an optional 3G/4G WWAN service for backhaul. In the FIPS 140-2 mode of operation, Aruba APs in conjunction with the Mobility Controller support the IEEE 802.11i/WPA2 standard along with optional Suite B cryptography for high-assurance applications. Aruba APs also provide wireless intrusion detection/prevention services, support wireless mesh topologies, and have Wi-Fi Alliance certification for IEEE 802.11a/b/g/n.

Approved algorithms

AlgorithmCAVP certificate
AES861, 1850, 1851
HMAC478, 1098, 1099
RNG969, 970
RSA933, 934, 935
SHS856, 1627, 1628, 1629
Triple-DES708, 1198, 1199

Other algorithms

MD5; Diffie-Hellman (key agreement; key establishment methodology provides 80 bits of encryption strength; non-compliant)

Validation history

DateTypeLab
2012-10-11InitialSAIC-VA
2013-07-26UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab
2014-01-23UpdateLeidos 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: 2012-10-11, 2013-07-26, 2014-01-23

Source documents