CellTrust Cryptographic Module (CTCM) Version 2.0 FIPS 140-2 Security Policy July 10, 2015 CellTrust Cryptographic Module 2.0 Security Policy © Copyright 2014 CellTrust® Corporation, All Rights Reserved. Trademarks featured or referred to within this CellTrust® document are the property of their respective trademark holders. Such use of non-CellTrust trademarks is intended for reference or identification purposes only and does not indicate affiliation, sponsorship or endorsement of CellTrust® or any CellTrust® product and service. Document Version: 2.0 Version Author Date Revisions 1.0 Behnam Shariati 4/6/2015 Initial Release 2.0 Behnam Shariati 6/25/2015 Updates based on CMVP feedback. © Copyright 2014 CellTrust® Corporation. Page 2 | 25 CellTrust Cryptographic Module 2.0 Security Policy Contents Contents........................................................................................................................................................................................3 1 Introduction.......................................................................................................................................................................4 2 TestedConfigurations.....................................................................................................................................................6 3 PortsandInterfaces......................................................................................................................................................79 4 ModesofOperationandCryptographicFunctionality...................................................................................810 4.1CriticalSecurityParametersandPublicKeys................................................................................................1012 5 Roles,AuthenticationandServices.....................................................................................................................1415 6 Selftest.........................................................................................................................................................................1617 7 OperationalEnvironment......................................................................................................................................1819 8 MitigationofotherAttacks....................................................................................................................................1920 AppendixA­Installation&UsageGuidance...........................................................................................................2021 . AppendixB­ControlledDistributionFileFingerprint........................................................................................2324 AppendixC­Compilers...................................................................................................................................................2425 AppendixD­References.................................................................................................................................................2528 © Copyright 2014 CellTrust® Corporation. Page 3 | 25 CellTrust Cryptographic Module 2.0 Security Policy 1 Introduction This document is the non-proprietary security policy for the CellTrust Cryptographic Module, hereafter referred to as the CTCM. The CTCM is a software library providing a C-language application program interface (API) for use by other processes that require cryptographic functionality. The CTCM is classified by FIPS 140-2 as a software module, multi-chip 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) or fipscanister.lib (Microsoft Windows®3). The CTCM performs no communications other than with the calling application (the process that invokes the CTCM services). Note that the CellTrust Cryptographic Module v2.0 is fully compatible with OpenSSL FIPS Object Module v2.0.5 and all earlier revisions of the OpenSSL FIPS Object Module v2.0. This CTCM incorporates support for new platforms without disturbing functionality for any previously tested platforms of the OpenSSL FIPS Object Module. The CellTrust Cryptographic Module v2.0 Module, being based on the OpenSSL FIPS Object Module v2.0.5 without modification, can be used in any environment supported by the earlier revisions of the OpenSSL Module, and those earlier revisions remain valid. The FIPS 140-2 security levels for the CTCM are as follows: Security Level Cryptographic Module Specification 1 Cryptographic Module Ports & Interfaces 1 Roles, Services & Authentication 2 Finite State Model 1 Physical Security NA Operational Environment 1 Cryptographic Key Management 1 EMI/EMC 1 Self-Tests 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 Windows is a registered trademark of Microsoft Corporation in the United States and other countries. © Copyright 2014 CellTrust® Corporation. Page 4 | 25 CellTrust Cryptographic Module 2.0 Security Policy The CTCM's software version for this validation is 2.0. The CTCM, being based on the OpenSSL FIPS Object Module, incorporates changes from the OpenSSL v2.0 module to support additional platforms. The CTCM can be used in all the environments supported by the earlier v2.0, v2.0.1, v2.0.2, v2.0.3 and v2.0.4 revisions of the OpenSSL FIPS Object Module. Figure 1 - Module Block Diagram © Copyright 2014 CellTrust® Corporation. Page 5 | 25 CellTrust Cryptographic Module 2.0 Security Policy 2 TestedConfigurations Optimizations # Operational Environment Processor EC B (Target) 1 Android 4.2 Nvidia Tegra 3 (ARMv7) None P U2 2 Android 4.2 Nvidia Tegra 3 (ARMv7) NEON P U2 3 Apple iOS 7.1 Apple A7 (ARMv8) None BKP U2 4 Apple iOS 7.1 Apple A7 (ARMv8) NEON 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 CTCM for the respective operational environments. © Copyright 2014 CellTrust® Corporation. Page 6 | 25 CellTrust Cryptographic Module 2.0 Security Policy 3 PortsandInterfaces The physical ports of the CTCM are the same as the computer system on which it is executing. The logical interface is a C-language application program interface (API). Logical Interface Type Description API entry point and corresponding Control input stack parameters API entry point data input stack Data input parameters API entry point return values and Status output status stack parameters API entry point data output stack Data output parameters Table 3 - Logical Interfaces © Copyright 2014 CellTrust® Corporation. Page 7 | 25 CellTrust Cryptographic Module 2.0 Security Policy 4 ModesofOperationandCryptographicFunctionality The CTCM supports only a FIPS 140-2 Approved mode. Tables 4 and 5 list the Approved and Non- approved but Allowed algorithms, respectively. Function Algorithm Options Cert # [ANSI X9.31] RNG AES 128/192/256 1119, 1314 Random Number Generation; Hash DRBG Symmetric key [SP 800-90] DRBG 4 HMAC DRBG, no reseed generation Prediction resistance CTR DRBG (AES), no derivation 264, 607 supported for all function variations Dual EC DRBG: P-256, P-384, P- 5215 [FIPS 197] AES Encryption, 128/192/256 CBC 2234, 3090 Decryption and CMAC 3-Key TDES TECB, TCBC, TCFB, [SP 800-67] 1398, 1780 TOFB; CMAC generate and verify Keyed Hash [FIPS 198] HMAC SHA-1, SHA-2 (256, 384, 512) 1363, 1937 4 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP80090] and [SP80057]. 5 While this RNG is included in the package, it is disabled functionally and cannot be used. © Copyright 2014 CellTrust® Corporation. Page 8 | 25 CellTrust Cryptographic Module 2.0 Security Policy Function Algorithm Options Cert # GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS, (2048/3072/4096 with all SHA-2 sizes) [FIPS 186-2] RSA 1145, 1581 SigVer9.31, SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA sizes) Digital Signature Key Pair, PKV, SigVer (all NIST and defined B, K, and P curves with all Asymmetric Key SHA sizes) 558 Generation [FIPS 186-2] ECDSA Key Pair, PKV, SigVer (all NIST 378 defined P curves with all SHA sizes) PQG Gen, Key Pair Gen, SigGen ( 2048/3072 with all SHA-2 sizes) [FIPS 186-4] DSA 693, 896 PQG Ver, Sig Ver (1024/2048/3072 with all SHA sizes) Message Digests [FIPS 180-3] SHA-1, SHA-2 (224, 256, 384, 512) 1923, 2553 All NIST defined B, K and P curves 372 ECC CDH (KAS) [SP 800-56A] (§5.7.1.2) All NIST defined P curves 49 Table 4 - FIPS Approved Cryptographic Functions © Copyright 2014 CellTrust® Corporation. Page 9 | 25 CellTrust Cryptographic Module 2.0 Security Policy The CTCM supports only NIST defined curves for use with ECDSA and ECC CDH. The CTCM 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 Non-compliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K Key Agreement EC DH and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. The RSA algorithm may be used by the calling application for encryption or decryption of keys. Key Encryption, RSA No claim is made for SP 800-56B compliance, Decryption and no CSPs are established into or exported out of the module using these services. Table 5 - Non-FIPS Approved But Allowed Cryptographic Functions 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 CTCM supports only a FIPS 140-2 Approved mode. The CTCM 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 CTCM 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 186-4 assurances are outside the scope of the CTCM, and are the responsibility of the calling process. 4.1 CriticalSecurityParametersandPublicKeys All CSPs used by the CTCM are described in this section. All access to these CSPs by CTCM services are described in Section 4. The CSP names are generic, corresponding to API parameter data structures. 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. © Copyright 2014 CellTrust® Corporation. Page 10 | 25 CellTrust Cryptographic Module 2.0 Security Policy CSP Name Description RSA SGK RSA (2048 to 16384 bits) signature generation key RSA (2048 to 16384 bits) key decryption (private key RSA KDK transport) key DSA SGK [FIPS 186-4] DSA (2048/3072) signature generation key ECDSA (All NIST defined B, K, and P curves) signature ECDSA SGK generation key EC DH (All NIST defined B, K, and P curves) private key EC DH Private 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 (3-Key) encrypt / decrypt key TDES CMAC TDES (3-Key) CMAC generate / verify key HMAC Key Keyed hash key (160/224/256/384/512) Seed (128 bit), AES 128/192/256 seed key and associated RNG CSPs state variables for ANS X9.31 AES based RNG7 V (440/880 bits) and C (440/880 bits), entropy input (length Hash_DRBG CSPs dependent on security strength) V (160/224/256/384/512 bits) and Key HMAC_DRBG CSPs (160/224/256/384/512 bits), entropy input (length dependent on security strength) V (128 bits) and Key (AES 128/192/256), entropy input CTR_DRBG CSPs (length dependent on security strength) S (P-256, P-384, P-521), entropy input (length dependent on Dual_EC_DRBG CSPs security strength) Pre-calculated HMAC-SHA-1 digest used for Crypto Officer CO-AD-Digest role authentication Pre-calculated HMAC-SHA-1 digest used for User role User-AD-Digest authentication Table 6 - 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. 7 There is an explicit test for equality of the seed and seed key inputs © Copyright 2014 CellTrust® Corporation. Page 11 | 25 CellTrust Cryptographic Module 2.0 Security Policy CSP Name Description RSA SVK RSA (1024 to 16384 bits) signature verification public key RSA (2048 to 16384 bits) key encryption (public key RSA KEK transport) key [FIPS 186-4] DSA (1024/2048/3072) signature verification DSA SVK key ECDSA (All NIST defined B, K and P curves) signature ECDSA SVK verification key EC DH (All NIST defined B, K and P curves) public key EC DH Public agreement key. Table 7 - Public Keys For all CSPs and Public Keys: Storage: RAM, associated to entities by memory location. The CTCM stores RNG and DRBG state values for the lifetime of the RNG or DRBG instance. The CTCM uses CSPs passed in by the calling application on the stack. The CTCM 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 CTCMs' default key generation service. Generation: The CTCM implements ANSI X9.31 compliant RNG and SP 800-90 compliant DRBG services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4. The calling application is responsible for storage of generated keys returned by the CTCM. Entry: All CSPs enter the CTCM's logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output: The CTCM 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 CTCM 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 CTCM. Private and secret keys as well as seeds and entropy input are provided to the CTCM 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 CTCM 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 non-overlapping sequence such that no two API functions will execute concurrently. An authorized application as user (Crypto-Officer and User) has access to all key data generated during the operation of the CTCM. © Copyright 2014 CellTrust® Corporation. Page 12 | 25 CellTrust Cryptographic Module 2.0 Security Policy In the event CTCM power is lost and restored the calling application must ensure that any AES-GCM keys used for encryption or decryption are re-distributed. CTCM 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 800-90] 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. © Copyright 2014 CellTrust® Corporation. Page 13 | 25 CellTrust Cryptographic Module 2.0 Security Policy 5 Roles,AuthenticationandServices The CTCM 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 CTCM 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 CTCM unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the CTCM during the CTCM 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 CTCM 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 CTCM. User Role (User): Loading the CTCM and calling any of the API functions. Crypto Officer Role (CO): Installation of the CTCM on the host computer system and calling of any API functions. All services implemented by the CTCM are listed below, along with a description of service CSP access. Service Role Description Initialize User, CO Module initialization. Does not access CSPs. Self-test 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 (Hash_DRBG CSPs, Zeroize User, CO 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. © Copyright 2014 CellTrust® Corporation. Page 14 | 25 CellTrust Cryptographic Module 2.0 Security Policy Service Role Description Used for random number and symmetric key generation. Seed or reseed an RNG or DRBG instance Determine security strength of an RNG or DRBG instance Random number generation User, CO 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: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, Asymmetric key User, CO ECDSA SVK generation There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP800-90 Used to encrypt or decrypt data. Symmetric User, CO Executes using AES EDK, TDES EDK (passed in by the calling encrypt/decrypt process). Used to generate or verify data integrity with CMAC. Symmetric digest User, CO Executes using AES CMAC, TDES, CMAC (passed in by the calling process). Used to generate a SHA-1 or SHA-2 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 establish keys into the module). Key transport8 User, CO 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 establish keys into the module). Key agreement User, CO 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 signature User, CO 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. 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 CellTrust Cryptographic Module. © Copyright 2014 CellTrust® Corporation. Page 15 | 25 CellTrust Cryptographic Module 2.0 Security Policy Table 8 - Services and CSP Access 6 Selftest The CTCM performs the self-tests listed below on invocation of Initialize or Self-test. Algorithm Type Test Attributes Software integrity KAT HMAC-SHA1 One KAT per SHA1, SHA224, SHA256, SHA384 and SHA512 HMAC KAT 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 128, 256 bit key sizes to support either the 256-bit key size (for XTS-AES KAT XTS-AES-128) or the 512-bit key size (for XTS-AES-256) AES CMAC KAT Sign and verify CBC mode, 128, 192, 256 key lengths TDES KAT Separate encrypt and decrypt, ECB mode, 3-Key TDES CMAC KAT CMAC generate and verify, CBC mode, 3-Key RSA KAT Sign and verify using 2048 bit key, SHA-256, PKCS#1 DSA PCT Sign and verify using 2048 bit key, SHA-384 CTR_DRBG: AES, 256 bit with and without derivation function HASH_DRBG: SHA256 DRBG KAT HMAC_DRBG: SHA256 Dual_EC_DRBG: P-256 and SHA256 Keygen, sign, verify using P-224, K-233 and SHA512. The K-233 ECDSA PCT self-test is not performed for operational environments that support prime curve only (see Table 2). ECC CDH KAT Shared secret calculation per SP 800-56A §5.7.1.2, IG 9.6 X9.31 RNG KAT 128, 192, 256 bit AES keys Table 9 - Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency test) The CTCM is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMAC-SHA-1 of the CTCM 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 power-up self-tests listed above with no operator intervention required, returning a "1" if all power-up self-tests succeed, and a "0" otherwise. If any component of the power-up self-test fails an internal flag is set to prevent subsequent invocation of any cryptographic 9 FIPS_mode_set() calls CTCM function FIPS_module_mode_set() © Copyright 2014 CellTrust® Corporation. Page 16 | 25 CellTrust Cryptographic Module 2.0 Security Policy 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. The power-up self-tests may also be performed on-demand 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 CTCM also implements the following conditional tests: Algorithm Test DRBG Tested as required by [SP800-90] Section 12 DRBG FIPS 140-2 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 10 - Conditional Tests In the event of a DRBG self-test failure the calling application must uninstantiate and reinstantiate the DRBG per the requirements of [SP 800-90]; this is not something the CTCM can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. The CTCM 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"). © Copyright 2014 CellTrust® Corporation. Page 17 | 25 CellTrust Cryptographic Module 2.0 Security Policy 7 OperationalEnvironment 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 CTCM functions entirely within the process space of the calling application, and implicitly satisfies the FIPS 140-2 requirement for a single user mode of operation. © Copyright 2014 CellTrust® Corporation. Page 18 | 25 CellTrust Cryptographic Module 2.0 Security Policy 8 MitigationofotherAttacks The CTCM is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. © Copyright 2014 CellTrust® Corporation. Page 19 | 25 CellTrust Cryptographic Module 2.0 Security Policy AppendixA­Installation&UsageGuidance 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 cross-compilation environments. Each of these command sets are relative to the top of the directory containing the uncompressed and expanded contents of the distribution files openssl-fips-2.0.5.tar.gz (all NIST defined curves as listed in Table 2 with the EC column marked "BKP") or openssl-fips-ecp-2.0.5.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 HMAC-SHA-1 digest of the distribution file; see Appendix B. An independently acquired FIPS 140-2 validated implementation of SHA-1 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. 3. Unpack the distribution gunzip -c openssl-fips-2.0.5.tar.gz | tar xf - © Copyright 2014 CellTrust® Corporation. Page 20 | 25 CellTrust Cryptographic Module 2.0 Security Policy cd openssl-fips-2.0.5 or gunzip -c openssl-fips-ecp-2.0.5.tar.gz | tar xf - cd openssl-fips-ecp-2.0.5 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 140-2. Linking the Runtime Executable Application Note that applications interfacing with the Cryptographic Module are outside of the cryptographic boundary. When linking the application with the Cryptographic Module two steps are necessary: 1. The HMAC-SHA-1 digest of the Cryptographic Module file must be calculated and verified against the installed digest to ensure the integrity of the Module. 2. A HMAC-SHA1 digest of the Cryptographic Module must be generated and embedded in the Cryptographic Module for use by the FIPS_mode_set()10 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the Cryptographic Module and to generate the new HMAC-SHA-1 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 HMAC-SHA-1 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, "no-asm" means that only C language code was compiled. For OpenSSL with x86 there are three possible optimization levels: No optimization (plain C) SSE2 optimization AES-NI+PCLMULQDQ+SSSE3 optimization 10 FIPS_mode_set() calls the Module function FIPS_module_mode_set() © Copyright 2014 CellTrust® Corporation. Page 21 | 25 CellTrust Cryptographic Module 2.0 Security Policy Other theoretically possible combinations (e.g. AES-NI only, or SSE3 only) are not addressed individually, so that a processor which does not support all three of AES-NI, PCLMULQDQ, and SSSE3 will fall back to SSE2 optimization. For more information, see: http://www.intel.com/support/processors/sb/CS-030123.htm?wapkw=sse2 http://software.intel.com/en-us/articles/intel-advanced-encryption-standard-instructions-aes- ni/?wapkw=aes-ni For the Cryptographic Module 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 © Copyright 2014 CellTrust® Corporation. Page 22 | 25 CellTrust Cryptographic Module 2.0 Security Policy AppendixB­ControlledDistributionFileFingerprint The CellTrust Cryptographic Module 2.0 consists of the CTCM (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 openssl-fips-2.0.5.tar.gz with HMACSHA- 1 digest of 54ad8102f73488e9f34d3143b55866a147582810 located at http://www.openssl.org/source/openssl-fips-2.0.5.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.5.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 openssl-fips-ecp-2.0.5.tar.gz with HMAC-SHA-1 digest of 63d8ff138080f1a369018fb0cc1ca9d276b1d39f located at http://www.openssl.org/source/openssl-fips-ecp-2.0.5.tar.gz. 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 HMACSHA-1 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 HMAC-SHA-1 value for the Module integrity check. © Copyright 2014 CellTrust® Corporation. Page 23 | 25 CellTrust Cryptographic Module 2.0 Security Policy AppendixC­Compilers This appendix lists the specific compilers used to generate the CTCM for the respective Operational Environments. Note this list does not imply that use of the CTCM 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 Android 4.2 gcc 4.6 2 Android 4.2 gcc 4.6 3 Apple iOS 7.1 gcc 4.6 4 Apple iOS 7.1 gcc 4.6 Table 11 ­ Compilers © Copyright 2014 CellTrust® Corporation. Page 24 | 25 CellTrust Cryptographic Module 2.0 Security Policy AppendixD­References Reference Full Specification Name Digital Signatures Using Reversible Public Key Cryptography for the Financial [ANS X9.31] Services Industry (rDSA) [FIPS 140-2] Security Requirements for Cryptographic modules, May 25, 2001 [FIPS 180-3] Secure Hash Standard [FIPS 186-4] Digital Signature Standard [FIPS 197] Advanced Encryption Standard [FIPS 198-1] The Keyed-Hash Message Authentication Code (HMAC) Recommendation for Block Cipher Modes of Operation: The CMAC Mode for [SP 800-38B] Authentication Recommendation for Block Cipher Modes of Operation: The CCM Mode for [SP 800-38C] Authentication and Confidentiality Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode [SP 800-38D] (GCM) and GMAC Recommendation for Pair-Wise Key Establishment Schemes Using Discrete [SP 800-56A] Logarithm Cryptography [SP 800-67R1] Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher [SP 800-89] Recommendation for Obtaining Assurances for Digital Signature Applications Recommendation for Random Number Generation Using Deterministic Random [SP 800-90] Bit Generators Transitions: Recommendation for Transitioning the Use of Cryptographic [SP 800-131A] Algorithms and Key Lengths © Copyright 2014 CellTrust® Corporation. Page 25 | 25