808bits

Kemp LoadMaster FIPS Object Module

FIPS 140-2 certificate #4639 · Progress Software Corporation · data as of 2026-10-21

Kemp LoadMaster FIPS Object Module, from Progress Software Corporation, holds FIPS 140-2 certificate #4639 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.

Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number4639
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorProgress Software Corporation · website
Software versionsv1.0

Module description

Quoted from the NIST CMVP entry for this certificate.

The LoadMaster is a family of load balancing appliances running a custom operating system developed by Kemp Technologies Inc.

Security level exceptions

  • Roles, Services, and Authentication: Level 2
  • Physical Security: N/A
  • Design Assurance: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms (9)

AlgorithmCAVP certificates
AESC2076
CVLC2076
DRBGC2076
DSAC2076
ECDSAC2076
HMACC2076
RSAC2076
SHSC2076
Triple-DESC2076

Allowed algorithms

NDRNG

Tested configurations

  • LMOS 7.2 on VMware ESXi 6.7 running Dell PowerEdge R830 with an Intel Xeon E5 4620 v4 Without PAA
  • LMOS 7.2 running on VMware ESXi 6.7 Dell PowerEdge R830 with an Intel Xeon E5 4620 v4 With PAA
  • LMOS 7.2 running LoadMasterX15 with an Intel Xeon E3 1275 v6 With PAA
  • LMOS 7.2 running LoadMasterX15 with an Intel Xeon E3 1275 v6 Without PAA

Validation history

DateTypeLab
2023-10-23InitialAcumen 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
  • Validation dates on record: 2023-10-23

Source documents