Aruba Virtual and Hardware Mobility Master Appliances with ArubaOS FIPS Firmware
Aruba Virtual and Hardware Mobility Master Appliances with ArubaOS FIPS Firmware, from Aruba, a Hewlett Packard Enterprise company, holds FIPS 140-2 certificate #3734 at overall level 1. 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.
Certificate
| Certificate number | 3734 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Firmware |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Aruba, a Hewlett Packard Enterprise company · website |
| Firmware versions | ArubaOS 8.2.2.5-FIPS, ArubaOS 8.5.0.3-FIPS and ArubaOS 8.6.0.4-FIPS |
Module description
Quoted from the NIST CMVP entry for this certificate.
Aruba's family of Mobility Masters simplify the management of multiple Aruba controllers running ArubaOS. Key features include a centralized dashboard to easily see and manage controllers, configuration hierarchy to customize deployments for various sites, and live firmware and feature upgrades to improve network reliability during active user sessions. The addition of licensing pools simplifies the transfer of licenses between different controllers to quickly address expanded deployment needs.
Security level exceptions
- Roles, Services, and Authentication: Level 2
- Mitigation of Other Attacks: N/A
Approved algorithms (8)
| Algorithm | CAVP certificates |
|---|---|
| AES | C413, C414 |
| CVL | C413, C414, C1972, C1974 |
| DRBG | C413 |
| ECDSA | C413, C414 |
| HMAC | C413, C414, C1972, C1974 |
| KTS | |
| RSA | C413, C414, C818 |
| SHS | C413, C414, C818, C1972, C1974 |
Allowed algorithms
Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (key agreement; key establishment methodology provides 128 or 192 bits of encryption strength); MD5; NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)
Tested configurations
- Aruba Mobility Master 10K - F1 Hardware Appliance (JZ398A) with ArubaOS 8.2.2.5-FIPS with an Intel Xeon Silver with PAA
- Aruba Mobility Master 10K - F1 Hardware Appliance (JZ398A) with ArubaOS 8.5.0.3-FIPS with an Intel Xeon Silver with PAA
- Aruba Mobility Master 10K - F1 Hardware Appliance (JZ398A) with ArubaOS 8.6.0.4-FIPS with an Intel Xeon Silver with PAA
- Aruba Mobility Master 1K - F1 Hardware Appliance (JZ396A) with ArubaOS 8.2.2.5-FIPS with an Intel Xeon Silver with PAA
- Aruba Mobility Master 1K - F1 Hardware Appliance (JZ396A) with ArubaOS 8.5.0.3-FIPS with an Intel Xeon Silver with PAA
- Aruba Mobility Master 1K - F1 Hardware Appliance (JZ396A) with ArubaOS 8.6.0.4-FIPS with an Intel Xeon Silver with PAA
- Aruba Mobility Master 5K - F1 Hardware Appliance (JZ397A) with ArubaOS 8.2.2.5-FIPS with an Intel Xeon Silver with PAA
- Aruba Mobility Master 5K - F1 Hardware Appliance (JZ397A) with ArubaOS 8.5.0.3-FIPS with an Intel Xeon Silver with PAA
- Aruba Mobility Master 5K - F1 Hardware Appliance (JZ397A) with ArubaOS 8.6.0.4-FIPS with an Intel Xeon Silver with PAA
- ArubaOS 8.2.2.5-FIPS on ESXi 6.5 running on an HPE ProLiant ML110 Gen10 with an Intel Xeon Silver with PAA
- ArubaOS 8.2.2.5-FIPS on ESXi 6.5 running on an HPE ProLiant ML110 Gen10 with an Intel Xeon Silver without PAA
- ArubaOS 8.5.0.3-FIPS on ESXi 6.5 running on an HPE ProLiant ML110 Gen10 with an Intel Xeon Silver with PAA
- ArubaOS 8.5.0.3-FIPS on ESXi 6.5 running on an HPE ProLiant ML110 Gen10 with an Intel Xeon Silver without PAA
- ArubaOS 8.6.0.4-FIPS on ESXi 6.5 running on an HPE ProLiant ML110 Gen10 with an Intel Xeon Silver with PAA
- ArubaOS 8.6.0.4-FIPS on ESXi 6.5 running on an HPE ProLiant ML110 Gen10 with an Intel Xeon Silver without PAA
Validation history
| Date | Type | Lab |
|---|---|---|
| 2020-10-27 | Initial | Leidos 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: 2020-10-27