808bits

Nimble Storage FIPS Object Module

FIPS 140-2 certificate #2422 · Nimble Storage, a Hewlett Packard Enterprise company · data as of 2026-10-09

Nimble Storage FIPS Object Module, from Nimble Storage, a Hewlett Packard Enterprise company, holds FIPS 140-2 certificate #2422 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 dependency on certificate #1747. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When built, installed, protected and initialized as assumed by the Crypto Officer role and as specified in the provided Security Policy. Appendix A of the provided Security Policy specifies the actual distribution tar file containing the source code of this module. There shall be no additions, deletions or alterations to the tar file contents as used during module build. The distribution tar file shall be verified as specified in Appendix A of the provided Security Policy. Installation and protection shall be completed as specified in Appendix A of the provided Security Policy. Initialization shall be invoked as per Section 4 of the provided Security Policy. Any deviation from specified verification, protection, installation and initialization procedures will result in a non FIPS 140-2 compliant module. This validation entry is a non-security relevant modification to Cert. #1747

Certificate

Certificate number2422
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-chip standalone
VendorNimble Storage, a Hewlett Packard Enterprise company · website
Software versions2.0.9

Module description

Quoted from the NIST CMVP entry for this certificate.

The Nimble Storage FIPS Object Module 2.0.9 is a general purpose cryptographic module built from the OpenSSL FIPS Object Module 2.0.9 source code, which is validated under certificate #1747. It is designed for ease of use with the popular OpenSSL cryptographic library and toolkit.

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
AES2484, 3351
CVL85, 496
DRBG342, 784
DSA764, 950
ECDSA413, 664
HMAC1526, 2134
RSA1273, 1718
SHS2102, 2778
Triple-DES1522, 1912

Other algorithms

EC Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 256 bits of encryption strength); RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength)

Tested configurations

  • Linux 2.6 running on a Nimble Storage AF3000 with PAA
  • Linux 2.6 running on a Nimble Storage AF5000 with PAA
  • Linux 2.6 running on a Nimble Storage AF7000 with PAA
  • Linux 2.6 running on a Nimble Storage AF9000 with PAA (single-user mode)
  • Linux 2.6 running on a Nimble Storage CS300 with PAA
  • Linux 2.6 running on a Nimble Storage CS500 with PAA
  • Linux 2.6 running on a Nimble Storage CS700 with PAA
  • Linux 3.4 64-bit under Citrix XenServer running on Intel Xeon E5-2430L (x86) without PAA
  • Linux 4.4 running on a Nimble Storage AF40 with PAA
  • Linux 4.4 running on a Nimble Storage AF7000 with PAA
  • Linux 4.4 running on a Nimble Storage CS240 without PAA
  • Linux 4.4 running on a Nimble Storage CS300 with PAA

Validation history

DateTypeLab
2015-08-11InitialLeidos Accredited Testing & Evaluation (AT&E) Lab
2016-03-01UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab
2016-06-07UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab
2016-07-25UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab
2018-03-26UpdateLeidos Accredited Testing & Evaluation (AT&E) Lab
2021-01-26UpdateLeidos 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: 2015-08-11, 2016-03-01, 2016-06-07, 2016-07-25, 2018-03-26, 2021-01-26

Source documents