OpenSSL FIPS Object Module SE Version 2.0.11 By the OpenSSL Software Foundation OpenSSL FIPS 140-2 Security Policy Version 2.0.11 December 8, 2015 OpenSSL FIPS 1402 Security Policy Copyright Notice Copyright © 20032015 the OpenSSL Software Foundation, Inc. This document may be freely reproduced in whole or part without permission and without restriction. Sponsored by: Intersoft International, Inc. sponsor of Beaglebone Black platforms Page 2 of 28 OpenSSL FIPS 1402 Security Policy Acknowledgments The OpenSSL Software Foundation (OSF) serves as the "vendor" for this validation. Project management coordination for this effort was provided by: Steve Marquess +1 877-673-6775 The OpenSSL Software Foundation marquess@openssl.com 1829 Mount Ephraim Road Adamstown, MD 21710 USA with technical work by: Stephen Henson 4 Monaco Place, shenson@openssl.com Westlands, Newcastle-under-Lyme shenson@drh-consultancy.co.uk Staffordshire. ST5 2QT. England, United Kingdom http://www.drh-consultancy.co.uk/ Andy Polyakov Chalmers University of Technology appro@openssl.org SE-412 96 Gothenburg appro@fy.chalmers.se Sweden Tim Hudson P.O. Box 6389 tjh@openssl.com Fairfield Gardens 4103 tjh@cryptsoft.com Australia ACN 074 537 821 http://www.cryptsoft.com/ in coordination with the OpenSSL Team at www.openssl.org. Validation testing was performed by InfoGard Laboratories. For information on validation or revalidations of software contact: Marc Ireland 805-783-0810 tel FIPS Program Manager, CISSP 805-783-0889 fax InfoGard Laboratories mireland@infogard.com 709 Fiero Lane, Suite 25 http://www.infogard.com/ San Luis Obispo, CA 93401 Page 3 of 28 OpenSSL FIPS 1402 Security Policy Modification History 20151105 Addition of two platforms: #20/21 Ubuntu 12.04 on x86 (without/with optimizations) 20150911 Addition of two platforms: #18 AIX 6.1 32bit on PPC with optimizations #19 AIX 6.1 64bit on PPC with optimizations 20150907 Fix typo in platform #4 description 20150814 Addition of six platforms: #12 AIX 6.1 32bit on PPC #13 AIX 6.1 64bit on PPC #14 AIX 7.1 32bit on PPC #15 AIX 7.1 64bit on PPC #16 DataGravity Discovery Series OS V2.0 on x86 #17 DataGravity Discovery Series OS V2.0 on x86 with optimizations 20150703 (2.0.11) Addition of new platform #11, VxWorks 6.7 on x86 Added note to Table 4c about Dual EC DRBG 20150508 (2.0.10) Addition of nine platforms: #2/3 iOS 8.1 64bit on Apple A7 (ARMv8) (without/with optimizations) #4 VxWorks 6.9 on Freescale P2020 (PPC) #5/6 iOS 8.1 32bit on Apple A7 (ARMv8) (without/with optimizations) #7/8 Android 5.0 on Qualcomm APQ8084 (ARMv7) (without/with optimizations) #9/10 Android 5.0 64bit on SAMSUNG Exynos7420 (ARMv8) (without/with optimizations) 20150414 (2.0.9) Initial validation with platform #1, TSLinux 2.4 on ARMv4 Page 4 of 28 OpenSSL FIPS 1402 Security Policy 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 [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 Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher 67R1] [SP 80089] Recommendation for Obtaining Assurances for Digital Signature Applications [SP 80090] Recommendation for Random Number Generation Using Deterministic Random Bit Generators [SP 800 Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key 131A] Lengths Page 5 of 28 OpenSSL FIPS 1402 Security Policy Table of Contents 1 Introduction.........................................................................................................................7 2 Tested Configurations.........................................................................................................9 3 Ports and Interfaces.............................................................................................................10 4 Modes of Operation and Cryptographic Functionality.......................................................11 4.1 Critical Security Parameters and Public Keys............................................................14 5 Roles, Authentication and Services....................................................................................17 6 Selftest...............................................................................................................................19 7 Operational Environment....................................................................................................21 8 Mitigation of other Attacks.................................................................................................22 Appendix A Installation and Usage Guidance.......................................................................23 Appendix B Controlled Distribution File Fingerprint...........................................................26 Appendix C Compilers..........................................................................................................28 Page 6 of 28 OpenSSL FIPS 1402 Security Policy 1 Introduction This document is the nonproprietary security policy for the OpenSSL FIPS Object Module SE, hereafter referred to as the Module. 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 (Linux®1/Unix®2 and Vxworks®3) or fipscanister.lib (Microsoft Windows®4). The Module performs no communications other than with the calling application (the process that invokes the Module services). Note that the OpenSSL FIPS Object Module SE v2.0.11 is fully backwards compatible with all earlier revisions of the OpenSSL FIPS Object Module SE. The v2.0.11 Module incorporates support for new platforms without disturbing functionality for any previously tested platforms. The v2.0.11 Module can be used in any environment supported by the earlier revisions of the Module, and those earlier revisions remain valid. 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 1 Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 2 UNIX is a registered trademark of The Open Group 3 Vxworks is a registered trademark owned by Wind River Systems, Inc 4 Windows is a registered trademark of Microsoft Corporation in the United States and other countries. Page 7 of 28 OpenSSL FIPS 1402 Security Policy The Module's software version for this validation is 2.0.11. The v2.0.11 Module incorporates changes from earlier revisions of the Module to support additional platforms. The v2.0.11 Module can be used in all the environments supported by the earlier v2.0.9 and v2.0.10 revisions of the Module. Figure 1 Module Block Diagram Page 8 of 28 OpenSSL FIPS 1402 Security Policy 2 Tested Configurations # Operational Environment Processor Optimiz EC B ations (Target) 1 TSLinux 2.4 Arm920Tid (ARMv4) None BKP U2 2 iOS 8.1 64bit Apple A7 (ARMv8) None BKP U2 3 iOS 8.1 64bit Apple A7 (ARMv8) NEON and BKP U2 Crypto Extensions 4 VxWorks 6.9 Freescale P2020 (PPC) None BKP U2 5 iOS 8.1 32bit Apple A7 (ARMv8) None BKP U2 6 iOS 8.1 32bit Apple A7 (ARMv8) NEON BKP U2 7 Android 5.0 Qualcomm APQ8084 (ARMv7) None BKP U2 8 Android 5.0 Qualcomm APQ8084 (ARMv7) NEON BKP U2 9 Android 5.0 64bit SAMSUNG Exynos7420 None BKP U2 (ARMv8) 10 Android 5.0 64bit SAMSUNG Exynos7420 NEON and BKP U2 (ARMv8) Crypto Extensions 11 VxWorks 6.7 Intel Core 2 Duo (x86) None BKP U2 12 AIX 6.1 32bit Power 7 (PPC) None BKP U2 13 AIX 6.1 64bit Power 7 (PPC) None BKP U2 14 AIX 7.1 32bit Power 7 (PPC) None BKP U2 15 AIX 7.1 64bit Power 7 (PPC) None BKP U2 16 DataGravity Discovery Series OS V2.0 Intel Xeon E52420 (x86) None BKP U2 17 DataGravity Discovery Series OS V2.0 Intel Xeon E52420 (x86) AESNI BKP U2 18 AIX 6.1 32bit Power 7 (PPC) optimizations BKP U2 19 AIX 6.1 64bit Power 7 (PPC) optimizations BKP U2 20 Ubuntu 12.04 Intel Xeon E52430L (x86) None BKP U2 21 Ubuntu 12.04 Intel Xeon E52430L (x86) 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 9 of 28 OpenSSL 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 10 of 28 OpenSSL 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 [ANS X9.31] RNG AES 128/192/256 1314 Generation; 1349 Symmetric key 1376 generation [SP 80090] DRBG5 Hash DRBG 607 Prediction resistance HMAC DRBG, no reseed 723 supported for all variations CTR DRBG (AES), no derivation function 845 [SP 80067] 3Key TDES TECB, TCBC, TCFB, TOFB; 1780 CMAC generate and verify 1853 1942 Encryption, [FIPS 197] AES 128/ 192/256 ECB, CBC, OFB, CFB 1, CFB 8, 3090 Decryption and CFB 128, CTR, XTS; CCM; GCM; CMAC 3264 CMAC [SP 80038B] CMAC generate and verify 3451 [SP 80038C] CCM [SP 80038D] GCM [SP 80038E] XTS Message Digests [FIPS 1803] SHA1, SHA2 (224, 256, 384, 512) 2553 2702 2847 [FIPS 198] HMAC SHA1, SHA2 (224, 256, 384, 512) 1937 Keyed Hash 2063 2197 Digital Signature and [FIPS 1862] RSA GenKey9.31, SigGen9.31, SigGenPKCS1.5, 1581 Asymmetric Key SigGenPSS, SigVer9.31, SigVerPKCS1.5, 1664 Generation SigVerPSS (2048/3072/4096 with all SHA2 1766 sizes) [FIPS 1864] DSA PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, 896 Sig Ver (1024/2048/3072 with all SHA2 sizes) 933 970 [FIPS 1862] ECDSA PKG: CURVES( P224 P384 P521 K233 K 558 283 K409 K571 B233 B283 B409 B571 ) 620 PKV: CURVES( P192 P224 P256 P384 P 698 521 K163 K233 K283 K409 K571 B163 B 233 B283 B409 B571 ) PKG: CURVES( P224 P384 P521 ) PKV: CURVES( P192 P224 P256 P384 P 521 ) 5 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP80090] and [SP80057]. Page 11 of 28 OpenSSL FIPS 1402 Security Policy [FIPS 1864] ECDSA PKG: CURVES( P224 P256 P384 P521 K 558 224 K256 K384 K521 B224 B256 B384 B 620 521 ExtraRandomBits TestingCandidates ) 698 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) ) PKG: CURVES( P224 P256 P384 P521 ) PKV: CURVES( ALLP ) SigGen: CURVES( P224: (SHA224, 256, 384, 512) P256: (SHA224, 256, 384, 512) P384: (SHA224, 256, 384, 512) P521: (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) ) [SP 80056A] (§5.7.1.2) All NIST defined B, K and P curves except sizes 372 163 and 192 472 ECC CDH (KAS) 534 All NIST defined P curves 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"). Page 12 of 28 OpenSSL FIPS 1402 Security Policy 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, RSA The RSA algorithm may be used by the calling application for Decryption 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 The Module implements the following services which are NonApproved per the SP 800131A transition: Function Algorithm Options Cert # Random Number [SP 80090] DRBG Dual EC DRBG Generation; (note the Dual EC DRBG algorithm shall not be Symmetric key used in the FIPS Approved mode of operation) generation Digital Signature and [FIPS 1862] RSA GenKey9.31, SigGen9.31, SigGenPKCS1.5, Asymmetric Key SigGenPSS (1024/1536 with all SHA sizes, Generation 2048/3072/4096 with SHA1) [FIPS 1862] DSA PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) [FIPS 1864] DSA PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA1) [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 ) [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) ) [SP 80056A] (§5.7.1.2) All NIST Recommended B, K and P curves ECC CDH (CVL) sizes 163 and 192 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. Page 13 of 28 OpenSSL FIPS 1402 Security Policy The Module requires an initialization sequence (see IG 9.5): the calling application invokes FIPS_mode_set()6, 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 1863 assurances are outside the scope of the Module, and are the responsibility of the calling process. 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 or [FIPS 1862] DSA (1024) 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 TDES EDK TDES (3Key) encrypt / decrypt key TDES CMAC TDES (3Key) CMAC generate / verify key HMAC Key Keyed hash key (160/224/256/384/512) RNG CSPs Seed (128 bit), AES 128/192/256 seed key and associated state variables for ANS X9.31 AES based RNG7 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) Dual_EC_DRBG CSPs S (P256, P384, P521), entropy input (length dependent on security strength) COADDigest Precalculated HMACSHA1 digest used for Crypto Officer role authentication 6 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. 7 There is an explicit test for equality of the seed and seed key inputs Page 14 of 28 OpenSSL FIPS 1402 Security Policy 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. Table 4.1b ­ Public Keys For all CSPs and Public Keys: Storage: RAM, associated to entities by memory location. The Module stores RNG and DRBG state values for the lifetime of the RNG or 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 RNG and DRBG state values used for the Modules' default key generation service. Generation: The Module implements ANSI X9.31 compliant RNG and 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 Page 15 of 28 OpenSSL FIPS 1402 Security Policy 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 for the [ANS X9.31] RNG mechanism, and as shown in [SP 80090] Table 2 (Hash_DRBG, HMAC_DRBG), Table 3 (CTR_DRBG) and Table 4 (Dual_EC_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 28 OpenSSL 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. Functions that provide module status information: Version (as unsigned long or const char *) Show status User, CO FIPS Mode (Boolean) Does not access CSPs. Functions that destroy CSPs: fips_rand_prng_reset: destroys RNG CSPs. fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs Zeroize User, CO (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs, Dual_EC_DRBG CSPs.) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. Page 17 of 28 OpenSSL FIPS 1402 Security Policy Service Role Description Used for random number and symmetric key generation. Seed or reseed an RNG or DRBG instance Random Determine security strength of an RNG or DRBG instance number User, CO generation Obtain random data Uses and updates RNG CSPs, Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs, Dual_EC_DRBG CSPs. Used to generate DSA, ECDSA and RSA keys: Asymmetric RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK User, CO key generation There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP80090 Symmetric Used to encrypt or decrypt data. User, CO encrypt/decrypt Executes using AES EDK, TDES EDK (passed in by the calling process). Symmetric Used to generate or verify data integrity with CMAC. User, CO digest Executes using AES CMAC, TDES, CMAC (passed in by the calling process). Used to generate a SHA1 or SHA2 message digest. Message digest User, CO Does not access CSPs. Used to generate or verify data integrity with HMAC. Keyed Hash User, CO Executes using HMAC Key (passed in by the calling process). Used to encrypt or decrypt a key value on behalf of the calling process (does not Key transport8 User, CO establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). Used to perform key agreement primitives on behalf of the calling process (does not Key agreement User, CO establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). Used to generate or verify RSA, DSA or ECDSA digital signatures. Digital User, CO Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, signature ECDSA SVK (passed in by the calling process). Utility User, CO Miscellaneous helper functions. Does not access CSPs. Table 5 Services and CSP Access 8 "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 OpenSSL FIPS Object Module SE. Page 18 of 28 OpenSSL FIPS 1402 Security Policy 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 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 TDES KAT Separate encrypt and decrypt, ECB mode, 3Key TDES 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 Dual_EC_DRBG: P256 and 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 X9.31 RNG KAT 128, 192, 256 bit AES keys 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()9 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()9 succeeds. 9 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 19 of 28 OpenSSL FIPS 1402 Security Policy 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 RSA Pairwise consistency test on each generation of a key pair ANSI X9.31 RNG Continuous test for stuck fault 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 28 OpenSSL 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 28 OpenSSL 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 28 OpenSSL 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.11.tar.gz (all NIST defined curves as listed in Table 2 with the EC column marked "BKP") or opensslfipsecp2.0.11.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 OSF10. 10 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://openssl.com/fips/verify.html. Page 23 of 28 OpenSSL FIPS 1402 Security Policy 3. Unpack the distribution gunzip -c openssl-fips-2.0.11.tar.gz | tar xf - cd openssl-fips-2.0.11 or gunzip -c openssl-fips-ecp-2.0.11.tar.gz | tar xf - cd openssl-fips-ecp-2.0.11 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()11 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()11 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()11 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: 11 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 24 of 28 OpenSSL FIPS 1402 Security Policy 1. No optimization (plain C) 2. SSE2 optimization 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 28 OpenSSL FIPS 1402 Security Policy Appendix B Controlled Distribution File Fingerprint The OpenSSL FIPS Object Module SE v2.0.11 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.11.tar.gz with HMAC SHA1 digest of b9d2a466c66841fcbf65a3cbe21abf81fe140bcf located at http://www.openssl.org/source/opensslfips2.0.11.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.11.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.11.tar.gz with HMACSHA1 digest of 571662bb0e413bd42f612c695c0b76deb2e9b33e located at http://www.openssl.org/source/opensslfipsecp2.0.11.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.11. 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.10.tar.gz Page 26 of 28 OpenSSL FIPS 1402 Security Policy URL: http://www.openssl.org/source/opensslfips2.0.10.tar.gz Digest: af8bda4bb9739e35b4ef00a9bc40d21a6a97a780 opensslfipsecp2.0.10.tar.gz URL: http://www.openssl.org/source/opensslfipsecp2.0.10.tar.gz Digest: 02cc9ddfffb2e917d1cdc9ebc97a9731c40f6394 opensslfips2.0.9.tar.gz URL: http://www.openssl.org/source/old/fips/opensslfips2.0.9.tar.gz Digest: 54552e9a3ed8d1561341e8945fcdec55af961322 opensslfipsecp2.0.9.tar.gz URL: http://www.openssl.org/source/old/fips/opensslfipsecp2.0.9.tar.gz Digest: 91d267688713c920f85bc5e69c8b5d34e1112672 Page 27 of 28 OpenSSL 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 TSLinux 2.4 gcc 4.3.2 2 iOS 8.1 64bit clang600.0.56 3 iOS 8.1 64bit clang600.0.56 4 VxWorks 6.9 gcc 4.3.3 5 iOS 8.1 32bit clang600.0.56 6 iOS 8.1 32bit clang600.0.56 7 Android 5.0 gcc 4.9 8 Android 5.0 gcc 4.9 9 Android 5.0 64bit gcc 4.9 10 Android 5.0 64bit gcc 4.9 11 VxWorks 6.7 gcc 4.1.2 12 AIX 6.1 32bit IBM XL C/C++ for AIX, V13.1 13 AIX 6.1 64bit IBM XL C/C++ for AIX, V13.1 14 AIX 7.1 32bit IBM XL C/C++ for AIX, V13.1 15 AIX 7.1 64bit IBM XL C/C++ for AIX, V13.1 16 DataGravity Discovery Series OS V2.0 gcc 4.7.2 17 DataGravity Discovery Series OS V2.0 gcc 4.7.2 18 AIX 6.1 32bit IBM XL C/C++ for AIX, V10.1 19 AIX 6.1 64bit IBM XL C/C++ for AIX, V10.1 20 Ubuntu 12.04 gcc 4.6.3 21 Ubuntu 12.04 gcc 4.6.3 Table C Compilers Page 28 of 28