808bits

Enterprise Secure Key Manager

FIPS 140-2 certificate #2862 · Utimaco Inc. · 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 operated in FIPS mode

Certificate

Certificate number2862
StandardFIPS 140-2
Statushistorical
Overall level2
Module typeHardware
EmbodimentMulti-Chip Stand Alone
VendorUtimaco Inc. · website
Software versionsN/A
Hardware versionsP/N M6H81AA , Version 5.0
Firmware versions7.0.1

Module description

Utimaco Enterprise Secure Key Manager (ESKM) provides key generation, retrieval, and management for encryption devices and solutions. ESKM is a hardened security appliance with secure access control, administration, and logging. ESKM supports high availability with automatic multi-site clustering, replication, and failover.

Security level exceptions

  • Roles, Services, and Authentication: Level 3
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES3995
CVL820, 821, 822, 823, 842
DRBG1185, 1186
ECDSA889
HMAC2609
KTS
KTS
KTS
RSA2051
SHS3297
Triple-DES2194

Other algorithms

Diffie-Hellman (key agreement; key establishment methodology provides 112 bits of encryption strength); EC Diffie-Hellman (CVL Cert. #842; key agreement; key establishment methodology provides 128 or 192 bits of encryption strength); NDRNG; RSA (key wrapping; key establishment methodology provides 112 bits of encryption strength; non-compliant less than 112 bits of encryption strength); DES; MD5; RC4; RSA (encrypt/decrypt)

Tested configurations

  • N/A

Validation history

DateTypeLab
2017-03-10InitialLeidos Accredited Testing & Evaluation (AT&E) Lab
2017-12-14UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab
2018-12-04UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab

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: 2017-03-10, 2017-12-14, 2018-12-04

Source documents