808bits

iLO 5 Cryptographic Module

FIPS 140-2 certificate #3122 · Hewlett Packard Enterprise Development LP · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When installed, initialized and configured as specified in the Security Policy Section 3

Certificate

Certificate number3122
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeHardware
EmbodimentMulti-Chip Embedded
VendorHewlett Packard Enterprise Development LP · website
Hardware versionsASIC (GXP: 815393-001) with Flash Memory (1819-1208), NVRAM (1819-1209), and DDR3 SDRAM (2660-0461)
Firmware versions1.11

Module description

The HP Integrated Lights-Out 5 (HP iLO 5) built into HP ProLiant Gen10 and Synergy(480 and 660) 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

AlgorithmCAVP certificate
AES4467, 4525
CKGvendor affirmed
CVL1201, 1202
DRBG1485
DSA1204
ECDSA1100
HMAC2985
KBKDF132
KTS
RSA2462
SHS3679, 3706
Triple-DES2412

Allowed algorithms

Diffie-Hellman (CVL Cert. #1202, key agreement; key establishment methodology provides 112 or 128 bits of encryption strength); EC Diffie-Hellman (CVL Certs. #1201 and #1202, key agreement; key establishment methodology provides 128 or 192 bits of encryption strength); MD5; NDRNG; RSA (CVL Cert. #1202, key wrapping; key establishment methodology provides between 112 and 128 bits of encryption strength)

Tested configurations

  • N/A

Validation history

DateTypeLab
2018-02-08InitialCGI Information Systems & Management Consultants 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: 2018-02-08

Source documents