Nutanix Cryptographic Module for OpenSSH Client
Nutanix Cryptographic Module for OpenSSH Client, from Nutanix, Inc., holds FIPS 140-2 certificate #4364 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.
Caveat: When operated in FIPS mode and configured as specified in Section 3 of the Security Policy with the Nutanix Cryptographic Module for OpenSSL validated to FIPS 140-2 under Cert. #4249 operating in FIPS mode. No assurance of the minimum strength of generated keys
Certificate
| Certificate number | 4364 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Nutanix, Inc. · website |
| Software versions | 6.0 |
Module description
Quoted from the NIST CMVP entry for this certificate.
The Nutanix Cryptographic Module for OpenSSH Client is a cryptographic software module, designated as a multi-chip standalone embodiment, and used in Nutanix solutions to provide FIPS 140-2 Approved SSH client-side secure communication.
Security level exceptions
- Physical Security: N/A
- Mitigation of Other Attacks: N/A
Approved algorithms (9)
Tested configurations
- CentOS 7.9 on Nutanix Acropolis Hypervisor (AHV) 7.1.1 running on a Nutanix NX-3360-G7 with an Intel® Xeon® Gold 6234 with PAA
- CentOS 7.9 on Nutanix Acropolis Hypervisor (AHV) 7.1.1 running on a Nutanix NX-3360-G7 with an Intel® Xeon® Gold 6234 without PAA
- CentOS 7.9 running on a Nutanix NX-3360-G7 with an Intel® Xeon® Gold 6234 with PAA
- CentOS 7.9 running on a Nutanix NX-3360-G7 with an Intel® Xeon® Gold 6234 without PAA (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2022-11-14 | Initial | Lightship Security, 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 at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2022-11-14