Aruba VIA Cryptographic Module
Aruba VIA Cryptographic Module, from Aruba, a Hewlett Packard Enterprise Company, holds FIPS 140-2 certificate #4351 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.
Caveat: When installed, initialized and configured as specified in Section 10 of the Security Policy. No assurance of the minimum strength of generated keys
Certificate
| Certificate number | 4351 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Aruba, a Hewlett Packard Enterprise Company · website |
| Software versions | 1.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Aruba VIA Cryptographic Module Version 1.0 is a software library that provides cryptographic services required by Aruba Virtual Intranet Access
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms (10)
| Algorithm | CAVP certificates |
|---|---|
| AES | A2147 |
| CKG | vendor affirmed |
| CVL | A2147 |
| DRBG | A2147 |
| ECDSA | A2147 |
| HMAC | A2147 |
| KAS-SSC | A2147 |
| RSA | A2147 |
| SHS | A2147 |
| Triple-DES | A2147 |
Allowed algorithms
RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength)
Tested configurations
- Android 11 running on a Samsung Galaxy S20 with a Samsung Exynos 990 Mongoose M5
- iOS 14 running on an iPhone 11 with an Apple A13 Bionic (single-user mode)
- Windows 10 64-bit running on a HP ZBook G7 with an Intel Core i5-11500H
Validation history
| Date | Type | Lab |
|---|---|---|
| 2022-11-01 | 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 at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2022-11-01