Nimble Storage FIPS Object Module

Extracted keywords

• 06.10.2026

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'AES 128/192/256 1202': 1, 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8': 1, 'platform #96, FreeBSD 8.4 on x86 without AESNI': 1, 'platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG': 1, 'platforms #90, #91': 1, 'platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86': 1, 'platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5': 1, 'platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition': 1, 'platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI': 1, 'platforms #77, #78 iOS 6.0 with/without NEON': 1}, '__delete__': ['platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8 | | 20140104 | Addition of new platform #96, FreeBSD 8.4 on x86 without AESNI | | 20140730 | Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG | | 20140728 | Changed processor names for platforms #90, #91 | | 20140711 | Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86 | | 20140612 | Temporarily remove misplaced platform, move Dual EC DRBG to the Non Approved Table 4c | | 20140529 | Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) | | 20140512 | Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition | | 20131108 | Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI | | 20131101 | Added two platforms #77, #78 iOS 6.0 with/without NEON | Page 4 of 29 ####### Nimble Storage FIPS 1402 Security Policy | 20130829 | Added new sponsor acknowledgment | |--------------|-----------------------------------------------------------------------------------------------------| | 20130814 | Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms | | 20130724 | Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 | | 20130609 | Added QNX, iOS 6.1, eCos for revision 2.0.5 | | 20130501 | Added OpenWRT 2.6 for revision 2.0.4 | | 20130301 | Added VMware Horizon Mobile 1.3, Apple OS X 10.7 , Apple iOS 5.0 | | 20130223 | Added WinEC7 and Android 4.0 for revision 2.0.3 | | 20130214 | Table 5: Removed references to nonexistent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM | | 20130128 | Added four platforms: Android 4.1 and Android 4.2 with and without NEON | | 20130108 | Reworded section 8 | | 20130103 | Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AESNI. | | 20121208 | Note EC DH Key Agreement and RSA Key Wrapping strength. | | 20121010 | Added NetBSD 5.1 on PowerPCe500, NetBSD 5.1 on Intel Xeon 5500 (x8664) for revision 2.0.2 | | 20110702 | Added DSP Media Framework, Linux 2.6/Freescale PowerPCe500, Android 4.0 | | 20110615 | Added iOS, WinCE 5, WinCE 6 OEs | ####### References | Reference | Full Specification Name | |--------------|---------------------------------------------------------------------------------------------------------| | [ANS X9.31] | Digital Signatures Using Reversible Public Key Cryptography for the Financial Services Industry (rDSA) | | [FIPS 1402] | Security Requirements for Cryptographic modules, May 25, 2001 | | [FIPS 1803] | Secure Hash Standard | | [FIPS 1864] | Digital Signature Standard | | [FIPS 197] | Advanced Encryption Standard | | [FIPS 1981] | The KeyedHash Message Authentication Code (HMAC) | | [SP 80038B] | Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication | | [SP 80038C] | Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality | Page 5 of 29 ####### Nimble Storage FIPS 1402 Security Policy | Reference | Full Specification Name | |----------------|---------------------------------------------------------------------------------------------------| | [SP 80038D] | Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC | | [SP 80056A] | Recommendation for PairWise Key Establishment Schemes Using Discrete Logarithm Cryptography | | [SP 800 67R1] | Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher | | [SP 80089] | Recommendation for Obtaining Assurances for Digital Signature Applications | | [SP 80090] | Recommendation for Random Number Generation Using Deterministic Random Bit Generators | | [SP 800 131A] | Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths | Page 6 of 29 Nimble Storage FIPS 1402 Security Policy ### Table of Contents | 1 Introduction.........................................................................................................................7 | |----------------------------------------------------------------------------------------------------------------------------------------------| | 2 Tested Configurations.........................................................................................................9 | | 3 Ports and Interfaces ............................................................................................................13 | | 4 Modes of Operation and Cryptographic Functionality ......................................................14 | | 4.1 Critical Security Parameters and Public Keys............................................................18 | | 5 Roles, Authentication and Services ...................................................................................21 | | 6 Selftest...............................................................................................................................23 | | 7 Operational Environment....................................................................................................25 | | 8 Mitigation of other Attacks.................................................................................................26 | | Appendix A Installation and Usage Guidance.......................................................................27 | | Appendix B Controlled Distribution File Fingerprint...........................................................30 | | Appendix C Compilers..........................................................................................................33 | Page 7 of 29 Nimble Storage FIPS 1402 Security Policy ## 1 Introduction This document is the nonproprietary security policy for the Nimble Storage FIPS Object Module, hereafter referred to as the Module, which is build from the OpenSSL FIPS Object Module source code according to the the instructions in Appendix A. The Module is a software library providing a Clanguage application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 1402 as a software module, multichip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the fipscanister object module, a single object module file named fipscanister.o compiled on Linux ®1 . The Module performs no communications other than with the calling application (the process that invokes the Module services). The FIPS 1402 security levels for the Module are as follows: | Security Requirement | Security Level | |-------------------------------------------|------------------| | Cryptographic Module Specification | 1 | | Cryptographic Module Ports and Interfaces | 1 | | Roles, Services, and Authentication | 2 | | Finite State Model | 1 | | Physical Security | NA | | Operational Environment | 1 | | Cryptographic Key Management | 1 | | EMI/EMC | 1 | | SelfTests | 1 | | Design Assurance | 3 | | Mitigation of Other Attacks | NA | Table 1 - Security Level of Security Requirements The Module\'s software version for this validation is 2.0.9. It is build from the 2.0.9 version of the OpenSSL FIPS Object Module source code. 1 Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Page 8 of 29 ####### Nimble Storage FIPS 1402 Security Policy Figure 1 Module Block Diagram Page 9 of 29 Nimble Storage FIPS 1402 Security Policy ## 2 Tested Configurations Table 2 Tested Configurations (B = Build Method; EC = Elliptic Curve Support). The EC column indicates support for prime curve only (P), or all NIST defined B, K, and P curves (BKP). | # | Operational Environment | Processor | Optimiz ations (Target) | EC | B | |-----|-----------------------------------------|---------------------------------|----------------------------|------|-----| | 1 | Linux 2.6 | Intel E52403V2 (x86_64) | AESNI | BKP | U2 | | 2 | Linux 2.6 | Intel E52450V2 (x86_64) | AESNI | BKP | U2 | | 3 | Linux 2.6 | Intel E52470V2 (x86_64) | AESNI | BKP | U2 | | 4 | Linux 3.4 64bit under Citrix XenServer | Intel Xeon E52430L (x86) | None | BKP | U2 | | 5 | Linux 2.6 | Intel E52603V3 (x86_64) | AESNI | BKP | U2 | | 6 | Linux 2.6 | Intel E52620V3 (x86_64) | AESNI | BKP | U2 | | 7 | Linux 2.6 | Intel E52680V3 (x86_64) | AESNI | BKP | U2 | | 8 | Linux 2.6 | Intel E52699V3 (x86_64) | AESNI | BKP | U2 | | 9 | Linux 4.4 | Intel E5504 (x86_64) | None | BKP | U2 | | 10 | Linux 4.4 | Intel E52403V2 (x86_64) | AESNI | BKP | U2 | | 11 | Linux 4.4 | Intel E52680V3 (x86_64) | AESNI | BKP | U2 | | 12 | Linux 4.4 | Intel Xeon Silver 4110 (x86_64) | AESNI | BKP | U2 | See Appendix A for additional information on build method and optimizations. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. Page 10 of 29 Nimble Storage FIPS 1402 Security Policy ## 3 Ports and Interfaces The physical ports of the Module are the same as the computer system on which it is executing. The logical interface is a Clanguage application program interface (API). Table 3 Logical interfaces | Logical interface type | Description | |--------------------------|-----------------------------------------------------------| | Control input | API entry point and corresponding stack parameters | | Data input | API entry point data input stack parameters | | Status output | API entry point return values and status stack parameters | | Data output | API entry point data output stack parameters | As a software module, control of the physical ports is outside module scope. However, when the module is performing selftests, or is in an error state, all output on the logical data output interface is inhibited. The module is singlethreaded and in error scenarios returns only an error value (no data output is returned). Page 11 of 29 Nimble Storage FIPS 1402 Security Policy ## 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 1402 Approved mode. Tables 4a and 4b list the Approved and Nonapproved but Allowed algorithms, respectively. | Function | Algorithm | Options | Cert # | |----------------------------------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------| | Random Number Generation; Symmetric key generation | [SP 80090A] DRBG 2 Prediction resistance supported for all variations | Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function | 342, 784 | | Encryption, Decryption and CMAC | [SP 80067] | 3Key TripleDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify | 1522, 1912 | | Encryption, Decryption and CMAC | [FIPS 197] AES | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 2484, 3351 | | Encryption, Decryption and CMAC | [SP 80038B] CMAC [SP 80038C] CCM [SP 80038D] GCM [SP 80038E] XTS | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 2484, 3351 | | Message Digests | [FIPS 1803] | SHA1, SHA2 (224, 256, 384, 512) | 2102, 2778 | | Keyed Hash | [FIPS 198] HMAC | SHA1, SHA2 (224, 256, 384, 512) | 1526, 2134 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] RSA | SigVer9.31 (1024/1536/2048/3072/4096 with SHA1/256/384/512) SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA 1/SHA2 sizes) | 1273, 1718 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] RSA | SigGen9.31 (2048/3072/4096 with SHA 256/384/512) SigGenPKCS1.5, SigGenPSS (2048/3072/4096 with all SHA2 sizes) | 1718 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA2 sizes) | 764, 950 | Page 12 of 29 Nimble Storage FIPS 1402 Security Policy Table 4a - FIPS Approved Cryptographic Functions | | [FIPS 1864] ECDSA | PKG: CURVES( P224 P256 P384 P521 K 224 K256 K384 K521 B224 B256 B384 B 521 ExtraRandomBits TestingCandidates ) PKV: CURVES( ALLP ALLK ALLB ) SigGen: CURVES( P224: (SHA224, 256, 384, 512) P256: (SHA224, 256, 384, 512) P384: (SHA224, 256, 384, 512) P521: (SHA224, 256, 384, 512) K233: (SHA224, 256, 384, 512) K283: (SHA224, 256, 384, 512) K409: (SHA224, 256, 384, 512) K571: (SHA224, 256, 384, 512) B233: (SHA224, 256, 384, 512) B283: (SHA224, 256, 384, 512) B409: (SHA 224, 256, 384, 512) B571: (SHA224, 256, 384, 512) ) SigVer: CURVES( P192: (SHA1, 224, 256, 384, 512) P224: (SHA1, 224, 256, 384, 512) P 256: (SHA1, 224, 256, 384, 512) P384: (SHA 1, 224, 256, 384, 512) P521: (SHA1, 224, 256, 384, 512) K163: (SHA1, 224, 256, 384, 512) K233: (SHA1, 224, 256, 384, 512) K283: (SHA1, 224, 256, 384, 512) K409: (SHA1, 224, 256, 384, 512) K571: (SHA1, 224, 256, 384, 512 B163: (SHA1, 224, 256, 384, 512) B 233: (SHA1, 224, 256, 384, 512) B283: (SHA 1, 224, 256, 384, 512) B409: (SHA1, 224, 256, 384, 512) B571: (SHA1, 224, 256, 384, 512) ) | 413, 664 | |---------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| | ECC CDH (CVL) | [SP 80056A] (§5.7.1.2) | All NIST defined B, K and P curves except sizes 163 and 192 | 85, 496 | The Module supports only NIST defined curves for use with ECDSA and ECC CDH. The Module supports two operational environment configurations for elliptic curve; NIST prime curve only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Table 4b - NonFIPS Approved But Allowed Cryptographic Functions | Category | Algorithm | Description | |----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC DH | Noncompliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. | | Key Encryption, Decryption | RSA | The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 80056B compliance, and no CSPs are established into or exported out of the module using these services. | Page 13 of 29 Nimble Storage FIPS 1402 Security Policy Table 4c - FIPS NonApproved Cryptographic Functions | Function | Algorithm | Options | Cert # | |----------------------------------------------------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| | Random Number Generation; Symmetric key generation | [ANS X9.31] RNG | AES 128/192/256 | 1202, 1363 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] RSA | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/4096 with SHA1) | 1273 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) | 764 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) | 764 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] ECDSA | PKG: CURVES( P192 K163 B163 ) SIG(gen): CURVES( P192 P224 P256 P384 P521 K163 K233 K283 K409 K571 B163 B233 B283 B409 B571 ) | 413 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] ECDSA | PKG: CURVES( P192 K163 B163 ) SigGen: CURVES( P192: (SHA1, 224, 256, 384, 512) P224:(SHA1) P256:(SHA1) P384: (SHA1) P521:(SHA1) K163: (SHA1, 224, 256, 384, 512) K233:(SHA1) K283:(SHA1) K409:(SHA1) K571:(SHA1) B163: (SHA1, 224, 256, 384, 512) B233:(SHA1) B283: (SHA1) B409:(SHA1) B571:(SHA1) ) | 413 | | ECC CDH (CVL) | [SP 80056A] (§5.7.1.2) | All NIST Recommended B, K and P curves sizes 163 and 192 | 85 | These algorithms shall not be used when operating in the FIPS Approved mode of operation. EC DH Key Agreement provides a maximum of 256 bits of security strength. RSA Key Wrapping provides a maximum of 256 bits of security strength. The Module requires an initialization sequence (see IG 9.5): the calling application invokes FIPS_mode_set() 3 , which returns a \'1\' for success and \'0\' for failure. If FIPS_mode_set() fails then all cryptographic services fail from then on. The application can test to see if FIPS mode has been successfully performed. The Module is a cryptographic engine library, which can be used only in conjunction with additional software. Aside from the use of the NIST defined elliptic curves as trusted third party domain parameters, all other FIPS 1864 assurances are outside the scope of the Module, and are the responsibility of the calling process. 3 The function call in the Module is FIPS_module_mode_set() which is typically used by an application via the FIPS_mode_set() wrapper function. Page 14 of 29 Nimble Storage FIPS 1402 Security Policy ### 4.1 Critical Security Parameters and Public Keys All CSPs used by the Module are described in this section. All access to these CSPs by Module services are described in Section 4. The CSP names are generic, corresponding to API parameter data structures. Table 4.1a - Critical Security Parameters | CSP Name | Description | |-----------------|------------------------------------------------------------------------------------------------------------------------| | RSA SGK | RSA (1024 to 16384 bits) signature generation key | | RSA KDK | RSA (1024 to 16384 bits) key decryption (private key transport) key | | DSA SGK | [FIPS 1864] DSA (1024/2048/3072) signature generation key | | ECDSA SGK | ECDSA (All NIST defined B, K, and P curves) signature generation key | | EC DH Private | EC DH (All NIST defined B, K, and P curves) private key agreement key. | | AES EDK | AES (128/192/256) encrypt / decrypt key | | AES CMAC | AES (128/192/256) CMAC generate / verify key | | AES GCM | AES (128/192/256) encrypt / decrypt / generate / verify key | | AES XTS | AES (256/512) XTS encrypt / decrypt key | | TripleDES EDK | TripleDES (3Key) encrypt / decrypt key | | TripleDES CMAC | TripleDES (3Key) CMAC generate / verify key | | HMAC Key | Keyed hash key (160/224/256/384/512) | | Hash_DRBG CSPs | V (440/888 bits) and C (440/888 bits), entropy input (length dependent on security strength) | | HMAC_DRBG CSPs | V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits), entropy input (length dependent on security strength) | | CTR_DRBG CSPs | V (128 bits) and Key (AES 128/192/256), entropy input (length dependent on security strength) | | COADDigest | Precalculated HMACSHA1 digest used for Crypto Officer role authentication | | UserADDigest | Precalculated HMACSHA1 digest used for User role authentication | Authentication data is loaded into the module during the module build process, performed by an authorized operator (Crypto Officer), and otherwise cannot be accessed. The module does not output intermediate key generation values. | CSP Name | Description | |--------------|--------------------------------------------------------------------------------------------------------------------| | RSA SVK | RSA (1024 to 16384 bits) signature verification public key | | RSA KEK | RSA (1024 to 16384 bits) key encryption (public key transport) key | | DSA SVK | [FIPS 1864] DSA (1024/2048/3072) signature verification key or [FIPS 1862] DSA (1024) signature verification key | | ECDSA SVK | ECDSA (All NIST defined B, K and P curves) signature verification key | | EC DH Public | EC DH (All NIST defined B, K and P curves) public key agreement key. | Page 15 of 29 Nimble Storage FIPS 1402 Security Policy ###### For all CSPs and Public Keys: Storage : RAM, associated to entities by memory location. The Module stores DRBG state values for the lifetime of the DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of DRBG state values used for the Modules\' default key generation service. Generation : The Module implements SP 80090 compliant DRBG services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry : All CSPs enter the Module\'s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output : The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Destruction : Zeroization of sensitive data is performed automatically by API function calls for temporarily stored CSPs. In addition, the module provides functions to explicitly destroy CSPs related to random number generation services. The calling application is responsible for parameters passed in and out of the module. Private and secret keys as well as seeds and entropy input are provided to the Module by the calling application, and are destroyed when released by the appropriate API function calls. Keys residing in internally allocated data structures (during the lifetime of an API call) can only be accessed using the Module defined API. The operating system protects memory and process space from unauthorized access. Only the calling application that creates or imports keys can use or export such keys. All API functions are executed by the invoking calling application in a nonoverlapping sequence such that no two API functions will execute concurrently. An authorized application as user (CryptoOfficer and User) has access to all key data generated during the operation of the Module. In the event Module power is lost and restored the calling application must ensure that any AESGCM keys used for encryption or decryption are redistributed. Module users (the calling applications) shall use entropy sources that meet the security strength required for the random number generation mechanism: 128 bits as shown in [SP 80090] Table 2 (Hash_DRBG, HMAC_DRBG), and Table 3 (CTR_DRBG). This entropy is supplied by means of callback functions. Those functions must return an error if the minimum entropy strength cannot be met. Table 4.1b - Public Keys Page 16 of 29 Nimble Storage FIPS 1402 Security Policy ## 5 Roles, Authentication and Services The Module implements the required User and Crypto Officer roles and requires authentication for those roles. Only one role may be active at a time and the Module does not allow concurrent operators. The User or Crypto Officer role is assumed by passing the appropriate password to the FIPS_module_mode_set() function. The password values may be specified at build time and must have a minimum length of 16 characters. Any attempt to authenticate with an invalid password will result in an immediate and permanent failure condition rendering the Module unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the Module during the Module build process, performed by the Crypto Officer, and otherwise cannot be accessed. Since minimum password length is 16 characters, the probability of a random successful authentication attempt in one try is a maximum of 1/256 16 , or less than 1/10 38 . The Module permanently disables further authentication attempts after a single failure, so this probability is independent of time. Both roles have access to all of the services provided by the Module. - User Role (User): Loading the Module and calling any of the API functions. - Crypto Officer Role (CO): Installation of the Module on the host computer system and calling of any API functions. All services implemented by the Module are listed below, along with a description of service CSP access. | Service | Role | Description | |--------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Initialize | User, CO | Module initialization. Does not access CSPs. | | Selftest | User, CO | Perform self tests (FIPS_selftest). Does not access CSPs. | | Show status | User, CO | Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. | | Zeroize | User, CO | Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. | | Random number generation | User, CO | Used for random number and symmetric key generation. Seed or reseed an DRBG instance Determine security strength of a DRBG instance | Page 17 of 29 Nimble Storage FIPS 1402 Security Policy | Service | Role | Description | |---------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. | | Asymmetric key generation | User, CO | Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP80090 | | Symmetric encrypt/decrypt | User, CO | Used to encrypt or decrypt data. Executes using AES EDK, TripleDES EDK (passed in by the calling process). | | Symmetric digest | User, CO | Used to generate or verify data integrity with CMAC. Executes using AES CMAC, TripleDES, CMAC (passed in by the calling process). | | Message digest | User, CO | Used to generate a SHA1 or SHA2 message digest. Does not access CSPs. | | Keyed Hash | User, CO | Used to generate or verify data integrity with HMAC. Executes using HMAC Key (passed in by the calling process). | | Key transport 4 | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | | Key agreement | User, CO | Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). | | Digital signature | User, CO | Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). | | Utility | User, CO | Miscellaneous helper functions. Does not access CSPs. | ## 6 Selftest The Module performs the selftests listed below on invocation of Initialize or Selftest. | Algorithm | Type | Test Attributes | |--------------------|--------|------------------------------------------------------------------------------------------------------------| | Software integrity | KAT | HMACSHA1 | | HMAC | KAT | One KAT per SHA1, SHA224, SHA256, SHA384 and SHA512 Per IG 9.3, this testing covers SHA POST requirements. | | AES | KAT | Separate encrypt and decrypt, ECB mode, 128 bit key length | | AES CCM | KAT | Separate encrypt and decrypt, 192 key length | Table 5 Services and CSP Access Page 18 of 29 Nimble Storage FIPS 1402 Security Policy Table 6a Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency test) | Algorithm | Type | Test Attributes | |-----------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | AES GCM | KAT | Separate encrypt and decrypt, 256 key length | | XTSAES | KAT | 128, 256 bit key sizes to support either the 256bit key size (for XTSAES128) or the 512bit key size (for XTSAES256) | | AES CMAC | KAT | Sign and verify CBC mode, 128, 192, 256 key lengths | | TripleDES | KAT | Separate encrypt and decrypt, ECB mode, 3Key | | TripleDES CMAC | KAT | CMAC generate and verify, CBC mode, 3Key | | RSA | KAT | Sign and verify using 2048 bit key, SHA256, PKCS#1 | | DSA | PCT | Sign and verify using 2048 bit key, SHA384 | | DRBG | KAT | CTR_DRBG: AES, 256 bit with and without derivation function HASH_DRBG: SHA256 HMAC_DRBG: SHA256 | | ECDSA | PCT | Keygen, sign, verify using P224, K233 and SHA512. The K233 selftest is not performed for operational environments that support prime curve only (see Table 2). | | ECC CDH | KAT | Shared secret calculation per SP 80056A §5.7.1.2, IG 9.6 | The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMACSHA1 of the Module distribution file as tested by the CMT Laboratory and listed in Appendix A is verified during installation of the Module file as described in Appendix A. The FIPS_mode_set() 5 function performs all powerup selftests listed above with no operator intervention required, returning a \'1\' if all powerup selftests succeed, and a \'0\' otherwise. If any component of the powerup selftest fails an internal flag is set to prevent subsequent invocation of any cryptographic function calls. The module will only enter the FIPS Approved mode if the module is reloaded and the call to FIPS_mode_set() 5 succeeds. The powerup selftests may also be performed ondemand by calling FIPS_selftest() , which returns a \'1\' for success and \'0\' for failure. Interpretation of this return code is the responsibility of the calling application. The Module also implements the following conditional tests: | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Tested as required by [SP80090] Section 11 | | DRBG | FIPS 1402 continuous test for stuck fault | | DSA | Pairwise consistency test on each generation of a key pair | | ECDSA | Pairwise consistency test on each generation of a key pair | Page 19 of 29 ####### Nimble Storage FIPS 1402 Security Policy Table 6b Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | RSA | Pairwise consistency test on each generation of a key pair | In the event of a DRBG selftest failure the calling application must uninstantiate and re instantiate the DRBG per the requirements of [SP 80090]; this is not something the Module can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. The Module supports two operational environment configurations for elliptic curve: NIST prime curves only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Page 20 of 29 Nimble Storage FIPS 1402 Security Policy ## 7 Operational Environment The tested operating systems segregate user processes into separate process spaces. Each process space is logically separated from all other processes by the operating system software and hardware. The Module functions entirely within the process space of the calling application, and implicitly satisfies the FIPS 1402 requirement for a single user mode of operation. Page 21 of 29 Nimble Storage FIPS 1402 Security Policy ## 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 1402. Page 22 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix A Installation and Usage Guidance The test platforms represent different combinations of installation instructions. For each platform there is a build system, the host providing the build environment in which the installation instructions are executed, and a target system on which the generated object code is executed. The build and target systems may be the same type of system or even the same device, or may be different systems - the Module supports crosscompilation environments. Each of these command sets are relative to the top of the directory containing the uncompressed and expanded contents of the distribution files opensslfips2.0.9.tar.gz (all NIST defined curves as listed in Table 2 with the EC column marked "BKP") or opensslfipsecp2.0.9.tar.gz (NIST prime curves only as listed in Table 2 with the EC column marked "P"). The command sets are: U1: ./config no-asm make make install U2: ./config make make install W1: ms\\do_fips no-asm W2: ms\\do_fips ####### Installation instructions 1. Download and copy the distribution file to the build system. These files can be downloaded from http://www.openssl.org/source /. 2. Verify the HMACSHA1 digest of the distribution file; see Appendix B. An independently acquired FIPS 1402 validated implemention of SHA1 HMAC must be used for this digest verification. Note that this verification can be performed on any convenient system and not necessarily on the specific build or target system. Alternatively, a copy of the distribution on physical media can be obtained from OSF 6 . 3. Unpack the distribution 6 For some prospective users the acquisition, installation, and configuration of a suitable FIPS 1402 validated product may not be convenient. OSF will on request mail a CD containing the source code distribution, via USPS or international post. A distribution file received by that means need not be verified by a FIPS 1402 validated implementation of HMACSHA1. For instructions on requesting this CD see http://opensslfoundation.com/fips/verify.html. Page 23 of 29 Nimble Storage FIPS 1402 Security Policy ``` gunzip -c openssl-fips-2.0.9.tar.gz | tar xf cd openssl-fips-2.0.9 or gunzip -c openssl-fips-ecp-2.0.9.tar.gz | tar xf cd openssl-fips-ecp-2.0.9 ``` 4. Execute one of the installation command sets U1, W1, U2, W2 as shown above. No other command sets shall be used. 5. The resulting fipscanister.o or fipscanister.lib file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 7 function. Note that failure to use one of the specified commands sets exactly as shown will result in a module that cannot be considered compliant with FIPS 1402. ####### Linking the Runtime Executable Application Note that applications interfacing with the FIPS Object Module are outside of the cryptographic boundary. When linking the application with the FIPS Object Module two steps are necessary: 1. The HMACSHA1 digest of the FIPS Object Module file must be calculated and verified against the installed digest to ensure the integrity of the FIPS object module. 2. A HMACSHA1 digest of the FIPS Object Module must be generated and embedded in the FIPS Object Module for use by the FIPS_mode_set() 7 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the FIPS Object Module and to generate the new HMACSHA1 digest for the runtime executable application. Failure to embed the digest in the executable object will prevent initialization of FIPS mode. At runtime the FIPS_mode_set() 7 function compares the embedded HMACSHA1 digest with a digest generated from the FIPS Object Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. ###### Optimization The \'asm\' designation means that assembler language optimizations were enabled when the binary code was built, \'noasm\' means that only C language code was compiled. For OpenSSL with x86 there are three possible optimization levels: 1. No optimization (plain C) 2. SSE2 optimization 7 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 24 of 29 Nimble Storage FIPS 1402 Security Policy ### 3. AESNI+PCLMULQDQ+SSSE3 optimization Other theoretically possible combinations (e.g. AESNI only, or SSE3 only) are not addressed individually, so that a processor which does not support all three of AESNI, PCLMULQDQ, and SSSE3 will fall back to SSE2 optimization. For more information, see: - [ http://www.intel.com/support/processors/sb/CS030123.htm?wapkw=sse2](http://www.intel.com/support/processors/sb/CS-030123.htm?wapkw=sse2) - [ http://software.intel.com/enus/articles/inteladvancedencryptionstandardinstructions aesni/?wapkw=aesni](http://software.intel.com/en-us/articles/intel-advanced-encryption-standard-instructions-aes-ni/?wapkw=aes-ni) For OpenSSL with ARM there are two possible optimization levels: 1. Without NEON 2. With NEON (ARM7 only) [For more information, see http://www.arm.com/products/processors/technologies/neon.php](http://www.arm.com/products/processors/technologies/neon.php) Page 25 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix B Controlled Distribution File Fingerprint The OpenSSL FIPS Object Module v2.0.9 consists of the FIPS Object Module (the fipscanister.o or fipscanister.lib contiguous unit of binary object code) generated from the specific source files. For all NIST defined curves (listed in Table 2 with the EC column marked "BKP") the source files are in the specific special OpenSSL distribution opensslfips2.0.9.tar.gz with HMAC SHA1 digest of 54552e9a3ed8d1561341e8945fcdec55af961322 [located at http://www.openssl.org/source/opensslfips2.0.9.tar.gz.](http://www.openssl.org/source/openssl-fips-2.0.9.tar.gz) The openssl command from a version of OpenSSL that incorporates a previously validated version of the module may be used: openssl sha1 -hmac etaonrishdlcupfm openssl-fips-2.0.9.tar.gz For NIST prime curves only (listed in Table 2 with the EC column marked "P") the source files are in the specific special OpenSSL distribution opensslfipsecp2.0.9.tar.gz with HMACSHA1 digest of 91d267688713c920f85bc5e69c8b5d34e1112672 located at http://www.openssl.org/source/opensslfipsecp2.0.9.tar.gz. Note this is from the previous revision of the FIPS Object Module as no modifications relevant to NIST prime curves only were introduced in revision 2.0.9. The set of files specified in this tar file constitutes the complete set of source files of this module. There shall be no additions, deletions, or alterations of this set as used during module build. The OpenSSL distribution tar file (and patch file if used) shall be verified using the above HMAC SHA1 digest(s). The arbitrary 16 byte key of: 65 74 61 6f 6e 72 69 73 68 64 6c 63 75 70 66 6d (equivalent to the ASCII string " etaonrishdlcupfm ") is used to generate the HMACSHA1 value for the FIPS Object Module integrity check. The functionality of all earlier revisions of the FIPS Object Module are subsumed by this latest revision, so there is no reason to use older revisions for any new deployments. However, older revisions remain valid. The source distribution files and corresponding HMACSHA1 digests are listed below: opensslfips2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.8.tar.gz Page 26 of 29 ####### Nimble Storage FIPS 1402 Security Policy Digest: 7f486fbb598f3247ab9db10c1308f1c19f384671 opensslfipsecp2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.8.tar.gz Digest: 7a5f40ef8cebe959372d16e26391fcf23689209b opensslfips2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.7.tar.gz Digest: 295064925a6d95271e2fa2920181ec060f95c7ab opensslfipsecp2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.7.tar.gz Digest: dddfdc78c7e827c61fe92bd4817a7f2c3e67153 opensslfips2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.6.tar.gz Digest: 2b8d831df22d4dfe6169aa2a8e74c35484c26c21 opensslfipsecp2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.6.tar.gz Digest: 852f43cd9ae1bd2eba60e4f9f1f266d3c16c0319 opensslfips2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.5.tar.gz Digest: 8b44f2a43d098f6858eb1ebe77b73f8f027a9c29 opensslfipsecp2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.5.tar.gz Digest: 148e4e127ffef1df80c0ed61bae35b07ec7b7b36 opensslfips2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.4.tar.gz Digest: eaa5f86dab2c5da7086aec4786bce27d3b3c1b8a opensslfipsecp2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.4.tar.gz Digest: 13302f75c82c8b482c9ac96828984a270a45c284 opensslfips2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.3.tar.gz Digest: 5dfe03bc3f57c2862ea97823ea3111d7faf711b2 Page 27 of 29 ####### Nimble Storage FIPS 1402 Security Policy opensslfipsecp2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.3.tar.gz Digest: 9d6b21218d7d5480aa0add68e682d321e3ffbfa7 opensslfips2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.2.tar.gz Digest: e099d5096eb69c2dd8591379f38b985801188663 opensslfipsecp2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.2.tar.gz Digest: 887fa6802c253c32e6c4c83b7a091118fa8c6217 opensslfips2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.1.tar.gz. Digest: 1e05b021fdcd6e77c6155512bbce2d0cbc725aec opensslfipsecp2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.1.tar.gz. Digest: af82c8ebb9d3276be11feffd35e6b55bd0d1839f opensslfips2.0.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.tar.gz. Digest: 2cdd29913c6523df8ad38da11c342b80ed3f1dae opensslfipsecp2.0.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.tar.gz. Digest: e8d5ee306425b278bf6c8b077dae8e4a542e8215 Page 28 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix C Compilers This appendix lists the specific compilers used to generate the Module for the respective Operational Environments. Note this list does not imply that use of the Module is restricted to only the listed compiler versions, only that the use of other versions has not been confirmed to produce a correct result. Table C Compilers | # | Operational Environment | Compiler | |-----|---------------------------|------------| | 1 | Linux 2.6 | gcc 4.1.2 | | 2 | Linux 2.6 | gcc 4.1.2 | | 3 | Linux 2.6 | gcc 4.1.2 | | 4 | Linux 3.4 | gcc 4.8.0 | | 5 | Linux 2.6 | gcc 4.1.2 | | 6 | Linux 2.6 | gcc 4.1.2 | | 7 | Linux 2.6 | gcc 4.1.2 | | 8 | Linux 2.6 | gcc 4.1.2 | | 9 | Linux 4.4 | gcc 4.1.2 | | 10 | Linux 4.4 | gcc 4.1.2 | | 11 | Linux 4.4 | gcc 4.1.2 | | 12 | Linux 4.4 | gcc 4.1.2 | Page 29 of 29']}}}} data.

  The computed heuristics were updated.

  • The policy_prunned_references property was updated, with the {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']} values discarded.
  • The policy_processed_references property was updated, with the {'directly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']}}, 'indirectly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']}}} data.
• 05.10.2026

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8 | | 20140104 | Addition of new platform #96, FreeBSD 8.4 on x86 without AESNI | | 20140730 | Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG | | 20140728 | Changed processor names for platforms #90, #91 | | 20140711 | Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86 | | 20140612 | Temporarily remove misplaced platform, move Dual EC DRBG to the Non Approved Table 4c | | 20140529 | Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) | | 20140512 | Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition | | 20131108 | Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI | | 20131101 | Added two platforms #77, #78 iOS 6.0 with/without NEON | Page 4 of 29 ####### Nimble Storage FIPS 1402 Security Policy | 20130829 | Added new sponsor acknowledgment | |--------------|-----------------------------------------------------------------------------------------------------| | 20130814 | Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms | | 20130724 | Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 | | 20130609 | Added QNX, iOS 6.1, eCos for revision 2.0.5 | | 20130501 | Added OpenWRT 2.6 for revision 2.0.4 | | 20130301 | Added VMware Horizon Mobile 1.3, Apple OS X 10.7 , Apple iOS 5.0 | | 20130223 | Added WinEC7 and Android 4.0 for revision 2.0.3 | | 20130214 | Table 5: Removed references to nonexistent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM | | 20130128 | Added four platforms: Android 4.1 and Android 4.2 with and without NEON | | 20130108 | Reworded section 8 | | 20130103 | Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AESNI. | | 20121208 | Note EC DH Key Agreement and RSA Key Wrapping strength. | | 20121010 | Added NetBSD 5.1 on PowerPCe500, NetBSD 5.1 on Intel Xeon 5500 (x8664) for revision 2.0.2 | | 20110702 | Added DSP Media Framework, Linux 2.6/Freescale PowerPCe500, Android 4.0 | | 20110615 | Added iOS, WinCE 5, WinCE 6 OEs | ####### References | Reference | Full Specification Name | |--------------|---------------------------------------------------------------------------------------------------------| | [ANS X9.31] | Digital Signatures Using Reversible Public Key Cryptography for the Financial Services Industry (rDSA) | | [FIPS 1402] | Security Requirements for Cryptographic modules, May 25, 2001 | | [FIPS 1803] | Secure Hash Standard | | [FIPS 1864] | Digital Signature Standard | | [FIPS 197] | Advanced Encryption Standard | | [FIPS 1981] | The KeyedHash Message Authentication Code (HMAC) | | [SP 80038B] | Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication | | [SP 80038C] | Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality | Page 5 of 29 ####### Nimble Storage FIPS 1402 Security Policy | Reference | Full Specification Name | |----------------|---------------------------------------------------------------------------------------------------| | [SP 80038D] | Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC | | [SP 80056A] | Recommendation for PairWise Key Establishment Schemes Using Discrete Logarithm Cryptography | | [SP 800 67R1] | Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher | | [SP 80089] | Recommendation for Obtaining Assurances for Digital Signature Applications | | [SP 80090] | Recommendation for Random Number Generation Using Deterministic Random Bit Generators | | [SP 800 131A] | Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths | Page 6 of 29 Nimble Storage FIPS 1402 Security Policy ### Table of Contents | 1 Introduction.........................................................................................................................7 | |----------------------------------------------------------------------------------------------------------------------------------------------| | 2 Tested Configurations.........................................................................................................9 | | 3 Ports and Interfaces ............................................................................................................13 | | 4 Modes of Operation and Cryptographic Functionality ......................................................14 | | 4.1 Critical Security Parameters and Public Keys............................................................18 | | 5 Roles, Authentication and Services ...................................................................................21 | | 6 Selftest...............................................................................................................................23 | | 7 Operational Environment....................................................................................................25 | | 8 Mitigation of other Attacks.................................................................................................26 | | Appendix A Installation and Usage Guidance.......................................................................27 | | Appendix B Controlled Distribution File Fingerprint...........................................................30 | | Appendix C Compilers..........................................................................................................33 | Page 7 of 29 Nimble Storage FIPS 1402 Security Policy ## 1 Introduction This document is the nonproprietary security policy for the Nimble Storage FIPS Object Module, hereafter referred to as the Module, which is build from the OpenSSL FIPS Object Module source code according to the the instructions in Appendix A. The Module is a software library providing a Clanguage application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 1402 as a software module, multichip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the fipscanister object module, a single object module file named fipscanister.o compiled on Linux ®1 . The Module performs no communications other than with the calling application (the process that invokes the Module services). The FIPS 1402 security levels for the Module are as follows: | Security Requirement | Security Level | |-------------------------------------------|------------------| | Cryptographic Module Specification | 1 | | Cryptographic Module Ports and Interfaces | 1 | | Roles, Services, and Authentication | 2 | | Finite State Model | 1 | | Physical Security | NA | | Operational Environment | 1 | | Cryptographic Key Management | 1 | | EMI/EMC | 1 | | SelfTests | 1 | | Design Assurance | 3 | | Mitigation of Other Attacks | NA | Table 1 - Security Level of Security Requirements The Module\'s software version for this validation is 2.0.9. It is build from the 2.0.9 version of the OpenSSL FIPS Object Module source code. 1 Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Page 8 of 29 ####### Nimble Storage FIPS 1402 Security Policy Figure 1 Module Block Diagram Page 9 of 29 Nimble Storage FIPS 1402 Security Policy ## 2 Tested Configurations Table 2 Tested Configurations (B = Build Method; EC = Elliptic Curve Support). The EC column indicates support for prime curve only (P), or all NIST defined B, K, and P curves (BKP). | # | Operational Environment | Processor | Optimiz ations (Target) | EC | B | |-----|-----------------------------------------|---------------------------------|----------------------------|------|-----| | 1 | Linux 2.6 | Intel E52403V2 (x86_64) | AESNI | BKP | U2 | | 2 | Linux 2.6 | Intel E52450V2 (x86_64) | AESNI | BKP | U2 | | 3 | Linux 2.6 | Intel E52470V2 (x86_64) | AESNI | BKP | U2 | | 4 | Linux 3.4 64bit under Citrix XenServer | Intel Xeon E52430L (x86) | None | BKP | U2 | | 5 | Linux 2.6 | Intel E52603V3 (x86_64) | AESNI | BKP | U2 | | 6 | Linux 2.6 | Intel E52620V3 (x86_64) | AESNI | BKP | U2 | | 7 | Linux 2.6 | Intel E52680V3 (x86_64) | AESNI | BKP | U2 | | 8 | Linux 2.6 | Intel E52699V3 (x86_64) | AESNI | BKP | U2 | | 9 | Linux 4.4 | Intel E5504 (x86_64) | None | BKP | U2 | | 10 | Linux 4.4 | Intel E52403V2 (x86_64) | AESNI | BKP | U2 | | 11 | Linux 4.4 | Intel E52680V3 (x86_64) | AESNI | BKP | U2 | | 12 | Linux 4.4 | Intel Xeon Silver 4110 (x86_64) | AESNI | BKP | U2 | See Appendix A for additional information on build method and optimizations. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. Page 10 of 29 Nimble Storage FIPS 1402 Security Policy ## 3 Ports and Interfaces The physical ports of the Module are the same as the computer system on which it is executing. The logical interface is a Clanguage application program interface (API). Table 3 Logical interfaces | Logical interface type | Description | |--------------------------|-----------------------------------------------------------| | Control input | API entry point and corresponding stack parameters | | Data input | API entry point data input stack parameters | | Status output | API entry point return values and status stack parameters | | Data output | API entry point data output stack parameters | As a software module, control of the physical ports is outside module scope. However, when the module is performing selftests, or is in an error state, all output on the logical data output interface is inhibited. The module is singlethreaded and in error scenarios returns only an error value (no data output is returned). Page 11 of 29 Nimble Storage FIPS 1402 Security Policy ## 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 1402 Approved mode. Tables 4a and 4b list the Approved and Nonapproved but Allowed algorithms, respectively. | Function | Algorithm | Options | Cert # | |----------------------------------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------| | Random Number Generation; Symmetric key generation | [SP 80090A] DRBG 2 Prediction resistance supported for all variations | Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function | 342, 784 | | Encryption, Decryption and CMAC | [SP 80067] | 3Key TripleDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify | 1522, 1912 | | Encryption, Decryption and CMAC | [FIPS 197] AES | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 2484, 3351 | | Encryption, Decryption and CMAC | [SP 80038B] CMAC [SP 80038C] CCM [SP 80038D] GCM [SP 80038E] XTS | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 2484, 3351 | | Message Digests | [FIPS 1803] | SHA1, SHA2 (224, 256, 384, 512) | 2102, 2778 | | Keyed Hash | [FIPS 198] HMAC | SHA1, SHA2 (224, 256, 384, 512) | 1526, 2134 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] RSA | SigVer9.31 (1024/1536/2048/3072/4096 with SHA1/256/384/512) SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA 1/SHA2 sizes) | 1273, 1718 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] RSA | SigGen9.31 (2048/3072/4096 with SHA 256/384/512) SigGenPKCS1.5, SigGenPSS (2048/3072/4096 with all SHA2 sizes) | 1718 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA2 sizes) | 764, 950 | Page 12 of 29 Nimble Storage FIPS 1402 Security Policy Table 4a - FIPS Approved Cryptographic Functions | | [FIPS 1864] ECDSA | PKG: CURVES( P224 P256 P384 P521 K 224 K256 K384 K521 B224 B256 B384 B 521 ExtraRandomBits TestingCandidates ) PKV: CURVES( ALLP ALLK ALLB ) SigGen: CURVES( P224: (SHA224, 256, 384, 512) P256: (SHA224, 256, 384, 512) P384: (SHA224, 256, 384, 512) P521: (SHA224, 256, 384, 512) K233: (SHA224, 256, 384, 512) K283: (SHA224, 256, 384, 512) K409: (SHA224, 256, 384, 512) K571: (SHA224, 256, 384, 512) B233: (SHA224, 256, 384, 512) B283: (SHA224, 256, 384, 512) B409: (SHA 224, 256, 384, 512) B571: (SHA224, 256, 384, 512) ) SigVer: CURVES( P192: (SHA1, 224, 256, 384, 512) P224: (SHA1, 224, 256, 384, 512) P 256: (SHA1, 224, 256, 384, 512) P384: (SHA 1, 224, 256, 384, 512) P521: (SHA1, 224, 256, 384, 512) K163: (SHA1, 224, 256, 384, 512) K233: (SHA1, 224, 256, 384, 512) K283: (SHA1, 224, 256, 384, 512) K409: (SHA1, 224, 256, 384, 512) K571: (SHA1, 224, 256, 384, 512 B163: (SHA1, 224, 256, 384, 512) B 233: (SHA1, 224, 256, 384, 512) B283: (SHA 1, 224, 256, 384, 512) B409: (SHA1, 224, 256, 384, 512) B571: (SHA1, 224, 256, 384, 512) ) | 413, 664 | |---------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| | ECC CDH (CVL) | [SP 80056A] (§5.7.1.2) | All NIST defined B, K and P curves except sizes 163 and 192 | 85, 496 | The Module supports only NIST defined curves for use with ECDSA and ECC CDH. The Module supports two operational environment configurations for elliptic curve; NIST prime curve only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Table 4b - NonFIPS Approved But Allowed Cryptographic Functions | Category | Algorithm | Description | |----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC DH | Noncompliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. | | Key Encryption, Decryption | RSA | The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 80056B compliance, and no CSPs are established into or exported out of the module using these services. | Page 13 of 29 Nimble Storage FIPS 1402 Security Policy Table 4c - FIPS NonApproved Cryptographic Functions | Function | Algorithm | Options | Cert # | |----------------------------------------------------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| | Random Number Generation; Symmetric key generation | [ANS X9.31] RNG | AES 128/192/256 | 1202, 1363 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] RSA | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/4096 with SHA1) | 1273 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) | 764 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) | 764 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] ECDSA | PKG: CURVES( P192 K163 B163 ) SIG(gen): CURVES( P192 P224 P256 P384 P521 K163 K233 K283 K409 K571 B163 B233 B283 B409 B571 ) | 413 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] ECDSA | PKG: CURVES( P192 K163 B163 ) SigGen: CURVES( P192: (SHA1, 224, 256, 384, 512) P224:(SHA1) P256:(SHA1) P384: (SHA1) P521:(SHA1) K163: (SHA1, 224, 256, 384, 512) K233:(SHA1) K283:(SHA1) K409:(SHA1) K571:(SHA1) B163: (SHA1, 224, 256, 384, 512) B233:(SHA1) B283: (SHA1) B409:(SHA1) B571:(SHA1) ) | 413 | | ECC CDH (CVL) | [SP 80056A] (§5.7.1.2) | All NIST Recommended B, K and P curves sizes 163 and 192 | 85 | These algorithms shall not be used when operating in the FIPS Approved mode of operation. EC DH Key Agreement provides a maximum of 256 bits of security strength. RSA Key Wrapping provides a maximum of 256 bits of security strength. The Module requires an initialization sequence (see IG 9.5): the calling application invokes FIPS_mode_set() 3 , which returns a \'1\' for success and \'0\' for failure. If FIPS_mode_set() fails then all cryptographic services fail from then on. The application can test to see if FIPS mode has been successfully performed. The Module is a cryptographic engine library, which can be used only in conjunction with additional software. Aside from the use of the NIST defined elliptic curves as trusted third party domain parameters, all other FIPS 1864 assurances are outside the scope of the Module, and are the responsibility of the calling process. 3 The function call in the Module is FIPS_module_mode_set() which is typically used by an application via the FIPS_mode_set() wrapper function. Page 14 of 29 Nimble Storage FIPS 1402 Security Policy ### 4.1 Critical Security Parameters and Public Keys All CSPs used by the Module are described in this section. All access to these CSPs by Module services are described in Section 4. The CSP names are generic, corresponding to API parameter data structures. Table 4.1a - Critical Security Parameters | CSP Name | Description | |-----------------|------------------------------------------------------------------------------------------------------------------------| | RSA SGK | RSA (1024 to 16384 bits) signature generation key | | RSA KDK | RSA (1024 to 16384 bits) key decryption (private key transport) key | | DSA SGK | [FIPS 1864] DSA (1024/2048/3072) signature generation key | | ECDSA SGK | ECDSA (All NIST defined B, K, and P curves) signature generation key | | EC DH Private | EC DH (All NIST defined B, K, and P curves) private key agreement key. | | AES EDK | AES (128/192/256) encrypt / decrypt key | | AES CMAC | AES (128/192/256) CMAC generate / verify key | | AES GCM | AES (128/192/256) encrypt / decrypt / generate / verify key | | AES XTS | AES (256/512) XTS encrypt / decrypt key | | TripleDES EDK | TripleDES (3Key) encrypt / decrypt key | | TripleDES CMAC | TripleDES (3Key) CMAC generate / verify key | | HMAC Key | Keyed hash key (160/224/256/384/512) | | Hash_DRBG CSPs | V (440/888 bits) and C (440/888 bits), entropy input (length dependent on security strength) | | HMAC_DRBG CSPs | V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits), entropy input (length dependent on security strength) | | CTR_DRBG CSPs | V (128 bits) and Key (AES 128/192/256), entropy input (length dependent on security strength) | | COADDigest | Precalculated HMACSHA1 digest used for Crypto Officer role authentication | | UserADDigest | Precalculated HMACSHA1 digest used for User role authentication | Authentication data is loaded into the module during the module build process, performed by an authorized operator (Crypto Officer), and otherwise cannot be accessed. The module does not output intermediate key generation values. | CSP Name | Description | |--------------|--------------------------------------------------------------------------------------------------------------------| | RSA SVK | RSA (1024 to 16384 bits) signature verification public key | | RSA KEK | RSA (1024 to 16384 bits) key encryption (public key transport) key | | DSA SVK | [FIPS 1864] DSA (1024/2048/3072) signature verification key or [FIPS 1862] DSA (1024) signature verification key | | ECDSA SVK | ECDSA (All NIST defined B, K and P curves) signature verification key | | EC DH Public | EC DH (All NIST defined B, K and P curves) public key agreement key. | Page 15 of 29 Nimble Storage FIPS 1402 Security Policy ###### For all CSPs and Public Keys: Storage : RAM, associated to entities by memory location. The Module stores DRBG state values for the lifetime of the DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of DRBG state values used for the Modules\' default key generation service. Generation : The Module implements SP 80090 compliant DRBG services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry : All CSPs enter the Module\'s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output : The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Destruction : Zeroization of sensitive data is performed automatically by API function calls for temporarily stored CSPs. In addition, the module provides functions to explicitly destroy CSPs related to random number generation services. The calling application is responsible for parameters passed in and out of the module. Private and secret keys as well as seeds and entropy input are provided to the Module by the calling application, and are destroyed when released by the appropriate API function calls. Keys residing in internally allocated data structures (during the lifetime of an API call) can only be accessed using the Module defined API. The operating system protects memory and process space from unauthorized access. Only the calling application that creates or imports keys can use or export such keys. All API functions are executed by the invoking calling application in a nonoverlapping sequence such that no two API functions will execute concurrently. An authorized application as user (CryptoOfficer and User) has access to all key data generated during the operation of the Module. In the event Module power is lost and restored the calling application must ensure that any AESGCM keys used for encryption or decryption are redistributed. Module users (the calling applications) shall use entropy sources that meet the security strength required for the random number generation mechanism: 128 bits as shown in [SP 80090] Table 2 (Hash_DRBG, HMAC_DRBG), and Table 3 (CTR_DRBG). This entropy is supplied by means of callback functions. Those functions must return an error if the minimum entropy strength cannot be met. Table 4.1b - Public Keys Page 16 of 29 Nimble Storage FIPS 1402 Security Policy ## 5 Roles, Authentication and Services The Module implements the required User and Crypto Officer roles and requires authentication for those roles. Only one role may be active at a time and the Module does not allow concurrent operators. The User or Crypto Officer role is assumed by passing the appropriate password to the FIPS_module_mode_set() function. The password values may be specified at build time and must have a minimum length of 16 characters. Any attempt to authenticate with an invalid password will result in an immediate and permanent failure condition rendering the Module unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the Module during the Module build process, performed by the Crypto Officer, and otherwise cannot be accessed. Since minimum password length is 16 characters, the probability of a random successful authentication attempt in one try is a maximum of 1/256 16 , or less than 1/10 38 . The Module permanently disables further authentication attempts after a single failure, so this probability is independent of time. Both roles have access to all of the services provided by the Module. - User Role (User): Loading the Module and calling any of the API functions. - Crypto Officer Role (CO): Installation of the Module on the host computer system and calling of any API functions. All services implemented by the Module are listed below, along with a description of service CSP access. | Service | Role | Description | |--------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Initialize | User, CO | Module initialization. Does not access CSPs. | | Selftest | User, CO | Perform self tests (FIPS_selftest). Does not access CSPs. | | Show status | User, CO | Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. | | Zeroize | User, CO | Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. | | Random number generation | User, CO | Used for random number and symmetric key generation. Seed or reseed an DRBG instance Determine security strength of a DRBG instance | Page 17 of 29 Nimble Storage FIPS 1402 Security Policy | Service | Role | Description | |---------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. | | Asymmetric key generation | User, CO | Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP80090 | | Symmetric encrypt/decrypt | User, CO | Used to encrypt or decrypt data. Executes using AES EDK, TripleDES EDK (passed in by the calling process). | | Symmetric digest | User, CO | Used to generate or verify data integrity with CMAC. Executes using AES CMAC, TripleDES, CMAC (passed in by the calling process). | | Message digest | User, CO | Used to generate a SHA1 or SHA2 message digest. Does not access CSPs. | | Keyed Hash | User, CO | Used to generate or verify data integrity with HMAC. Executes using HMAC Key (passed in by the calling process). | | Key transport 4 | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | | Key agreement | User, CO | Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). | | Digital signature | User, CO | Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). | | Utility | User, CO | Miscellaneous helper functions. Does not access CSPs. | ## 6 Selftest The Module performs the selftests listed below on invocation of Initialize or Selftest. | Algorithm | Type | Test Attributes | |--------------------|--------|------------------------------------------------------------------------------------------------------------| | Software integrity | KAT | HMACSHA1 | | HMAC | KAT | One KAT per SHA1, SHA224, SHA256, SHA384 and SHA512 Per IG 9.3, this testing covers SHA POST requirements. | | AES | KAT | Separate encrypt and decrypt, ECB mode, 128 bit key length | | AES CCM | KAT | Separate encrypt and decrypt, 192 key length | Table 5 Services and CSP Access Page 18 of 29 Nimble Storage FIPS 1402 Security Policy Table 6a Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency test) | Algorithm | Type | Test Attributes | |-----------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | AES GCM | KAT | Separate encrypt and decrypt, 256 key length | | XTSAES | KAT | 128, 256 bit key sizes to support either the 256bit key size (for XTSAES128) or the 512bit key size (for XTSAES256) | | AES CMAC | KAT | Sign and verify CBC mode, 128, 192, 256 key lengths | | TripleDES | KAT | Separate encrypt and decrypt, ECB mode, 3Key | | TripleDES CMAC | KAT | CMAC generate and verify, CBC mode, 3Key | | RSA | KAT | Sign and verify using 2048 bit key, SHA256, PKCS#1 | | DSA | PCT | Sign and verify using 2048 bit key, SHA384 | | DRBG | KAT | CTR_DRBG: AES, 256 bit with and without derivation function HASH_DRBG: SHA256 HMAC_DRBG: SHA256 | | ECDSA | PCT | Keygen, sign, verify using P224, K233 and SHA512. The K233 selftest is not performed for operational environments that support prime curve only (see Table 2). | | ECC CDH | KAT | Shared secret calculation per SP 80056A §5.7.1.2, IG 9.6 | The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMACSHA1 of the Module distribution file as tested by the CMT Laboratory and listed in Appendix A is verified during installation of the Module file as described in Appendix A. The FIPS_mode_set() 5 function performs all powerup selftests listed above with no operator intervention required, returning a \'1\' if all powerup selftests succeed, and a \'0\' otherwise. If any component of the powerup selftest fails an internal flag is set to prevent subsequent invocation of any cryptographic function calls. The module will only enter the FIPS Approved mode if the module is reloaded and the call to FIPS_mode_set() 5 succeeds. The powerup selftests may also be performed ondemand by calling FIPS_selftest() , which returns a \'1\' for success and \'0\' for failure. Interpretation of this return code is the responsibility of the calling application. The Module also implements the following conditional tests: | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Tested as required by [SP80090] Section 11 | | DRBG | FIPS 1402 continuous test for stuck fault | | DSA | Pairwise consistency test on each generation of a key pair | | ECDSA | Pairwise consistency test on each generation of a key pair | Page 19 of 29 ####### Nimble Storage FIPS 1402 Security Policy Table 6b Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | RSA | Pairwise consistency test on each generation of a key pair | In the event of a DRBG selftest failure the calling application must uninstantiate and re instantiate the DRBG per the requirements of [SP 80090]; this is not something the Module can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. The Module supports two operational environment configurations for elliptic curve: NIST prime curves only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Page 20 of 29 Nimble Storage FIPS 1402 Security Policy ## 7 Operational Environment The tested operating systems segregate user processes into separate process spaces. Each process space is logically separated from all other processes by the operating system software and hardware. The Module functions entirely within the process space of the calling application, and implicitly satisfies the FIPS 1402 requirement for a single user mode of operation. Page 21 of 29 Nimble Storage FIPS 1402 Security Policy ## 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 1402. Page 22 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix A Installation and Usage Guidance The test platforms represent different combinations of installation instructions. For each platform there is a build system, the host providing the build environment in which the installation instructions are executed, and a target system on which the generated object code is executed. The build and target systems may be the same type of system or even the same device, or may be different systems - the Module supports crosscompilation environments. Each of these command sets are relative to the top of the directory containing the uncompressed and expanded contents of the distribution files opensslfips2.0.9.tar.gz (all NIST defined curves as listed in Table 2 with the EC column marked "BKP") or opensslfipsecp2.0.9.tar.gz (NIST prime curves only as listed in Table 2 with the EC column marked "P"). The command sets are: U1: ./config no-asm make make install U2: ./config make make install W1: ms\\do_fips no-asm W2: ms\\do_fips ####### Installation instructions 1. Download and copy the distribution file to the build system. These files can be downloaded from http://www.openssl.org/source /. 2. Verify the HMACSHA1 digest of the distribution file; see Appendix B. An independently acquired FIPS 1402 validated implemention of SHA1 HMAC must be used for this digest verification. Note that this verification can be performed on any convenient system and not necessarily on the specific build or target system. Alternatively, a copy of the distribution on physical media can be obtained from OSF 6 . 3. Unpack the distribution 6 For some prospective users the acquisition, installation, and configuration of a suitable FIPS 1402 validated product may not be convenient. OSF will on request mail a CD containing the source code distribution, via USPS or international post. A distribution file received by that means need not be verified by a FIPS 1402 validated implementation of HMACSHA1. For instructions on requesting this CD see http://opensslfoundation.com/fips/verify.html. Page 23 of 29 Nimble Storage FIPS 1402 Security Policy ``` gunzip -c openssl-fips-2.0.9.tar.gz | tar xf cd openssl-fips-2.0.9 or gunzip -c openssl-fips-ecp-2.0.9.tar.gz | tar xf cd openssl-fips-ecp-2.0.9 ``` 4. Execute one of the installation command sets U1, W1, U2, W2 as shown above. No other command sets shall be used. 5. The resulting fipscanister.o or fipscanister.lib file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 7 function. Note that failure to use one of the specified commands sets exactly as shown will result in a module that cannot be considered compliant with FIPS 1402. ####### Linking the Runtime Executable Application Note that applications interfacing with the FIPS Object Module are outside of the cryptographic boundary. When linking the application with the FIPS Object Module two steps are necessary: 1. The HMACSHA1 digest of the FIPS Object Module file must be calculated and verified against the installed digest to ensure the integrity of the FIPS object module. 2. A HMACSHA1 digest of the FIPS Object Module must be generated and embedded in the FIPS Object Module for use by the FIPS_mode_set() 7 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the FIPS Object Module and to generate the new HMACSHA1 digest for the runtime executable application. Failure to embed the digest in the executable object will prevent initialization of FIPS mode. At runtime the FIPS_mode_set() 7 function compares the embedded HMACSHA1 digest with a digest generated from the FIPS Object Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. ###### Optimization The \'asm\' designation means that assembler language optimizations were enabled when the binary code was built, \'noasm\' means that only C language code was compiled. For OpenSSL with x86 there are three possible optimization levels: 1. No optimization (plain C) 2. SSE2 optimization 7 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 24 of 29 Nimble Storage FIPS 1402 Security Policy ### 3. AESNI+PCLMULQDQ+SSSE3 optimization Other theoretically possible combinations (e.g. AESNI only, or SSE3 only) are not addressed individually, so that a processor which does not support all three of AESNI, PCLMULQDQ, and SSSE3 will fall back to SSE2 optimization. For more information, see: - [ http://www.intel.com/support/processors/sb/CS030123.htm?wapkw=sse2](http://www.intel.com/support/processors/sb/CS-030123.htm?wapkw=sse2) - [ http://software.intel.com/enus/articles/inteladvancedencryptionstandardinstructions aesni/?wapkw=aesni](http://software.intel.com/en-us/articles/intel-advanced-encryption-standard-instructions-aes-ni/?wapkw=aes-ni) For OpenSSL with ARM there are two possible optimization levels: 1. Without NEON 2. With NEON (ARM7 only) [For more information, see http://www.arm.com/products/processors/technologies/neon.php](http://www.arm.com/products/processors/technologies/neon.php) Page 25 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix B Controlled Distribution File Fingerprint The OpenSSL FIPS Object Module v2.0.9 consists of the FIPS Object Module (the fipscanister.o or fipscanister.lib contiguous unit of binary object code) generated from the specific source files. For all NIST defined curves (listed in Table 2 with the EC column marked "BKP") the source files are in the specific special OpenSSL distribution opensslfips2.0.9.tar.gz with HMAC SHA1 digest of 54552e9a3ed8d1561341e8945fcdec55af961322 [located at http://www.openssl.org/source/opensslfips2.0.9.tar.gz.](http://www.openssl.org/source/openssl-fips-2.0.9.tar.gz) The openssl command from a version of OpenSSL that incorporates a previously validated version of the module may be used: openssl sha1 -hmac etaonrishdlcupfm openssl-fips-2.0.9.tar.gz For NIST prime curves only (listed in Table 2 with the EC column marked "P") the source files are in the specific special OpenSSL distribution opensslfipsecp2.0.9.tar.gz with HMACSHA1 digest of 91d267688713c920f85bc5e69c8b5d34e1112672 located at http://www.openssl.org/source/opensslfipsecp2.0.9.tar.gz. Note this is from the previous revision of the FIPS Object Module as no modifications relevant to NIST prime curves only were introduced in revision 2.0.9. The set of files specified in this tar file constitutes the complete set of source files of this module. There shall be no additions, deletions, or alterations of this set as used during module build. The OpenSSL distribution tar file (and patch file if used) shall be verified using the above HMAC SHA1 digest(s). The arbitrary 16 byte key of: 65 74 61 6f 6e 72 69 73 68 64 6c 63 75 70 66 6d (equivalent to the ASCII string " etaonrishdlcupfm ") is used to generate the HMACSHA1 value for the FIPS Object Module integrity check. The functionality of all earlier revisions of the FIPS Object Module are subsumed by this latest revision, so there is no reason to use older revisions for any new deployments. However, older revisions remain valid. The source distribution files and corresponding HMACSHA1 digests are listed below: opensslfips2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.8.tar.gz Page 26 of 29 ####### Nimble Storage FIPS 1402 Security Policy Digest: 7f486fbb598f3247ab9db10c1308f1c19f384671 opensslfipsecp2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.8.tar.gz Digest: 7a5f40ef8cebe959372d16e26391fcf23689209b opensslfips2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.7.tar.gz Digest: 295064925a6d95271e2fa2920181ec060f95c7ab opensslfipsecp2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.7.tar.gz Digest: dddfdc78c7e827c61fe92bd4817a7f2c3e67153 opensslfips2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.6.tar.gz Digest: 2b8d831df22d4dfe6169aa2a8e74c35484c26c21 opensslfipsecp2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.6.tar.gz Digest: 852f43cd9ae1bd2eba60e4f9f1f266d3c16c0319 opensslfips2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.5.tar.gz Digest: 8b44f2a43d098f6858eb1ebe77b73f8f027a9c29 opensslfipsecp2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.5.tar.gz Digest: 148e4e127ffef1df80c0ed61bae35b07ec7b7b36 opensslfips2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.4.tar.gz Digest: eaa5f86dab2c5da7086aec4786bce27d3b3c1b8a opensslfipsecp2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.4.tar.gz Digest: 13302f75c82c8b482c9ac96828984a270a45c284 opensslfips2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.3.tar.gz Digest: 5dfe03bc3f57c2862ea97823ea3111d7faf711b2 Page 27 of 29 ####### Nimble Storage FIPS 1402 Security Policy opensslfipsecp2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.3.tar.gz Digest: 9d6b21218d7d5480aa0add68e682d321e3ffbfa7 opensslfips2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.2.tar.gz Digest: e099d5096eb69c2dd8591379f38b985801188663 opensslfipsecp2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.2.tar.gz Digest: 887fa6802c253c32e6c4c83b7a091118fa8c6217 opensslfips2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.1.tar.gz. Digest: 1e05b021fdcd6e77c6155512bbce2d0cbc725aec opensslfipsecp2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.1.tar.gz. Digest: af82c8ebb9d3276be11feffd35e6b55bd0d1839f opensslfips2.0.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.tar.gz. Digest: 2cdd29913c6523df8ad38da11c342b80ed3f1dae opensslfipsecp2.0.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.tar.gz. Digest: e8d5ee306425b278bf6c8b077dae8e4a542e8215 Page 28 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix C Compilers This appendix lists the specific compilers used to generate the Module for the respective Operational Environments. Note this list does not imply that use of the Module is restricted to only the listed compiler versions, only that the use of other versions has not been confirmed to produce a correct result. Table C Compilers | # | Operational Environment | Compiler | |-----|---------------------------|------------| | 1 | Linux 2.6 | gcc 4.1.2 | | 2 | Linux 2.6 | gcc 4.1.2 | | 3 | Linux 2.6 | gcc 4.1.2 | | 4 | Linux 3.4 | gcc 4.8.0 | | 5 | Linux 2.6 | gcc 4.1.2 | | 6 | Linux 2.6 | gcc 4.1.2 | | 7 | Linux 2.6 | gcc 4.1.2 | | 8 | Linux 2.6 | gcc 4.1.2 | | 9 | Linux 4.4 | gcc 4.1.2 | | 10 | Linux 4.4 | gcc 4.1.2 | | 11 | Linux 4.4 | gcc 4.1.2 | | 12 | Linux 4.4 | gcc 4.1.2 | Page 29 of 29': 1}, '__delete__': ['AES 128/192/256 1202', 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8', 'platform #96, FreeBSD 8.4 on x86 without AESNI', 'platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG', 'platforms #90, #91', 'platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86', 'platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5', 'platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition', 'platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI', 'platforms #77, #78 iOS 6.0 with/without NEON']}}}} data.

  The computed heuristics were updated.

  • The policy_prunned_references property was updated, with the {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']} values added.
  • The policy_processed_references property was updated, with the {'directly_referencing': {'__add__': {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']}}, 'indirectly_referencing': {'__add__': {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']}}} data.
• 24.09.2026

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'AES 128/192/256 1202': 1, 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8': 1, 'platform #96, FreeBSD 8.4 on x86 without AESNI': 1, 'platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG': 1, 'platforms #90, #91': 1, 'platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86': 1, 'platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5': 1, 'platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition': 1, 'platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI': 1, 'platforms #77, #78 iOS 6.0 with/without NEON': 1}, '__delete__': ['platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8 | | 20140104 | Addition of new platform #96, FreeBSD 8.4 on x86 without AESNI | | 20140730 | Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG | | 20140728 | Changed processor names for platforms #90, #91 | | 20140711 | Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86 | | 20140612 | Temporarily remove misplaced platform, move Dual EC DRBG to the Non Approved Table 4c | | 20140529 | Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) | | 20140512 | Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition | | 20131108 | Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI | | 20131101 | Added two platforms #77, #78 iOS 6.0 with/without NEON | Page 4 of 29 ####### Nimble Storage FIPS 1402 Security Policy | 20130829 | Added new sponsor acknowledgment | |--------------|-----------------------------------------------------------------------------------------------------| | 20130814 | Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms | | 20130724 | Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 | | 20130609 | Added QNX, iOS 6.1, eCos for revision 2.0.5 | | 20130501 | Added OpenWRT 2.6 for revision 2.0.4 | | 20130301 | Added VMware Horizon Mobile 1.3, Apple OS X 10.7 , Apple iOS 5.0 | | 20130223 | Added WinEC7 and Android 4.0 for revision 2.0.3 | | 20130214 | Table 5: Removed references to nonexistent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM | | 20130128 | Added four platforms: Android 4.1 and Android 4.2 with and without NEON | | 20130108 | Reworded section 8 | | 20130103 | Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AESNI. | | 20121208 | Note EC DH Key Agreement and RSA Key Wrapping strength. | | 20121010 | Added NetBSD 5.1 on PowerPCe500, NetBSD 5.1 on Intel Xeon 5500 (x8664) for revision 2.0.2 | | 20110702 | Added DSP Media Framework, Linux 2.6/Freescale PowerPCe500, Android 4.0 | | 20110615 | Added iOS, WinCE 5, WinCE 6 OEs | ####### References | Reference | Full Specification Name | |--------------|---------------------------------------------------------------------------------------------------------| | [ANS X9.31] | Digital Signatures Using Reversible Public Key Cryptography for the Financial Services Industry (rDSA) | | [FIPS 1402] | Security Requirements for Cryptographic modules, May 25, 2001 | | [FIPS 1803] | Secure Hash Standard | | [FIPS 1864] | Digital Signature Standard | | [FIPS 197] | Advanced Encryption Standard | | [FIPS 1981] | The KeyedHash Message Authentication Code (HMAC) | | [SP 80038B] | Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication | | [SP 80038C] | Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality | Page 5 of 29 ####### Nimble Storage FIPS 1402 Security Policy | Reference | Full Specification Name | |----------------|---------------------------------------------------------------------------------------------------| | [SP 80038D] | Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC | | [SP 80056A] | Recommendation for PairWise Key Establishment Schemes Using Discrete Logarithm Cryptography | | [SP 800 67R1] | Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher | | [SP 80089] | Recommendation for Obtaining Assurances for Digital Signature Applications | | [SP 80090] | Recommendation for Random Number Generation Using Deterministic Random Bit Generators | | [SP 800 131A] | Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths | Page 6 of 29 Nimble Storage FIPS 1402 Security Policy ### Table of Contents | 1 Introduction.........................................................................................................................7 | |----------------------------------------------------------------------------------------------------------------------------------------------| | 2 Tested Configurations.........................................................................................................9 | | 3 Ports and Interfaces ............................................................................................................13 | | 4 Modes of Operation and Cryptographic Functionality ......................................................14 | | 4.1 Critical Security Parameters and Public Keys............................................................18 | | 5 Roles, Authentication and Services ...................................................................................21 | | 6 Selftest...............................................................................................................................23 | | 7 Operational Environment....................................................................................................25 | | 8 Mitigation of other Attacks.................................................................................................26 | | Appendix A Installation and Usage Guidance.......................................................................27 | | Appendix B Controlled Distribution File Fingerprint...........................................................30 | | Appendix C Compilers..........................................................................................................33 | Page 7 of 29 Nimble Storage FIPS 1402 Security Policy ## 1 Introduction This document is the nonproprietary security policy for the Nimble Storage FIPS Object Module, hereafter referred to as the Module, which is build from the OpenSSL FIPS Object Module source code according to the the instructions in Appendix A. The Module is a software library providing a Clanguage application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 1402 as a software module, multichip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the fipscanister object module, a single object module file named fipscanister.o compiled on Linux ®1 . The Module performs no communications other than with the calling application (the process that invokes the Module services). The FIPS 1402 security levels for the Module are as follows: | Security Requirement | Security Level | |-------------------------------------------|------------------| | Cryptographic Module Specification | 1 | | Cryptographic Module Ports and Interfaces | 1 | | Roles, Services, and Authentication | 2 | | Finite State Model | 1 | | Physical Security | NA | | Operational Environment | 1 | | Cryptographic Key Management | 1 | | EMI/EMC | 1 | | SelfTests | 1 | | Design Assurance | 3 | | Mitigation of Other Attacks | NA | Table 1 - Security Level of Security Requirements The Module\'s software version for this validation is 2.0.9. It is build from the 2.0.9 version of the OpenSSL FIPS Object Module source code. 1 Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Page 8 of 29 ####### Nimble Storage FIPS 1402 Security Policy Figure 1 Module Block Diagram Page 9 of 29 Nimble Storage FIPS 1402 Security Policy ## 2 Tested Configurations Table 2 Tested Configurations (B = Build Method; EC = Elliptic Curve Support). The EC column indicates support for prime curve only (P), or all NIST defined B, K, and P curves (BKP). | # | Operational Environment | Processor | Optimiz ations (Target) | EC | B | |-----|-----------------------------------------|---------------------------------|----------------------------|------|-----| | 1 | Linux 2.6 | Intel E52403V2 (x86_64) | AESNI | BKP | U2 | | 2 | Linux 2.6 | Intel E52450V2 (x86_64) | AESNI | BKP | U2 | | 3 | Linux 2.6 | Intel E52470V2 (x86_64) | AESNI | BKP | U2 | | 4 | Linux 3.4 64bit under Citrix XenServer | Intel Xeon E52430L (x86) | None | BKP | U2 | | 5 | Linux 2.6 | Intel E52603V3 (x86_64) | AESNI | BKP | U2 | | 6 | Linux 2.6 | Intel E52620V3 (x86_64) | AESNI | BKP | U2 | | 7 | Linux 2.6 | Intel E52680V3 (x86_64) | AESNI | BKP | U2 | | 8 | Linux 2.6 | Intel E52699V3 (x86_64) | AESNI | BKP | U2 | | 9 | Linux 4.4 | Intel E5504 (x86_64) | None | BKP | U2 | | 10 | Linux 4.4 | Intel E52403V2 (x86_64) | AESNI | BKP | U2 | | 11 | Linux 4.4 | Intel E52680V3 (x86_64) | AESNI | BKP | U2 | | 12 | Linux 4.4 | Intel Xeon Silver 4110 (x86_64) | AESNI | BKP | U2 | See Appendix A for additional information on build method and optimizations. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. Page 10 of 29 Nimble Storage FIPS 1402 Security Policy ## 3 Ports and Interfaces The physical ports of the Module are the same as the computer system on which it is executing. The logical interface is a Clanguage application program interface (API). Table 3 Logical interfaces | Logical interface type | Description | |--------------------------|-----------------------------------------------------------| | Control input | API entry point and corresponding stack parameters | | Data input | API entry point data input stack parameters | | Status output | API entry point return values and status stack parameters | | Data output | API entry point data output stack parameters | As a software module, control of the physical ports is outside module scope. However, when the module is performing selftests, or is in an error state, all output on the logical data output interface is inhibited. The module is singlethreaded and in error scenarios returns only an error value (no data output is returned). Page 11 of 29 Nimble Storage FIPS 1402 Security Policy ## 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 1402 Approved mode. Tables 4a and 4b list the Approved and Nonapproved but Allowed algorithms, respectively. | Function | Algorithm | Options | Cert # | |----------------------------------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------| | Random Number Generation; Symmetric key generation | [SP 80090A] DRBG 2 Prediction resistance supported for all variations | Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function | 342, 784 | | Encryption, Decryption and CMAC | [SP 80067] | 3Key TripleDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify | 1522, 1912 | | Encryption, Decryption and CMAC | [FIPS 197] AES | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 2484, 3351 | | Encryption, Decryption and CMAC | [SP 80038B] CMAC [SP 80038C] CCM [SP 80038D] GCM [SP 80038E] XTS | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 2484, 3351 | | Message Digests | [FIPS 1803] | SHA1, SHA2 (224, 256, 384, 512) | 2102, 2778 | | Keyed Hash | [FIPS 198] HMAC | SHA1, SHA2 (224, 256, 384, 512) | 1526, 2134 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] RSA | SigVer9.31 (1024/1536/2048/3072/4096 with SHA1/256/384/512) SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA 1/SHA2 sizes) | 1273, 1718 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] RSA | SigGen9.31 (2048/3072/4096 with SHA 256/384/512) SigGenPKCS1.5, SigGenPSS (2048/3072/4096 with all SHA2 sizes) | 1718 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA2 sizes) | 764, 950 | Page 12 of 29 Nimble Storage FIPS 1402 Security Policy Table 4a - FIPS Approved Cryptographic Functions | | [FIPS 1864] ECDSA | PKG: CURVES( P224 P256 P384 P521 K 224 K256 K384 K521 B224 B256 B384 B 521 ExtraRandomBits TestingCandidates ) PKV: CURVES( ALLP ALLK ALLB ) SigGen: CURVES( P224: (SHA224, 256, 384, 512) P256: (SHA224, 256, 384, 512) P384: (SHA224, 256, 384, 512) P521: (SHA224, 256, 384, 512) K233: (SHA224, 256, 384, 512) K283: (SHA224, 256, 384, 512) K409: (SHA224, 256, 384, 512) K571: (SHA224, 256, 384, 512) B233: (SHA224, 256, 384, 512) B283: (SHA224, 256, 384, 512) B409: (SHA 224, 256, 384, 512) B571: (SHA224, 256, 384, 512) ) SigVer: CURVES( P192: (SHA1, 224, 256, 384, 512) P224: (SHA1, 224, 256, 384, 512) P 256: (SHA1, 224, 256, 384, 512) P384: (SHA 1, 224, 256, 384, 512) P521: (SHA1, 224, 256, 384, 512) K163: (SHA1, 224, 256, 384, 512) K233: (SHA1, 224, 256, 384, 512) K283: (SHA1, 224, 256, 384, 512) K409: (SHA1, 224, 256, 384, 512) K571: (SHA1, 224, 256, 384, 512 B163: (SHA1, 224, 256, 384, 512) B 233: (SHA1, 224, 256, 384, 512) B283: (SHA 1, 224, 256, 384, 512) B409: (SHA1, 224, 256, 384, 512) B571: (SHA1, 224, 256, 384, 512) ) | 413, 664 | |---------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| | ECC CDH (CVL) | [SP 80056A] (§5.7.1.2) | All NIST defined B, K and P curves except sizes 163 and 192 | 85, 496 | The Module supports only NIST defined curves for use with ECDSA and ECC CDH. The Module supports two operational environment configurations for elliptic curve; NIST prime curve only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Table 4b - NonFIPS Approved But Allowed Cryptographic Functions | Category | Algorithm | Description | |----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC DH | Noncompliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. | | Key Encryption, Decryption | RSA | The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 80056B compliance, and no CSPs are established into or exported out of the module using these services. | Page 13 of 29 Nimble Storage FIPS 1402 Security Policy Table 4c - FIPS NonApproved Cryptographic Functions | Function | Algorithm | Options | Cert # | |----------------------------------------------------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| | Random Number Generation; Symmetric key generation | [ANS X9.31] RNG | AES 128/192/256 | 1202, 1363 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] RSA | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/4096 with SHA1) | 1273 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) | 764 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) | 764 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] ECDSA | PKG: CURVES( P192 K163 B163 ) SIG(gen): CURVES( P192 P224 P256 P384 P521 K163 K233 K283 K409 K571 B163 B233 B283 B409 B571 ) | 413 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] ECDSA | PKG: CURVES( P192 K163 B163 ) SigGen: CURVES( P192: (SHA1, 224, 256, 384, 512) P224:(SHA1) P256:(SHA1) P384: (SHA1) P521:(SHA1) K163: (SHA1, 224, 256, 384, 512) K233:(SHA1) K283:(SHA1) K409:(SHA1) K571:(SHA1) B163: (SHA1, 224, 256, 384, 512) B233:(SHA1) B283: (SHA1) B409:(SHA1) B571:(SHA1) ) | 413 | | ECC CDH (CVL) | [SP 80056A] (§5.7.1.2) | All NIST Recommended B, K and P curves sizes 163 and 192 | 85 | These algorithms shall not be used when operating in the FIPS Approved mode of operation. EC DH Key Agreement provides a maximum of 256 bits of security strength. RSA Key Wrapping provides a maximum of 256 bits of security strength. The Module requires an initialization sequence (see IG 9.5): the calling application invokes FIPS_mode_set() 3 , which returns a \'1\' for success and \'0\' for failure. If FIPS_mode_set() fails then all cryptographic services fail from then on. The application can test to see if FIPS mode has been successfully performed. The Module is a cryptographic engine library, which can be used only in conjunction with additional software. Aside from the use of the NIST defined elliptic curves as trusted third party domain parameters, all other FIPS 1864 assurances are outside the scope of the Module, and are the responsibility of the calling process. 3 The function call in the Module is FIPS_module_mode_set() which is typically used by an application via the FIPS_mode_set() wrapper function. Page 14 of 29 Nimble Storage FIPS 1402 Security Policy ### 4.1 Critical Security Parameters and Public Keys All CSPs used by the Module are described in this section. All access to these CSPs by Module services are described in Section 4. The CSP names are generic, corresponding to API parameter data structures. Table 4.1a - Critical Security Parameters | CSP Name | Description | |-----------------|------------------------------------------------------------------------------------------------------------------------| | RSA SGK | RSA (1024 to 16384 bits) signature generation key | | RSA KDK | RSA (1024 to 16384 bits) key decryption (private key transport) key | | DSA SGK | [FIPS 1864] DSA (1024/2048/3072) signature generation key | | ECDSA SGK | ECDSA (All NIST defined B, K, and P curves) signature generation key | | EC DH Private | EC DH (All NIST defined B, K, and P curves) private key agreement key. | | AES EDK | AES (128/192/256) encrypt / decrypt key | | AES CMAC | AES (128/192/256) CMAC generate / verify key | | AES GCM | AES (128/192/256) encrypt / decrypt / generate / verify key | | AES XTS | AES (256/512) XTS encrypt / decrypt key | | TripleDES EDK | TripleDES (3Key) encrypt / decrypt key | | TripleDES CMAC | TripleDES (3Key) CMAC generate / verify key | | HMAC Key | Keyed hash key (160/224/256/384/512) | | Hash_DRBG CSPs | V (440/888 bits) and C (440/888 bits), entropy input (length dependent on security strength) | | HMAC_DRBG CSPs | V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits), entropy input (length dependent on security strength) | | CTR_DRBG CSPs | V (128 bits) and Key (AES 128/192/256), entropy input (length dependent on security strength) | | COADDigest | Precalculated HMACSHA1 digest used for Crypto Officer role authentication | | UserADDigest | Precalculated HMACSHA1 digest used for User role authentication | Authentication data is loaded into the module during the module build process, performed by an authorized operator (Crypto Officer), and otherwise cannot be accessed. The module does not output intermediate key generation values. | CSP Name | Description | |--------------|--------------------------------------------------------------------------------------------------------------------| | RSA SVK | RSA (1024 to 16384 bits) signature verification public key | | RSA KEK | RSA (1024 to 16384 bits) key encryption (public key transport) key | | DSA SVK | [FIPS 1864] DSA (1024/2048/3072) signature verification key or [FIPS 1862] DSA (1024) signature verification key | | ECDSA SVK | ECDSA (All NIST defined B, K and P curves) signature verification key | | EC DH Public | EC DH (All NIST defined B, K and P curves) public key agreement key. | Page 15 of 29 Nimble Storage FIPS 1402 Security Policy ###### For all CSPs and Public Keys: Storage : RAM, associated to entities by memory location. The Module stores DRBG state values for the lifetime of the DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of DRBG state values used for the Modules\' default key generation service. Generation : The Module implements SP 80090 compliant DRBG services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry : All CSPs enter the Module\'s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output : The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Destruction : Zeroization of sensitive data is performed automatically by API function calls for temporarily stored CSPs. In addition, the module provides functions to explicitly destroy CSPs related to random number generation services. The calling application is responsible for parameters passed in and out of the module. Private and secret keys as well as seeds and entropy input are provided to the Module by the calling application, and are destroyed when released by the appropriate API function calls. Keys residing in internally allocated data structures (during the lifetime of an API call) can only be accessed using the Module defined API. The operating system protects memory and process space from unauthorized access. Only the calling application that creates or imports keys can use or export such keys. All API functions are executed by the invoking calling application in a nonoverlapping sequence such that no two API functions will execute concurrently. An authorized application as user (CryptoOfficer and User) has access to all key data generated during the operation of the Module. In the event Module power is lost and restored the calling application must ensure that any AESGCM keys used for encryption or decryption are redistributed. Module users (the calling applications) shall use entropy sources that meet the security strength required for the random number generation mechanism: 128 bits as shown in [SP 80090] Table 2 (Hash_DRBG, HMAC_DRBG), and Table 3 (CTR_DRBG). This entropy is supplied by means of callback functions. Those functions must return an error if the minimum entropy strength cannot be met. Table 4.1b - Public Keys Page 16 of 29 Nimble Storage FIPS 1402 Security Policy ## 5 Roles, Authentication and Services The Module implements the required User and Crypto Officer roles and requires authentication for those roles. Only one role may be active at a time and the Module does not allow concurrent operators. The User or Crypto Officer role is assumed by passing the appropriate password to the FIPS_module_mode_set() function. The password values may be specified at build time and must have a minimum length of 16 characters. Any attempt to authenticate with an invalid password will result in an immediate and permanent failure condition rendering the Module unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the Module during the Module build process, performed by the Crypto Officer, and otherwise cannot be accessed. Since minimum password length is 16 characters, the probability of a random successful authentication attempt in one try is a maximum of 1/256 16 , or less than 1/10 38 . The Module permanently disables further authentication attempts after a single failure, so this probability is independent of time. Both roles have access to all of the services provided by the Module. - User Role (User): Loading the Module and calling any of the API functions. - Crypto Officer Role (CO): Installation of the Module on the host computer system and calling of any API functions. All services implemented by the Module are listed below, along with a description of service CSP access. | Service | Role | Description | |--------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Initialize | User, CO | Module initialization. Does not access CSPs. | | Selftest | User, CO | Perform self tests (FIPS_selftest). Does not access CSPs. | | Show status | User, CO | Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. | | Zeroize | User, CO | Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. | | Random number generation | User, CO | Used for random number and symmetric key generation. Seed or reseed an DRBG instance Determine security strength of a DRBG instance | Page 17 of 29 Nimble Storage FIPS 1402 Security Policy | Service | Role | Description | |---------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. | | Asymmetric key generation | User, CO | Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP80090 | | Symmetric encrypt/decrypt | User, CO | Used to encrypt or decrypt data. Executes using AES EDK, TripleDES EDK (passed in by the calling process). | | Symmetric digest | User, CO | Used to generate or verify data integrity with CMAC. Executes using AES CMAC, TripleDES, CMAC (passed in by the calling process). | | Message digest | User, CO | Used to generate a SHA1 or SHA2 message digest. Does not access CSPs. | | Keyed Hash | User, CO | Used to generate or verify data integrity with HMAC. Executes using HMAC Key (passed in by the calling process). | | Key transport 4 | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | | Key agreement | User, CO | Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). | | Digital signature | User, CO | Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). | | Utility | User, CO | Miscellaneous helper functions. Does not access CSPs. | ## 6 Selftest The Module performs the selftests listed below on invocation of Initialize or Selftest. | Algorithm | Type | Test Attributes | |--------------------|--------|------------------------------------------------------------------------------------------------------------| | Software integrity | KAT | HMACSHA1 | | HMAC | KAT | One KAT per SHA1, SHA224, SHA256, SHA384 and SHA512 Per IG 9.3, this testing covers SHA POST requirements. | | AES | KAT | Separate encrypt and decrypt, ECB mode, 128 bit key length | | AES CCM | KAT | Separate encrypt and decrypt, 192 key length | Table 5 Services and CSP Access Page 18 of 29 Nimble Storage FIPS 1402 Security Policy Table 6a Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency test) | Algorithm | Type | Test Attributes | |-----------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | AES GCM | KAT | Separate encrypt and decrypt, 256 key length | | XTSAES | KAT | 128, 256 bit key sizes to support either the 256bit key size (for XTSAES128) or the 512bit key size (for XTSAES256) | | AES CMAC | KAT | Sign and verify CBC mode, 128, 192, 256 key lengths | | TripleDES | KAT | Separate encrypt and decrypt, ECB mode, 3Key | | TripleDES CMAC | KAT | CMAC generate and verify, CBC mode, 3Key | | RSA | KAT | Sign and verify using 2048 bit key, SHA256, PKCS#1 | | DSA | PCT | Sign and verify using 2048 bit key, SHA384 | | DRBG | KAT | CTR_DRBG: AES, 256 bit with and without derivation function HASH_DRBG: SHA256 HMAC_DRBG: SHA256 | | ECDSA | PCT | Keygen, sign, verify using P224, K233 and SHA512. The K233 selftest is not performed for operational environments that support prime curve only (see Table 2). | | ECC CDH | KAT | Shared secret calculation per SP 80056A §5.7.1.2, IG 9.6 | The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMACSHA1 of the Module distribution file as tested by the CMT Laboratory and listed in Appendix A is verified during installation of the Module file as described in Appendix A. The FIPS_mode_set() 5 function performs all powerup selftests listed above with no operator intervention required, returning a \'1\' if all powerup selftests succeed, and a \'0\' otherwise. If any component of the powerup selftest fails an internal flag is set to prevent subsequent invocation of any cryptographic function calls. The module will only enter the FIPS Approved mode if the module is reloaded and the call to FIPS_mode_set() 5 succeeds. The powerup selftests may also be performed ondemand by calling FIPS_selftest() , which returns a \'1\' for success and \'0\' for failure. Interpretation of this return code is the responsibility of the calling application. The Module also implements the following conditional tests: | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Tested as required by [SP80090] Section 11 | | DRBG | FIPS 1402 continuous test for stuck fault | | DSA | Pairwise consistency test on each generation of a key pair | | ECDSA | Pairwise consistency test on each generation of a key pair | Page 19 of 29 ####### Nimble Storage FIPS 1402 Security Policy Table 6b Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | RSA | Pairwise consistency test on each generation of a key pair | In the event of a DRBG selftest failure the calling application must uninstantiate and re instantiate the DRBG per the requirements of [SP 80090]; this is not something the Module can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. The Module supports two operational environment configurations for elliptic curve: NIST prime curves only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Page 20 of 29 Nimble Storage FIPS 1402 Security Policy ## 7 Operational Environment The tested operating systems segregate user processes into separate process spaces. Each process space is logically separated from all other processes by the operating system software and hardware. The Module functions entirely within the process space of the calling application, and implicitly satisfies the FIPS 1402 requirement for a single user mode of operation. Page 21 of 29 Nimble Storage FIPS 1402 Security Policy ## 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 1402. Page 22 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix A Installation and Usage Guidance The test platforms represent different combinations of installation instructions. For each platform there is a build system, the host providing the build environment in which the installation instructions are executed, and a target system on which the generated object code is executed. The build and target systems may be the same type of system or even the same device, or may be different systems - the Module supports crosscompilation environments. Each of these command sets are relative to the top of the directory containing the uncompressed and expanded contents of the distribution files opensslfips2.0.9.tar.gz (all NIST defined curves as listed in Table 2 with the EC column marked "BKP") or opensslfipsecp2.0.9.tar.gz (NIST prime curves only as listed in Table 2 with the EC column marked "P"). The command sets are: U1: ./config no-asm make make install U2: ./config make make install W1: ms\\do_fips no-asm W2: ms\\do_fips ####### Installation instructions 1. Download and copy the distribution file to the build system. These files can be downloaded from http://www.openssl.org/source /. 2. Verify the HMACSHA1 digest of the distribution file; see Appendix B. An independently acquired FIPS 1402 validated implemention of SHA1 HMAC must be used for this digest verification. Note that this verification can be performed on any convenient system and not necessarily on the specific build or target system. Alternatively, a copy of the distribution on physical media can be obtained from OSF 6 . 3. Unpack the distribution 6 For some prospective users the acquisition, installation, and configuration of a suitable FIPS 1402 validated product may not be convenient. OSF will on request mail a CD containing the source code distribution, via USPS or international post. A distribution file received by that means need not be verified by a FIPS 1402 validated implementation of HMACSHA1. For instructions on requesting this CD see http://opensslfoundation.com/fips/verify.html. Page 23 of 29 Nimble Storage FIPS 1402 Security Policy ``` gunzip -c openssl-fips-2.0.9.tar.gz | tar xf cd openssl-fips-2.0.9 or gunzip -c openssl-fips-ecp-2.0.9.tar.gz | tar xf cd openssl-fips-ecp-2.0.9 ``` 4. Execute one of the installation command sets U1, W1, U2, W2 as shown above. No other command sets shall be used. 5. The resulting fipscanister.o or fipscanister.lib file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 7 function. Note that failure to use one of the specified commands sets exactly as shown will result in a module that cannot be considered compliant with FIPS 1402. ####### Linking the Runtime Executable Application Note that applications interfacing with the FIPS Object Module are outside of the cryptographic boundary. When linking the application with the FIPS Object Module two steps are necessary: 1. The HMACSHA1 digest of the FIPS Object Module file must be calculated and verified against the installed digest to ensure the integrity of the FIPS object module. 2. A HMACSHA1 digest of the FIPS Object Module must be generated and embedded in the FIPS Object Module for use by the FIPS_mode_set() 7 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the FIPS Object Module and to generate the new HMACSHA1 digest for the runtime executable application. Failure to embed the digest in the executable object will prevent initialization of FIPS mode. At runtime the FIPS_mode_set() 7 function compares the embedded HMACSHA1 digest with a digest generated from the FIPS Object Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. ###### Optimization The \'asm\' designation means that assembler language optimizations were enabled when the binary code was built, \'noasm\' means that only C language code was compiled. For OpenSSL with x86 there are three possible optimization levels: 1. No optimization (plain C) 2. SSE2 optimization 7 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 24 of 29 Nimble Storage FIPS 1402 Security Policy ### 3. AESNI+PCLMULQDQ+SSSE3 optimization Other theoretically possible combinations (e.g. AESNI only, or SSE3 only) are not addressed individually, so that a processor which does not support all three of AESNI, PCLMULQDQ, and SSSE3 will fall back to SSE2 optimization. For more information, see: - [ http://www.intel.com/support/processors/sb/CS030123.htm?wapkw=sse2](http://www.intel.com/support/processors/sb/CS-030123.htm?wapkw=sse2) - [ http://software.intel.com/enus/articles/inteladvancedencryptionstandardinstructions aesni/?wapkw=aesni](http://software.intel.com/en-us/articles/intel-advanced-encryption-standard-instructions-aes-ni/?wapkw=aes-ni) For OpenSSL with ARM there are two possible optimization levels: 1. Without NEON 2. With NEON (ARM7 only) [For more information, see http://www.arm.com/products/processors/technologies/neon.php](http://www.arm.com/products/processors/technologies/neon.php) Page 25 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix B Controlled Distribution File Fingerprint The OpenSSL FIPS Object Module v2.0.9 consists of the FIPS Object Module (the fipscanister.o or fipscanister.lib contiguous unit of binary object code) generated from the specific source files. For all NIST defined curves (listed in Table 2 with the EC column marked "BKP") the source files are in the specific special OpenSSL distribution opensslfips2.0.9.tar.gz with HMAC SHA1 digest of 54552e9a3ed8d1561341e8945fcdec55af961322 [located at http://www.openssl.org/source/opensslfips2.0.9.tar.gz.](http://www.openssl.org/source/openssl-fips-2.0.9.tar.gz) The openssl command from a version of OpenSSL that incorporates a previously validated version of the module may be used: openssl sha1 -hmac etaonrishdlcupfm openssl-fips-2.0.9.tar.gz For NIST prime curves only (listed in Table 2 with the EC column marked "P") the source files are in the specific special OpenSSL distribution opensslfipsecp2.0.9.tar.gz with HMACSHA1 digest of 91d267688713c920f85bc5e69c8b5d34e1112672 located at http://www.openssl.org/source/opensslfipsecp2.0.9.tar.gz. Note this is from the previous revision of the FIPS Object Module as no modifications relevant to NIST prime curves only were introduced in revision 2.0.9. The set of files specified in this tar file constitutes the complete set of source files of this module. There shall be no additions, deletions, or alterations of this set as used during module build. The OpenSSL distribution tar file (and patch file if used) shall be verified using the above HMAC SHA1 digest(s). The arbitrary 16 byte key of: 65 74 61 6f 6e 72 69 73 68 64 6c 63 75 70 66 6d (equivalent to the ASCII string " etaonrishdlcupfm ") is used to generate the HMACSHA1 value for the FIPS Object Module integrity check. The functionality of all earlier revisions of the FIPS Object Module are subsumed by this latest revision, so there is no reason to use older revisions for any new deployments. However, older revisions remain valid. The source distribution files and corresponding HMACSHA1 digests are listed below: opensslfips2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.8.tar.gz Page 26 of 29 ####### Nimble Storage FIPS 1402 Security Policy Digest: 7f486fbb598f3247ab9db10c1308f1c19f384671 opensslfipsecp2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.8.tar.gz Digest: 7a5f40ef8cebe959372d16e26391fcf23689209b opensslfips2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.7.tar.gz Digest: 295064925a6d95271e2fa2920181ec060f95c7ab opensslfipsecp2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.7.tar.gz Digest: dddfdc78c7e827c61fe92bd4817a7f2c3e67153 opensslfips2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.6.tar.gz Digest: 2b8d831df22d4dfe6169aa2a8e74c35484c26c21 opensslfipsecp2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.6.tar.gz Digest: 852f43cd9ae1bd2eba60e4f9f1f266d3c16c0319 opensslfips2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.5.tar.gz Digest: 8b44f2a43d098f6858eb1ebe77b73f8f027a9c29 opensslfipsecp2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.5.tar.gz Digest: 148e4e127ffef1df80c0ed61bae35b07ec7b7b36 opensslfips2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.4.tar.gz Digest: eaa5f86dab2c5da7086aec4786bce27d3b3c1b8a opensslfipsecp2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.4.tar.gz Digest: 13302f75c82c8b482c9ac96828984a270a45c284 opensslfips2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.3.tar.gz Digest: 5dfe03bc3f57c2862ea97823ea3111d7faf711b2 Page 27 of 29 ####### Nimble Storage FIPS 1402 Security Policy opensslfipsecp2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.3.tar.gz Digest: 9d6b21218d7d5480aa0add68e682d321e3ffbfa7 opensslfips2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.2.tar.gz Digest: e099d5096eb69c2dd8591379f38b985801188663 opensslfipsecp2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.2.tar.gz Digest: 887fa6802c253c32e6c4c83b7a091118fa8c6217 opensslfips2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.1.tar.gz. Digest: 1e05b021fdcd6e77c6155512bbce2d0cbc725aec opensslfipsecp2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.1.tar.gz. Digest: af82c8ebb9d3276be11feffd35e6b55bd0d1839f opensslfips2.0.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.tar.gz. Digest: 2cdd29913c6523df8ad38da11c342b80ed3f1dae opensslfipsecp2.0.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.tar.gz. Digest: e8d5ee306425b278bf6c8b077dae8e4a542e8215 Page 28 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix C Compilers This appendix lists the specific compilers used to generate the Module for the respective Operational Environments. Note this list does not imply that use of the Module is restricted to only the listed compiler versions, only that the use of other versions has not been confirmed to produce a correct result. Table C Compilers | # | Operational Environment | Compiler | |-----|---------------------------|------------| | 1 | Linux 2.6 | gcc 4.1.2 | | 2 | Linux 2.6 | gcc 4.1.2 | | 3 | Linux 2.6 | gcc 4.1.2 | | 4 | Linux 3.4 | gcc 4.8.0 | | 5 | Linux 2.6 | gcc 4.1.2 | | 6 | Linux 2.6 | gcc 4.1.2 | | 7 | Linux 2.6 | gcc 4.1.2 | | 8 | Linux 2.6 | gcc 4.1.2 | | 9 | Linux 4.4 | gcc 4.1.2 | | 10 | Linux 4.4 | gcc 4.1.2 | | 11 | Linux 4.4 | gcc 4.1.2 | | 12 | Linux 4.4 | gcc 4.1.2 | Page 29 of 29']}}}} data.
  • The br1_deviations property was set to 45.

  The computed heuristics were updated.

  • The policy_prunned_references property was updated, with the {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']} values discarded.
  • The policy_processed_references property was updated, with the {'directly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']}}, 'indirectly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']}}} data.
• 23.09.2026

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The following values were inserted: {'is_br1_format': False, 'br1_deviations': 0, 'br1_tables': None}.
  • The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8 | | 20140104 | Addition of new platform #96, FreeBSD 8.4 on x86 without AESNI | | 20140730 | Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG | | 20140728 | Changed processor names for platforms #90, #91 | | 20140711 | Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86 | | 20140612 | Temporarily remove misplaced platform, move Dual EC DRBG to the Non Approved Table 4c | | 20140529 | Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) | | 20140512 | Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition | | 20131108 | Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI | | 20131101 | Added two platforms #77, #78 iOS 6.0 with/without NEON | Page 4 of 29 ####### Nimble Storage FIPS 1402 Security Policy | 20130829 | Added new sponsor acknowledgment | |--------------|-----------------------------------------------------------------------------------------------------| | 20130814 | Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms | | 20130724 | Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 | | 20130609 | Added QNX, iOS 6.1, eCos for revision 2.0.5 | | 20130501 | Added OpenWRT 2.6 for revision 2.0.4 | | 20130301 | Added VMware Horizon Mobile 1.3, Apple OS X 10.7 , Apple iOS 5.0 | | 20130223 | Added WinEC7 and Android 4.0 for revision 2.0.3 | | 20130214 | Table 5: Removed references to nonexistent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM | | 20130128 | Added four platforms: Android 4.1 and Android 4.2 with and without NEON | | 20130108 | Reworded section 8 | | 20130103 | Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AESNI. | | 20121208 | Note EC DH Key Agreement and RSA Key Wrapping strength. | | 20121010 | Added NetBSD 5.1 on PowerPCe500, NetBSD 5.1 on Intel Xeon 5500 (x8664) for revision 2.0.2 | | 20110702 | Added DSP Media Framework, Linux 2.6/Freescale PowerPCe500, Android 4.0 | | 20110615 | Added iOS, WinCE 5, WinCE 6 OEs | ####### References | Reference | Full Specification Name | |--------------|---------------------------------------------------------------------------------------------------------| | [ANS X9.31] | Digital Signatures Using Reversible Public Key Cryptography for the Financial Services Industry (rDSA) | | [FIPS 1402] | Security Requirements for Cryptographic modules, May 25, 2001 | | [FIPS 1803] | Secure Hash Standard | | [FIPS 1864] | Digital Signature Standard | | [FIPS 197] | Advanced Encryption Standard | | [FIPS 1981] | The KeyedHash Message Authentication Code (HMAC) | | [SP 80038B] | Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication | | [SP 80038C] | Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality | Page 5 of 29 ####### Nimble Storage FIPS 1402 Security Policy | Reference | Full Specification Name | |----------------|---------------------------------------------------------------------------------------------------| | [SP 80038D] | Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC | | [SP 80056A] | Recommendation for PairWise Key Establishment Schemes Using Discrete Logarithm Cryptography | | [SP 800 67R1] | Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher | | [SP 80089] | Recommendation for Obtaining Assurances for Digital Signature Applications | | [SP 80090] | Recommendation for Random Number Generation Using Deterministic Random Bit Generators | | [SP 800 131A] | Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths | Page 6 of 29 Nimble Storage FIPS 1402 Security Policy ### Table of Contents | 1 Introduction.........................................................................................................................7 | |----------------------------------------------------------------------------------------------------------------------------------------------| | 2 Tested Configurations.........................................................................................................9 | | 3 Ports and Interfaces ............................................................................................................13 | | 4 Modes of Operation and Cryptographic Functionality ......................................................14 | | 4.1 Critical Security Parameters and Public Keys............................................................18 | | 5 Roles, Authentication and Services ...................................................................................21 | | 6 Selftest...............................................................................................................................23 | | 7 Operational Environment....................................................................................................25 | | 8 Mitigation of other Attacks.................................................................................................26 | | Appendix A Installation and Usage Guidance.......................................................................27 | | Appendix B Controlled Distribution File Fingerprint...........................................................30 | | Appendix C Compilers..........................................................................................................33 | Page 7 of 29 Nimble Storage FIPS 1402 Security Policy ## 1 Introduction This document is the nonproprietary security policy for the Nimble Storage FIPS Object Module, hereafter referred to as the Module, which is build from the OpenSSL FIPS Object Module source code according to the the instructions in Appendix A. The Module is a software library providing a Clanguage application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 1402 as a software module, multichip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the fipscanister object module, a single object module file named fipscanister.o compiled on Linux ®1 . The Module performs no communications other than with the calling application (the process that invokes the Module services). The FIPS 1402 security levels for the Module are as follows: | Security Requirement | Security Level | |-------------------------------------------|------------------| | Cryptographic Module Specification | 1 | | Cryptographic Module Ports and Interfaces | 1 | | Roles, Services, and Authentication | 2 | | Finite State Model | 1 | | Physical Security | NA | | Operational Environment | 1 | | Cryptographic Key Management | 1 | | EMI/EMC | 1 | | SelfTests | 1 | | Design Assurance | 3 | | Mitigation of Other Attacks | NA | Table 1 - Security Level of Security Requirements The Module\'s software version for this validation is 2.0.9. It is build from the 2.0.9 version of the OpenSSL FIPS Object Module source code. 1 Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Page 8 of 29 ####### Nimble Storage FIPS 1402 Security Policy Figure 1 Module Block Diagram Page 9 of 29 Nimble Storage FIPS 1402 Security Policy ## 2 Tested Configurations Table 2 Tested Configurations (B = Build Method; EC = Elliptic Curve Support). The EC column indicates support for prime curve only (P), or all NIST defined B, K, and P curves (BKP). | # | Operational Environment | Processor | Optimiz ations (Target) | EC | B | |-----|-----------------------------------------|---------------------------------|----------------------------|------|-----| | 1 | Linux 2.6 | Intel E52403V2 (x86_64) | AESNI | BKP | U2 | | 2 | Linux 2.6 | Intel E52450V2 (x86_64) | AESNI | BKP | U2 | | 3 | Linux 2.6 | Intel E52470V2 (x86_64) | AESNI | BKP | U2 | | 4 | Linux 3.4 64bit under Citrix XenServer | Intel Xeon E52430L (x86) | None | BKP | U2 | | 5 | Linux 2.6 | Intel E52603V3 (x86_64) | AESNI | BKP | U2 | | 6 | Linux 2.6 | Intel E52620V3 (x86_64) | AESNI | BKP | U2 | | 7 | Linux 2.6 | Intel E52680V3 (x86_64) | AESNI | BKP | U2 | | 8 | Linux 2.6 | Intel E52699V3 (x86_64) | AESNI | BKP | U2 | | 9 | Linux 4.4 | Intel E5504 (x86_64) | None | BKP | U2 | | 10 | Linux 4.4 | Intel E52403V2 (x86_64) | AESNI | BKP | U2 | | 11 | Linux 4.4 | Intel E52680V3 (x86_64) | AESNI | BKP | U2 | | 12 | Linux 4.4 | Intel Xeon Silver 4110 (x86_64) | AESNI | BKP | U2 | See Appendix A for additional information on build method and optimizations. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. Page 10 of 29 Nimble Storage FIPS 1402 Security Policy ## 3 Ports and Interfaces The physical ports of the Module are the same as the computer system on which it is executing. The logical interface is a Clanguage application program interface (API). Table 3 Logical interfaces | Logical interface type | Description | |--------------------------|-----------------------------------------------------------| | Control input | API entry point and corresponding stack parameters | | Data input | API entry point data input stack parameters | | Status output | API entry point return values and status stack parameters | | Data output | API entry point data output stack parameters | As a software module, control of the physical ports is outside module scope. However, when the module is performing selftests, or is in an error state, all output on the logical data output interface is inhibited. The module is singlethreaded and in error scenarios returns only an error value (no data output is returned). Page 11 of 29 Nimble Storage FIPS 1402 Security Policy ## 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 1402 Approved mode. Tables 4a and 4b list the Approved and Nonapproved but Allowed algorithms, respectively. | Function | Algorithm | Options | Cert # | |----------------------------------------------------|------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|------------| | Random Number Generation; Symmetric key generation | [SP 80090A] DRBG 2 Prediction resistance supported for all variations | Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function | 342, 784 | | Encryption, Decryption and CMAC | [SP 80067] | 3Key TripleDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify | 1522, 1912 | | Encryption, Decryption and CMAC | [FIPS 197] AES | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 2484, 3351 | | Encryption, Decryption and CMAC | [SP 80038B] CMAC [SP 80038C] CCM [SP 80038D] GCM [SP 80038E] XTS | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 2484, 3351 | | Message Digests | [FIPS 1803] | SHA1, SHA2 (224, 256, 384, 512) | 2102, 2778 | | Keyed Hash | [FIPS 198] HMAC | SHA1, SHA2 (224, 256, 384, 512) | 1526, 2134 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] RSA | SigVer9.31 (1024/1536/2048/3072/4096 with SHA1/256/384/512) SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA 1/SHA2 sizes) | 1273, 1718 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] RSA | SigGen9.31 (2048/3072/4096 with SHA 256/384/512) SigGenPKCS1.5, SigGenPSS (2048/3072/4096 with all SHA2 sizes) | 1718 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA2 sizes) | 764, 950 | Page 12 of 29 Nimble Storage FIPS 1402 Security Policy Table 4a - FIPS Approved Cryptographic Functions | | [FIPS 1864] ECDSA | PKG: CURVES( P224 P256 P384 P521 K 224 K256 K384 K521 B224 B256 B384 B 521 ExtraRandomBits TestingCandidates ) PKV: CURVES( ALLP ALLK ALLB ) SigGen: CURVES( P224: (SHA224, 256, 384, 512) P256: (SHA224, 256, 384, 512) P384: (SHA224, 256, 384, 512) P521: (SHA224, 256, 384, 512) K233: (SHA224, 256, 384, 512) K283: (SHA224, 256, 384, 512) K409: (SHA224, 256, 384, 512) K571: (SHA224, 256, 384, 512) B233: (SHA224, 256, 384, 512) B283: (SHA224, 256, 384, 512) B409: (SHA 224, 256, 384, 512) B571: (SHA224, 256, 384, 512) ) SigVer: CURVES( P192: (SHA1, 224, 256, 384, 512) P224: (SHA1, 224, 256, 384, 512) P 256: (SHA1, 224, 256, 384, 512) P384: (SHA 1, 224, 256, 384, 512) P521: (SHA1, 224, 256, 384, 512) K163: (SHA1, 224, 256, 384, 512) K233: (SHA1, 224, 256, 384, 512) K283: (SHA1, 224, 256, 384, 512) K409: (SHA1, 224, 256, 384, 512) K571: (SHA1, 224, 256, 384, 512 B163: (SHA1, 224, 256, 384, 512) B 233: (SHA1, 224, 256, 384, 512) B283: (SHA 1, 224, 256, 384, 512) B409: (SHA1, 224, 256, 384, 512) B571: (SHA1, 224, 256, 384, 512) ) | 413, 664 | |---------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| | ECC CDH (CVL) | [SP 80056A] (§5.7.1.2) | All NIST defined B, K and P curves except sizes 163 and 192 | 85, 496 | The Module supports only NIST defined curves for use with ECDSA and ECC CDH. The Module supports two operational environment configurations for elliptic curve; NIST prime curve only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Table 4b - NonFIPS Approved But Allowed Cryptographic Functions | Category | Algorithm | Description | |----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC DH | Noncompliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. | | Key Encryption, Decryption | RSA | The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 80056B compliance, and no CSPs are established into or exported out of the module using these services. | Page 13 of 29 Nimble Storage FIPS 1402 Security Policy Table 4c - FIPS NonApproved Cryptographic Functions | Function | Algorithm | Options | Cert # | |----------------------------------------------------|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------| | Random Number Generation; Symmetric key generation | [ANS X9.31] RNG | AES 128/192/256 | 1202, 1363 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] RSA | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/4096 with SHA1) | 1273 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) | 764 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) | 764 | | Digital Signature and Asymmetric Key Generation | [FIPS 1862] ECDSA | PKG: CURVES( P192 K163 B163 ) SIG(gen): CURVES( P192 P224 P256 P384 P521 K163 K233 K283 K409 K571 B163 B233 B283 B409 B571 ) | 413 | | Digital Signature and Asymmetric Key Generation | [FIPS 1864] ECDSA | PKG: CURVES( P192 K163 B163 ) SigGen: CURVES( P192: (SHA1, 224, 256, 384, 512) P224:(SHA1) P256:(SHA1) P384: (SHA1) P521:(SHA1) K163: (SHA1, 224, 256, 384, 512) K233:(SHA1) K283:(SHA1) K409:(SHA1) K571:(SHA1) B163: (SHA1, 224, 256, 384, 512) B233:(SHA1) B283: (SHA1) B409:(SHA1) B571:(SHA1) ) | 413 | | ECC CDH (CVL) | [SP 80056A] (§5.7.1.2) | All NIST Recommended B, K and P curves sizes 163 and 192 | 85 | These algorithms shall not be used when operating in the FIPS Approved mode of operation. EC DH Key Agreement provides a maximum of 256 bits of security strength. RSA Key Wrapping provides a maximum of 256 bits of security strength. The Module requires an initialization sequence (see IG 9.5): the calling application invokes FIPS_mode_set() 3 , which returns a \'1\' for success and \'0\' for failure. If FIPS_mode_set() fails then all cryptographic services fail from then on. The application can test to see if FIPS mode has been successfully performed. The Module is a cryptographic engine library, which can be used only in conjunction with additional software. Aside from the use of the NIST defined elliptic curves as trusted third party domain parameters, all other FIPS 1864 assurances are outside the scope of the Module, and are the responsibility of the calling process. 3 The function call in the Module is FIPS_module_mode_set() which is typically used by an application via the FIPS_mode_set() wrapper function. Page 14 of 29 Nimble Storage FIPS 1402 Security Policy ### 4.1 Critical Security Parameters and Public Keys All CSPs used by the Module are described in this section. All access to these CSPs by Module services are described in Section 4. The CSP names are generic, corresponding to API parameter data structures. Table 4.1a - Critical Security Parameters | CSP Name | Description | |-----------------|------------------------------------------------------------------------------------------------------------------------| | RSA SGK | RSA (1024 to 16384 bits) signature generation key | | RSA KDK | RSA (1024 to 16384 bits) key decryption (private key transport) key | | DSA SGK | [FIPS 1864] DSA (1024/2048/3072) signature generation key | | ECDSA SGK | ECDSA (All NIST defined B, K, and P curves) signature generation key | | EC DH Private | EC DH (All NIST defined B, K, and P curves) private key agreement key. | | AES EDK | AES (128/192/256) encrypt / decrypt key | | AES CMAC | AES (128/192/256) CMAC generate / verify key | | AES GCM | AES (128/192/256) encrypt / decrypt / generate / verify key | | AES XTS | AES (256/512) XTS encrypt / decrypt key | | TripleDES EDK | TripleDES (3Key) encrypt / decrypt key | | TripleDES CMAC | TripleDES (3Key) CMAC generate / verify key | | HMAC Key | Keyed hash key (160/224/256/384/512) | | Hash_DRBG CSPs | V (440/888 bits) and C (440/888 bits), entropy input (length dependent on security strength) | | HMAC_DRBG CSPs | V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits), entropy input (length dependent on security strength) | | CTR_DRBG CSPs | V (128 bits) and Key (AES 128/192/256), entropy input (length dependent on security strength) | | COADDigest | Precalculated HMACSHA1 digest used for Crypto Officer role authentication | | UserADDigest | Precalculated HMACSHA1 digest used for User role authentication | Authentication data is loaded into the module during the module build process, performed by an authorized operator (Crypto Officer), and otherwise cannot be accessed. The module does not output intermediate key generation values. | CSP Name | Description | |--------------|--------------------------------------------------------------------------------------------------------------------| | RSA SVK | RSA (1024 to 16384 bits) signature verification public key | | RSA KEK | RSA (1024 to 16384 bits) key encryption (public key transport) key | | DSA SVK | [FIPS 1864] DSA (1024/2048/3072) signature verification key or [FIPS 1862] DSA (1024) signature verification key | | ECDSA SVK | ECDSA (All NIST defined B, K and P curves) signature verification key | | EC DH Public | EC DH (All NIST defined B, K and P curves) public key agreement key. | Page 15 of 29 Nimble Storage FIPS 1402 Security Policy ###### For all CSPs and Public Keys: Storage : RAM, associated to entities by memory location. The Module stores DRBG state values for the lifetime of the DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of DRBG state values used for the Modules\' default key generation service. Generation : The Module implements SP 80090 compliant DRBG services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry : All CSPs enter the Module\'s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output : The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Destruction : Zeroization of sensitive data is performed automatically by API function calls for temporarily stored CSPs. In addition, the module provides functions to explicitly destroy CSPs related to random number generation services. The calling application is responsible for parameters passed in and out of the module. Private and secret keys as well as seeds and entropy input are provided to the Module by the calling application, and are destroyed when released by the appropriate API function calls. Keys residing in internally allocated data structures (during the lifetime of an API call) can only be accessed using the Module defined API. The operating system protects memory and process space from unauthorized access. Only the calling application that creates or imports keys can use or export such keys. All API functions are executed by the invoking calling application in a nonoverlapping sequence such that no two API functions will execute concurrently. An authorized application as user (CryptoOfficer and User) has access to all key data generated during the operation of the Module. In the event Module power is lost and restored the calling application must ensure that any AESGCM keys used for encryption or decryption are redistributed. Module users (the calling applications) shall use entropy sources that meet the security strength required for the random number generation mechanism: 128 bits as shown in [SP 80090] Table 2 (Hash_DRBG, HMAC_DRBG), and Table 3 (CTR_DRBG). This entropy is supplied by means of callback functions. Those functions must return an error if the minimum entropy strength cannot be met. Table 4.1b - Public Keys Page 16 of 29 Nimble Storage FIPS 1402 Security Policy ## 5 Roles, Authentication and Services The Module implements the required User and Crypto Officer roles and requires authentication for those roles. Only one role may be active at a time and the Module does not allow concurrent operators. The User or Crypto Officer role is assumed by passing the appropriate password to the FIPS_module_mode_set() function. The password values may be specified at build time and must have a minimum length of 16 characters. Any attempt to authenticate with an invalid password will result in an immediate and permanent failure condition rendering the Module unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the Module during the Module build process, performed by the Crypto Officer, and otherwise cannot be accessed. Since minimum password length is 16 characters, the probability of a random successful authentication attempt in one try is a maximum of 1/256 16 , or less than 1/10 38 . The Module permanently disables further authentication attempts after a single failure, so this probability is independent of time. Both roles have access to all of the services provided by the Module. - User Role (User): Loading the Module and calling any of the API functions. - Crypto Officer Role (CO): Installation of the Module on the host computer system and calling of any API functions. All services implemented by the Module are listed below, along with a description of service CSP access. | Service | Role | Description | |--------------------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Initialize | User, CO | Module initialization. Does not access CSPs. | | Selftest | User, CO | Perform self tests (FIPS_selftest). Does not access CSPs. | | Show status | User, CO | Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. | | Zeroize | User, CO | Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. | | Random number generation | User, CO | Used for random number and symmetric key generation. Seed or reseed an DRBG instance Determine security strength of a DRBG instance | Page 17 of 29 Nimble Storage FIPS 1402 Security Policy | Service | Role | Description | |---------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | | | Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. | | Asymmetric key generation | User, CO | Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP80090 | | Symmetric encrypt/decrypt | User, CO | Used to encrypt or decrypt data. Executes using AES EDK, TripleDES EDK (passed in by the calling process). | | Symmetric digest | User, CO | Used to generate or verify data integrity with CMAC. Executes using AES CMAC, TripleDES, CMAC (passed in by the calling process). | | Message digest | User, CO | Used to generate a SHA1 or SHA2 message digest. Does not access CSPs. | | Keyed Hash | User, CO | Used to generate or verify data integrity with HMAC. Executes using HMAC Key (passed in by the calling process). | | Key transport 4 | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | | Key agreement | User, CO | Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). | | Digital signature | User, CO | Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). | | Utility | User, CO | Miscellaneous helper functions. Does not access CSPs. | ## 6 Selftest The Module performs the selftests listed below on invocation of Initialize or Selftest. | Algorithm | Type | Test Attributes | |--------------------|--------|------------------------------------------------------------------------------------------------------------| | Software integrity | KAT | HMACSHA1 | | HMAC | KAT | One KAT per SHA1, SHA224, SHA256, SHA384 and SHA512 Per IG 9.3, this testing covers SHA POST requirements. | | AES | KAT | Separate encrypt and decrypt, ECB mode, 128 bit key length | | AES CCM | KAT | Separate encrypt and decrypt, 192 key length | Table 5 Services and CSP Access Page 18 of 29 Nimble Storage FIPS 1402 Security Policy Table 6a Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency test) | Algorithm | Type | Test Attributes | |-----------------|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | AES GCM | KAT | Separate encrypt and decrypt, 256 key length | | XTSAES | KAT | 128, 256 bit key sizes to support either the 256bit key size (for XTSAES128) or the 512bit key size (for XTSAES256) | | AES CMAC | KAT | Sign and verify CBC mode, 128, 192, 256 key lengths | | TripleDES | KAT | Separate encrypt and decrypt, ECB mode, 3Key | | TripleDES CMAC | KAT | CMAC generate and verify, CBC mode, 3Key | | RSA | KAT | Sign and verify using 2048 bit key, SHA256, PKCS#1 | | DSA | PCT | Sign and verify using 2048 bit key, SHA384 | | DRBG | KAT | CTR_DRBG: AES, 256 bit with and without derivation function HASH_DRBG: SHA256 HMAC_DRBG: SHA256 | | ECDSA | PCT | Keygen, sign, verify using P224, K233 and SHA512. The K233 selftest is not performed for operational environments that support prime curve only (see Table 2). | | ECC CDH | KAT | Shared secret calculation per SP 80056A §5.7.1.2, IG 9.6 | The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMACSHA1 of the Module distribution file as tested by the CMT Laboratory and listed in Appendix A is verified during installation of the Module file as described in Appendix A. The FIPS_mode_set() 5 function performs all powerup selftests listed above with no operator intervention required, returning a \'1\' if all powerup selftests succeed, and a \'0\' otherwise. If any component of the powerup selftest fails an internal flag is set to prevent subsequent invocation of any cryptographic function calls. The module will only enter the FIPS Approved mode if the module is reloaded and the call to FIPS_mode_set() 5 succeeds. The powerup selftests may also be performed ondemand by calling FIPS_selftest() , which returns a \'1\' for success and \'0\' for failure. Interpretation of this return code is the responsibility of the calling application. The Module also implements the following conditional tests: | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Tested as required by [SP80090] Section 11 | | DRBG | FIPS 1402 continuous test for stuck fault | | DSA | Pairwise consistency test on each generation of a key pair | | ECDSA | Pairwise consistency test on each generation of a key pair | Page 19 of 29 ####### Nimble Storage FIPS 1402 Security Policy Table 6b Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | RSA | Pairwise consistency test on each generation of a key pair | In the event of a DRBG selftest failure the calling application must uninstantiate and re instantiate the DRBG per the requirements of [SP 80090]; this is not something the Module can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. The Module supports two operational environment configurations for elliptic curve: NIST prime curves only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Page 20 of 29 Nimble Storage FIPS 1402 Security Policy ## 7 Operational Environment The tested operating systems segregate user processes into separate process spaces. Each process space is logically separated from all other processes by the operating system software and hardware. The Module functions entirely within the process space of the calling application, and implicitly satisfies the FIPS 1402 requirement for a single user mode of operation. Page 21 of 29 Nimble Storage FIPS 1402 Security Policy ## 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 1402. Page 22 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix A Installation and Usage Guidance The test platforms represent different combinations of installation instructions. For each platform there is a build system, the host providing the build environment in which the installation instructions are executed, and a target system on which the generated object code is executed. The build and target systems may be the same type of system or even the same device, or may be different systems - the Module supports crosscompilation environments. Each of these command sets are relative to the top of the directory containing the uncompressed and expanded contents of the distribution files opensslfips2.0.9.tar.gz (all NIST defined curves as listed in Table 2 with the EC column marked "BKP") or opensslfipsecp2.0.9.tar.gz (NIST prime curves only as listed in Table 2 with the EC column marked "P"). The command sets are: U1: ./config no-asm make make install U2: ./config make make install W1: ms\\do_fips no-asm W2: ms\\do_fips ####### Installation instructions 1. Download and copy the distribution file to the build system. These files can be downloaded from http://www.openssl.org/source /. 2. Verify the HMACSHA1 digest of the distribution file; see Appendix B. An independently acquired FIPS 1402 validated implemention of SHA1 HMAC must be used for this digest verification. Note that this verification can be performed on any convenient system and not necessarily on the specific build or target system. Alternatively, a copy of the distribution on physical media can be obtained from OSF 6 . 3. Unpack the distribution 6 For some prospective users the acquisition, installation, and configuration of a suitable FIPS 1402 validated product may not be convenient. OSF will on request mail a CD containing the source code distribution, via USPS or international post. A distribution file received by that means need not be verified by a FIPS 1402 validated implementation of HMACSHA1. For instructions on requesting this CD see http://opensslfoundation.com/fips/verify.html. Page 23 of 29 Nimble Storage FIPS 1402 Security Policy ``` gunzip -c openssl-fips-2.0.9.tar.gz | tar xf cd openssl-fips-2.0.9 or gunzip -c openssl-fips-ecp-2.0.9.tar.gz | tar xf cd openssl-fips-ecp-2.0.9 ``` 4. Execute one of the installation command sets U1, W1, U2, W2 as shown above. No other command sets shall be used. 5. The resulting fipscanister.o or fipscanister.lib file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 7 function. Note that failure to use one of the specified commands sets exactly as shown will result in a module that cannot be considered compliant with FIPS 1402. ####### Linking the Runtime Executable Application Note that applications interfacing with the FIPS Object Module are outside of the cryptographic boundary. When linking the application with the FIPS Object Module two steps are necessary: 1. The HMACSHA1 digest of the FIPS Object Module file must be calculated and verified against the installed digest to ensure the integrity of the FIPS object module. 2. A HMACSHA1 digest of the FIPS Object Module must be generated and embedded in the FIPS Object Module for use by the FIPS_mode_set() 7 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the FIPS Object Module and to generate the new HMACSHA1 digest for the runtime executable application. Failure to embed the digest in the executable object will prevent initialization of FIPS mode. At runtime the FIPS_mode_set() 7 function compares the embedded HMACSHA1 digest with a digest generated from the FIPS Object Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. ###### Optimization The \'asm\' designation means that assembler language optimizations were enabled when the binary code was built, \'noasm\' means that only C language code was compiled. For OpenSSL with x86 there are three possible optimization levels: 1. No optimization (plain C) 2. SSE2 optimization 7 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 24 of 29 Nimble Storage FIPS 1402 Security Policy ### 3. AESNI+PCLMULQDQ+SSSE3 optimization Other theoretically possible combinations (e.g. AESNI only, or SSE3 only) are not addressed individually, so that a processor which does not support all three of AESNI, PCLMULQDQ, and SSSE3 will fall back to SSE2 optimization. For more information, see: - [ http://www.intel.com/support/processors/sb/CS030123.htm?wapkw=sse2](http://www.intel.com/support/processors/sb/CS-030123.htm?wapkw=sse2) - [ http://software.intel.com/enus/articles/inteladvancedencryptionstandardinstructions aesni/?wapkw=aesni](http://software.intel.com/en-us/articles/intel-advanced-encryption-standard-instructions-aes-ni/?wapkw=aes-ni) For OpenSSL with ARM there are two possible optimization levels: 1. Without NEON 2. With NEON (ARM7 only) [For more information, see http://www.arm.com/products/processors/technologies/neon.php](http://www.arm.com/products/processors/technologies/neon.php) Page 25 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix B Controlled Distribution File Fingerprint The OpenSSL FIPS Object Module v2.0.9 consists of the FIPS Object Module (the fipscanister.o or fipscanister.lib contiguous unit of binary object code) generated from the specific source files. For all NIST defined curves (listed in Table 2 with the EC column marked "BKP") the source files are in the specific special OpenSSL distribution opensslfips2.0.9.tar.gz with HMAC SHA1 digest of 54552e9a3ed8d1561341e8945fcdec55af961322 [located at http://www.openssl.org/source/opensslfips2.0.9.tar.gz.](http://www.openssl.org/source/openssl-fips-2.0.9.tar.gz) The openssl command from a version of OpenSSL that incorporates a previously validated version of the module may be used: openssl sha1 -hmac etaonrishdlcupfm openssl-fips-2.0.9.tar.gz For NIST prime curves only (listed in Table 2 with the EC column marked "P") the source files are in the specific special OpenSSL distribution opensslfipsecp2.0.9.tar.gz with HMACSHA1 digest of 91d267688713c920f85bc5e69c8b5d34e1112672 located at http://www.openssl.org/source/opensslfipsecp2.0.9.tar.gz. Note this is from the previous revision of the FIPS Object Module as no modifications relevant to NIST prime curves only were introduced in revision 2.0.9. The set of files specified in this tar file constitutes the complete set of source files of this module. There shall be no additions, deletions, or alterations of this set as used during module build. The OpenSSL distribution tar file (and patch file if used) shall be verified using the above HMAC SHA1 digest(s). The arbitrary 16 byte key of: 65 74 61 6f 6e 72 69 73 68 64 6c 63 75 70 66 6d (equivalent to the ASCII string " etaonrishdlcupfm ") is used to generate the HMACSHA1 value for the FIPS Object Module integrity check. The functionality of all earlier revisions of the FIPS Object Module are subsumed by this latest revision, so there is no reason to use older revisions for any new deployments. However, older revisions remain valid. The source distribution files and corresponding HMACSHA1 digests are listed below: opensslfips2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.8.tar.gz Page 26 of 29 ####### Nimble Storage FIPS 1402 Security Policy Digest: 7f486fbb598f3247ab9db10c1308f1c19f384671 opensslfipsecp2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.8.tar.gz Digest: 7a5f40ef8cebe959372d16e26391fcf23689209b opensslfips2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.7.tar.gz Digest: 295064925a6d95271e2fa2920181ec060f95c7ab opensslfipsecp2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.7.tar.gz Digest: dddfdc78c7e827c61fe92bd4817a7f2c3e67153 opensslfips2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.6.tar.gz Digest: 2b8d831df22d4dfe6169aa2a8e74c35484c26c21 opensslfipsecp2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.6.tar.gz Digest: 852f43cd9ae1bd2eba60e4f9f1f266d3c16c0319 opensslfips2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.5.tar.gz Digest: 8b44f2a43d098f6858eb1ebe77b73f8f027a9c29 opensslfipsecp2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.5.tar.gz Digest: 148e4e127ffef1df80c0ed61bae35b07ec7b7b36 opensslfips2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.4.tar.gz Digest: eaa5f86dab2c5da7086aec4786bce27d3b3c1b8a opensslfipsecp2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.4.tar.gz Digest: 13302f75c82c8b482c9ac96828984a270a45c284 opensslfips2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.3.tar.gz Digest: 5dfe03bc3f57c2862ea97823ea3111d7faf711b2 Page 27 of 29 ####### Nimble Storage FIPS 1402 Security Policy opensslfipsecp2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.3.tar.gz Digest: 9d6b21218d7d5480aa0add68e682d321e3ffbfa7 opensslfips2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.2.tar.gz Digest: e099d5096eb69c2dd8591379f38b985801188663 opensslfipsecp2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.2.tar.gz Digest: 887fa6802c253c32e6c4c83b7a091118fa8c6217 opensslfips2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.1.tar.gz. Digest: 1e05b021fdcd6e77c6155512bbce2d0cbc725aec opensslfipsecp2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.1.tar.gz. Digest: af82c8ebb9d3276be11feffd35e6b55bd0d1839f opensslfips2.0.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.tar.gz. Digest: 2cdd29913c6523df8ad38da11c342b80ed3f1dae opensslfipsecp2.0.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.tar.gz. Digest: e8d5ee306425b278bf6c8b077dae8e4a542e8215 Page 28 of 29 Nimble Storage FIPS 1402 Security Policy ## Appendix C Compilers This appendix lists the specific compilers used to generate the Module for the respective Operational Environments. Note this list does not imply that use of the Module is restricted to only the listed compiler versions, only that the use of other versions has not been confirmed to produce a correct result. Table C Compilers | # | Operational Environment | Compiler | |-----|---------------------------|------------| | 1 | Linux 2.6 | gcc 4.1.2 | | 2 | Linux 2.6 | gcc 4.1.2 | | 3 | Linux 2.6 | gcc 4.1.2 | | 4 | Linux 3.4 | gcc 4.8.0 | | 5 | Linux 2.6 | gcc 4.1.2 | | 6 | Linux 2.6 | gcc 4.1.2 | | 7 | Linux 2.6 | gcc 4.1.2 | | 8 | Linux 2.6 | gcc 4.1.2 | | 9 | Linux 4.4 | gcc 4.1.2 | | 10 | Linux 4.4 | gcc 4.1.2 | | 11 | Linux 4.4 | gcc 4.1.2 | | 12 | Linux 4.4 | gcc 4.1.2 | Page 29 of 29': 1}, '__delete__': ['AES 128/192/256 1202', 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8', 'platform #96, FreeBSD 8.4 on x86 without AESNI', 'platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG', 'platforms #90, #91', 'platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86', 'platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5', 'platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition', 'platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI', 'platforms #77, #78 iOS 6.0 with/without NEON']}}}, 'symmetric_crypto': {'__update__': {'constructions': {'__update__': {'MAC': {'__update__': {'HMAC': 8}}}}}}, 'asymmetric_crypto': {'__update__': {'ECC': {'__update__': {'ECDSA': {'__update__': {'ECDSA': 16}}, 'ECC': {'__update__': {'ECC': 6}}}}, 'FF': {'__update__': {'DH': {'__update__': {'DH': 10}}, 'DSA': {'__update__': {'DSA': 17}}}}}}, 'crypto_scheme': {'__update__': {'KA': {'__update__': {'Key Agreement': 3}}}}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 20}}}}, 'crypto_library': {'__update__': {'OpenSSL': {'__update__': {'OpenSSL': 15}}}}} data.

  The computed heuristics were updated.

  • The policy_prunned_references property was updated, with the {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']} values added.
  • The policy_processed_references property was updated, with the {'directly_referencing': {'__add__': {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']}}, 'indirectly_referencing': {'__add__': {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']}}} data.
• 21.09.2026

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The following values were inserted: {'module_algorithms': {'_type': 'Set', 'elements': ['DSA#950', 'RSA#1718', 'AES#3351', 'SHS#2778', 'DRBG#784', 'CVL#85', 'ECDSA#664', 'HMAC#2134', 'ECDSA#413', 'DRBG#342', 'Triple-DES#1912', 'AES#2484', 'DSA#764', 'Triple-DES#1522', 'RSA#1273', 'HMAC#1526', 'CVL#496', 'SHS#2102']}, 'policy_algorithms': {'_type': 'Set', 'elements': ['#764', '#950', '#1526', '#413', '#342', '#3351', '#1718', '#1202', '#784', '#1912', '#1522', '#1363', '#2102', '#2484', '#1273', '#2778', '#2134', '#85']}}.
  • The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'DRBG 2': 1, 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8': 1, 'platform #96, FreeBSD 8.4 on x86 without AESNI': 1, 'platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG': 1, 'platforms #90, #91': 1, 'platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86': 1, 'platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5': 1, 'platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition': 1, 'platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI': 1, 'platforms #77, #78 iOS 6.0 with/without NEON': 1}, '__update__': {'AES 128/192/256': 2}, '__delete__': ['AES 128/ 192/256', 'DRBG2', 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8 20140104 Addition of new platform #96, FreeBSD 8.4 on x86 without AESNI 20140730 Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG 20140728 Changed processor names for platforms #90, #91 20140711 Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86 20140612 Temporarily remove misplaced platform, move Dual EC DRBG to the Non Approved Table 4c 20140529 Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) 20140512 Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition 20131108 Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI 20131101 Added two platforms #77, #78 iOS 6.0 with/without NEON 20131002 Added six platforms (Linux 3.4 x86 virtualized under XenSource/VMware/Hyper V, with/without AESNI) Page 4 of 29 Nimble Storage FIPS 1402 Security Policy Updated URL in Appendix A footnote 20130829 Added new sponsor acknowledgment 20130814 Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms 20130724 Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 20130609 Added QNX, iOS 6.1, eCos for revision 2.0.5 20130501 Added OpenWRT 2.6 for revision 2.0.4 20130301 Added VMware Horizon Mobile 1.3, Apple OS X 10.7 , Apple iOS 5.0 20130223 Added WinEC7 and Android 4.0 for revision 2.0.3 20130214 Table 5: Removed references to nonexistent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM 20130128 Added four platforms: Android 4.1 and Android 4.2 with and without NEON 20130108 Reworded section 8 20130103 Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AESNI. 20121208 Note EC DH Key Agreement and RSA Key Wrapping strength. 20121010 Added NetBSD 5.1 on PowerPCe500, NetBSD 5.1 on Intel Xeon 5500 (x8664) for revision 2.0.2 20110702 Added DSP Media Framework, Linux 2.6/Freescale PowerPCe500, Android 4.0 20110615 Added iOS, WinCE 5, WinCE 6 OEs References Reference Full Specification Name [ANS X9.31] Digital Signatures Using Reversible Public Key Cryptography for the Financial Services Industry (rDSA) [FIPS 1402] Security Requirements for Cryptographic modules, May 25, 2001 [FIPS 1803] Secure Hash Standard [FIPS 1864] Digital Signature Standard [FIPS 197] Advanced Encryption Standard [FIPS 1981] The KeyedHash Message Authentication Code (HMAC) [SP 80038B] Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication [SP 80038C] Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality Page 5 of 29 Nimble Storage FIPS 1402 Security Policy Reference Full Specification Name [SP 80038D] Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC [SP 80056A] Recommendation for PairWise Key Establishment Schemes Using Discrete Logarithm Cryptography [SP 800 67R1] Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher [SP 80089] Recommendation for Obtaining Assurances for Digital Signature Applications [SP 80090] Recommendation for Random Number Generation Using Deterministic Random Bit Generators [SP 800 131A] Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths Page 6 of 29 Nimble Storage FIPS 1402 Security Policy Table of Contents 1 Introduction.........................................................................................................................7 2 Tested Configurations.........................................................................................................9 3 Ports and Interfaces ............................................................................................................13 4 Modes of Operation and Cryptographic Functionality ......................................................14 4.1 Critical Security Parameters and Public Keys............................................................18 5 Roles, Authentication and Services ...................................................................................21 6 Selftest...............................................................................................................................23 7 Operational Environment....................................................................................................25 8 Mitigation of other Attacks.................................................................................................26 Appendix A Installation and Usage Guidance.......................................................................27 Appendix B Controlled Distribution File Fingerprint...........................................................30 Appendix C Compilers..........................................................................................................33 Page 7 of 29 Nimble Storage FIPS 1402 Security Policy 1 Introduction This document is the nonproprietary security policy for the Nimble Storage FIPS Object Module, hereafter referred to as the Module, which is build from the OpenSSL FIPS Object Module source code according to the the instructions in Appendix A. The Module is a software library providing a Clanguage application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 1402 as a software module, multichip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the fipscanister object module, a single object module file named fipscanister.o compiled on Linux®1 . The Module performs no communications other than with the calling application (the process that invokes the Module services). The FIPS 1402 security levels for the Module are as follows: Security Requirement Security Level Cryptographic Module Specification 1 Cryptographic Module Ports and Interfaces 1 Roles, Services, and Authentication 2 Finite State Model 1 Physical Security NA Operational Environment 1 Cryptographic Key Management 1 EMI/EMC 1 SelfTests 1 Design Assurance 3 Mitigation of Other Attacks NA Table 1 – Security Level of Security Requirements The Module’s software version for this validation is 2.0.9. It is build from the 2.0.9 version of the OpenSSL FIPS Object Module source code. 1 Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Page 8 of 29 Nimble Storage FIPS 1402 Security Policy Page 9 of 29 Figure 1 Module Block Diagram Nimble Storage FIPS 1402 Security Policy 2 Tested Configurations # Operational Environment Processor Optimiz ations (Target) EC B 1 Linux 2.6 Intel E52403V2 (x86_64) AESNI BKP U2 2 Linux 2.6 Intel E52450V2 (x86_64) AESNI BKP U2 3 Linux 2.6 Intel E52470V2 (x86_64) AESNI BKP U2 4 Linux 3.4 64bit under Citrix XenServer Intel Xeon E52430L (x86) None BKP U2 5 Linux 2.6 Intel E52603V3 (x86_64) AESNI BKP U2 6 Linux 2.6 Intel E52620V3 (x86_64) AESNI BKP U2 7 Linux 2.6 Intel E52680V3 (x86_64) AESNI BKP U2 8 Linux 2.6 Intel E52699V3 (x86_64) AESNI BKP U2 9 Linux 4.4 Intel E5504 (x86_64) None BKP U2 10 Linux 4.4 Intel E52403V2 (x86_64) AESNI BKP U2 11 Linux 4.4 Intel E52680V3 (x86_64) AESNI BKP U2 12 Linux 4.4 Intel Xeon Silver 4110 (x86_64) AESNI BKP U2 Table 2 Tested Configurations (B = Build Method; EC = Elliptic Curve Support). The EC column indicates support for prime curve only (P), or all NIST defined B, K, and P curves (BKP). See Appendix A for additional information on build method and optimizations. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. Page 10 of 29 Nimble Storage FIPS 1402 Security Policy 3 Ports and Interfaces The physical ports of the Module are the same as the computer system on which it is executing. The logical interface is a Clanguage application program interface (API). Logical interface type Description Control input API entry point and corresponding stack parameters Data input API entry point data input stack parameters Status output API entry point return values and status stack parameters Data output API entry point data output stack parameters Table 3 Logical interfaces As a software module, control of the physical ports is outside module scope. However, when the module is performing selftests, or is in an error state, all output on the logical data output interface is inhibited. The module is singlethreaded and in error scenarios returns only an error value (no data output is returned). Page 11 of 29 Nimble Storage FIPS 1402 Security Policy 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 1402 Approved mode. Tables 4a and 4b list the Approved and Nonapproved but Allowed algorithms, respectively. Function Algorithm Options Cert # Random Number Generation; Symmetric key generation [SP 80090A] DRBG2 Prediction resistance supported for all variations Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function 342, 784 Encryption, Decryption and CMAC [SP 80067] 3Key TripleDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify 1522, 1912 [FIPS 197] AES 128/ 192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify 2484, 3351 [SP 80038B] CMAC [SP 80038C] CCM [SP 80038D] GCM [SP 80038E] XTS Message Digests [FIPS 1803] SHA1, SHA2 (224, 256, 384, 512) 2102, 2778 Keyed Hash [FIPS 198] HMAC SHA1, SHA2 (224, 256, 384, 512) 1526, 2134 Digital Signature and Asymmetric Key Generation [FIPS 1862] RSA SigVer9.31 (1024/1536/2048/3072/4096 with SHA1/256/384/512) SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA 1/SHA2 sizes) 1273, 1718 [FIPS 1864] RSA SigGen9.31 (2048/3072/4096 with SHA 256/384/512) SigGenPKCS1.5, SigGenPSS (2048/3072/4096 with all SHA2 sizes) 1718 [FIPS 1864] DSA PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA2 sizes) 764, 950 2 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP80090] and [SP80057]. Page 12 of 29 Nimble Storage FIPS 1402 Security Policy [FIPS 1864] ECDSA PKG: CURVES( P224 P256 P384 P521 K 224 K256 K384 K521 B224 B256 B384 B 521 ExtraRandomBits TestingCandidates ) PKV: CURVES( ALLP ALLK ALLB ) SigGen: CURVES( P224: (SHA224, 256, 384, 512) P256: (SHA224, 256, 384, 512) P384: (SHA224, 256, 384, 512) P521: (SHA224, 256, 384, 512) K233: (SHA224, 256, 384, 512) K283: (SHA224, 256, 384, 512) K409: (SHA224, 256, 384, 512) K571: (SHA224, 256, 384, 512) B233: (SHA224, 256, 384, 512) B283: (SHA224, 256, 384, 512) B409: (SHA 224, 256, 384, 512) B571: (SHA224, 256, 384, 512) ) SigVer: CURVES( P192: (SHA1, 224, 256, 384, 512) P224: (SHA1, 224, 256, 384, 512) P 256: (SHA1, 224, 256, 384, 512) P384: (SHA 1, 224, 256, 384, 512) P521: (SHA1, 224, 256, 384, 512) K163: (SHA1, 224, 256, 384, 512) K233: (SHA1, 224, 256, 384, 512) K283: (SHA1, 224, 256, 384, 512) K409: (SHA1, 224, 256, 384, 512) K571: (SHA1, 224, 256, 384, 512 B163: (SHA1, 224, 256, 384, 512) B 233: (SHA1, 224, 256, 384, 512) B283: (SHA 1, 224, 256, 384, 512) B409: (SHA1, 224, 256, 384, 512) B571: (SHA1, 224, 256, 384, 512) ) 413, 664 ECC CDH (CVL) [SP 80056A] (§5.7.1.2) All NIST defined B, K and P curves except sizes 163 and 192 85, 496 Table 4a – FIPS Approved Cryptographic Functions The Module supports only NIST defined curves for use with ECDSA and ECC CDH. The Module supports two operational environment configurations for elliptic curve; NIST prime curve only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Category Algorithm Description Key Agreement EC DH Noncompliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. Key Encryption, Decryption RSA The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 80056B compliance, and no CSPs are established into or exported out of the module using these services. Table 4b – NonFIPS Approved But Allowed Cryptographic Functions Page 13 of 29 Nimble Storage FIPS 1402 Security Policy Function Algorithm Options Cert # Random Number Generation; Symmetric key generation [ANS X9.31] RNG AES 128/192/256 1202, 1363 Digital Signature and Asymmetric Key Generation [FIPS 1862] RSA GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/4096 with SHA1) 1273 [FIPS 1862] DSA PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) 764 [FIPS 1864] DSA PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) 764 [FIPS 1862] ECDSA PKG: CURVES( P192 K163 B163 ) SIG(gen): CURVES( P192 P224 P256 P384 P521 K163 K233 K283 K409 K571 B163 B233 B283 B409 B571 ) 413 [FIPS 1864] ECDSA PKG: CURVES( P192 K163 B163 ) SigGen: CURVES( P192: (SHA1, 224, 256, 384, 512) P224:(SHA1) P256:(SHA1) P384: (SHA1) P521:(SHA1) K163: (SHA1, 224, 256, 384, 512) K233:(SHA1) K283:(SHA1) K409:(SHA1) K571:(SHA1) B163: (SHA1, 224, 256, 384, 512) B233:(SHA1) B283: (SHA1) B409:(SHA1) B571:(SHA1) ) 413 ECC CDH (CVL) [SP 80056A] (§5.7.1.2) All NIST Recommended B, K and P curves sizes 163 and 192 85 Table 4c – FIPS NonApproved Cryptographic Functions These algorithms shall not be used when operating in the FIPS Approved mode of operation. EC DH Key Agreement provides a maximum of 256 bits of security strength. RSA Key Wrapping provides a maximum of 256 bits of security strength. The Module requires an initialization sequence (see IG 9.5): the calling application invokes FIPS_mode_set()3 , which returns a “1” for success and “0” for failure. If FIPS_mode_set() fails then all cryptographic services fail from then on. The application can test to see if FIPS mode has been successfully performed. The Module is a cryptographic engine library, which can be used only in conjunction with additional software. Aside from the use of the NIST defined elliptic curves as trusted third party domain parameters, all other FIPS 1864 assurances are outside the scope of the Module, and are the responsibility of the calling process. 3 The function call in the Module is FIPS_module_mode_set() which is typically used by an application via the FIPS_mode_set() wrapper function. Page 14 of 29 Nimble Storage FIPS 1402 Security Policy 4.1 Critical Security Parameters and Public Keys All CSPs used by the Module are described in this section. All access to these CSPs by Module services are described in Section 4. The CSP names are generic, corresponding to API parameter data structures. CSP Name Description RSA SGK RSA (1024 to 16384 bits) signature generation key RSA KDK RSA (1024 to 16384 bits) key decryption (private key transport) key DSA SGK [FIPS 1864] DSA (1024/2048/3072) signature generation key ECDSA SGK ECDSA (All NIST defined B, K, and P curves) signature generation key EC DH Private EC DH (All NIST defined B, K, and P curves) private key agreement key. AES EDK AES (128/192/256) encrypt / decrypt key AES CMAC AES (128/192/256) CMAC generate / verify key AES GCM AES (128/192/256) encrypt / decrypt / generate / verify key AES XTS AES (256/512) XTS encrypt / decrypt key TripleDES EDK TripleDES (3Key) encrypt / decrypt key TripleDES CMAC TripleDES (3Key) CMAC generate / verify key HMAC Key Keyed hash key (160/224/256/384/512) Hash_DRBG CSPs V (440/888 bits) and C (440/888 bits), entropy input (length dependent on security strength) HMAC_DRBG CSPs V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits), entropy input (length dependent on security strength) CTR_DRBG CSPs V (128 bits) and Key (AES 128/192/256), entropy input (length dependent on security strength) COADDigest Precalculated HMACSHA1 digest used for Crypto Officer role authentication UserADDigest Precalculated HMACSHA1 digest used for User role authentication Table 4.1a – Critical Security Parameters Authentication data is loaded into the module during the module build process, performed by an authorized operator (Crypto Officer), and otherwise cannot be accessed. The module does not output intermediate key generation values. CSP Name Description RSA SVK RSA (1024 to 16384 bits) signature verification public key RSA KEK RSA (1024 to 16384 bits) key encryption (public key transport) key DSA SVK [FIPS 1864] DSA (1024/2048/3072) signature verification key or [FIPS 1862] DSA (1024) signature verification key ECDSA SVK ECDSA (All NIST defined B, K and P curves) signature verification key EC DH Public EC DH (All NIST defined B, K and P curves) public key agreement key. Page 15 of 29 Nimble Storage FIPS 1402 Security Policy Table 4.1b – Public Keys For all CSPs and Public Keys: Storage: RAM, associated to entities by memory location. The Module stores DRBG state values for the lifetime of the DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of DRBG state values used for the Modules\' default key generation service. Generation: The Module implements SP 80090 compliant DRBG services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry: All CSPs enter the Module’s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output: The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Destruction: Zeroization of sensitive data is performed automatically by API function calls for temporarily stored CSPs. In addition, the module provides functions to explicitly destroy CSPs related to random number generation services. The calling application is responsible for parameters passed in and out of the module. Private and secret keys as well as seeds and entropy input are provided to the Module by the calling application, and are destroyed when released by the appropriate API function calls. Keys residing in internally allocated data structures (during the lifetime of an API call) can only be accessed using the Module defined API. The operating system protects memory and process space from unauthorized access. Only the calling application that creates or imports keys can use or export such keys. All API functions are executed by the invoking calling application in a nonoverlapping sequence such that no two API functions will execute concurrently. An authorized application as user (CryptoOfficer and User) has access to all key data generated during the operation of the Module. In the event Module power is lost and restored the calling application must ensure that any AESGCM keys used for encryption or decryption are redistributed. Module users (the calling applications) shall use entropy sources that meet the security strength required for the random number generation mechanism: 128 bits as shown in [SP 80090] Table 2 (Hash_DRBG, HMAC_DRBG), and Table 3 (CTR_DRBG). This entropy is supplied by means of callback functions. Those functions must return an error if the minimum entropy strength cannot be met. Page 16 of 29 Nimble Storage FIPS 1402 Security Policy 5 Roles, Authentication and Services The Module implements the required User and Crypto Officer roles and requires authentication for those roles. Only one role may be active at a time and the Module does not allow concurrent operators. The User or Crypto Officer role is assumed by passing the appropriate password to the FIPS_module_mode_set() function. The password values may be specified at build time and must have a minimum length of 16 characters. Any attempt to authenticate with an invalid password will result in an immediate and permanent failure condition rendering the Module unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the Module during the Module build process, performed by the Crypto Officer, and otherwise cannot be accessed. Since minimum password length is 16 characters, the probability of a random successful authentication attempt in one try is a maximum of 1/25616 , or less than 1/1038 . The Module permanently disables further authentication attempts after a single failure, so this probability is independent of time. Both roles have access to all of the services provided by the Module. User Role (User): Loading the Module and calling any of the API functions. Crypto Officer Role (CO): Installation of the Module on the host computer system and calling of any API functions. All services implemented by the Module are listed below, along with a description of service CSP access. Service Role Description Initialize User, CO Module initialization. Does not access CSPs. Selftest User, CO Perform self tests (FIPS_selftest). Does not access CSPs. Show status User, CO Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. Zeroize User, CO Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. Random number generation User, CO Used for random number and symmetric key generation. Seed or reseed an DRBG instance Determine security strength of a DRBG instance Page 17 of 29 Nimble Storage FIPS 1402 Security Policy Service Role Description Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. Asymmetric key generation User, CO Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP80090 Symmetric encrypt/decrypt User, CO Used to encrypt or decrypt data. Executes using AES EDK, TripleDES EDK (passed in by the calling process). Symmetric digest User, CO Used to generate or verify data integrity with CMAC. Executes using AES CMAC, TripleDES, CMAC (passed in by the calling process). Message digest User, CO Used to generate a SHA1 or SHA2 message digest. Does not access CSPs. Keyed Hash User, CO Used to generate or verify data integrity with HMAC. Executes using HMAC Key (passed in by the calling process). Key transport4 User, CO Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). Key agreement User, CO Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). Digital signature User, CO Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). Utility User, CO Miscellaneous helper functions. Does not access CSPs. Table 5 Services and CSP Access 6 Selftest The Module performs the selftests listed below on invocation of Initialize or Selftest. Algorithm Type Test Attributes Software integrity KAT HMACSHA1 HMAC KAT One KAT per SHA1, SHA224, SHA256, SHA384 and SHA512 Per IG 9.3, this testing covers SHA POST requirements. AES KAT Separate encrypt and decrypt, ECB mode, 128 bit key length AES CCM KAT Separate encrypt and decrypt, 192 key length 4 "Key transport" can refer to a) moving keys in and out of the module or b) the use of keys by an external application. The latter definition is the one that applies to the Nimble Storage FIPS Object Module. Page 18 of 29 Nimble Storage FIPS 1402 Security Policy Algorithm Type Test Attributes AES GCM KAT Separate encrypt and decrypt, 256 key length XTSAES KAT 128, 256 bit key sizes to support either the 256bit key size (for XTSAES128) or the 512bit key size (for XTSAES256) AES CMAC KAT Sign and verify CBC mode, 128, 192, 256 key lengths TripleDES KAT Separate encrypt and decrypt, ECB mode, 3Key TripleDES CMAC KAT CMAC generate and verify, CBC mode, 3Key RSA KAT Sign and verify using 2048 bit key, SHA256, PKCS#1 DSA PCT Sign and verify using 2048 bit key, SHA384 DRBG KAT CTR_DRBG: AES, 256 bit with and without derivation function HASH_DRBG: SHA256 HMAC_DRBG: SHA256 ECDSA PCT Keygen, sign, verify using P224, K233 and SHA512. The K233 selftest is not performed for operational environments that support prime curve only (see Table 2). ECC CDH KAT Shared secret calculation per SP 80056A §5.7.1.2, IG 9.6 Table 6a Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency test) The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMACSHA1 of the Module distribution file as tested by the CMT Laboratory and listed in Appendix A is verified during installation of the Module file as described in Appendix A. The FIPS_mode_set()5 function performs all powerup selftests listed above with no operator intervention required, returning a “1” if all powerup selftests succeed, and a “0” otherwise. If any component of the powerup selftest fails an internal flag is set to prevent subsequent invocation of any cryptographic function calls. The module will only enter the FIPS Approved mode if the module is reloaded and the call to FIPS_mode_set()5 succeeds. The powerup selftests may also be performed ondemand by calling FIPS_selftest(), which returns a “1” for success and “0” for failure. Interpretation of this return code is the responsibility of the calling application. The Module also implements the following conditional tests: Algorithm Test DRBG Tested as required by [SP80090] Section 11 DRBG FIPS 1402 continuous test for stuck fault DSA Pairwise consistency test on each generation of a key pair ECDSA Pairwise consistency test on each generation of a key pair 5 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 19 of 29 Nimble Storage FIPS 1402 Security Policy Algorithm Test RSA Pairwise consistency test on each generation of a key pair Table 6b Conditional Tests In the event of a DRBG selftest failure the calling application must uninstantiate and re instantiate the DRBG per the requirements of [SP 80090]; this is not something the Module can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. The Module supports two operational environment configurations for elliptic curve: NIST prime curves only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Page 20 of 29 Nimble Storage FIPS 1402 Security Policy 7 Operational Environment The tested operating systems segregate user processes into separate process spaces. Each process space is logically separated from all other processes by the operating system software and hardware. The Module functions entirely within the process space of the calling application, and implicitly satisfies the FIPS 1402 requirement for a single user mode of operation. Page 21 of 29 Nimble Storage FIPS 1402 Security Policy 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 1402. Page 22 of 29 Nimble Storage FIPS 1402 Security Policy Appendix A Installation and Usage Guidance The test platforms represent different combinations of installation instructions. For each platform there is a build system, the host providing the build environment in which the installation instructions are executed, and a target system on which the generated object code is executed. The build and target systems may be the same type of system or even the same device, or may be different systems – the Module supports crosscompilation environments. Each of these command sets are relative to the top of the directory containing the uncompressed and expanded contents of the distribution files opensslfips2.0.9.tar.gz (all NIST defined curves as listed in Table 2 with the EC column marked "BKP") or opensslfipsecp2.0.9.tar.gz (NIST prime curves only as listed in Table 2 with the EC column marked "P"). The command sets are: U1: ./config no-asm make make install U2: ./config make make install W1: ms\\do_fips no-asm W2: ms\\do_fips Installation instructions 1. Download and copy the distribution file to the build system. These files can be downloaded from http://www.openssl.org/source/. 2. Verify the HMACSHA1 digest of the distribution file; see Appendix B. An independently acquired FIPS 1402 validated implemention of SHA1 HMAC must be used for this digest verification. Note that this verification can be performed on any convenient system and not necessarily on the specific build or target system. Alternatively, a copy of the distribution on physical media can be obtained from OSF6 . 3. Unpack the distribution 6 For some prospective users the acquisition, installation, and configuration of a suitable FIPS 1402 validated product may not be convenient. OSF will on request mail a CD containing the source code distribution, via USPS or international post. A distribution file received by that means need not be verified by a FIPS 1402 validated implementation of HMACSHA1. For instructions on requesting this CD see http://opensslfoundation.com/fips/verify.html. Page 23 of 29 Nimble Storage FIPS 1402 Security Policy gunzip -c openssl-fips-2.0.9.tar.gz | tar xf - cd openssl-fips-2.0.9 or gunzip -c openssl-fips-ecp-2.0.9.tar.gz | tar xf - cd openssl-fips-ecp-2.0.9 4. Execute one of the installation command sets U1, W1, U2, W2 as shown above. No other command sets shall be used. 5. The resulting fipscanister.o or fipscanister.lib file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set()7 function. Note that failure to use one of the specified commands sets exactly as shown will result in a module that cannot be considered compliant with FIPS 1402. Linking the Runtime Executable Application Note that applications interfacing with the FIPS Object Module are outside of the cryptographic boundary. When linking the application with the FIPS Object Module two steps are necessary: 1. The HMACSHA1 digest of the FIPS Object Module file must be calculated and verified against the installed digest to ensure the integrity of the FIPS object module. 2. A HMACSHA1 digest of the FIPS Object Module must be generated and embedded in the FIPS Object Module for use by the FIPS_mode_set()7 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the FIPS Object Module and to generate the new HMACSHA1 digest for the runtime executable application. Failure to embed the digest in the executable object will prevent initialization of FIPS mode. At runtime the FIPS_mode_set()7 function compares the embedded HMACSHA1 digest with a digest generated from the FIPS Object Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. Optimization The “asm” designation means that assembler language optimizations were enabled when the binary code was built, “noasm” means that only C language code was compiled. For OpenSSL with x86 there are three possible optimization levels: 1. No optimization (plain C) 2. SSE2 optimization 7 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 24 of 29 Nimble Storage FIPS 1402 Security Policy 3. AESNI+PCLMULQDQ+SSSE3 optimization Other theoretically possible combinations (e.g. AESNI only, or SSE3 only) are not addressed individually, so that a processor which does not support all three of AESNI, PCLMULQDQ, and SSSE3 will fall back to SSE2 optimization. For more information, see: http://www.intel.com/support/processors/sb/CS030123.htm?wapkw=sse2 http://software.intel.com/enus/articles/inteladvancedencryptionstandardinstructions aesni/?wapkw=aesni For OpenSSL with ARM there are two possible optimization levels: 1. Without NEON 2. With NEON (ARM7 only) For more information, see http://www.arm.com/products/processors/technologies/neon.php Page 25 of 29 Nimble Storage FIPS 1402 Security Policy Appendix B Controlled Distribution File Fingerprint The OpenSSL FIPS Object Module v2.0.9 consists of the FIPS Object Module (the fipscanister.o or fipscanister.lib contiguous unit of binary object code) generated from the specific source files. For all NIST defined curves (listed in Table 2 with the EC column marked "BKP") the source files are in the specific special OpenSSL distribution opensslfips2.0.9.tar.gz with HMAC SHA1 digest of 54552e9a3ed8d1561341e8945fcdec55af961322 located at http://www.openssl.org/source/opensslfips2.0.9.tar.gz. The openssl command from a version of OpenSSL that incorporates a previously validated version of the module may be used: openssl sha1 -hmac etaonrishdlcupfm openssl-fips-2.0.9.tar.gz For NIST prime curves only (listed in Table 2 with the EC column marked "P") the source files are in the specific special OpenSSL distribution opensslfipsecp2.0.9.tar.gz with HMACSHA1 digest of 91d267688713c920f85bc5e69c8b5d34e1112672 located at http://www.openssl.org/source/opensslfipsecp2.0.9.tar.gz. Note this is from the previous revision of the FIPS Object Module as no modifications relevant to NIST prime curves only were introduced in revision 2.0.9. The set of files specified in this tar file constitutes the complete set of source files of this module. There shall be no additions, deletions, or alterations of this set as used during module build. The OpenSSL distribution tar file (and patch file if used) shall be verified using the above HMAC SHA1 digest(s). The arbitrary 16 byte key of: 65 74 61 6f 6e 72 69 73 68 64 6c 63 75 70 66 6d (equivalent to the ASCII string "etaonrishdlcupfm") is used to generate the HMACSHA1 value for the FIPS Object Module integrity check. The functionality of all earlier revisions of the FIPS Object Module are subsumed by this latest revision, so there is no reason to use older revisions for any new deployments. However, older revisions remain valid. The source distribution files and corresponding HMACSHA1 digests are listed below: opensslfips2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.8.tar.gz Page 26 of 29 Nimble Storage FIPS 1402 Security Policy Digest: 7f486fbb598f3247ab9db10c1308f1c19f384671 opensslfipsecp2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.8.tar.gz Digest: 7a5f40ef8cebe959372d16e26391fcf23689209b opensslfips2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.7.tar.gz Digest: 295064925a6d95271e2fa2920181ec060f95c7ab opensslfipsecp2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.7.tar.gz Digest: dddfdc78c7e827c61fe92bd4817a7f2c3e67153 opensslfips2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.6.tar.gz Digest: 2b8d831df22d4dfe6169aa2a8e74c35484c26c21 opensslfipsecp2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.6.tar.gz Digest: 852f43cd9ae1bd2eba60e4f9f1f266d3c16c0319 opensslfips2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.5.tar.gz Digest: 8b44f2a43d098f6858eb1ebe77b73f8f027a9c29 opensslfipsecp2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.5.tar.gz Digest: 148e4e127ffef1df80c0ed61bae35b07ec7b7b36 opensslfips2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.4.tar.gz Digest: eaa5f86dab2c5da7086aec4786bce27d3b3c1b8a opensslfipsecp2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.4.tar.gz Digest: 13302f75c82c8b482c9ac96828984a270a45c284 opensslfips2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.3.tar.gz Digest: 5dfe03bc3f57c2862ea97823ea3111d7faf711b2 Page 27 of 29 Nimble Storage FIPS 1402 Security Policy opensslfipsecp2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.3.tar.gz Digest: 9d6b21218d7d5480aa0add68e682d321e3ffbfa7 opensslfips2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.2.tar.gz Digest: e099d5096eb69c2dd8591379f38b985801188663 opensslfipsecp2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.2.tar.gz Digest: 887fa6802c253c32e6c4c83b7a091118fa8c6217 opensslfips2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.1.tar.gz. Digest: 1e05b021fdcd6e77c6155512bbce2d0cbc725aec opensslfipsecp2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.1.tar.gz. Digest: af82c8ebb9d3276be11feffd35e6b55bd0d1839f opensslfips2.0.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.tar.gz. Digest: 2cdd29913c6523df8ad38da11c342b80ed3f1dae opensslfipsecp2.0.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.tar.gz. Digest: e8d5ee306425b278bf6c8b077dae8e4a542e8215 Page 28 of 29 Nimble Storage FIPS 1402 Security Policy Appendix C Compilers This appendix lists the specific compilers used to generate the Module for the respective Operational Environments. Note this list does not imply that use of the Module is restricted to only the listed compiler versions, only that the use of other versions has not been confirmed to produce a correct result. # Operational Environment Compiler 1 Linux 2.6 gcc 4.1.2 2 Linux 2.6 gcc 4.1.2 3 Linux 2.6 gcc 4.1.2 4 Linux 3.4 gcc 4.8.0 5 Linux 2.6 gcc 4.1.2 6 Linux 2.6 gcc 4.1.2 7 Linux 2.6 gcc 4.1.2 8 Linux 2.6 gcc 4.1.2 9 Linux 4.4 gcc 4.1.2 10 Linux 4.4 gcc 4.1.2 11 Linux 4.4 gcc 4.1.2 12 Linux 4.4 gcc 4.1.2 Table C Compilers Page 29 of 29']}}}, 'symmetric_crypto': {'__update__': {'constructions': {'__update__': {'MAC': {'__update__': {'HMAC': 7, 'CMAC': 18}}}}}}, 'asymmetric_crypto': {'__update__': {'ECC': {'__update__': {'ECDSA': {'__update__': {'ECDSA': 15}}, 'ECC': {'__update__': {'ECC': 5}}}}, 'FF': {'__update__': {'DH': {'__update__': {'DH': 9}}, 'DSA': {'__update__': {'DSA': 16}}}}}}, 'crypto_scheme': {'__update__': {'KA': {'__update__': {'Key Agreement': 2}}}}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 14}}}}, 'cipher_mode': {'__update__': {'ECB': {'__update__': {'ECB': 4}}, 'CBC': {'__update__': {'CBC': 4}}, 'CTR': {'__update__': {'CTR': 3}}, 'CFB': {'__update__': {'CFB': 6}}, 'OFB': {'__update__': {'OFB': 2}}, 'GCM': {'__update__': {'GCM': 7}}, 'CCM': {'__update__': {'CCM': 5}}, 'XTS': {'__update__': {'XTS': 5}}}}, 'crypto_library': {'__update__': {'OpenSSL': {'__update__': {'OpenSSL': 5}}}}} data.

  The computed heuristics were updated.

  • The algorithms property was updated, with the {'_type': 'Set', 'elements': ['#764', '#950', '#1526', '#413', '#342', '#3351', '#1718', '#1912', '#1202', '#784', '#1522', '#1363', '#2102', '#2484', '#1273', '#2778', '#2134', '#85']} values added.
  • The policy_prunned_references property was updated, with the {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']} values discarded.
  • The policy_processed_references property was updated, with the {'directly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']}}, 'indirectly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '96', '90', '77', '81', '86']}}} data.

  The state was updated.

  • The policy property was updated, with the {'txt_hash': '07501be4ee354492e5ddb96e6f41aadaae151f8a1e5b05191d4cff5f07dcf163', 'json_hash': 'c6bf3a330db7748a3b7962d33aa229522d47ed55fb6ca6062a7a14f763b3efd2'} data.
• 15.12.2025

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The state was updated.

  • The following values were inserted: {'policy_json_hash': None}.
  • The following properties were deleted: ['policy_convert_garbage'].
• 08.09.2025

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web extraction data was updated.

  • The validation_history property was updated.
• 09.02.2023

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The cert_id was updated.

  • The new value is 2422.

  The web extraction data was updated.

  • The following values were inserted: {'validation_history': [{'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2015-08-11', 'validation_type': 'Initial', 'lab': 'LEIDOS CSTL'}, {'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2016-03-01', 'validation_type': 'Update', 'lab': 'LEIDOS CSTL'}, {'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2016-06-07', 'validation_type': 'Update', 'lab': 'LEIDOS CSTL'}, {'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2016-07-25', 'validation_type': 'Update', 'lab': 'LEIDOS CSTL'}, {'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2018-03-26', 'validation_type': 'Update', 'lab': 'LEIDOS CSTL'}, {'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2021-01-26', 'validation_type': 'Update', 'lab': 'LEIDOS CSTL'}], 'vendor_url': 'http://www.nimblestorage.com', 'certificate_pdf_url': 'https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/certificates/FIPS140ConsolidatedCertList0056.pdf', 'hw_versions': None, 'fw_versions': None}.
  • The standard property was set to FIPS 140-2.
  • The status property was set to historical.
  • The level property was set to 1.
  • The embodiment property was set to Multi-Chip Stand Alone.
  • The mentioned_certs property was updated, with the {'1747': 1} data.
  • The following properties were deleted: ['date_validation', 'algorithms', 'vendor_www', 'lab', 'lab_nvlap', 'security_policy_www', 'certificate_www', 'hw_version', 'fw_version', 'product_url'].

  The PDF extraction data was updated.

  • The following values were inserted: {'policy_metadata': {'pdf_file_size_bytes': 744852, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 29, '/Author': 'CPUBuilders Customer', '/Creator': 'Writer', '/Producer': 'LibreOffice 4.3', '/CreationDate': "D:20201026164238-07'00'", 'pdf_hyperlinks': {'_type': 'Set', 'elements': ['http://www.openssl.org/source/', 'http://www.openssl.org/source/openssl-fips-2.0.4.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.4.tar.gz', 'http://csrc.nist.gov/publications/nistpubs/800-38C/SP800-38C_updated-July20_2007.pdf', 'http://www.arm.com/products/processors/technologies/neon.php', 'http://www.openssl.org/source/openssl-fips-2.0.3.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.5.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.7.tar.gz', 'http://www.intel.com/support/processors/sb/CS-030123.htm?wapkw=sse2', 'http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.2.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.9.tar.gz', 'http://opensslfoundation.com/fips/verify.html', 'http://csrc.nist.gov/publications/nistpubs/800-67/SP800-67.pdf', 'http://www.openssl.org/source/openssl-fips-2.0.2.tar.gz', 'http://www.openssl.org/source/openssl-fips-2.0.5.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.3.tar.gz', 'http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf', 'http://www.openssl.org/source/openssl-fips-2.0.9.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.tar.gz', 'http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf', 'http://www.openssl.org/source/openssl-fips-2.0.1.tar.gz', 'http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-56A/SP800-56A_Revision1_Mar08-2007.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-90/SP800-90revised_March2007.pdf', 'http://www.openssl.org/source/openssl-fips-2.0.tar.gz', 'http://www.securenetterm.com/', 'http://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1_final.pdf', 'http://software.intel.com/en-us/articles/intel-advanced-encryption-standard-instructions-aes-ni/?wapkw=aes-ni', 'http://openssl.org/', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.1.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.8.tar.gz', 'http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-89/SP-800-89_November2006.pdf', 'http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf', 'http://www.openssl.org/source/openssl-fips-2.0.7.tar.gz', 'http://www.openssl.org/source/openssl-fips-2.0.6.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.6.tar.gz', 'http://www.openssl.org/source/openssl-fips-2.0.8.tar.gz']}}}.
  • The following properties were deleted: ['cert_id', 'algorithms', 'clean_cert_ids', 'st_metadata'].

  The computed heuristics were updated.

  • The following values were inserted: {'policy_prunned_references': {'_type': 'Set', 'elements': ['99', '98', '93', '86', '80', '84', '77', '81', '100', '87', '78', '91', '96', '101', '89', '92', '94', '79', '83', '88', '95', '90', '82']}, 'module_prunned_references': {'_type': 'Set', 'elements': ['1747']}, 'policy_processed_references': {'_type': 'sec_certs.sample.certificate.References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': {'_type': 'Set', 'elements': ['99', '98', '93', '86', '80', '84', '77', '81', '100', '87', '78', '91', '96', '101', '89', '92', '94', '79', '83', '88', '95', '90', '82']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['99', '98', '93', '86', '80', '84', '77', '81', '100', '87', '78', '91', '96', '101', '89', '92', '94', '79', '83', '88', '95', '90', '82']}}, 'module_processed_references': {'_type': 'sec_certs.sample.certificate.References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': {'_type': 'Set', 'elements': ['1747']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['1747']}}, 'direct_transitive_cves': None, 'indirect_transitive_cves': None}.
  • The algorithms property was set to {'_type': 'Set', 'elements': ['DSA#950', 'RSA#1718', 'AES#3351', 'SHS#2778', 'DRBG#784', 'ECDSA#664', 'ECDSA#413', 'CVL#85', 'HMAC#2134', 'DRBG#342', 'Triple-DES#1912', 'AES#2484', 'DSA#764', 'Triple-DES#1522', 'RSA#1273', 'HMAC#1526', 'CVL#496', 'SHS#2102']}.
  • The following properties were deleted: ['keywords', 'unmatched_algs', 'clean_cert_ids', 'st_references', 'web_references'].

  The state was updated.

  • The following values were inserted: {'module_download_ok': True, 'policy_download_ok': True, 'policy_convert_garbage': False, 'policy_convert_ok': True, 'module_extract_ok': True, 'policy_extract_ok': True, 'policy_pdf_hash': '87ebf260b7a3398ad5ba87a9f33c858339950f3479054ef243d8a4553283cb03', 'policy_txt_hash': 'bad2c0d7ab0d2d0228a3df856d52151daf11ed3aa8a4b34c02b84a7de595c721'}.
  • The following properties were deleted: ['sp_path', 'html_path', 'tables_done', 'file_status', 'txt_state'].
• 05.11.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web extraction data was updated.

  • The algorithms property was updated, with the {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#342', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1273', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2778', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1912', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2134', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2484', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#85', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#764', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#413', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1522', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#784', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1526', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1718', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#496', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#3351', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#664', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#950', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2102', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}]} values discarded.

  The computed heuristics were updated.

  • The algorithms property was updated, with the {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#342', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1273', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1912', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2778', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2134', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2102', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2484', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#85', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#413', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1522', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#784', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1718', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#664', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#496', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#3351', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1526', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#950', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#764', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}]} values discarded.
• 25.10.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The keywords property was updated, with the {'fips_cert_id': {'__update__': {'Cert': {'__delete__': ['#1']}}}, 'fips_certlike': {'__update__': {'Certlike': {'__update__': {'SHA2': 1, 'SHA1': 1, 'DSA (1024': 1}, '__delete__': ['PKCS1', 'AES GCM 2013', 'AES (128', 'AES (256', 'AES KAT 128', 'DRBG 2014', 'DES (3']}}}, 'symmetric_crypto': {'__update__': {'AES_competition': {'__update__': {'AES': {'__update__': {'AES': 20}}}, '__delete__': ['E2']}, 'DES': {'__delete__': ['DES']}, 'constructions': {'__update__': {'MAC': {'__update__': {'HMAC': 8}}}}}}, 'asymmetric_crypto': {'__update__': {'ECC': {'__update__': {'ECC': {'__update__': {'ECC': 4}}}}, 'FF': {'__update__': {'DH': {'__update__': {'DH': 10}}, 'DSA': {'__update__': {'DSA': 17}}}}}}, 'hash_function': {'__update__': {'SHA': {'__update__': {'SHA1': {'__update__': {'SHA1': 1}}, 'SHA2': {'__update__': {'SHA2': 1}}}, '__delete__': ['SHA3']}}}, 'crypto_scheme': {'__update__': {'KA': {'__delete__': ['KA']}}, '__delete__': ['MAC']}, 'crypto_protocol': {}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 19}}, 'RNG': {'__delete__': ['RBG']}}}, 'cipher_mode': {'__update__': {'ECB': {'__update__': {'ECB': 3}}, 'CBC': {'__update__': {'CBC': 3}}, 'CTR': {'__update__': {'CTR': 2}}, 'CFB': {'__update__': {'CFB': 3}}, 'OFB': {'__update__': {'OFB': 1}}, 'GCM': {'__update__': {'GCM': 6}}, 'XTS': {'__update__': {'XTS': 4}}}}, 'tee_name': {}, 'standard_id': {'__update__': {'FIPS': {'__update__': {'FIPS 198': 1}, '__delete__': ['FIPS 140', 'FIPS 186', 'FIPS 180']}, 'PKCS': {'__delete__': ['PKCS1']}}, '__delete__': ['NIST']}} data.
  • The algorithms property was set to {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4110', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 11', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 64', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '283', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '131', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2778', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 15', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '571', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '440', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '64', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '57', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '89', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1202', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 29', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '950', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 85', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1912', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2450', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '56', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 19', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '67', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '90', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2430', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 11', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2102', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1526', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4096', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '496', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '86', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 764', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3351', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2484', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2403', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 140', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 12', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 12', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1273', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'c 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2680', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1718', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1536', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 25', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1522', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1273', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 413', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '784', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3072', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2001', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1718', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2620', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 10', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 17', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '888', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 10', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '521', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 186', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 14', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '31', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 198', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1024', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2699', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '409', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '233', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1038', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 180', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '664', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 342', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '5504', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1363', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2603', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A\n2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2470', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2134', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 197', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 13', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '160', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 8', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '25616', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 8', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '38', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '8', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}]}.
  • The clean_cert_ids property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated, with the {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4110', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 11', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 64', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '283', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '131', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2778', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 15', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '571', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '440', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '64', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '57', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '89', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1202', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 29', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '950', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 85', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1912', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2450', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '56', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 19', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '67', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '90', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2430', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 11', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2102', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1526', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4096', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '496', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '86', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 764', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3351', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2484', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2403', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 140', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 12', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 12', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1273', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'c 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2680', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1718', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1536', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 25', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1522', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1273', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 413', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '784', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3072', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2001', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1718', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2620', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 10', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 17', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '888', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 10', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '521', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 186', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 14', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '31', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 198', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1024', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2699', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '409', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '233', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1038', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 180', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '664', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 342', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '5504', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1363', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2603', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A\n2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2470', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2134', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 197', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 13', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '160', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 8', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '25616', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 8', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '38', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '8', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}]} values added.
  • The clean_cert_ids property was updated.
  • The st_references property was updated, with the {'directly_referencing': {'_type': 'Set', 'elements': ['93', '95']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['93', '95']}} data.
  • The web_references property was updated, with the {'directly_referencing': {'_type': 'Set', 'elements': ['1747']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['1747']}} data.

  The state was updated.

  • The tables_done property was set to True.
• 08.10.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The computed heuristics were updated.

  • The st_references property was updated, with the {'directly_referencing': None, 'indirectly_referencing': None} data.
  • The web_references property was updated, with the {'directly_referencing': None, 'indirectly_referencing': None} data.
• 17.07.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web extraction data was updated.

  • This property was added with value {'_type': 'sec_certs.sample.fips.FIPSCertificate.WebData', 'module_name': 'Nimble Storage FIPS Object Module', 'standard': 'FIPS140-2', 'status': 'Historical', 'date_sunset': None, 'date_validation': ['2015-08-11', '2016-03-01', '2016-06-07', '2016-07-25', '2018-03-26', '2021-01-26'], 'level': '1', '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', 'exceptions': ['Roles, Services, and Authentication: Level 2', 'Physical Security: N/A', 'Design Assurance: Level 3', 'Mitigation of Other Attacks: N/A'], 'module_type': 'Software', 'embodiment': 'Multi Chip Standalone', 'algorithms': {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1912', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1747', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#85', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#413', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#496', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#342', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1273', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2484', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#764', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2134', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1522', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1718', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1526', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2778', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#3351', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#784', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#664', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#950', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2102', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}]}, 'tested_conf': ['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'], 'description': '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.', 'mentioned_certs': {'1747': {'count': 1}}, 'vendor': 'Nimble Storage, a Hewlett Packard Enterprise company', 'vendor_www': 'http://www.nimblestorage.com', 'lab': None, 'lab_nvlap': None, 'historical_reason': 'Moved to historical list due to dependency on certificate #1747', 'security_policy_www': 'https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp2422.pdf', 'certificate_www': 'https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/certificates/FIPS140ConsolidatedCertList0056.pdf', 'hw_version': None, 'fw_version': None, 'revoked_reason': None, 'revoked_link': None, 'sw_versions': '2.0.9', 'product_url': None}.

  The PDF extraction data was updated.

  • This property was added with value {'_type': 'sec_certs.sample.fips.FIPSCertificate.PdfData', 'cert_id': 2422, 'keywords': {'fips_cert_id': {'Cert': {'#764': 1, '#1273': 1, '#97': 1, '#98': 1, '#99': 1, '#100': 1, '#101': 1, '#96': 1, '#94': 1, '#95': 1, '#90': 2, '#91': 2, '#88': 1, '#89': 1, '#92': 1, '#93': 1, '#86': 1, '#87': 1, '#81': 1, '#82': 1, '#83': 1, '#84': 1, '#85': 1, '#79': 1, '#80': 1, '#77': 1, '#78': 1, '#1': 1}}, 'fips_security_level': {}, 'fips_certlike': {'Certlike': {'SHA2': 2, 'SHA1': 3, 'SHA224': 1, 'SHA256': 3, 'SHA384': 1, 'SHA512': 2, 'PKCS1': 6, 'PKCS#1': 2, 'AES GCM 2013': 1, 'AES 128/ 192/256': 1, 'AES 128/192/256 1202': 1, 'AES (128': 3, 'AES (256': 1, 'AES 128/192/256': 1, 'AES KAT 128': 1, 'AES, 256': 1, 'DRBG 2014': 1, 'DRBG2': 1, 'DES (3': 2, 'DSA (1024': 3, 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64bit on ARMv8 20140104 Addition of new platform #96, FreeBSD 8.4 on x86 without AESNI 20140730 Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and reremoval of Dual EC DRBG 20140728 Changed processor names for platforms #90, #91 20140711 Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86 20140612 Temporarily remove misplaced platform, move Dual EC DRBG to the Non Approved Table 4c 20140529 Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED ASTSeries (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) 20140512 Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are nonApproved per the SP 800131A transition 20131108 Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AESNI 20131101 Added two platforms #77, #78 iOS 6.0 with/without NEON 20131002 Added six platforms (Linux 3.4 x86 virtualized under XenSource/VMware/Hyper V, with/without AESNI) Page 4 of 29 Nimble Storage FIPS 1402 Security Policy Updated URL in Appendix A footnote 20130829 Added new sponsor acknowledgment 20130814 Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms 20130724 Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 20130609 Added QNX, iOS 6.1, eCos for revision 2.0.5 20130501 Added OpenWRT 2.6 for revision 2.0.4 20130301 Added VMware Horizon Mobile 1.3, Apple OS X 10.7 , Apple iOS 5.0 20130223 Added WinEC7 and Android 4.0 for revision 2.0.3 20130214 Table 5: Removed references to nonexistent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM 20130128 Added four platforms: Android 4.1 and Android 4.2 with and without NEON 20130108 Reworded section 8 20130103 Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AESNI. 20121208 Note EC DH Key Agreement and RSA Key Wrapping strength. 20121010 Added NetBSD 5.1 on PowerPCe500, NetBSD 5.1 on Intel Xeon 5500 (x8664) for revision 2.0.2 20110702 Added DSP Media Framework, Linux 2.6/Freescale PowerPCe500, Android 4.0 20110615 Added iOS, WinCE 5, WinCE 6 OEs References Reference Full Specification Name [ANS X9.31] Digital Signatures Using Reversible Public Key Cryptography for the Financial Services Industry (rDSA) [FIPS 1402] Security Requirements for Cryptographic modules, May 25, 2001 [FIPS 1803] Secure Hash Standard [FIPS 1864] Digital Signature Standard [FIPS 197] Advanced Encryption Standard [FIPS 1981] The KeyedHash Message Authentication Code (HMAC) [SP 80038B] Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication [SP 80038C] Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality Page 5 of 29 Nimble Storage FIPS 1402 Security Policy Reference Full Specification Name [SP 80038D] Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC [SP 80056A] Recommendation for PairWise Key Establishment Schemes Using Discrete Logarithm Cryptography [SP 800 67R1] Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher [SP 80089] Recommendation for Obtaining Assurances for Digital Signature Applications [SP 80090] Recommendation for Random Number Generation Using Deterministic Random Bit Generators [SP 800 131A] Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths Page 6 of 29 Nimble Storage FIPS 1402 Security Policy Table of Contents 1 Introduction.........................................................................................................................7 2 Tested Configurations.........................................................................................................9 3 Ports and Interfaces ............................................................................................................13 4 Modes of Operation and Cryptographic Functionality ......................................................14 4.1 Critical Security Parameters and Public Keys............................................................18 5 Roles, Authentication and Services ...................................................................................21 6 Selftest...............................................................................................................................23 7 Operational Environment....................................................................................................25 8 Mitigation of other Attacks.................................................................................................26 Appendix A Installation and Usage Guidance.......................................................................27 Appendix B Controlled Distribution File Fingerprint...........................................................30 Appendix C Compilers..........................................................................................................33 Page 7 of 29 Nimble Storage FIPS 1402 Security Policy 1 Introduction This document is the nonproprietary security policy for the Nimble Storage FIPS Object Module, hereafter referred to as the Module, which is build from the OpenSSL FIPS Object Module source code according to the the instructions in Appendix A. The Module is a software library providing a Clanguage application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 1402 as a software module, multichip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the fipscanister object module, a single object module file named fipscanister.o compiled on Linux®1 . The Module performs no communications other than with the calling application (the process that invokes the Module services). The FIPS 1402 security levels for the Module are as follows: Security Requirement Security Level Cryptographic Module Specification 1 Cryptographic Module Ports and Interfaces 1 Roles, Services, and Authentication 2 Finite State Model 1 Physical Security NA Operational Environment 1 Cryptographic Key Management 1 EMI/EMC 1 SelfTests 1 Design Assurance 3 Mitigation of Other Attacks NA Table 1 – Security Level of Security Requirements The Module’s software version for this validation is 2.0.9. It is build from the 2.0.9 version of the OpenSSL FIPS Object Module source code. 1 Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Page 8 of 29 Nimble Storage FIPS 1402 Security Policy Page 9 of 29 Figure 1 Module Block Diagram Nimble Storage FIPS 1402 Security Policy 2 Tested Configurations # Operational Environment Processor Optimiz ations (Target) EC B 1 Linux 2.6 Intel E52403V2 (x86_64) AESNI BKP U2 2 Linux 2.6 Intel E52450V2 (x86_64) AESNI BKP U2 3 Linux 2.6 Intel E52470V2 (x86_64) AESNI BKP U2 4 Linux 3.4 64bit under Citrix XenServer Intel Xeon E52430L (x86) None BKP U2 5 Linux 2.6 Intel E52603V3 (x86_64) AESNI BKP U2 6 Linux 2.6 Intel E52620V3 (x86_64) AESNI BKP U2 7 Linux 2.6 Intel E52680V3 (x86_64) AESNI BKP U2 8 Linux 2.6 Intel E52699V3 (x86_64) AESNI BKP U2 9 Linux 4.4 Intel E5504 (x86_64) None BKP U2 10 Linux 4.4 Intel E52403V2 (x86_64) AESNI BKP U2 11 Linux 4.4 Intel E52680V3 (x86_64) AESNI BKP U2 12 Linux 4.4 Intel Xeon Silver 4110 (x86_64) AESNI BKP U2 Table 2 Tested Configurations (B = Build Method; EC = Elliptic Curve Support). The EC column indicates support for prime curve only (P), or all NIST defined B, K, and P curves (BKP). See Appendix A for additional information on build method and optimizations. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. Page 10 of 29 Nimble Storage FIPS 1402 Security Policy 3 Ports and Interfaces The physical ports of the Module are the same as the computer system on which it is executing. The logical interface is a Clanguage application program interface (API). Logical interface type Description Control input API entry point and corresponding stack parameters Data input API entry point data input stack parameters Status output API entry point return values and status stack parameters Data output API entry point data output stack parameters Table 3 Logical interfaces As a software module, control of the physical ports is outside module scope. However, when the module is performing selftests, or is in an error state, all output on the logical data output interface is inhibited. The module is singlethreaded and in error scenarios returns only an error value (no data output is returned). Page 11 of 29 Nimble Storage FIPS 1402 Security Policy 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 1402 Approved mode. Tables 4a and 4b list the Approved and Nonapproved but Allowed algorithms, respectively. Function Algorithm Options Cert # Random Number Generation; Symmetric key generation [SP 80090A] DRBG2 Prediction resistance supported for all variations Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function 342, 784 Encryption, Decryption and CMAC [SP 80067] 3Key TripleDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify 1522, 1912 [FIPS 197] AES 128/ 192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify 2484, 3351 [SP 80038B] CMAC [SP 80038C] CCM [SP 80038D] GCM [SP 80038E] XTS Message Digests [FIPS 1803] SHA1, SHA2 (224, 256, 384, 512) 2102, 2778 Keyed Hash [FIPS 198] HMAC SHA1, SHA2 (224, 256, 384, 512) 1526, 2134 Digital Signature and Asymmetric Key Generation [FIPS 1862] RSA SigVer9.31 (1024/1536/2048/3072/4096 with SHA1/256/384/512) SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA 1/SHA2 sizes) 1273, 1718 [FIPS 1864] RSA SigGen9.31 (2048/3072/4096 with SHA 256/384/512) SigGenPKCS1.5, SigGenPSS (2048/3072/4096 with all SHA2 sizes) 1718 [FIPS 1864] DSA PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA2 sizes) 764, 950 2 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP80090] and [SP80057]. Page 12 of 29 Nimble Storage FIPS 1402 Security Policy [FIPS 1864] ECDSA PKG: CURVES( P224 P256 P384 P521 K 224 K256 K384 K521 B224 B256 B384 B 521 ExtraRandomBits TestingCandidates ) PKV: CURVES( ALLP ALLK ALLB ) SigGen: CURVES( P224: (SHA224, 256, 384, 512) P256: (SHA224, 256, 384, 512) P384: (SHA224, 256, 384, 512) P521: (SHA224, 256, 384, 512) K233: (SHA224, 256, 384, 512) K283: (SHA224, 256, 384, 512) K409: (SHA224, 256, 384, 512) K571: (SHA224, 256, 384, 512) B233: (SHA224, 256, 384, 512) B283: (SHA224, 256, 384, 512) B409: (SHA 224, 256, 384, 512) B571: (SHA224, 256, 384, 512) ) SigVer: CURVES( P192: (SHA1, 224, 256, 384, 512) P224: (SHA1, 224, 256, 384, 512) P 256: (SHA1, 224, 256, 384, 512) P384: (SHA 1, 224, 256, 384, 512) P521: (SHA1, 224, 256, 384, 512) K163: (SHA1, 224, 256, 384, 512) K233: (SHA1, 224, 256, 384, 512) K283: (SHA1, 224, 256, 384, 512) K409: (SHA1, 224, 256, 384, 512) K571: (SHA1, 224, 256, 384, 512 B163: (SHA1, 224, 256, 384, 512) B 233: (SHA1, 224, 256, 384, 512) B283: (SHA 1, 224, 256, 384, 512) B409: (SHA1, 224, 256, 384, 512) B571: (SHA1, 224, 256, 384, 512) ) 413, 664 ECC CDH (CVL) [SP 80056A] (§5.7.1.2) All NIST defined B, K and P curves except sizes 163 and 192 85, 496 Table 4a – FIPS Approved Cryptographic Functions The Module supports only NIST defined curves for use with ECDSA and ECC CDH. The Module supports two operational environment configurations for elliptic curve; NIST prime curve only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Category Algorithm Description Key Agreement EC DH Noncompliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. Key Encryption, Decryption RSA The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 80056B compliance, and no CSPs are established into or exported out of the module using these services. Table 4b – NonFIPS Approved But Allowed Cryptographic Functions Page 13 of 29 Nimble Storage FIPS 1402 Security Policy Function Algorithm Options Cert # Random Number Generation; Symmetric key generation [ANS X9.31] RNG AES 128/192/256 1202, 1363 Digital Signature and Asymmetric Key Generation [FIPS 1862] RSA GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/4096 with SHA1) 1273 [FIPS 1862] DSA PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) 764 [FIPS 1864] DSA PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) 764 [FIPS 1862] ECDSA PKG: CURVES( P192 K163 B163 ) SIG(gen): CURVES( P192 P224 P256 P384 P521 K163 K233 K283 K409 K571 B163 B233 B283 B409 B571 ) 413 [FIPS 1864] ECDSA PKG: CURVES( P192 K163 B163 ) SigGen: CURVES( P192: (SHA1, 224, 256, 384, 512) P224:(SHA1) P256:(SHA1) P384: (SHA1) P521:(SHA1) K163: (SHA1, 224, 256, 384, 512) K233:(SHA1) K283:(SHA1) K409:(SHA1) K571:(SHA1) B163: (SHA1, 224, 256, 384, 512) B233:(SHA1) B283: (SHA1) B409:(SHA1) B571:(SHA1) ) 413 ECC CDH (CVL) [SP 80056A] (§5.7.1.2) All NIST Recommended B, K and P curves sizes 163 and 192 85 Table 4c – FIPS NonApproved Cryptographic Functions These algorithms shall not be used when operating in the FIPS Approved mode of operation. EC DH Key Agreement provides a maximum of 256 bits of security strength. RSA Key Wrapping provides a maximum of 256 bits of security strength. The Module requires an initialization sequence (see IG 9.5): the calling application invokes FIPS_mode_set()3 , which returns a “1” for success and “0” for failure. If FIPS_mode_set() fails then all cryptographic services fail from then on. The application can test to see if FIPS mode has been successfully performed. The Module is a cryptographic engine library, which can be used only in conjunction with additional software. Aside from the use of the NIST defined elliptic curves as trusted third party domain parameters, all other FIPS 1864 assurances are outside the scope of the Module, and are the responsibility of the calling process. 3 The function call in the Module is FIPS_module_mode_set() which is typically used by an application via the FIPS_mode_set() wrapper function. Page 14 of 29 Nimble Storage FIPS 1402 Security Policy 4.1 Critical Security Parameters and Public Keys All CSPs used by the Module are described in this section. All access to these CSPs by Module services are described in Section 4. The CSP names are generic, corresponding to API parameter data structures. CSP Name Description RSA SGK RSA (1024 to 16384 bits) signature generation key RSA KDK RSA (1024 to 16384 bits) key decryption (private key transport) key DSA SGK [FIPS 1864] DSA (1024/2048/3072) signature generation key ECDSA SGK ECDSA (All NIST defined B, K, and P curves) signature generation key EC DH Private EC DH (All NIST defined B, K, and P curves) private key agreement key. AES EDK AES (128/192/256) encrypt / decrypt key AES CMAC AES (128/192/256) CMAC generate / verify key AES GCM AES (128/192/256) encrypt / decrypt / generate / verify key AES XTS AES (256/512) XTS encrypt / decrypt key TripleDES EDK TripleDES (3Key) encrypt / decrypt key TripleDES CMAC TripleDES (3Key) CMAC generate / verify key HMAC Key Keyed hash key (160/224/256/384/512) Hash_DRBG CSPs V (440/888 bits) and C (440/888 bits), entropy input (length dependent on security strength) HMAC_DRBG CSPs V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits), entropy input (length dependent on security strength) CTR_DRBG CSPs V (128 bits) and Key (AES 128/192/256), entropy input (length dependent on security strength) COADDigest Precalculated HMACSHA1 digest used for Crypto Officer role authentication UserADDigest Precalculated HMACSHA1 digest used for User role authentication Table 4.1a – Critical Security Parameters Authentication data is loaded into the module during the module build process, performed by an authorized operator (Crypto Officer), and otherwise cannot be accessed. The module does not output intermediate key generation values. CSP Name Description RSA SVK RSA (1024 to 16384 bits) signature verification public key RSA KEK RSA (1024 to 16384 bits) key encryption (public key transport) key DSA SVK [FIPS 1864] DSA (1024/2048/3072) signature verification key or [FIPS 1862] DSA (1024) signature verification key ECDSA SVK ECDSA (All NIST defined B, K and P curves) signature verification key EC DH Public EC DH (All NIST defined B, K and P curves) public key agreement key. Page 15 of 29 Nimble Storage FIPS 1402 Security Policy Table 4.1b – Public Keys For all CSPs and Public Keys: Storage: RAM, associated to entities by memory location. The Module stores DRBG state values for the lifetime of the DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of DRBG state values used for the Modules\' default key generation service. Generation: The Module implements SP 80090 compliant DRBG services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry: All CSPs enter the Module’s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output: The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Destruction: Zeroization of sensitive data is performed automatically by API function calls for temporarily stored CSPs. In addition, the module provides functions to explicitly destroy CSPs related to random number generation services. The calling application is responsible for parameters passed in and out of the module. Private and secret keys as well as seeds and entropy input are provided to the Module by the calling application, and are destroyed when released by the appropriate API function calls. Keys residing in internally allocated data structures (during the lifetime of an API call) can only be accessed using the Module defined API. The operating system protects memory and process space from unauthorized access. Only the calling application that creates or imports keys can use or export such keys. All API functions are executed by the invoking calling application in a nonoverlapping sequence such that no two API functions will execute concurrently. An authorized application as user (CryptoOfficer and User) has access to all key data generated during the operation of the Module. In the event Module power is lost and restored the calling application must ensure that any AESGCM keys used for encryption or decryption are redistributed. Module users (the calling applications) shall use entropy sources that meet the security strength required for the random number generation mechanism: 128 bits as shown in [SP 80090] Table 2 (Hash_DRBG, HMAC_DRBG), and Table 3 (CTR_DRBG). This entropy is supplied by means of callback functions. Those functions must return an error if the minimum entropy strength cannot be met. Page 16 of 29 Nimble Storage FIPS 1402 Security Policy 5 Roles, Authentication and Services The Module implements the required User and Crypto Officer roles and requires authentication for those roles. Only one role may be active at a time and the Module does not allow concurrent operators. The User or Crypto Officer role is assumed by passing the appropriate password to the FIPS_module_mode_set() function. The password values may be specified at build time and must have a minimum length of 16 characters. Any attempt to authenticate with an invalid password will result in an immediate and permanent failure condition rendering the Module unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the Module during the Module build process, performed by the Crypto Officer, and otherwise cannot be accessed. Since minimum password length is 16 characters, the probability of a random successful authentication attempt in one try is a maximum of 1/25616 , or less than 1/1038 . The Module permanently disables further authentication attempts after a single failure, so this probability is independent of time. Both roles have access to all of the services provided by the Module. User Role (User): Loading the Module and calling any of the API functions. Crypto Officer Role (CO): Installation of the Module on the host computer system and calling of any API functions. All services implemented by the Module are listed below, along with a description of service CSP access. Service Role Description Initialize User, CO Module initialization. Does not access CSPs. Selftest User, CO Perform self tests (FIPS_selftest). Does not access CSPs. Show status User, CO Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. Zeroize User, CO Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. Random number generation User, CO Used for random number and symmetric key generation. Seed or reseed an DRBG instance Determine security strength of a DRBG instance Page 17 of 29 Nimble Storage FIPS 1402 Security Policy Service Role Description Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. Asymmetric key generation User, CO Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP80090 Symmetric encrypt/decrypt User, CO Used to encrypt or decrypt data. Executes using AES EDK, TripleDES EDK (passed in by the calling process). Symmetric digest User, CO Used to generate or verify data integrity with CMAC. Executes using AES CMAC, TripleDES, CMAC (passed in by the calling process). Message digest User, CO Used to generate a SHA1 or SHA2 message digest. Does not access CSPs. Keyed Hash User, CO Used to generate or verify data integrity with HMAC. Executes using HMAC Key (passed in by the calling process). Key transport4 User, CO Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). Key agreement User, CO Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). Digital signature User, CO Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). Utility User, CO Miscellaneous helper functions. Does not access CSPs. Table 5 Services and CSP Access 6 Selftest The Module performs the selftests listed below on invocation of Initialize or Selftest. Algorithm Type Test Attributes Software integrity KAT HMACSHA1 HMAC KAT One KAT per SHA1, SHA224, SHA256, SHA384 and SHA512 Per IG 9.3, this testing covers SHA POST requirements. AES KAT Separate encrypt and decrypt, ECB mode, 128 bit key length AES CCM KAT Separate encrypt and decrypt, 192 key length 4 "Key transport" can refer to a) moving keys in and out of the module or b) the use of keys by an external application. The latter definition is the one that applies to the Nimble Storage FIPS Object Module. Page 18 of 29 Nimble Storage FIPS 1402 Security Policy Algorithm Type Test Attributes AES GCM KAT Separate encrypt and decrypt, 256 key length XTSAES KAT 128, 256 bit key sizes to support either the 256bit key size (for XTSAES128) or the 512bit key size (for XTSAES256) AES CMAC KAT Sign and verify CBC mode, 128, 192, 256 key lengths TripleDES KAT Separate encrypt and decrypt, ECB mode, 3Key TripleDES CMAC KAT CMAC generate and verify, CBC mode, 3Key RSA KAT Sign and verify using 2048 bit key, SHA256, PKCS#1 DSA PCT Sign and verify using 2048 bit key, SHA384 DRBG KAT CTR_DRBG: AES, 256 bit with and without derivation function HASH_DRBG: SHA256 HMAC_DRBG: SHA256 ECDSA PCT Keygen, sign, verify using P224, K233 and SHA512. The K233 selftest is not performed for operational environments that support prime curve only (see Table 2). ECC CDH KAT Shared secret calculation per SP 80056A §5.7.1.2, IG 9.6 Table 6a Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency test) The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMACSHA1 of the Module distribution file as tested by the CMT Laboratory and listed in Appendix A is verified during installation of the Module file as described in Appendix A. The FIPS_mode_set()5 function performs all powerup selftests listed above with no operator intervention required, returning a “1” if all powerup selftests succeed, and a “0” otherwise. If any component of the powerup selftest fails an internal flag is set to prevent subsequent invocation of any cryptographic function calls. The module will only enter the FIPS Approved mode if the module is reloaded and the call to FIPS_mode_set()5 succeeds. The powerup selftests may also be performed ondemand by calling FIPS_selftest(), which returns a “1” for success and “0” for failure. Interpretation of this return code is the responsibility of the calling application. The Module also implements the following conditional tests: Algorithm Test DRBG Tested as required by [SP80090] Section 11 DRBG FIPS 1402 continuous test for stuck fault DSA Pairwise consistency test on each generation of a key pair ECDSA Pairwise consistency test on each generation of a key pair 5 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 19 of 29 Nimble Storage FIPS 1402 Security Policy Algorithm Test RSA Pairwise consistency test on each generation of a key pair Table 6b Conditional Tests In the event of a DRBG selftest failure the calling application must uninstantiate and re instantiate the DRBG per the requirements of [SP 80090]; this is not something the Module can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. The Module supports two operational environment configurations for elliptic curve: NIST prime curves only (listed in Table 2 with the EC column marked "P") and all NIST defined curves (listed in Table 2 with the EC column marked "BKP"). Page 20 of 29 Nimble Storage FIPS 1402 Security Policy 7 Operational Environment The tested operating systems segregate user processes into separate process spaces. Each process space is logically separated from all other processes by the operating system software and hardware. The Module functions entirely within the process space of the calling application, and implicitly satisfies the FIPS 1402 requirement for a single user mode of operation. Page 21 of 29 Nimble Storage FIPS 1402 Security Policy 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 1402. Page 22 of 29 Nimble Storage FIPS 1402 Security Policy Appendix A Installation and Usage Guidance The test platforms represent different combinations of installation instructions. For each platform there is a build system, the host providing the build environment in which the installation instructions are executed, and a target system on which the generated object code is executed. The build and target systems may be the same type of system or even the same device, or may be different systems – the Module supports crosscompilation environments. Each of these command sets are relative to the top of the directory containing the uncompressed and expanded contents of the distribution files opensslfips2.0.9.tar.gz (all NIST defined curves as listed in Table 2 with the EC column marked "BKP") or opensslfipsecp2.0.9.tar.gz (NIST prime curves only as listed in Table 2 with the EC column marked "P"). The command sets are: U1: ./config no-asm make make install U2: ./config make make install W1: ms\\do_fips no-asm W2: ms\\do_fips Installation instructions 1. Download and copy the distribution file to the build system. These files can be downloaded from http://www.openssl.org/source/. 2. Verify the HMACSHA1 digest of the distribution file; see Appendix B. An independently acquired FIPS 1402 validated implemention of SHA1 HMAC must be used for this digest verification. Note that this verification can be performed on any convenient system and not necessarily on the specific build or target system. Alternatively, a copy of the distribution on physical media can be obtained from OSF6 . 3. Unpack the distribution 6 For some prospective users the acquisition, installation, and configuration of a suitable FIPS 1402 validated product may not be convenient. OSF will on request mail a CD containing the source code distribution, via USPS or international post. A distribution file received by that means need not be verified by a FIPS 1402 validated implementation of HMACSHA1. For instructions on requesting this CD see http://opensslfoundation.com/fips/verify.html. Page 23 of 29 Nimble Storage FIPS 1402 Security Policy gunzip -c openssl-fips-2.0.9.tar.gz | tar xf - cd openssl-fips-2.0.9 or gunzip -c openssl-fips-ecp-2.0.9.tar.gz | tar xf - cd openssl-fips-ecp-2.0.9 4. Execute one of the installation command sets U1, W1, U2, W2 as shown above. No other command sets shall be used. 5. The resulting fipscanister.o or fipscanister.lib file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set()7 function. Note that failure to use one of the specified commands sets exactly as shown will result in a module that cannot be considered compliant with FIPS 1402. Linking the Runtime Executable Application Note that applications interfacing with the FIPS Object Module are outside of the cryptographic boundary. When linking the application with the FIPS Object Module two steps are necessary: 1. The HMACSHA1 digest of the FIPS Object Module file must be calculated and verified against the installed digest to ensure the integrity of the FIPS object module. 2. A HMACSHA1 digest of the FIPS Object Module must be generated and embedded in the FIPS Object Module for use by the FIPS_mode_set()7 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the FIPS Object Module and to generate the new HMACSHA1 digest for the runtime executable application. Failure to embed the digest in the executable object will prevent initialization of FIPS mode. At runtime the FIPS_mode_set()7 function compares the embedded HMACSHA1 digest with a digest generated from the FIPS Object Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. Optimization The “asm” designation means that assembler language optimizations were enabled when the binary code was built, “noasm” means that only C language code was compiled. For OpenSSL with x86 there are three possible optimization levels: 1. No optimization (plain C) 2. SSE2 optimization 7 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 24 of 29 Nimble Storage FIPS 1402 Security Policy 3. AESNI+PCLMULQDQ+SSSE3 optimization Other theoretically possible combinations (e.g. AESNI only, or SSE3 only) are not addressed individually, so that a processor which does not support all three of AESNI, PCLMULQDQ, and SSSE3 will fall back to SSE2 optimization. For more information, see: http://www.intel.com/support/processors/sb/CS030123.htm?wapkw=sse2 http://software.intel.com/enus/articles/inteladvancedencryptionstandardinstructions aesni/?wapkw=aesni For OpenSSL with ARM there are two possible optimization levels: 1. Without NEON 2. With NEON (ARM7 only) For more information, see http://www.arm.com/products/processors/technologies/neon.php Page 25 of 29 Nimble Storage FIPS 1402 Security Policy Appendix B Controlled Distribution File Fingerprint The OpenSSL FIPS Object Module v2.0.9 consists of the FIPS Object Module (the fipscanister.o or fipscanister.lib contiguous unit of binary object code) generated from the specific source files. For all NIST defined curves (listed in Table 2 with the EC column marked "BKP") the source files are in the specific special OpenSSL distribution opensslfips2.0.9.tar.gz with HMAC SHA1 digest of 54552e9a3ed8d1561341e8945fcdec55af961322 located at http://www.openssl.org/source/opensslfips2.0.9.tar.gz. The openssl command from a version of OpenSSL that incorporates a previously validated version of the module may be used: openssl sha1 -hmac etaonrishdlcupfm openssl-fips-2.0.9.tar.gz For NIST prime curves only (listed in Table 2 with the EC column marked "P") the source files are in the specific special OpenSSL distribution opensslfipsecp2.0.9.tar.gz with HMACSHA1 digest of 91d267688713c920f85bc5e69c8b5d34e1112672 located at http://www.openssl.org/source/opensslfipsecp2.0.9.tar.gz. Note this is from the previous revision of the FIPS Object Module as no modifications relevant to NIST prime curves only were introduced in revision 2.0.9. The set of files specified in this tar file constitutes the complete set of source files of this module. There shall be no additions, deletions, or alterations of this set as used during module build. The OpenSSL distribution tar file (and patch file if used) shall be verified using the above HMAC SHA1 digest(s). The arbitrary 16 byte key of: 65 74 61 6f 6e 72 69 73 68 64 6c 63 75 70 66 6d (equivalent to the ASCII string "etaonrishdlcupfm") is used to generate the HMACSHA1 value for the FIPS Object Module integrity check. The functionality of all earlier revisions of the FIPS Object Module are subsumed by this latest revision, so there is no reason to use older revisions for any new deployments. However, older revisions remain valid. The source distribution files and corresponding HMACSHA1 digests are listed below: opensslfips2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.8.tar.gz Page 26 of 29 Nimble Storage FIPS 1402 Security Policy Digest: 7f486fbb598f3247ab9db10c1308f1c19f384671 opensslfipsecp2.0.8.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.8.tar.gz Digest: 7a5f40ef8cebe959372d16e26391fcf23689209b opensslfips2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.7.tar.gz Digest: 295064925a6d95271e2fa2920181ec060f95c7ab opensslfipsecp2.0.7.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.7.tar.gz Digest: dddfdc78c7e827c61fe92bd4817a7f2c3e67153 opensslfips2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.6.tar.gz Digest: 2b8d831df22d4dfe6169aa2a8e74c35484c26c21 opensslfipsecp2.0.6.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.6.tar.gz Digest: 852f43cd9ae1bd2eba60e4f9f1f266d3c16c0319 opensslfips2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.5.tar.gz Digest: 8b44f2a43d098f6858eb1ebe77b73f8f027a9c29 opensslfipsecp2.0.5.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.5.tar.gz Digest: 148e4e127ffef1df80c0ed61bae35b07ec7b7b36 opensslfips2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.4.tar.gz Digest: eaa5f86dab2c5da7086aec4786bce27d3b3c1b8a opensslfipsecp2.0.4.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.4.tar.gz Digest: 13302f75c82c8b482c9ac96828984a270a45c284 opensslfips2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.3.tar.gz Digest: 5dfe03bc3f57c2862ea97823ea3111d7faf711b2 Page 27 of 29 Nimble Storage FIPS 1402 Security Policy opensslfipsecp2.0.3.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.3.tar.gz Digest: 9d6b21218d7d5480aa0add68e682d321e3ffbfa7 opensslfips2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.2.tar.gz Digest: e099d5096eb69c2dd8591379f38b985801188663 opensslfipsecp2.0.2.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.2.tar.gz Digest: 887fa6802c253c32e6c4c83b7a091118fa8c6217 opensslfips2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.1.tar.gz. Digest: 1e05b021fdcd6e77c6155512bbce2d0cbc725aec opensslfipsecp2.0.1.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.1.tar.gz. Digest: af82c8ebb9d3276be11feffd35e6b55bd0d1839f opensslfips2.0.tar.gz URL: http://www.openssl.org/source/opensslfips2.0.tar.gz. Digest: 2cdd29913c6523df8ad38da11c342b80ed3f1dae opensslfipsecp2.0.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.tar.gz. Digest: e8d5ee306425b278bf6c8b077dae8e4a542e8215 Page 28 of 29 Nimble Storage FIPS 1402 Security Policy Appendix C Compilers This appendix lists the specific compilers used to generate the Module for the respective Operational Environments. Note this list does not imply that use of the Module is restricted to only the listed compiler versions, only that the use of other versions has not been confirmed to produce a correct result. # Operational Environment Compiler 1 Linux 2.6 gcc 4.1.2 2 Linux 2.6 gcc 4.1.2 3 Linux 2.6 gcc 4.1.2 4 Linux 3.4 gcc 4.8.0 5 Linux 2.6 gcc 4.1.2 6 Linux 2.6 gcc 4.1.2 7 Linux 2.6 gcc 4.1.2 8 Linux 2.6 gcc 4.1.2 9 Linux 4.4 gcc 4.1.2 10 Linux 4.4 gcc 4.1.2 11 Linux 4.4 gcc 4.1.2 12 Linux 4.4 gcc 4.1.2 Table C Compilers Page 29 of 29': 1}}, 'vendor': {}, 'eval_facility': {}, 'symmetric_crypto': {'AES_competition': {'AES': {'AES': 42}, 'E2': {'E2': 2}}, 'DES': {'DES': {'DEA': 1, 'DES': 9}, '3DES': {'TDEA': 1}}, 'constructions': {'MAC': {'HMAC': 28, 'CMAC': 15}}}, 'asymmetric_crypto': {'ECC': {'ECDSA': {'ECDSA': 16}, 'ECC': {'ECC': 6}}, 'FF': {'DH': {'DH': 16}, 'DSA': {'DSA': 34}}}, 'pq_crypto': {}, 'hash_function': {'SHA': {'SHA1': {'SHA1': 3}, 'SHA2': {'SHA224': 1, 'SHA256': 3, 'SHA384': 1, 'SHA512': 2, 'SHA2': 6}, 'SHA3': {'SHA3': 1}}}, 'crypto_scheme': {'MAC': {'MAC': 44}, 'KA': {'KA': 15, 'Key Agreement': 3, 'Key agreement': 2}}, 'crypto_protocol': {'TLS': {'SSL': {'SSL': 15}}}, 'randomness': {'PRNG': {'DRBG': 37}, 'RNG': {'RNG': 2, 'RBG': 37}}, 'cipher_mode': {'ECB': {'ECB': 4}, 'CBC': {'CBC': 4}, 'CTR': {'CTR': 7}, 'CFB': {'CFB': 4}, 'OFB': {'OFB': 2}, 'GCM': {'GCM': 7}, 'CCM': {'CCM': 4}, 'XTS': {'XTS': 7}}, 'ecc_curve': {}, 'crypto_engine': {}, 'tls_cipher_suite': {}, 'crypto_library': {'OpenSSL': {'OpenSSL': 15}}, 'vulnerability': {}, 'side_channel_analysis': {}, 'device_model': {}, 'tee_name': {'IBM': {'SE': 6}}, 'os_name': {}, 'cplc_data': {}, 'ic_data_group': {}, 'standard_id': {'FIPS': {'FIPS 140-2': 1, 'FIPS 140': 39, 'FIPS 186': 15, 'FIPS 180': 2, 'FIPS 197': 2, 'FIPS 198': 2}, 'NIST': {'SP 805-7': 1}, 'PKCS': {'PKCS1': 3, 'PKCS#1': 1}}, 'javacard_version': {}, 'javacard_api_const': {}, 'javacard_packages': {}, 'certification_process': {}}, 'algorithms': {'_type': 'Set', 'elements': []}, 'clean_cert_ids': {'#98': 1, '#99': 1, '#100': 1, '#101': 1, '#96': 1, '#94': 1, '#95': 1, '#90': 2, '#91': 2, '#88': 1, '#89': 1, '#92': 1, '#93': 1, '#86': 1, '#87': 1, '#81': 1, '#82': 1, '#83': 1, '#84': 1, '#79': 1, '#80': 1, '#77': 1, '#78': 1}, 'st_metadata': {'pdf_file_size_bytes': 744852, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 29, '/Author': 'CPUBuilders Customer', '/Creator': 'Writer', '/Producer': 'LibreOffice 4.3', '/CreationDate': "D:20201026164238-07'00'", 'pdf_hyperlinks': {'_type': 'Set', 'elements': ['http://www.openssl.org/source/', 'http://www.openssl.org/source/openssl-fips-2.0.4.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.4.tar.gz', 'http://csrc.nist.gov/publications/nistpubs/800-38C/SP800-38C_updated-July20_2007.pdf', 'http://www.arm.com/products/processors/technologies/neon.php', 'http://www.openssl.org/source/openssl-fips-2.0.3.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.5.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.7.tar.gz', 'http://www.intel.com/support/processors/sb/CS-030123.htm?wapkw=sse2', 'http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.2.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.9.tar.gz', 'http://opensslfoundation.com/fips/verify.html', 'http://csrc.nist.gov/publications/nistpubs/800-67/SP800-67.pdf', 'http://www.openssl.org/source/openssl-fips-2.0.2.tar.gz', 'http://www.openssl.org/source/openssl-fips-2.0.5.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.3.tar.gz', 'http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf', 'http://www.openssl.org/source/openssl-fips-2.0.9.tar.gz', 'http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.tar.gz', 'http://csrc.nist.gov/publications/nistpubs/800-90/SP800-90revised_March2007.pdf', 'http://www.securenetterm.com/', 'http://csrc.nist.gov/publications/nistpubs/800-56A/SP800-56A_Revision1_Mar08-2007.pdf', 'http://www.openssl.org/source/openssl-fips-2.0.tar.gz', 'http://www.openssl.org/source/openssl-fips-2.0.1.tar.gz', 'http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf', 'http://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1_final.pdf', 'http://software.intel.com/en-us/articles/intel-advanced-encryption-standard-instructions-aes-ni/?wapkw=aes-ni', 'http://openssl.org/', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.1.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.8.tar.gz', 'http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-89/SP-800-89_November2006.pdf', 'http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf', 'http://www.openssl.org/source/openssl-fips-2.0.7.tar.gz', 'http://www.openssl.org/source/openssl-fips-2.0.6.tar.gz', 'http://www.openssl.org/source/openssl-fips-ecp-2.0.6.tar.gz', 'http://www.openssl.org/source/openssl-fips-2.0.8.tar.gz']}}}.

  The _type was updated.

  • The new value is sec_certs.sample.fips.FIPSCertificate.

  The computed heuristics were updated.

  • The following values were inserted: {'clean_cert_ids': {'#95': 1, '#89': 1, '#93': 1}}.
  • The _type property was set to sec_certs.sample.fips.FIPSCertificate.Heuristics.
  • The keywords property was set to {}.
  • The algorithms property was set to {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1912', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1747', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#85', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#413', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#496', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#342', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1273', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2484', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#764', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2134', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1522', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1718', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1526', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2778', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#3351', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#784', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#664', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#950', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2102', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}]}.
  • The st_references property was updated, with the {'_type': 'sec_certs.sample.certificate.References', 'directly_referencing': {'_type': 'Set', 'elements': ['93', '95', '89']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['93', '95', '89']}} data.
  • The web_references property was updated, with the {'_type': 'sec_certs.sample.certificate.References'} data.

  The state was updated.

  • The _type property was set to sec_certs.sample.fips.FIPSCertificate.InternalState.
  • The following properties were deleted: ['fragment_path'].

  The web_scan was updated.

  • This property was removed.

  The pdf_scan was updated.

  • This property was removed.
• 29.06.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 25.06.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 23.06.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 14.06.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The pdf_scan was updated.

  • The keywords property was updated, with the {'rules_standard_id': {'__update__': {'FIPS ?(?:PUB )?[0-9]+?': {'__delete__': ['FIPS 197']}}}, 'rules_block_cipher_modes': {'__insert__': {'CCM': {'CCM': {'count': 1}}, 'XTS': {'XTS': {'count': 1}}}, '__update__': {'ECB': {'__update__': {'ECB': {'__update__': {'count': 1}}}}, 'CBC': {'__update__': {'CBC': {'__update__': {'count': 1}}}}, 'CTR': {'__update__': {'CTR': {'__update__': {'count': 1}}}}, 'CFB': {'__update__': {'CFB': {'__update__': {'count': 1}}}}, 'OFB': {'__update__': {'OFB': {'__update__': {'count': 1}}}}, 'GCM': {'__update__': {'GCM': {'__update__': {'count': 1}}}}}}, 'rules_crypto_libs': {'__update__': {'OpenSSL': {'__update__': {'OpenSSL': {'__update__': {'count': 1}}}}}}, 'rules_other': {'__update__': {'library': {'__update__': {'library': {'__update__': {'count': 1}}}}}}} data.

  The computed heuristics were updated.

  • The keywords property was updated, with the {'rules_standard_id': {'__update__': {'FIPS ?(?:PUB )?[0-9]+?': {'__delete__': ['FIPS 197']}}}, 'rules_block_cipher_modes': {'__insert__': {'CCM': {'CCM': {'count': 1}}, 'XTS': {'XTS': {'count': 1}}}, '__update__': {'ECB': {'__update__': {'ECB': {'__update__': {'count': 1}}}}, 'CBC': {'__update__': {'CBC': {'__update__': {'count': 1}}}}, 'CTR': {'__update__': {'CTR': {'__update__': {'count': 1}}}}, 'CFB': {'__update__': {'CFB': {'__update__': {'count': 1}}}}, 'OFB': {'__update__': {'OFB': {'__update__': {'count': 1}}}}, 'GCM': {'__update__': {'GCM': {'__update__': {'count': 1}}}}}}, 'rules_crypto_libs': {'__update__': {'OpenSSL': {'__update__': {'OpenSSL': {'__update__': {'count': 1}}}}}}, 'rules_other': {'__update__': {'library': {'__update__': {'library': {'__update__': {'count': 1}}}}}}} data.
  • The algorithms property was updated.
• 07.06.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 24.05.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 22.05.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 20.05.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 19.05.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 18.05.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 17.05.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 13.05.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 18.04.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 11.03.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 10.03.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 08.03.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.
  • The following properties were deleted: ['connections'].

  The pdf_scan was updated.

  • The following properties were deleted: ['connections'].

  The computed heuristics were updated.

  • The following values were inserted: {'st_references': {'_type': 'References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': None, 'indirectly_referencing': None}, 'web_references': {'_type': 'References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': {'_type': 'Set', 'elements': ['1747']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['1747']}}}.
  • The algorithms property was updated.
  • The following properties were deleted: ['connections', 'directly_affected_by', 'indirectly_affected_by', 'directly_affecting', 'indirectly_affecting'].
• 23.02.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 18.02.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
  • The extracted_versions property was set to {'_type': 'Set', 'elements': ['-']}.
• 12.02.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 11.02.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 03.02.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 02.02.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The module_type property was set to Software.
  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 31.01.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The algorithms property was updated.

  The computed heuristics were updated.

  • The algorithms property was updated.
• 30.01.2022

  New

  The certificate was first processed.

  Show diff

  New certificate

  A new FIPS 140 certificate with the product name Nimble Storage FIPS Object Module was processed.