808bits

Aruba AP-120 Series Wireless Access Points

FIPS 140-2 certificate #1109 · Aruba Networks, Inc. · data as of 2026-09-13

Aruba AP-120 Series Wireless Access Points, from Aruba Networks, Inc., holds FIPS 140-2 certificate #1109 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 and with the tamper evidence seals installed as indicated in the Security Policy

Certificate

Certificate number1109
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-chip standalone
VendorAruba Networks, Inc. · website
Hardware versionsAP-124-F1 Rev. 01and AP-125-F1 Rev. 01
Firmware versionsArubaOS 3.3.2.18-FIPS, ArubaOS 3.3.2.19-FIPS, ArubaOS 3.3.2.20-FIPS, ArubaOS 3.3.2.21-FIPS, ArubaOS 3.4.2.3-FIPS, ArubaOS 3.4.4.0-FIPS or ArubaOS 3.4.5.1-FIPS

Module description

Quoted from the NIST CMVP entry for this certificate.

Aruba's single and multi-radio wireless access points serve as secure network on-ramps, aggregating wireless user traffic and forwarding it to Aruba's highly secure Multi-Service Mobility Controllers, where per-user role based access controls are applied. In the FIPS 140-2 mode of operation, Aruba APs in conjunction with the Mobility Controller support the IEEE 802.11i client standard, the xSec client and 256-bit AES encryption. Also, Aruba APs can provide Air Monitoring for intrusion detection and have Wi-Fi Alliance certification for IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and IEEE 802.11

Approved algorithms (6)

AlgorithmCAVP certificates
AES861, 900
HMAC478, 503
RNG516
RSA435, 436
SHS891, 856, 892
Triple-DES708, 734

Other algorithms

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

Validation history

DateTypeLab
2009-03-26InitialSAIC-VA
2009-05-18Update
2009-07-24Update
2009-12-10UpdateSAIC-VA
2010-02-12Update
2010-05-05Update
2010-10-25UpdateSAIC-VA
2011-01-31UpdateSAIC-VA
2011-03-14Update
2011-07-19UpdateSAIC-VA
2013-02-06UpdateLeidos 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: 2009-03-26, 2009-05-18, 2009-07-24, 2009-12-10, 2010-02-12, 2010-05-05, 2010-10-25, 2011-01-31, 2011-03-14, 2011-07-19, 2013-02-06

Source documents