Aruba Common Cryptographic Module
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy. No assurance of the minimum strength of generated keys
Certificate
| Certificate number | 2573 |
|---|---|
| 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
The Aruba Common Cryptographic Module Version 1.0 is a software shared library that provides cryptographic services required by Aruba software applications.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms
| Algorithm | CAVP certificate |
|---|---|
| AES | 2744, 2746 |
| CVL | 265, 266 |
| DRBG | 496, 498 |
| ECDSA | 499, 500 |
| HMAC | 1721, 1722 |
| RSA | 1483, 1484 |
| SHS | 2316, 2317 |
| Triple-DES | 1652, 1653 |
Other 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); RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength); DES; Blowfish; ARC2; ARC4; MD2; MD4; MD5; HMAC-MD5; AES EAX; AES XCBC; AES MAC (non-compliant); RSAES-OAEP
Tested configurations
- Android 4.0 running on a Droid 3 Smartphone
- iOS9 running on an iPad 2 (single-user mode)
- Red Hat Enterprise Linux 6 with Linux 2.6 Kernel (32-bit) running on a Dell Dimension 9200
- Windows 7 Enterprise 32-bit User Mode running on an IBM ThinkPad Lenovo
- Windows 7 Enterprise 64-bit User Mode running on an IBM ThinkPad Lenovo
Validation history
| Date | Type | Lab |
|---|---|---|
| 2016-03-01 | Initial | UL Verification Services, Inc. |
| 2017-02-28 | Update | UL 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: 2016-03-01, 2017-02-28