OpenSSL FIPS 140-2 Extron Security Policy
© 2020 Extron Electronics Page 1 of 26
Extron FIPS Module
Module Version 2.0.10
Extron FIPS 140-2 Non-Proprietary
Security Policy
Document Version 1.0.1
August 27, 2020
References
Reference Full Specification Name
[ANS X9.31]
Digital Signatures Using Reversible Public Key Cryptography for the Financial Services
Industry (rDSA), ANSI X9.31-1998
[FIPS 140­2] Security Requirements for Cryptographic modules, May 2001
[FIPS 180­4] Secure Hash Standard, August 2015
[FIPS 186­4] Digital Signature Standard (DSS), July 2013
[FIPS 197] Advanced Encryption Standard, November 2001
[FIPS 198­1] The Keyed­Hash Message Authentication Code (HMAC), July 2008
[SP 800­38B]
Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication,
May 2005 (Updated October 2016)
[SP 800­38C]
Recommendation for Block Cipher Modes of Operation: The CCM Mode for
Authentication and Confidentiality, May 2004 (Updated July 2007)
[SP 800­38D]
Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and
GMAC, November 2007
[SP 800­56A]
Recommendation for Pair­Wise Key Establishment Schemes Using Discrete Logarithm
Cryptography, March 2007
[SP 800-56Br2]
Recommendation for Pair-Wise Key-Establishment Using Integer Factorization
Cryptography, March 2019
[SP 800­ 67r2]
Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher, November
2017
[SP 800­89]
Recommendation for Obtaining Assurances for Digital Signature Applications, November
2006
[SP 800­90Ar1]
Recommendation for Random Number Generation Using Deterministic Random Bit
Generators, June 2015
[SP 800­131Ar2]
Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and
Key Lengths, March 2019
OpenSSL FIPS 140-2 Extron Security Policy
© 2020 Extron Electronics Page 3 of 26
Table of Contents
1 Introduction.........................................................................................................................4
2 Tested Configurations .........................................................................................................6
3 Ports and Interfaces ............................................................................................................8
4 Modes of Operation and Cryptographic Functionality.......................................................9
4.1 Critical Security Parameters and Public Keys .......................................................11
5 Roles, Authentication, and Services.................................................................................. 14
6 Self-Test............................................................................................................................. 16
7 Operational Environment .................................................................................................18
8. Mitigation of other Attacks.......................................................................................... 19
Appendix A Installation and Usage Guidance............................................................... 20
Appendix B Controlled Distribution File Fingerprint....................................................23
Appendix C Compilers ....................................................................................................25
OpenSSL FIPS 140-2 Extron Security Policy
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.
© 2020 Extron Electronics Page 4 of 26
1 Introduction
This document is the non-proprietary security policy for the Extron FIPS Module, hereafter
referred to as the Module.
The Module is a software library providing a C-language application program interface (API) for
use by other processes that require cryptographic functionality. The Module 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 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 Extron FIPS Module v2.0.10 is fully backwards compatible with all earlier versions of
the OpenSSL FIPS Object Module RE. The v2.0.10 Module incorporates support for new platforms
without disturbing functionality for any previously tested platforms. The v2.0.10 Module can be
used in any environment supported by the earlier revisions of the Module, and those earlier
revisions remain valid.
The FIPS 140­2 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
Self­Tests 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.10. The v2.0.10 Module incorporates
changes from the v2.0 module to support additional platforms. The v2.0.10 Module can be used in
all the environments supported by the earlier v2.0.9 revision of the Module.
OpenSSL FIPS 140-2 Extron Security Policy
© 2020 Extron Electronics Page 5 of 26
Figure 1 ­ Module Block Diagram
2 Tested Configurations
# Operational Environment Processor
Optimiz
ations
(Target)
EC B
1 TS-Linux 2.4 Arm920Tid (ARMv4) None BKP U2
2 iOS 8.1 64-bit Apple A7 (ARMv8) None BKP U2
3 iOS 8.1 64-bit Apple A7 (ARMv8)
NEON
and
Crypto
Extensions
BKP U2
4 VxWorks 6.9 Freescale P2020 (PPC) None BKP U2
5 iOS 8.1 32-bit Apple A7 (ARMv8) None BKP U2
6 iOS 8.1 32-bit Apple A7 (ARMv8) NEON BKP U2
7 Android 5.0 32-bit Qualcomm APQ8084 (ARMv7) None BKP U2
8 Android 5.0 32-bit Qualcomm APQ8084 (ARMv7) NEON BKP U2
9 Android 5.0 64-bit
SAMSUNG Exynos7420
(ARMv8)
None BKP U2
10 Android 5.0 64-bit
SAMSUNG Exynos7420
(ARMv8)
NEON
and
Crypto
Extensions
BKP U2
11 FreeBSD 10.2 Intel Xeon E5-2430L (x86) None BKP U2
12 FreeBSD 10.2 Intel Xeon E5-2430L (x86) AES-NI BKP U2
13 Yocto Linux 3.10 Freescale i.MX6 (ARMv7) None BKP U2
14 Yocto Linux 3.10 Freescale i.MX6 (ARMv7) NEON BKP U2
15 Linux 4.4 ARM926EJ-S (ARMv5) None BKP U2
16 Timesys 2.6 PowerPC 440 (PPC) None BKP U2
17 uClinux-dist-5.0
Marvell Feroceon 88FR131
(ARMv5TE)
None BKP U1
18 uClinux-dist-5.0 Marvell Armada 370 (ARMv7) None BKP U1
19 uClibc 0.9 ARM926EJS (ARMv5TEJ) None BKP U1
20 uClibc 0.9 Marvell PJ4 (ARMv7) None BKP U1
OpenSSL FIPS 140-2 Extron Security Policy
© 2020 Extron Electronics Page 7 of 26
# Operational Environment Processor
Optimiz
ations
(Target)
EC B
21 uClibc 0.9 ARM922T (ARMv4T) None BKP U1
22 LMOS 7.2 Intel Xeon E3-1231 (x86) None BKP U2
23 LMOS 7.2 Intel Xeon E3-1231 (x86) AES-NI BKP U2
24 Debian 7.9 Marvell Mohawk (ARMv5TE) None BKP U2
25 Linux 3.16 Atmel ATSAMA5D35 (ARMv7) None BKP U1
26 Linux 3.16
Atmel ATSAM9G45
(ARMv5TEJ)
None BKP U1
27 Android 4.4 32-bit Intel Atom Z3735F (x86) None BKP U1
28 Linux 3.14 ARM Cortex A9 (ARMv7) None BKP U2
29 Linux 3.14 ARM Cortex A9 (ARMv7) NEON BKP U2
30 LMOS 7.2 under VMware ESXi 6.5 Intel Xeon E5-2430L (x86) None BKP U2
31 LMOS 7.2 under VMware ESXi 6.5 Intel Xeon E5-2430L (x86) AES-NI BKP U2
32 BAE Systems STOP 8.2 64-bit running
on BAE XTS-600-W-T Intel Xeon E5-1650 None BKP U2
33 BAE Systems STOP 8.2 64-bit running
on BAE XTS-600-W-T Intel Xeon E5-1650 AES-NI BKP U2
34 Ubuntu 12.04
Compulab CM-FX6 Cortex-A9
(ARMv7)
None BKP U1
35 Linux 4.9.11 running on an Extron
NAVigator iMX.6 Cortex A9 None BKP U2
36 Linux 4.9.11 running on an Extron
NAVigator iMX.6 Cortex A9 NEON BKP U2
37 Linux 4.14.0 running on an Extron E
101 Zynq Ultrascale+ Cortex A53 None BKP U2
38 Linux 4.14.0 running on an Extron E
101 Zynq Ultrascale+ Cortex A53 NEON BKP U2
39 Linux 4.14.0 running on an Extron
SD 101 Zynq Ultrascale+ Cortex A53 None BKP U2
40 Linux 4.14.0 running on an Extron
SD 101 Zynq Ultrascale+ Cortex A53 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
foralistofthespecificcompilersusedtogeneratetheModulefortherespectiveoperational
environments.
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 C­language 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 moduleisperformingself­tests,orisinanerrorstate,alloutputonthelogicaldata
output interfaceisinhibited.Themoduleissingle­threadedandinerrorscenariosreturnsonly
anerror value (no data output is returned).
OpenSSL FIPS 140-2 Extron Security Policy
8 FIPS_mode_set() calls Module function FIPS_module_mode_set()
© 2020 Extron Electronics Page 9 of 26
4 Modes of Operation and Cryptographic Functionality
The Module supports a FIPS 140­2 Approved mode and a Non-Approved Mode. Tables 4a
and 4b list the Approved and Non­approved but Allowed algorithms, respectively.
Function Algorithm Options Cert #
Random Number
Generation;
Symmetric key
generation
[SP 800­90r1] DRBG5
Prediction resistance
supported for all variations
Hash DRBG
HMAC DRBG, no reseed
CTR DRBG (AES), no derivation function
607
723
C1924
Encryption,
Decryption and
CMAC
[SP 800­67r2]
3-Key TDES TECB, TCBC, TCFB, TOFB;
CMAC generate and verify
1780
1853
C1924
[FIPS 197] AES
128/ 192/256 ECB, CBC, OFB, CFB 1, CFB 8,
CFB 128, CTR, XTS; CCM; GCM; CMAC
generate and verify
3090
3264
C1924
[SP 800-38B] CMAC
[SP 800­38C] CCM
[SP 800­38D] GCM
[SP 800­38E] XTS
Message Digests [FIPS 180­4] SHA­1, SHA­2 (224, 256, 384, 512)
2553
2702
C1924
Keyed Hash [FIPS 198] HMAC SHA­1, SHA­2 (224, 256, 384, 512)
1937
2063
C1924
Digital Signature and
Asymmetric Key
Generation
[FIPS 186­2] RSA
SigGen9.31, SigGenPKCS1.5, SigGenPSS
(4096 with all SHA-2 sizes)
SigVer9.31, SigVerPKCS1.5, SigVerPSS
(1024/1536/2048/3072/4096 with all SHA sizes)
1581
1664
C1924
[FIPS 186­4] RSA
SigGen9.31, SigGenPKCS1.5, SigGenPSS
(2048/3072 with all SHA-2 sizes)
1581
1664
C1924
[FIPS 186-4] DSA
Key Pair Gen (2048/3072)
PQG Gen, Sig Gen (2048/3072 with all SHA-2
sizes)
PQG Ver, Sig Ver (1024/2048/3072 with all
SHA
sizes)
896
933
C1924
[FIPS 186-4] ECDSA
PKG: CURVES (P-224 P-256 P-384 P-521 K-
224 K-256 K-384 K-571 B-224 B-256 B-384 B-
571 ExtraRandomBits TestingCandidates)
PKV: CURVES (ALL-P ALL-K ALL-B)
SigGen: CURVES (P-224: (SHA-224, 256, 384,
512) P-256: (SHA-224, 256, 384, 512) P-384:
(SHA-224, 256, 384, 512) P-521: (SHA-224,
256, 384, 512) K-233: (SHA-224, 256, 384, 512)
K-283: (SHA-224, 256, 384, 512) K-409: (SHA-
224, 256, 384, 512) K-571: (SHA-224, 256, 384,
512) B-233: (SHA-224, 256, 384, 512) B-283:
(SHA-224, 256, 384, 512) B-409: (SHA-224,
256, 384, 512) B-571: (SHA-224, 256, 384, 512)
558
620
C1924
Table 4a – FIPS Approved Cryptographic Functions
Note: Not all algorithms, modes, or key sizes verified through CAVP certificates are implemented in
the Approved mode by the module.
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 Non-compliant (untested) DH scheme using elliptic curve, supporting all NIST
defined B, K and P curves except sizes 163 and 192. Key agreement is a service
provided for calling process use but is not used to establish keys into the Module.
(key agreement; key establishment methodology provides between 112 and 256
bits of encryption strength)
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 800-
56Br2 compliance, and no CSPs are established into or exported
out of the module using these services. (key agreement; key
establishment methodology provides between 112 and 256 bits of
encryption strength)
Table 4b – Non­FIPS Approved But Allowed Cryptographic Functions
TheModuleimplementsthefollowingserviceswhichareNon­ApprovedpertheSP800­131A
transition:
Function Algorithm Options
Random Number
Generation; Symmetric
key
generation
[ANS X9.31] RNG AES 128/192/256
)
SigVer: CURVES (P-192: (SHA-1, 224, 256,
384, 512) P-224: (SHA-1, 224, 256, 384, 512) P-
256: (SHA-1, 224, 256, 384, 512) P-384: (SHA-
1, 224, 256, 384, 512) P-521: (SHA-1, 224, 256,
384, 512) K-163: (SHA-1, 224, 256, 384, 512)
K-233: (SHA-1, 224, 256, 384, 512) K-283:
(SHA-1, 224, 256, 384, 512) K-409: (SHA-1,
224, 256, 384, 512) K-571: (SHA-1, 224, 256,
384, 512 B-163: (SHA-1, 224, 256, 384, 512) B-
233: (SHA-1, 224, 256, 384, 512) B-283: (SHA-
1, 224, 256, 384, 512) B-409: (SHA-1, 224, 256,
384, 512) B-571: (SHA-1, 224, 256, 384, 512))
ECC CDH (KAS) [SP 800-56A] (§5.7.1.2)
All NIST defined B, K and P curves except sizes
163 and 192
372
472
C1924
OpenSSL FIPS 140-2 Extron Security Policy
6 "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 RE.
© 2020 Extron Electronics Page 11 of 26
Random Number
Generation; Symmetric
key
generation
[SP 800­90Ar1] DRBG Dual EC DRBG
(note the Dual EC DRBG algorithm shall not be
used in the FIPS Approved mode of operation)
Digital Signature and
Asymmetric Key
Generation
[FIPS 186­2] RSA GenKey9.31 (1024/1536/2048, 3072, 4096),
SigGen9.31, SigGenPKCS1.5, SigGenPSS
(1024/1536/2048/3072 with all SHA sizes, 4096 with
SHA-1)
[FIPS 186­2] DSA PQG Gen, Key Pair Gen, Sig Gen (1024 with all
SHA sizes, 2048/3072 with SHA-1)
[FIPS 186­4] DSA PQG Gen, Key Pair Gen, Sig Gen (1024 with all
SHA sizes, 2048/3072 with SHA-1)
[FIPS 186­2] ECDSA PKG: CURVES (P-192 K-163 B-163)
SIG (gen): CURVES (P-192 P-224 P-256 P-384
P-521 K-163 K-233 K-283 K-409 K-571 B-163
B-233 B-283 B-409 B-571)
[FIPS 186­4] ECDSA PKG: CURVES (P-192 K-163 B-163)
SigGen: CURVES (P-192: (SHA-1, 224, 256,
384, 512) P-224:(SHA-1) P-256:(SHA-1) P-384:
(SHA-1) P-521:(SHA-1) K-163: (SHA-1, 224,
256, 384, 512) K-233:(SHA-1) K-283:(SHA-1)
K-409:(SHA-1) K-571:(SHA-1) B-163: (SHA-1,
224, 256, 384, 512) B-233:(SHA-1) B-283:
(SHA-1) B-409:(SHA-1) B-571:(SHA-1))
ECC CDH (CVL)
[SP 800­56A] (§5.7.1.2) All NIST Recommended B, K and P curves
sizes 163 and 192
Table 4c – FIPS Non­Approved Cryptographic Functions
X9.31 RNG is Non-Approved effective December 31, 2015, per the CMVP Notice "X9.31 RNG
transition, December 31, 2015".
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()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 186-3 assurances are outside the scope of the Module, and are
the responsibility of the calling process.
4.1 Critical Security Parameters and Public Keys
AllCSPsusedbytheModulearedescribedinthissection.AllaccesstotheseCSPsbyModule services
aredescribedinSection4. TheCSPnamesaregeneric,correspondingtoAPIparameter 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 186­4] DSA (1024/2048/3072) signature generation key or [FIPS 186­2] DSA
(1024) signature generation key
ECDSA SGK ECDSA (All NIST defined B, K, and P curves except sizes 163 and 192) signature generation
key
EC DH Private EC DH (All NIST defined B, K, and P curves except sizes 163 and 192) 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 (3­Key) encrypt / decrypt key
TDES CMAC TDES (3­Key) 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)
CO­AD­Digest Pre-calculated HMAC-SHA-1 digest used for Crypto Officer role authentication
User­AD­Digest Pre­calculated HMAC­SHA­1 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 186­4] DSA (1024/2048/3072) signature verification key or [FIPS 186­2] 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 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 800-90Ar1 compliant DRBG services for creation of
OpenSSL FIPS 140-2 Extron Security Policy
© 2020 Extron Electronics Page 13 of 26
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 (Crypto-Officer 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
AES-GCM keys used for encryption or decryption are re-distributed.
Module users (the calling applications) shall use entropy sources that meet the security strength
required for the random number generation mechanism as shown in [SP 800-90Ar1] 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.
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 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.
Self­test User, CO Performs 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 *)
• FIPSMode(Boolean)
Does not accessCSPs.
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 a DRBG instance
• Determine security strength of a DRBGinstance
• Obtain random data
UsesandupdatesHash_DRBGCSPs,HMAC_DRBGCSPs,CTR_DRBGCSPs.
OpenSSL FIPS 140-2 Extron Security Policy
7 "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 RE.
© 2020 Extron Electronics Page 15 of 26
Service Role Description
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 SP800-90Ar1
Symmetric
encrypt/decrypt
User, CO
Used to encrypt or decrypt data.
Executes using AES EDK, TDES EDK (passed in by the calling process).
Symmetric
digest
User, CO
Used to generate or verify data integrity with CMAC.
Executes using AES CMAC, TDES, CMAC (passed in by the calling process).
Message digest User, CO
Used to generate a SHA­1 or SHA­2 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 transport7
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
Usedtoperformkeyagreement primitivesonbehalf of the callingprocess (does not
establish keys into the module).
ExecutesusingECDHPrivate,ECDHPublic(passedinbythecallingprocess).
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
OpenSSL FIPS 140-2 Extron Security Policy
8 FIPS_mode_set() calls Module function FIPS_module_mode_set()
© 2020 Extron Electronics Page 16 of 26
6 Self-Test
The Module performs the self­tests listed below on invocation of Initialize or Self­Test.
Algorithm Type Test Attributes
Software integrity KAT HMAC-SHA1
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
XTS-AES KAT 128, 256-bit key sizes to support either the 256-bit key size (for 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
Triple-DES KAT Separate encrypt and decrypt, ECB mode, 3-Key
Triple-DES 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
DRBG KAT CTR_DRBG:AES,256-bitwithandwithoutderivationfunction
HASH_DRBG: SHA256
HMAC_DRBG: SHA256
Dual_EC_DRBG: P-256 and SHA256
ECDSA PCT Keygen, sign, verify using P-224, K-233 and SHA512. The K-233 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
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 HMAC-SHA-1 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()8 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 function calls. The module will only enter the FIPS Approved
mode if the module is reloaded and the call to FIPS_mode_set()8 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.
OpenSSL FIPS 140-2 Extron Security Policy
© 2020 Extron Electronics Page 17 of 26
The Module also implements the following conditional tests:
Algorithm Test
DRBG Tested as required by [SP800-90Ar1] Section 11
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
Table 6b ­ Conditional Tests
In the event of a DRBG self-test failure the calling application must un-instantiate and re-
instantiate the DRBG per the requirements of [SP 800-90Ar1]; 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").
7 Operational Environment
Thetestedoperatingsystemssegregateuserprocessesintoseparateprocessspaces. Each process
spaceislogicallyseparatedfromallotherprocessesbytheoperatingsystemsoftware andhardware.
TheModulefunctionsentirelywithintheprocessspaceofthecallingapplication, andimplicitlysatisfies
theFIPS140­2requirementforasingleusermodeofoperation.
OpenSSL FIPS 140-2 Extron Security Policy
© 2020 Extron Electronics Page 19 of 26
8. Mitigation of other Attacks
ThemoduleisnotdesignedtomitigateagainstattackswhichareoutsideofthescopeofFIPS 140­2.
OpenSSL FIPS 140-2 Extron Security Policy
9 For some prospective users the acquisition, installation, and configuration of a suitable FIPS 140-2 validated
product may not be convenient. OVS 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 140-2
validated implementation of HMAC-SHA-1. For instructions on requesting this CD see http://openssl.com/fips/verify.html.
© 2020 Extron Electronics Page 20 of 26
Appendix A Installation and Usage Guidance
Thetestplatformsrepresentdifferentcombinationsofinstallationinstructions. Foreach platform
there is a build system, the host providing the build environment in which the installation
instructionsareexecuted,andatargetsystemonwhichthegeneratedobjectcodeis executed. The
buildandtargetsystemsmaybethesametypeofsystemoreventhesamedevice ormaybedifferent
systems–theModulesupportscross­compilationenvironments.
Eachofthesecommandsetsarerelativetothetopofthedirectorycontainingtheuncompressed and
expandedcontentsofthedistributionfilesopenssl­fips­2.0.10.tar.gz(allNISTdefined curves as
listed in Table 2 with the EC column marked "BKP") oropenssl­fips­ecp­2.0.10.tar.gz (NIST prime
curves onlyas listed in Table 2 with theEC 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. Downloadandcopythedistributionfiletothebuildsystem.
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
independentlyacquiredFIPS140­2validatedimplementationofSHA­1HMACmustbe used
forthisdigestverification. Notethat thisverificationcan beperformedonany convenient
systemandnotnecessarilyonthespecificbuildortargetsystem.
Alternatively, a copy of the distribution on physical media can be obtained from OVS9.
3. Unpack the distribution
gunzip -c openssl-fips-2.0.10.tar.gz | tar xf -
cd openssl-fips-2.0.10
OpenSSL FIPS 140-2 Extron Security Policy
© 2020 Extron Electronics Page 21 of 26
or
gunzip -c openssl-fips-ecp-2.0.10.tar.gz | tar xf -
cd openssl-fips-ecp-2.0.10
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. ThecallingapplicationenablesFIPSmodebycallingtheFIPS_mode_set()10 function.
Notethat failuretouse oneofthe specifiedcommands sets exactly asshown will result ina
module that cannot be considered compliant with FIPS 140-2.
Linking the Runtime Executable Application
NotethatapplicationsinterfacingwiththeFIPSObjectModuleareoutsideofthecryptographic
boundary. WhenlinkingtheapplicationwiththeFIPSObjectModuletwostepsarenecessary:
1. The HMAC-SHA-1 digest of the FIPS Object Module file must be calculated and verified
against the installed digest to ensuretheintegrity of the FIPSobject module.
2. AHMAC-SHA1 digest of the FIPS Object Module must be generated andembedded in the
FIPS Object 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 FIPS
Object Module and to generate the new HMAC-SHA-1 digest for the runtime executable
application. Failuretoembedthedigestintheexecutableobjectwillpreventinitializationof
FIPS mode.
At runtime the FIPS_mode_set()10
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
chainofvalidationfromtheoriginalsourcetotheruntimeexecutableapplicationfile.
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:
1. No optimization (plain C)
2. SSE2 optimization
3. AES-NI+PCLMULQDQ+SSSE3 optimization
Other theoretically possible combinations (e.g., AES-NI only, or SSE3 only) are not
10 FIPS_mode_set() calls Module function FIPS_module_mode_set()
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-
instructionsaes-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
OpenSSL FIPS 140-2 Extron Security Policy
© 2020 Extron Electronics Page 23 of 26
Appendix B Controlled Distribution File Fingerprint
TheExtron FIPS Module v2.0.10consistsoftheFIPSObjectModule(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.10.tar.gz withHMAC-
SHA-1 digest of
af8bda4bb9739e35b4ef00a9bc40d21a6a97a780
located at http://www.openssl.org/source/openssl-fips-2.0.10.tar.gz.
Theopenssl commandfromaversionofOpenSSLthatincorporatesapreviouslyvalidated
version of the module may be used:
openssl sha1 -hmac etaonrishdlcupfm openssl-fips-2.0.10.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.10.tar.gz with
HMAC-SHA-1 digest of
02cc9ddfffb2e917d1cdc9ebc97a9731c40f6394
located at http://www.openssl.org/source/openssl-fips-ecp-2.0.10.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.10.
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 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
HMAC-SHA-1 digests are listed below:
openssl-fips-2.0.9.tar.gz
URL: http://www.openssl.org/source/openssl-fips-2.0.9.tar.gz
Digest: 54552e9a3ed8d1561341e8945fcdec55af961322
openssl-fips-ecp-2.0.9.tar.gz
URL: http://www.openssl.org/source/openssl-fips-ecp-2.0.9.tar.gz
Digest: 91d267688713c920f85bc5e69c8b5d34e1112672
OpenSSL FIPS 140-2 Extron Security Policy
© 2020 Extron Electronics Page 25 of 26
Appendix C Compilers
ThisappendixliststhespecificcompilersusedtogeneratetheModulefortherespective
OperationalEnvironments.NotethislistdoesnotimplythatuseoftheModuleisrestrictedto
onlythelistedcompilerversions,onlythattheuseofotherversionshasnotbeenconfirmedto
produce a correct result.
# Operational Environment Compiler
1 TS-Linux 2.4 gcc 4.3.2
2 iOS 8.1 64-bit clang-600.0.56
3 iOS 8.1 64-bit clang-600.0.56
4 VxWorks 6.9 gcc 4.3.3
5 iOS 8.1 32-bit clang-600.0.56
6 iOS 8.1 32-bit clang-600.0.56
7 Android 5.0 gcc 4.9
8 Android 5.0 gcc 4.9
9 Android 5.0 64-bit gcc 4.9
10 Android 5.0 64-bit gcc 4.9
11 FreeBSD 10.2 clang 3.4.1
12 FreeBSD 10.2 clang 3.4.1
13 Yocto Linux 3.10 gcc 4.8.1
14 Yocto Linux 3.10 gcc 4.8.1
15 Linux 4.4 gcc 4.8.3
16 Timesys 2.6 gcc 4.6.3
17 uClinux-dist-5.0 gcc 4.8.3
18 uClinux-dist-5.0 gcc 4.8.3
19 uClibc 0.9 gcc 4.8.1
20 uClibc 0.9 gcc 4.8.1
21 uClibc 0.9 gcc 4.8.1
22 LMOS 7.2 gcc 4.8.4
# Operational Environment Compiler
23 LMOS 7.2 gcc 4.8.4
24 Debian 7.9 gcc 4.4.5
25 Linux 3.16 gcc 4.8.3
26 Linux 3.16 gcc 4.8.3
27 Android 4.4 gcc 4.8
28 Linux 3.14 gcc 4.8.2
29 Linux 3.14 gcc 4.8.2
30 LMOS 7.2 gcc 4.8.4
31 LMOS 7.2 gcc 4.8.4
32 BAE Systems STOP 8.2 64-bit gcc 4.8.5
33 BAE Systems STOP 8.2 64-bit gcc 4.8.5
34 Ubuntu 12.04 gcc 4.6.3
35 Linux 4.9.11 gcc 7.2.1
36 Linux 4.14.0 gcc 7.2.1
Table C ­ Compilers