808bits

LoadMaster FIPS Object Module

FIPS 140-2 certificate #3736 · Kemp Technologies Inc. · data as of 2026-08-28
Historical. SP 800-56Arev3 transition. 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 number3736
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorKemp Technologies Inc. · website
Software versionsv1.0

Module description

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

AlgorithmCAVP certificate
AESC2076
CKGvendor affirmed
CVLC2076
DRBGC2076
DSAC2076
ECDSAC2076
HMACC2076
RSAC2076
SHSC2076
Triple-DESC2076

Allowed algorithms

Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #C2076, key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); NDRNG; RSA (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength)

Tested configurations

  • LMOS 7.2 on Vmware ESXi 6.7 running on a Dell PowerEdge R830 with an Intel Xeon E5 4620 v4 processor with PAA
  • LMOS 7.2 on Vmware ESXi 6.7 running on a Dell PowerEdge R830 with an Intel Xeon E5 4620 v4 processor without PAA (single-user mode)
  • LMOS 7.2 running on LoadMasterX15 with an Intel Xeon E3 1275 V6 processor with PAA
  • LMOS 7.2 running on LoadMasterX15 with an Intel Xeon E3 1275 V6 processor without PAA

Validation history

DateTypeLab
2020-10-27InitialAcumen 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: 2020-10-27

Source documents