808bits

Nutanix Cryptographic Module for OpenSSH Server

FIPS 140-2 certificate #3473 · Nutanix, 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 with Nutanix Cryptographic Module for OpenSSL validated to FIPS 140-2 under Cert. #3460 operating in FIPS mode

Certificate

Certificate number3473
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorNutanix, Inc. · website
Software versionsOpenSSH server RPM package 7.4p1-16.el7 and fipscheck RPM package 1.4.1-6.el7

Module description

The Nutanix Cryptographic Module for OpenSSH Server provides server-side support for SSH version 2. This cryptographic module functions together with the Nutanix Cryptographic Module for OpenSSL to provide FIPS validated cryptography for SSH connections.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
AES5562, C661
CVL1994, 1998
DRBG2216
ECDSA1499
HMAC3708
SHS4465

Allowed algorithms

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

Tested configurations

  • CentOS 7.5 running on Nutanix NX-3360-G6 with Intel Xeon Silver-4116 with PAA
  • CentOS 7.5 running on Nutanix NX-3360-G6 with Intel Xeon Silver-4116 without PAA (single-user mode)

Validation history

DateTypeLab
2019-06-12InitialUL Verification Services, Inc.
2020-07-13UpdateUL Verification Services, Inc.
2020-07-29UpdateUL Verification Services, 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: 2019-06-12, 2020-07-13, 2020-07-29

Source documents