iLO 5 Cryptographic Module
iLO 5 Cryptographic Module, from Hewlett Packard Enterprise Development LP, holds FIPS 140-2 certificate #4831 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 the Security Policy Section 3
Certificate
| Certificate number | 4831 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Hardware |
| Embodiment | Multi-Chip Embedded |
| Vendor | Hewlett Packard Enterprise Development LP · website |
| Hardware versions | ASIC (GXP: 815393-001) with Flash Memory (1819-1208), NVRAM (1819-1209), and DDR3 SDRAM (2660-0461) |
| Firmware versions | 2.45 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The HP Integrated Lights-Out 5 (HP iLO 5) built into HP ProLiant Gen10 and Synergy servers is an autonomous secure management component embedded directly on the server motherboard. iLO helps simplify initial server setup, power and thermal optimization, remote server administration, and provides server health monitoring with the HP Active Health System (AHS).
Security level exceptions
- Mitigation of Other Attacks: N/A
Approved algorithms (14)
| Algorithm | CAVP certificates |
|---|---|
| AES | 4467, A2273 |
| CKG | vendor affirmed |
| CVL | A2273 |
| DRBG | A2273 |
| DSA | A2273 |
| ECDSA | A2273 |
| ENT | |
| HMAC | A2273 |
| KAS | |
| KAS-SSC | A2273 |
| KBKDF | A2273 |
| KTS | |
| RSA | A2273 |
| SHS | 3679, A2273 |
Allowed algorithms
RSA (key wrapping; key establishment methodology provides between 112 and 256 bits of encryption strength)
Tested configurations
- N/A
Validation history
| Date | Type | Lab |
|---|---|---|
| 2024-10-11 | Initial | Acumen Security |
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: 2024-10-11