WIXLIB

FIPS 140-2 Non-Proprietary Security Policy, Version 0.7June 25, 2018#3379#3365HMAC21FIPS PUB 198-1SHA-1, SHA-224,SHA-256. SHA-384,SHA-512160, 224, 256, 384, 512messageauthentication#2744#2731RSA22FIPS PUB 186-4SigGen9.31,SigGenPKCS231.5,SigGenPSS24,2048, 3072digital PSS1024, 2048, 3072digital signatureverificationKeyGen9.312048, 3072key pair generationSHA26-1,-message digestKeying option ple-DES27FIPS PUB 180-4SHA-224,SHA-256, SHA-384,SHA-512NIST SP 800-67rev2 TECB, TCBCCAVP28Note1: No parts of the SSH and TLS protocols, other than the KDFs, have been tested by theand CMVP.Note2: The module explicitly disallows the use of SHA-1 when generating digital signatures.Note3: The module employs a CKG method whose resulting symmetric key or generated seed is an unmodified output of the DRBG.The module also implements the following non-Approved algorithm: EC Diffie-Hellman (key agreement: key establishment methodology provides 128 or 192 bits of encryptionstrength)o supports curves P-256 and P-384o allowed per FIPS IG D.8 scenario #3As a software module, the HPE SimpliVity OmniStack Crypto Library has both a logical cryptographic boundary anda physical cryptographic boundary. The physical and logical boundaries are described in Sections 2.2.1 and 2.2.2,respectively.2.2.1 Physical Cryptographic BoundaryAs a software cryptographic module, the module has no physical components. Therefore, the physical boundaryof the cryptographic module is defined by the hard enclosure around the host server on which it runs.The host server hardware, the OmniCube CN-3400-12bcc, consists of a motherboard, a Central Processing Unit(CPU), random access memory (RAM), read-only memory (ROM), hard disk(s), hardware case, power supply, andfans. Other devices may be attached to the hardware appliance such as a monitor, keyboard, mouse, DVD29 drive,printer, video adapter, audio adapter, or network adapter. In the validated configuration, the processor is an IntelXeon processor. Please see Figure 2 for a block diagram the host server and a depiction of the physicalcryptographic boundary.21HMAC – (keyed-) Hashed Message Authentication CodeRSA – Rivest Shamir Adleman23PKCS – Public Key Cryptography Standard24 PSS – Probabilistic Signature Scheme25 SHS – Secure Hash Standard26 SHA – Secure Hash Algorithm27 DES – Data Encryption Standard28CAVP – Cryptographic Algorithm Validation Program29 DVD – Digital Versatile Disc22HPE SimpliVity OmniStack Crypto Library 2018 Hewlett Packard Enterprise Development LPThis document may be freely reproduced and distributed whole and intact including this copyright notice.Page 8 of 25

FIPS 140-2 Non-Proprietary Security Policy, Version 0.7HardwareManagementJune 25, TAControllerLEDs/LCDSerialCPU(s)I/O ntrollerExternalPower SupplyPlaintext dataEncrypted dataControl inputStatus outputCrypto boundaryUSBBIOSPCI/PCIeSlotsKEY:BIOS – Basic Input/Output SystemCPU – Central Processing UnitSATA – Serial Advanced Technology AttachmentSCSI – Small Computer System InterfacePCI – Peripheral Component InterconnectPCIe – PCI expressHDD – Hard Disk DriveDVD – Digital Video DiscUSB – Universal Serial BusRAM – Random Access MemoryFigure 2 – Host Server Physical Block Diagram2.2.2 Logical Cryptographic BoundaryThe module is used by the calling application to provide symmetric cipher operation, digital signature generationand verification, hashing, cryptographic key generation, random number generation, message authenticationfunctions, and secure key agreement/key exchange protocol support. The module is entirely contained within thephysical cryptographic boundary described in Section 2.2.1.FIGURE 3 shows the logical block diagram of the module executing in memory and its interactions withsurrounding software components, as well as the module’s logical cryptographic boundary.HPE SimpliVity OmniStack Crypto Library 2018 Hewlett Packard Enterprise Development LPThis document may be freely reproduced and distributed whole and intact including this copyright notice.Page 9 of 25

FIPS 140-2 Non-Proprietary Security Policy, Version 0.7June 25, 2018CallingApplicationAPI FunctionOmniStack CryptoLibraryGuest OS(Ubuntu 14.04.5 LTS orWindows Server 2012 R2)KEY:Guest VMLogical CryptographicBoundaryVMware ESXi 6.0.0Physical CryptographicBoundaryData InputData OutputControl InputStatus OutputSystem CallsHost Server HardwareFigure 3 – Logical Block Diagram2.3Module InterfacesThe module isolates communications to logical interfaces that are defined in the software as an API30. The APIinterface is mapped to the following four logical interfaces: Data InputData OutputControl InputStatus OutputThe module’s physical boundary features the physical ports of a host server. The module’s manual controls,physical indicators, and physical, logical, and electrical characteristics are those of the host server. The module’slogical interfaces are at a lower level in the software. The physical data and control input through physicalmechanisms is translated into the logical data and control inputs for the software module. A mapping of the FIPS140-2 logical interfaces, the physical interfaces, and the module interfaces can be found in Table 3.Table 3 – FIPS 140-2 Logical Interface MappingsFIPS InterfaceData Input3031Physical InterfaceModule Interface (API)USB 31 ports (keyboard, mouse, data), The API calls that accept input data for processingnetwork interface, serial portsthrough their arguments.API – Application Programming InterfaceUSB – Universal Serial BusHPE SimpliVity OmniStack Crypto Library 2018 Hewlett Packard Enterprise Development LPThis document may be freely reproduced and distributed whole and intact including this copyright notice.Page 10 of 25

FIPS 140-2 Non-Proprietary Security Policy, Version 0.7FIPS InterfaceJune 25, 2018Physical InterfaceModule Interface (API)Data OutputGraphics controller, USB ports, network The API calls that return, by means of their returninterface, serial portscodes or arguments, generated or processed data backto the caller.Control InputUSB ports (keyboard, mouse), network The API calls that are used to initialize and control theinterface, serial portsoperation of the module.Status OutputGraphic controller, network interface, Return values for API calls.serial ports, Audio ports, LCD32/LEDs33Power InputAC34 power socket-Note: As a software module, control of the physical ports is outside the scope of the module.2.4Roles and ServicesThere are two authorized roles that module operators may assume: Crypto Officer (CO) role and a User role. Sinceno authentication mechanisms are implemented, roles are assumed implicitly. When invoking a module service,a module operator implicitly assumes the CO and User roles simultaneously; thus, both roles have access to allmodule services. The module does not allow multiple concurrent operators in the FIPS-Approved mode ofoperation. As per section 6.1 of the Implementation Guidance for FIPS PUB 140-2 and the CMVP, the callingapplication that loaded the module is the only operator.Descriptions of the services available are provided in Table 4 below. Please note that the keys and Critical SecurityParameters (CSPs) listed in the table indicate the type of access required using the following notation: R – Read: The CSP is read.W – Write: The CSP is established, generated, modified, or zeroized.X – Execute: The CSP is used within an Approved or Allowed security function or authenticationmechanism.Table 4 – Operator ServicesServiceOperatorDescriptionCSP and Type of AccessCOUserRun power-up self-teston demand Performs power-up self-testsNoneShow status Returns the current operational mode ofthe moduleNone32LCD – Liquid Crystal DisplayLED – Light Emitting Diode34 AC – Alternating Current33HPE SimpliVity OmniStack Crypto Library 2018 Hewlett Packard Enterprise Development LPThis document may be freely reproduced and distributed whole and intact including this copyright notice.Page 11 of 25

FIPS 140-2 Non-Proprietary Security Policy, Version 0.7Service35OperatorJune 25, 2018DescriptionCSP and Type of AccessCOUserZeroize Zeroizes and de-allocates memorycontaining sensitive dataAES key – WTriple-DES key – WHMAC key – WRSA private/public key – WECDSA private/public key – WECDH35 public/private components – WDRBG Seed – WDRBG Entropy – WDRBG ‘C’ value – WDRBG ‘V’ value – WZeroize DRBG CSPs Zeroizes and de-allocates memorycontaining DRBG CSPsDRBG Seed – WDRBG Entropy – WDRBG ‘C’ value – WDRBG ‘V’ value – WGenerate randomnumber Returns the specified number of randombits to the calling applicationDRBG Seed – WRXDRBG Entropy – RXDRBG ‘C’ value – WRXDRBG ‘V’ value – WRXGenerate messagedigest Compute and return a message digestusing SHS algorithmsNoneGenerate keyed hash(HMAC) Compute and return a messageauthentication codeHMAC key – RXGenerate symmetrickey Generate and return the specified type ofsymmetric key (Triple-DES or AES)AES key – WTriple-DES Key – WPerform symmetricencryption Encrypt plaintext using supplied key andalgorithm specification (Triple-DES orAES)AES key – RXTriple-DES key – RXPerform symmetricdecryption Decrypt ciphertext using supplied key and AES key – RXalgorithm specification (Triple-DES orTriple-DES key – RXAES)Perform authenticatedsymmetric encryption Encrypt plaintext using supplied AES GCM AES GCM key – RXkey and IVAES GCM IV – RXPerform authenticatedsymmetric decryption Decrypt ciphertext using supplied AESGCM key and IVAES GCM key – RXAES GCM IV – RXGenerate asymmetrickey pair Generate and return the specified type ofasymmetric key pair (RSA or ECDSA)RSA private/public key – WECDSA private/public key – WCalculate keyagreement primitive Calculate ECDH key agreement primitiveECDH Public/Private components – WRXGenerate signature Generate a signature for the suppliedmessage using the specified key andalgorithm (RSA or ECDSA)RSA private key – RXECDSA private key – RXVerify signature Verify the signature on the suppliedmessage using the specified key andalgorithm (RSA or ECDSA)RSA public key – RXECDSA public key – RXECDH – Elliptic Curve Diffie-HellmanHPE SimpliVity OmniStack Crypto Library 2018 Hewlett Packard Enterprise Development LPThis document may be freely reproduced and distributed whole and intact including this copyright notice.Page 12 of 25

FIPS 140-2 Non-Proprietary Security Policy, Version 0.7ServiceOperatorJune 25, 2018DescriptionCSP and Type of AccessCOUserPerform SSH keyderivation Establish SSH protocol keys via SSH KDFSSH shared secret – R, XAES key – WAES GCM key – WTriple-DES key – WHMAC key – WPerform TLS keyderivation Establish TLS protocol keys via TLS KDFTLS pre-master secret – R, XTLS master secret – WAES key – WAES GCM key – WTriple-DES key – WHMAC key – W2.5Physical SecurityThe cryptographic module is a software module and does not include physical security mechanisms. Therefore,as per section G.3 of the Implementation Guidance for FIPS PUB 140-2 and the CMVP, requirements for physicalsecurity are not applicable.2.6Operational EnvironmentThe module was tested and found to be compliant with FIPS 140-2 requirements on the following platforms andenvironments: HPE OmniCube CN-3400-12bcc appliance with an Intel Xeon E5-2600 V3 Series processor with VMwareESXi 6.0.0 hosting a virtual machine running Ubuntu 14.04.5 LTS OS (OVC) HPE OmniCube CN-3400-12bcc appliance with an Intel Xeon E5-2600 V3 Series processor with VMwareESXi 6.0.0 hosting a virtual machine running Windows Server 2012 R2 OS (Arbiter)As per section 6.1 of the Implementation Guidance for FIPS PUB 140-2 and the CMVP, the application that makescalls to the cryptographic module is the single user of the cryptographic module, even when the application isserving multiple clients.All cryptographic keys and CSPs are under the control of the OS, which protects its CSPs against unauthorizeddisclosure, modification, and substitution. Additionally, the OS provides dedicated process space to eachexecuting process, and the module operates entirely within the calling application’s process space. The moduleonly allows access to CSPs through its well-defined API.2.7Cryptographic Key ManagementHPE SimpliVity OmniStack Crypto Library 2018 Hewlett Packard Enterprise Development LPThis document may be freely reproduced and distributed whole and intact including this copyright notice.Page 13 of 25

FIPS 140-2 Non-Proprietary Security Policy, Version 0.7June 25, 2018The module supports the CSPs listed below in Table 5.Table 5 – Cryptographic Keys, Cryptographic Key Components, and CSPsCSPAES keyCSP TypeGeneration/InputAES 128, 192, 256-bit keyInternally generated viaApproved DRBGOutputStorageZeroizationUseOutput in plaintextKeys are not persistentlystored by the modulePower cycle/reboot;remove power; unloadmoduleEncryption, decryptionOutput in plaintextKeys are not persistentlystored by the modulePower cycle/reboot;remove power; unloadmoduleEncryption, decryptionNever output from themodulePlaintext in volatilememoryPower cycle/reboot;remove power; unloadmoduleInitialization vector forAES GCMORInternally derived viaTLS/SSH KDFORAES GCM keyAES GCM 128, 192, 256bit keyInput via API callparameterInternally generated viaApproved DRBGORInternally derived viaTLS/SSH KDFORAES GCM IV363696-bit valueInput via API callparameterInternally generated viaApproved DRBG(per SP 800-38Dsection 8.2.1)IV – Initialization VectorHPE SimpliVity OmniStack Crypto Library 2018 Hewlett Packard Enterprise Development LPThis document may be freely reproduced and distributed whole and intact including this copyright notice.Page 14 of 25

FIPS 140-2 Non-Proprietary Security Policy, Version 0.7CSPTriple-DES keyCSP TypeTriple-DES 168-bit key(Keying opt

HPE SimpliVity OmniStack Crypto Library 2018 Hewlett Packard Enterprise Development LP This document may be freely reproduced and distributed whole and intact including this copyright notice. Page 4 of 25 1. Introduction 1.1 Purpose This is a non-proprietary Cryptographic Module Security Policy for the HPE SimpliVity OmniStack Crypto Library