This page was not yet optimized for use on mobile devices.

Digi ConnectCore Security Module

Certificate details

Certificate ID	#3176
Status	historical
Historical reason	186-2 transition
Validation dates	26.04.2018 , 12.06.2018
Standard	FIPS 140-2
Security level	1
Type	Software
Embodiment	Multi-Chip Stand Alone
Caveat	When built, installed, protected and initialized as assumed by the Crypto Officer role and as specified in the provided Security Policy. Appendix A of the provided Security Policy specifies the actual distribution tar file containing the source code of this module. There shall be no additions, deletions or alterations to the tar file contents as used during module build. The distribution tar file shall be verified as specified in Appendix A of the provided Security Policy. Installation and protection shall be completed as specified in Appendix A of the provided Security Policy. Initialization shall be invoked as per Section 4 of the provided Security Policy. Any deviation from specified verification, protection, installation and initialization procedures will result in a non FIPS 140-2 compliant module. This validation entry is a non-security relevant modification to Cert. #2398
Exceptions	Roles, Services, and Authentication: Level 2 Physical Security: N/A Design Assurance: Level 3 Mitigation of Other Attacks: N/A
Description	The Digi ConnectCore Security Module provides cryptographic services for Digi International Inc. products.
Tested configurations	Yocto Linux 2.4 running on ConnectCore 6/6UL SoM (ARMv7) without PAA (gcc Compiler Version 7.3.0), Yocto Linux 2.4 running on ConnectCore 6/6UL SoM (ARMv7) with PAA (gcc Compiler Version 7.3.0) (single-user mode)
Vendor	Digi International, Inc. http://www.digi.com
Lab	Acumen Security
Algorithms	AES#5323 CVL#1788 DRBG#2053 DSA#1375 ECDSA#1397 HMAC#3521 RSA#2851 SHS#4275 Triple-DES#2686
References	This certificate's webpage directly references 1 certificates, transitively this expands into 1 certificates.

Certificate

Webpage

Security policy

Security policy PDF TXT

Extracted keywords

Symmetric Algorithms

AES, TDEA, TDES, HMAC, CMAC

Asymmetric Algorithms

ECDSA, ECC, DH, DSA

Hash functions

SHA-1, SHA1, SHA-224, SHA224, SHA256, SHA384, SHA512, SHA-256, SHA-384, SHA-2

Schemes

Key Agreement, Key agreement

Randomness

DRBG, RNG

Libraries

OpenSSL

Elliptic Curves

P-224, P-521, P-192, P-256, P-384, K-409, B-233, B-409, K-233, B-163, B-283, B-571, K-256, K-521, B-256

Block cipher modes

ECB, CBC, CTR, CFB, OFB, GCM, CCM, XTS

Security level

level 1

Standards

FIPS 140-2, FIPS 180-3, FIPS 186-4, FIPS 197, FIPS 198-1, FIPS 198, FIPS 186-2, FIPS 186-3, SP 800-38B, SP 800-38C, SP 800-38D, SP 800-56A, SP 800-89, SP 800-90, SP 800-67, SP 800-38E, SP 800-56B, SP 800-131A, PKCS#1

Author	CPUBuilders Customer
Creation date	D:20180330153146-04'00'
Pages	25
Creator	Writer
Producer	LibreOffice 5.1

Automated analysis

Automated inference - use with caution

All attributes shown in this section (e.g., links between certificates, products, vendors, and known CVEs) are generated by automated heuristics and have not been reviewed by humans. These methods can produce false positives or false negatives and should not be treated as definitive without independent verification. This applies equally to the Cross-references section below. If you want to know more about how this data is computed and how reliable it is, see our documentation on automated analysis. If you believe any information here is inaccurate or harmful, please submit feedback.

No automatically derived data are available in this section.

Cross-references

Processing updates

06.10.2026

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'HMAC SHA-1': 1, 'platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON': 1}, '__update__': {'AES 128/192/256': 3}, '__delete__': ['platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON Page 3 of 25 ####### Digi ConnectCore Security Module - FIPS 140-2 Security Policy ####### References | Reference | Full Specification Name | |----------------|---------------------------------------------------------------------------------------------------------| | [ANS X9.31] | Digital Signatures Using Reversible Public Key Cryptography for the Financial 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) | | [SP 800-38B] | Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication | | [SP 800-38C] | Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality | | [SP 800-38D] | Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC | | [SP 800-56A] | Recommendation for Pair-Wise Key Establishment Schemes Using Discrete 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 | | [SP 800-90] | Recommendation for Random Number Generation Using Deterministic Random Bit Generators | | [SP 800- 131A] | Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths | Page 4 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ##### Table of Contents | 1 Introduction.........................................................................................................................6 | |----------------------------------------------------------------------------------------------------------------------------------------------| | 2 Tested Configurations.........................................................................................................8 | | 2.1 Tested Environments...................................................................................................8 | | 2.2 Vendor Affirmed Environments..................................................................................8 | | 3 Ports and Interfaces.............................................................................................................9 | | 4 Modes of Operation and Cryptographic Functionality.......................................................10 | | 4.1 Critical Security Parameters and Public Keys.............................................................13 | | 5 Roles, Authentication and Services....................................................................................16 | | 6 Self-test...............................................................................................................................18 | | 7 Operational Environment....................................................................................................20 | | 8 Mitigation of other Attacks.................................................................................................21 | | Appendix A Installation and Usage Guidance.......................................................................22 | | Appendix B Controlled Distribution File Fingerprint...........................................................24 | | Appendix C Compilers..........................................................................................................25 | Page 5 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 1 Introduction This document is the non-proprietary security policy for the Digi ConnectCore Security Module , hereafter referred to as the Module. The Module is based on the OpenSSL FIPS Object Module v2.0 . 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 fi pscanister.o . The Module performs no communications other than with the calling application (the process that invokes the Module services). Note that the Digi ConnectCore Security Module v1.0 is fully backwards compatible with all earlier revisions of the Digi ConnectCore Security Module . The v1.0 Module incorporates support for new platforms without disturbing functionality for any previously tested platforms. The v1.0 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 Page 6 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ####### The Module\'s software version for this validation is 1.0. Figure 1 - Module Block Diagram Page 7 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ### 2 Tested Configurations ### 2.1 Tested Environments Table 2.1 - Tested Configurations | # | Operational Environment | Processor | Optimiz-ations (Target) | |-----|---------------------------|-------------------------------|---------------------------| | 1 | Yocto Linux 2.4 | ConnectCore 6/6UL SoM (ARMv7) | None | | 2 | Yocto Linux 2.4 | ConnectCore 6/6UL SoM (ARMv7) | NEON | See Appendix A for additional information on build method. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. ### 2.2 Vendor Affirmed Environments The following platforms have not been tested as part of this FIPS 140-2 level 1 validation. However Digi International \'vendor affirms\' that these platforms are equivalent to the tested and validated platforms and the Module will function the same way and provide the same security services on any of the systems listed below. Table 2.2 - Vendor Affirmed Configurations | # | Operational Environment | Processor | Optimiz-ations (Target) | |-----|---------------------------|---------------------------|---------------------------| | 1 | Yocto Linux 2.4 | ConnectCore 6 SoM (ARMv7) | None | | 2 | Yocto Linux 2.4 | ConnectCore 6 SoM (ARMv7) | NEON | Page 8 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 C-language application program interface (API). Table 3 - Logical interfaces | Logical interface type | Description | |--------------------------|-----------------------------------------------------------| | Control input | API entry point and corresponding stack parameters | | Data input | API entry point data input stack parameters | | Status output | API entry point return values and status stack parameters | | Data output | API entry point data output stack parameters | As a software module, control of the physical ports is outside module scope. However, when the module is performing self-tests, or is in an error state, all output on the logical data output interface is inhibited. The module is single-threaded and in error scenarios returns only an error value (no data output is returned). Page 9 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 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-90] DRBG 1 Prediction resistance supported for all variations | Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function | 2053 | | Encryption, Decryption and CMAC | [SP 800-67] | 3-Key TDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify | 2686 | | | [FIPS 197] AES | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 5323 | | Message | [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM [SP 800-38E] XTS | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 5323 | | Digests | [FIPS 180-3] | SHA-1, SHA-2 (224, 256, 384, 512) | 4275 | | Keyed Hash | [FIPS 198] HMAC | SHA-1, SHA-2 (224, 256, 384, 512) | 3521 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] RSA | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS, SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072/4096 with all SHA-2 sizes) | 2851 | | | [FIPS 186-4] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA-2 sizes) | 1375 | | | [FIPS 186-2] ECDSA | PKG: CURVES( P-224 P-384 P-521 K-233 K- 283 K-409 K-571 B-233 B-283 B-409 B-571 ) PKV: 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 ) | 1397 | | | | PKG: CURVES( P-224 P-384 P-521 ) PKV: CURVES( P-192 P-224 P-256 P-384 P-521 ) | 1397 | Page 10 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4a - FIPS Approved Cryptographic Functions | | [FIPS 186-4] ECDSA | PKG: CURVES( P-224 P-256 P-384 P-521 K- 224 K-256 K-384 K-521 B-224 B-256 B-384 B- 521 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) ) 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) ) | | |---------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| | | [FIPS 186-4] ECDSA | PKG: CURVES( P-224 P-256 P-384 P-521 ) PKV: CURVES( ALL-P ) 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) ) 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) ) | | | ECC CDH (KAS) | [SP 800-56A] (§5.7.1.2) | All NIST defined B, K and P curves except sizes 163 and 192 | 1788 | The Module supports only NIST defined curves for use with ECDSA and ECC CDH. Page 11 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy | Category | Algorithm | Description | |----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC DH | Non-compliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. | | Key Encryption, Decryption | RSA | The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. | Table 4b - Non-FIPS Approved But Allowed Cryptographic Functions The Module implements the following services which are Non-Approved per the SP 800-131A transition: | Function | Algorithm | Options | Cert # | |----------------------------------------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| | Random Number Generation; Symmetric key generation | [ANS X9.31] RNG | AES 128/192/256 | | | Random Number Generation; Symmetric key generation | [SP 800-90] 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, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/4096 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [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 ) | | | Digital Signature and Asymmetric Key Generation | [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) ) | | Page 12 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4c - FIPS Non-Approved Cryptographic Functions | ECC CDH (CVL) | [SP 800-56A] (§5.7.1.2) | All NIST Recommended B, K and P curves sizes 163 and 192 | |-----------------|---------------------------|------------------------------------------------------------| 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() 2 , 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 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 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) 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 (3-Key) encrypt / decrypt key | Page 13 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4.1a - Critical Security Parameters | 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 | 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. | ###### 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-90 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. Table 4.1b - Public Keys Page 14 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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-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. Page 15 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 5 Roles, Authentication and Services The Module implements the required User and Crypto Officer roles and requires authentication for those roles. Only one role may be active at a time and the Module does not allow concurrent operators. The User or Crypto Officer role is assumed by passing the appropriate password to the FIPS_module_mode_set() function. The password values may be specified at build time and must have a minimum length of 16 characters. Any attempt to authenticate with an invalid password will result in an immediate and permanent failure condition rendering the Module unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the Module during the Module build process, performed by the Crypto Officer, and otherwise cannot be accessed. Since minimum password length is 16 characters, the probability of a random successful authentication attempt in one try is a maximum of 1/256 16 , or less than 1/10 38 . The Module permanently disables further authentication attempts after a single failure, so this probability is independent of time. Both roles have access to all of the services provided by the Module. - User Role (User): Loading the Module and calling any of the API functions. - Crypto Officer Role (CO): Installation of the Module on the host computer system and calling of any API functions. All services implemented by the Module are listed below, along with a description of service CSP access. | Service | Role | Description | |-------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Initialize | User, CO | Module initialization. Does not access CSPs. | | Self-test | User, CO | Perform self tests (FIPS_selftest). Does not access CSPs. | | Show status | User, CO | Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. | | Zeroize | User, CO | Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. | | Random | User, CO | Used for random number and symmetric key generation. | Page 16 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 5 - Services and CSP Access | Service | Role | Description | |---------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | number generation | | Seed or reseed a DRBG instance Determine security strength of a DRBG instance Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. | | Asymmetric key generation | User, CO | Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP800-90 | | 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 transport 3 | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | | Key agreement | User, CO | Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). | | Digital signature | User, CO | Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). | | Utility | User, CO | Miscellaneous helper functions. Does not access CSPs. | 3 "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 Digi ConnectCore Security Module . Page 17 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 6 Self-test The Module performs the self-tests listed below on invocation of Initialize or Self-test. Table 6a - Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency 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 | | 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 | | DRBG | KAT | CTR_DRBG: AES, 256 bit with and without derivation function 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.1). | | ECC CDH | KAT | Shared secret calculation per SP 800-56A §5.7.1.2, IG 9.6 | The Module is installed using 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() 4 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() 4 succeeds. 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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 Module also implements the following conditional tests: Table 6b - Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Tested as required by [SP800-90] 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 | 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 Module can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. Page 19 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 140-2 requirement for a single user mode of operation. Page 20 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. Page 21 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix A Installation and Usage Guidance 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 digi-fips-1.0.tar.gz . The command sets are: ``` ./config make make install ``` ####### Installation instructions 1. Download and copy the distribution file to the build system. 2. Verify the HMAC-SHA-1 digest of the distribution file; see Appendix B. An independently acquired FIPS 140-2 validated implemention 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 4. Execute the installation command sets as shown above. No other command sets shall be used. 5. The resulting fi pscanister.o file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 5 function. ``` gunzip -c digi-fips-1.0.tar.gz | tar xf - ``` 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 Module are outside of the cryptographic boundary. When linking the application with the Module two steps are necessary: 1. The HMAC-SHA-1 digest of the Module file must be calculated and verified against the installed digest to ensure the integrity of the Module. 5 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 22 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 2. A HMAC-SHA1 digest of the Module must be generated and embedded in the Module for use by the FIPS_mode_set() 5 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the 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() 5 function compares the embedded HMAC-SHA-1 digest with a digest generated from the Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. Page 23 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix B Controlled Distribution File Fingerprint The Digi ConnectCore Security Module v1.0 consists of the Module (the fi pscanister.o contiguous unit of binary object code) generated from the specific source files. The source files are in the specific special distribution file digi-fips-1.0.tar.gz with HMACSHA-1 digest of e8dbfa6cb9e22a049ec625ffb7ccaf33e6116598 The distribution is obtained by directly contacting Digi International, Inc. 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 distribution file (and patch file if used) shall be verified using the above HMAC-SHA-1 digest. Page 24 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix C Compilers This appendix lists the specific compilers used to generate the Module for the respective Operational Environments. Note this list does not imply that use of the Module is restricted to only the listed compiler versions, only that the use of other versions has not been confirmed to produce a correct result. Table C - Compilers | # | Operational Environment | Compiler | |-----|---------------------------|------------| | 1 | Yocto Linux 2.4 | gcc 7.3.0 | | 2 | Yocto Linux 2.4 | gcc 7.3.0 | Page 25 of 25']}}}} data.
05.10.2026

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON Page 3 of 25 ####### Digi ConnectCore Security Module - FIPS 140-2 Security Policy ####### References | Reference | Full Specification Name | |----------------|---------------------------------------------------------------------------------------------------------| | [ANS X9.31] | Digital Signatures Using Reversible Public Key Cryptography for the Financial 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) | | [SP 800-38B] | Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication | | [SP 800-38C] | Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality | | [SP 800-38D] | Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC | | [SP 800-56A] | Recommendation for Pair-Wise Key Establishment Schemes Using Discrete 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 | | [SP 800-90] | Recommendation for Random Number Generation Using Deterministic Random Bit Generators | | [SP 800- 131A] | Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths | Page 4 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ##### Table of Contents | 1 Introduction.........................................................................................................................6 | |----------------------------------------------------------------------------------------------------------------------------------------------| | 2 Tested Configurations.........................................................................................................8 | | 2.1 Tested Environments...................................................................................................8 | | 2.2 Vendor Affirmed Environments..................................................................................8 | | 3 Ports and Interfaces.............................................................................................................9 | | 4 Modes of Operation and Cryptographic Functionality.......................................................10 | | 4.1 Critical Security Parameters and Public Keys.............................................................13 | | 5 Roles, Authentication and Services....................................................................................16 | | 6 Self-test...............................................................................................................................18 | | 7 Operational Environment....................................................................................................20 | | 8 Mitigation of other Attacks.................................................................................................21 | | Appendix A Installation and Usage Guidance.......................................................................22 | | Appendix B Controlled Distribution File Fingerprint...........................................................24 | | Appendix C Compilers..........................................................................................................25 | Page 5 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 1 Introduction This document is the non-proprietary security policy for the Digi ConnectCore Security Module , hereafter referred to as the Module. The Module is based on the OpenSSL FIPS Object Module v2.0 . 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 fi pscanister.o . The Module performs no communications other than with the calling application (the process that invokes the Module services). Note that the Digi ConnectCore Security Module v1.0 is fully backwards compatible with all earlier revisions of the Digi ConnectCore Security Module . The v1.0 Module incorporates support for new platforms without disturbing functionality for any previously tested platforms. The v1.0 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 Page 6 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ####### The Module\'s software version for this validation is 1.0. Figure 1 - Module Block Diagram Page 7 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ### 2 Tested Configurations ### 2.1 Tested Environments Table 2.1 - Tested Configurations | # | Operational Environment | Processor | Optimiz-ations (Target) | |-----|---------------------------|-------------------------------|---------------------------| | 1 | Yocto Linux 2.4 | ConnectCore 6/6UL SoM (ARMv7) | None | | 2 | Yocto Linux 2.4 | ConnectCore 6/6UL SoM (ARMv7) | NEON | See Appendix A for additional information on build method. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. ### 2.2 Vendor Affirmed Environments The following platforms have not been tested as part of this FIPS 140-2 level 1 validation. However Digi International \'vendor affirms\' that these platforms are equivalent to the tested and validated platforms and the Module will function the same way and provide the same security services on any of the systems listed below. Table 2.2 - Vendor Affirmed Configurations | # | Operational Environment | Processor | Optimiz-ations (Target) | |-----|---------------------------|---------------------------|---------------------------| | 1 | Yocto Linux 2.4 | ConnectCore 6 SoM (ARMv7) | None | | 2 | Yocto Linux 2.4 | ConnectCore 6 SoM (ARMv7) | NEON | Page 8 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 C-language application program interface (API). Table 3 - Logical interfaces | Logical interface type | Description | |--------------------------|-----------------------------------------------------------| | Control input | API entry point and corresponding stack parameters | | Data input | API entry point data input stack parameters | | Status output | API entry point return values and status stack parameters | | Data output | API entry point data output stack parameters | As a software module, control of the physical ports is outside module scope. However, when the module is performing self-tests, or is in an error state, all output on the logical data output interface is inhibited. The module is single-threaded and in error scenarios returns only an error value (no data output is returned). Page 9 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 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-90] DRBG 1 Prediction resistance supported for all variations | Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function | 2053 | | Encryption, Decryption and CMAC | [SP 800-67] | 3-Key TDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify | 2686 | | | [FIPS 197] AES | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 5323 | | Message | [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM [SP 800-38E] XTS | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 5323 | | Digests | [FIPS 180-3] | SHA-1, SHA-2 (224, 256, 384, 512) | 4275 | | Keyed Hash | [FIPS 198] HMAC | SHA-1, SHA-2 (224, 256, 384, 512) | 3521 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] RSA | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS, SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072/4096 with all SHA-2 sizes) | 2851 | | | [FIPS 186-4] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA-2 sizes) | 1375 | | | [FIPS 186-2] ECDSA | PKG: CURVES( P-224 P-384 P-521 K-233 K- 283 K-409 K-571 B-233 B-283 B-409 B-571 ) PKV: 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 ) | 1397 | | | | PKG: CURVES( P-224 P-384 P-521 ) PKV: CURVES( P-192 P-224 P-256 P-384 P-521 ) | 1397 | Page 10 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4a - FIPS Approved Cryptographic Functions | | [FIPS 186-4] ECDSA | PKG: CURVES( P-224 P-256 P-384 P-521 K- 224 K-256 K-384 K-521 B-224 B-256 B-384 B- 521 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) ) 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) ) | | |---------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| | | [FIPS 186-4] ECDSA | PKG: CURVES( P-224 P-256 P-384 P-521 ) PKV: CURVES( ALL-P ) 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) ) 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) ) | | | ECC CDH (KAS) | [SP 800-56A] (§5.7.1.2) | All NIST defined B, K and P curves except sizes 163 and 192 | 1788 | The Module supports only NIST defined curves for use with ECDSA and ECC CDH. Page 11 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy | Category | Algorithm | Description | |----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC DH | Non-compliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. | | Key Encryption, Decryption | RSA | The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. | Table 4b - Non-FIPS Approved But Allowed Cryptographic Functions The Module implements the following services which are Non-Approved per the SP 800-131A transition: | Function | Algorithm | Options | Cert # | |----------------------------------------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| | Random Number Generation; Symmetric key generation | [ANS X9.31] RNG | AES 128/192/256 | | | Random Number Generation; Symmetric key generation | [SP 800-90] 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, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/4096 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [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 ) | | | Digital Signature and Asymmetric Key Generation | [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) ) | | Page 12 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4c - FIPS Non-Approved Cryptographic Functions | ECC CDH (CVL) | [SP 800-56A] (§5.7.1.2) | All NIST Recommended B, K and P curves sizes 163 and 192 | |-----------------|---------------------------|------------------------------------------------------------| 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() 2 , 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 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 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) 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 (3-Key) encrypt / decrypt key | Page 13 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4.1a - Critical Security Parameters | 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 | 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. | ###### 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-90 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. Table 4.1b - Public Keys Page 14 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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-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. Page 15 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 5 Roles, Authentication and Services The Module implements the required User and Crypto Officer roles and requires authentication for those roles. Only one role may be active at a time and the Module does not allow concurrent operators. The User or Crypto Officer role is assumed by passing the appropriate password to the FIPS_module_mode_set() function. The password values may be specified at build time and must have a minimum length of 16 characters. Any attempt to authenticate with an invalid password will result in an immediate and permanent failure condition rendering the Module unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the Module during the Module build process, performed by the Crypto Officer, and otherwise cannot be accessed. Since minimum password length is 16 characters, the probability of a random successful authentication attempt in one try is a maximum of 1/256 16 , or less than 1/10 38 . The Module permanently disables further authentication attempts after a single failure, so this probability is independent of time. Both roles have access to all of the services provided by the Module. - User Role (User): Loading the Module and calling any of the API functions. - Crypto Officer Role (CO): Installation of the Module on the host computer system and calling of any API functions. All services implemented by the Module are listed below, along with a description of service CSP access. | Service | Role | Description | |-------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Initialize | User, CO | Module initialization. Does not access CSPs. | | Self-test | User, CO | Perform self tests (FIPS_selftest). Does not access CSPs. | | Show status | User, CO | Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. | | Zeroize | User, CO | Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. | | Random | User, CO | Used for random number and symmetric key generation. | Page 16 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 5 - Services and CSP Access | Service | Role | Description | |---------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | number generation | | Seed or reseed a DRBG instance Determine security strength of a DRBG instance Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. | | Asymmetric key generation | User, CO | Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP800-90 | | 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 transport 3 | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | | Key agreement | User, CO | Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). | | Digital signature | User, CO | Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). | | Utility | User, CO | Miscellaneous helper functions. Does not access CSPs. | 3 "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 Digi ConnectCore Security Module . Page 17 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 6 Self-test The Module performs the self-tests listed below on invocation of Initialize or Self-test. Table 6a - Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency 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 | | 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 | | DRBG | KAT | CTR_DRBG: AES, 256 bit with and without derivation function 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.1). | | ECC CDH | KAT | Shared secret calculation per SP 800-56A §5.7.1.2, IG 9.6 | The Module is installed using 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() 4 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() 4 succeeds. 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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 Module also implements the following conditional tests: Table 6b - Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Tested as required by [SP800-90] 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 | 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 Module can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. Page 19 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 140-2 requirement for a single user mode of operation. Page 20 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. Page 21 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix A Installation and Usage Guidance 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 digi-fips-1.0.tar.gz . The command sets are: ``` ./config make make install ``` ####### Installation instructions 1. Download and copy the distribution file to the build system. 2. Verify the HMAC-SHA-1 digest of the distribution file; see Appendix B. An independently acquired FIPS 140-2 validated implemention 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 4. Execute the installation command sets as shown above. No other command sets shall be used. 5. The resulting fi pscanister.o file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 5 function. ``` gunzip -c digi-fips-1.0.tar.gz | tar xf - ``` 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 Module are outside of the cryptographic boundary. When linking the application with the Module two steps are necessary: 1. The HMAC-SHA-1 digest of the Module file must be calculated and verified against the installed digest to ensure the integrity of the Module. 5 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 22 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 2. A HMAC-SHA1 digest of the Module must be generated and embedded in the Module for use by the FIPS_mode_set() 5 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the 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() 5 function compares the embedded HMAC-SHA-1 digest with a digest generated from the Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. Page 23 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix B Controlled Distribution File Fingerprint The Digi ConnectCore Security Module v1.0 consists of the Module (the fi pscanister.o contiguous unit of binary object code) generated from the specific source files. The source files are in the specific special distribution file digi-fips-1.0.tar.gz with HMACSHA-1 digest of e8dbfa6cb9e22a049ec625ffb7ccaf33e6116598 The distribution is obtained by directly contacting Digi International, Inc. 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 distribution file (and patch file if used) shall be verified using the above HMAC-SHA-1 digest. Page 24 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix C Compilers This appendix lists the specific compilers used to generate the Module for the respective Operational Environments. Note this list does not imply that use of the Module is restricted to only the listed compiler versions, only that the use of other versions has not been confirmed to produce a correct result. Table C - Compilers | # | Operational Environment | Compiler | |-----|---------------------------|------------| | 1 | Yocto Linux 2.4 | gcc 7.3.0 | | 2 | Yocto Linux 2.4 | gcc 7.3.0 | Page 25 of 25': 1}, '__update__': {'AES 128/192/256': 2}, '__delete__': ['HMAC SHA-1', 'platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON']}}}} data.
24.09.2026

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'HMAC SHA-1': 1, 'platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON': 1}, '__update__': {'AES 128/192/256': 3}, '__delete__': ['platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON Page 3 of 25 ####### Digi ConnectCore Security Module - FIPS 140-2 Security Policy ####### References | Reference | Full Specification Name | |----------------|---------------------------------------------------------------------------------------------------------| | [ANS X9.31] | Digital Signatures Using Reversible Public Key Cryptography for the Financial 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) | | [SP 800-38B] | Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication | | [SP 800-38C] | Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality | | [SP 800-38D] | Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC | | [SP 800-56A] | Recommendation for Pair-Wise Key Establishment Schemes Using Discrete 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 | | [SP 800-90] | Recommendation for Random Number Generation Using Deterministic Random Bit Generators | | [SP 800- 131A] | Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths | Page 4 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ##### Table of Contents | 1 Introduction.........................................................................................................................6 | |----------------------------------------------------------------------------------------------------------------------------------------------| | 2 Tested Configurations.........................................................................................................8 | | 2.1 Tested Environments...................................................................................................8 | | 2.2 Vendor Affirmed Environments..................................................................................8 | | 3 Ports and Interfaces.............................................................................................................9 | | 4 Modes of Operation and Cryptographic Functionality.......................................................10 | | 4.1 Critical Security Parameters and Public Keys.............................................................13 | | 5 Roles, Authentication and Services....................................................................................16 | | 6 Self-test...............................................................................................................................18 | | 7 Operational Environment....................................................................................................20 | | 8 Mitigation of other Attacks.................................................................................................21 | | Appendix A Installation and Usage Guidance.......................................................................22 | | Appendix B Controlled Distribution File Fingerprint...........................................................24 | | Appendix C Compilers..........................................................................................................25 | Page 5 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 1 Introduction This document is the non-proprietary security policy for the Digi ConnectCore Security Module , hereafter referred to as the Module. The Module is based on the OpenSSL FIPS Object Module v2.0 . 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 fi pscanister.o . The Module performs no communications other than with the calling application (the process that invokes the Module services). Note that the Digi ConnectCore Security Module v1.0 is fully backwards compatible with all earlier revisions of the Digi ConnectCore Security Module . The v1.0 Module incorporates support for new platforms without disturbing functionality for any previously tested platforms. The v1.0 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 Page 6 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ####### The Module\'s software version for this validation is 1.0. Figure 1 - Module Block Diagram Page 7 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ### 2 Tested Configurations ### 2.1 Tested Environments Table 2.1 - Tested Configurations | # | Operational Environment | Processor | Optimiz-ations (Target) | |-----|---------------------------|-------------------------------|---------------------------| | 1 | Yocto Linux 2.4 | ConnectCore 6/6UL SoM (ARMv7) | None | | 2 | Yocto Linux 2.4 | ConnectCore 6/6UL SoM (ARMv7) | NEON | See Appendix A for additional information on build method. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. ### 2.2 Vendor Affirmed Environments The following platforms have not been tested as part of this FIPS 140-2 level 1 validation. However Digi International \'vendor affirms\' that these platforms are equivalent to the tested and validated platforms and the Module will function the same way and provide the same security services on any of the systems listed below. Table 2.2 - Vendor Affirmed Configurations | # | Operational Environment | Processor | Optimiz-ations (Target) | |-----|---------------------------|---------------------------|---------------------------| | 1 | Yocto Linux 2.4 | ConnectCore 6 SoM (ARMv7) | None | | 2 | Yocto Linux 2.4 | ConnectCore 6 SoM (ARMv7) | NEON | Page 8 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 C-language application program interface (API). Table 3 - Logical interfaces | Logical interface type | Description | |--------------------------|-----------------------------------------------------------| | Control input | API entry point and corresponding stack parameters | | Data input | API entry point data input stack parameters | | Status output | API entry point return values and status stack parameters | | Data output | API entry point data output stack parameters | As a software module, control of the physical ports is outside module scope. However, when the module is performing self-tests, or is in an error state, all output on the logical data output interface is inhibited. The module is single-threaded and in error scenarios returns only an error value (no data output is returned). Page 9 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 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-90] DRBG 1 Prediction resistance supported for all variations | Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function | 2053 | | Encryption, Decryption and CMAC | [SP 800-67] | 3-Key TDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify | 2686 | | | [FIPS 197] AES | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 5323 | | Message | [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM [SP 800-38E] XTS | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 5323 | | Digests | [FIPS 180-3] | SHA-1, SHA-2 (224, 256, 384, 512) | 4275 | | Keyed Hash | [FIPS 198] HMAC | SHA-1, SHA-2 (224, 256, 384, 512) | 3521 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] RSA | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS, SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072/4096 with all SHA-2 sizes) | 2851 | | | [FIPS 186-4] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA-2 sizes) | 1375 | | | [FIPS 186-2] ECDSA | PKG: CURVES( P-224 P-384 P-521 K-233 K- 283 K-409 K-571 B-233 B-283 B-409 B-571 ) PKV: 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 ) | 1397 | | | | PKG: CURVES( P-224 P-384 P-521 ) PKV: CURVES( P-192 P-224 P-256 P-384 P-521 ) | 1397 | Page 10 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4a - FIPS Approved Cryptographic Functions | | [FIPS 186-4] ECDSA | PKG: CURVES( P-224 P-256 P-384 P-521 K- 224 K-256 K-384 K-521 B-224 B-256 B-384 B- 521 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) ) 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) ) | | |---------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| | | [FIPS 186-4] ECDSA | PKG: CURVES( P-224 P-256 P-384 P-521 ) PKV: CURVES( ALL-P ) 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) ) 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) ) | | | ECC CDH (KAS) | [SP 800-56A] (§5.7.1.2) | All NIST defined B, K and P curves except sizes 163 and 192 | 1788 | The Module supports only NIST defined curves for use with ECDSA and ECC CDH. Page 11 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy | Category | Algorithm | Description | |----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC DH | Non-compliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. | | Key Encryption, Decryption | RSA | The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. | Table 4b - Non-FIPS Approved But Allowed Cryptographic Functions The Module implements the following services which are Non-Approved per the SP 800-131A transition: | Function | Algorithm | Options | Cert # | |----------------------------------------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| | Random Number Generation; Symmetric key generation | [ANS X9.31] RNG | AES 128/192/256 | | | Random Number Generation; Symmetric key generation | [SP 800-90] 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, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/4096 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [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 ) | | | Digital Signature and Asymmetric Key Generation | [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) ) | | Page 12 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4c - FIPS Non-Approved Cryptographic Functions | ECC CDH (CVL) | [SP 800-56A] (§5.7.1.2) | All NIST Recommended B, K and P curves sizes 163 and 192 | |-----------------|---------------------------|------------------------------------------------------------| 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() 2 , 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 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 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) 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 (3-Key) encrypt / decrypt key | Page 13 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4.1a - Critical Security Parameters | 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 | 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. | ###### 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-90 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. Table 4.1b - Public Keys Page 14 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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-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. Page 15 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 5 Roles, Authentication and Services The Module implements the required User and Crypto Officer roles and requires authentication for those roles. Only one role may be active at a time and the Module does not allow concurrent operators. The User or Crypto Officer role is assumed by passing the appropriate password to the FIPS_module_mode_set() function. The password values may be specified at build time and must have a minimum length of 16 characters. Any attempt to authenticate with an invalid password will result in an immediate and permanent failure condition rendering the Module unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the Module during the Module build process, performed by the Crypto Officer, and otherwise cannot be accessed. Since minimum password length is 16 characters, the probability of a random successful authentication attempt in one try is a maximum of 1/256 16 , or less than 1/10 38 . The Module permanently disables further authentication attempts after a single failure, so this probability is independent of time. Both roles have access to all of the services provided by the Module. - User Role (User): Loading the Module and calling any of the API functions. - Crypto Officer Role (CO): Installation of the Module on the host computer system and calling of any API functions. All services implemented by the Module are listed below, along with a description of service CSP access. | Service | Role | Description | |-------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Initialize | User, CO | Module initialization. Does not access CSPs. | | Self-test | User, CO | Perform self tests (FIPS_selftest). Does not access CSPs. | | Show status | User, CO | Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. | | Zeroize | User, CO | Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. | | Random | User, CO | Used for random number and symmetric key generation. | Page 16 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 5 - Services and CSP Access | Service | Role | Description | |---------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | number generation | | Seed or reseed a DRBG instance Determine security strength of a DRBG instance Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. | | Asymmetric key generation | User, CO | Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP800-90 | | 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 transport 3 | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | | Key agreement | User, CO | Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). | | Digital signature | User, CO | Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). | | Utility | User, CO | Miscellaneous helper functions. Does not access CSPs. | 3 "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 Digi ConnectCore Security Module . Page 17 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 6 Self-test The Module performs the self-tests listed below on invocation of Initialize or Self-test. Table 6a - Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency 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 | | 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 | | DRBG | KAT | CTR_DRBG: AES, 256 bit with and without derivation function 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.1). | | ECC CDH | KAT | Shared secret calculation per SP 800-56A §5.7.1.2, IG 9.6 | The Module is installed using 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() 4 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() 4 succeeds. 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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 Module also implements the following conditional tests: Table 6b - Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Tested as required by [SP800-90] 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 | 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 Module can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. Page 19 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 140-2 requirement for a single user mode of operation. Page 20 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. Page 21 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix A Installation and Usage Guidance 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 digi-fips-1.0.tar.gz . The command sets are: ``` ./config make make install ``` ####### Installation instructions 1. Download and copy the distribution file to the build system. 2. Verify the HMAC-SHA-1 digest of the distribution file; see Appendix B. An independently acquired FIPS 140-2 validated implemention 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 4. Execute the installation command sets as shown above. No other command sets shall be used. 5. The resulting fi pscanister.o file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 5 function. ``` gunzip -c digi-fips-1.0.tar.gz | tar xf - ``` 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 Module are outside of the cryptographic boundary. When linking the application with the Module two steps are necessary: 1. The HMAC-SHA-1 digest of the Module file must be calculated and verified against the installed digest to ensure the integrity of the Module. 5 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 22 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 2. A HMAC-SHA1 digest of the Module must be generated and embedded in the Module for use by the FIPS_mode_set() 5 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the 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() 5 function compares the embedded HMAC-SHA-1 digest with a digest generated from the Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. Page 23 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix B Controlled Distribution File Fingerprint The Digi ConnectCore Security Module v1.0 consists of the Module (the fi pscanister.o contiguous unit of binary object code) generated from the specific source files. The source files are in the specific special distribution file digi-fips-1.0.tar.gz with HMACSHA-1 digest of e8dbfa6cb9e22a049ec625ffb7ccaf33e6116598 The distribution is obtained by directly contacting Digi International, Inc. 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 distribution file (and patch file if used) shall be verified using the above HMAC-SHA-1 digest. Page 24 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix C Compilers This appendix lists the specific compilers used to generate the Module for the respective Operational Environments. Note this list does not imply that use of the Module is restricted to only the listed compiler versions, only that the use of other versions has not been confirmed to produce a correct result. Table C - Compilers | # | Operational Environment | Compiler | |-----|---------------------------|------------| | 1 | Yocto Linux 2.4 | gcc 7.3.0 | | 2 | Yocto Linux 2.4 | gcc 7.3.0 | Page 25 of 25']}}}} data.

The br1_deviations property was set to 43.
23.09.2026

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The following values were inserted: {'is_br1_format': False, 'br1_deviations': 0, 'br1_tables': None}.

The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON Page 3 of 25 ####### Digi ConnectCore Security Module - FIPS 140-2 Security Policy ####### References | Reference | Full Specification Name | |----------------|---------------------------------------------------------------------------------------------------------| | [ANS X9.31] | Digital Signatures Using Reversible Public Key Cryptography for the Financial 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) | | [SP 800-38B] | Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication | | [SP 800-38C] | Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality | | [SP 800-38D] | Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC | | [SP 800-56A] | Recommendation for Pair-Wise Key Establishment Schemes Using Discrete 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 | | [SP 800-90] | Recommendation for Random Number Generation Using Deterministic Random Bit Generators | | [SP 800- 131A] | Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths | Page 4 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ##### Table of Contents | 1 Introduction.........................................................................................................................6 | |----------------------------------------------------------------------------------------------------------------------------------------------| | 2 Tested Configurations.........................................................................................................8 | | 2.1 Tested Environments...................................................................................................8 | | 2.2 Vendor Affirmed Environments..................................................................................8 | | 3 Ports and Interfaces.............................................................................................................9 | | 4 Modes of Operation and Cryptographic Functionality.......................................................10 | | 4.1 Critical Security Parameters and Public Keys.............................................................13 | | 5 Roles, Authentication and Services....................................................................................16 | | 6 Self-test...............................................................................................................................18 | | 7 Operational Environment....................................................................................................20 | | 8 Mitigation of other Attacks.................................................................................................21 | | Appendix A Installation and Usage Guidance.......................................................................22 | | Appendix B Controlled Distribution File Fingerprint...........................................................24 | | Appendix C Compilers..........................................................................................................25 | Page 5 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 1 Introduction This document is the non-proprietary security policy for the Digi ConnectCore Security Module , hereafter referred to as the Module. The Module is based on the OpenSSL FIPS Object Module v2.0 . 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 fi pscanister.o . The Module performs no communications other than with the calling application (the process that invokes the Module services). Note that the Digi ConnectCore Security Module v1.0 is fully backwards compatible with all earlier revisions of the Digi ConnectCore Security Module . The v1.0 Module incorporates support for new platforms without disturbing functionality for any previously tested platforms. The v1.0 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 Page 6 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ####### The Module\'s software version for this validation is 1.0. Figure 1 - Module Block Diagram Page 7 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ### 2 Tested Configurations ### 2.1 Tested Environments Table 2.1 - Tested Configurations | # | Operational Environment | Processor | Optimiz-ations (Target) | |-----|---------------------------|-------------------------------|---------------------------| | 1 | Yocto Linux 2.4 | ConnectCore 6/6UL SoM (ARMv7) | None | | 2 | Yocto Linux 2.4 | ConnectCore 6/6UL SoM (ARMv7) | NEON | See Appendix A for additional information on build method. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. ### 2.2 Vendor Affirmed Environments The following platforms have not been tested as part of this FIPS 140-2 level 1 validation. However Digi International \'vendor affirms\' that these platforms are equivalent to the tested and validated platforms and the Module will function the same way and provide the same security services on any of the systems listed below. Table 2.2 - Vendor Affirmed Configurations | # | Operational Environment | Processor | Optimiz-ations (Target) | |-----|---------------------------|---------------------------|---------------------------| | 1 | Yocto Linux 2.4 | ConnectCore 6 SoM (ARMv7) | None | | 2 | Yocto Linux 2.4 | ConnectCore 6 SoM (ARMv7) | NEON | Page 8 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 C-language application program interface (API). Table 3 - Logical interfaces | Logical interface type | Description | |--------------------------|-----------------------------------------------------------| | Control input | API entry point and corresponding stack parameters | | Data input | API entry point data input stack parameters | | Status output | API entry point return values and status stack parameters | | Data output | API entry point data output stack parameters | As a software module, control of the physical ports is outside module scope. However, when the module is performing self-tests, or is in an error state, all output on the logical data output interface is inhibited. The module is single-threaded and in error scenarios returns only an error value (no data output is returned). Page 9 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 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-90] DRBG 1 Prediction resistance supported for all variations | Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function | 2053 | | Encryption, Decryption and CMAC | [SP 800-67] | 3-Key TDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify | 2686 | | | [FIPS 197] AES | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 5323 | | Message | [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM [SP 800-38E] XTS | 128/192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify | 5323 | | Digests | [FIPS 180-3] | SHA-1, SHA-2 (224, 256, 384, 512) | 4275 | | Keyed Hash | [FIPS 198] HMAC | SHA-1, SHA-2 (224, 256, 384, 512) | 3521 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] RSA | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS, SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072/4096 with all SHA-2 sizes) | 2851 | | | [FIPS 186-4] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA-2 sizes) | 1375 | | | [FIPS 186-2] ECDSA | PKG: CURVES( P-224 P-384 P-521 K-233 K- 283 K-409 K-571 B-233 B-283 B-409 B-571 ) PKV: 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 ) | 1397 | | | | PKG: CURVES( P-224 P-384 P-521 ) PKV: CURVES( P-192 P-224 P-256 P-384 P-521 ) | 1397 | Page 10 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4a - FIPS Approved Cryptographic Functions | | [FIPS 186-4] ECDSA | PKG: CURVES( P-224 P-256 P-384 P-521 K- 224 K-256 K-384 K-521 B-224 B-256 B-384 B- 521 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) ) 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) ) | | |---------------|-------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------| | | [FIPS 186-4] ECDSA | PKG: CURVES( P-224 P-256 P-384 P-521 ) PKV: CURVES( ALL-P ) 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) ) 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) ) | | | ECC CDH (KAS) | [SP 800-56A] (§5.7.1.2) | All NIST defined B, K and P curves except sizes 163 and 192 | 1788 | The Module supports only NIST defined curves for use with ECDSA and ECC CDH. Page 11 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy | Category | Algorithm | Description | |----------------------------|-------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC DH | Non-compliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. | | Key Encryption, Decryption | RSA | The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. | Table 4b - Non-FIPS Approved But Allowed Cryptographic Functions The Module implements the following services which are Non-Approved per the SP 800-131A transition: | Function | Algorithm | Options | Cert # | |----------------------------------------------------|--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| | Random Number Generation; Symmetric key generation | [ANS X9.31] RNG | AES 128/192/256 | | | Random Number Generation; Symmetric key generation | [SP 800-90] 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, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/4096 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] DSA | PQG Gen, Key Pair Gen, Sig Gen (1024 with all SHA sizes, 2048/3072 with SHA-1) | | | Digital Signature and Asymmetric Key Generation | [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 ) | | | Digital Signature and Asymmetric Key Generation | [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) ) | | Page 12 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4c - FIPS Non-Approved Cryptographic Functions | ECC CDH (CVL) | [SP 800-56A] (§5.7.1.2) | All NIST Recommended B, K and P curves sizes 163 and 192 | |-----------------|---------------------------|------------------------------------------------------------| 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() 2 , 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 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 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) 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 (3-Key) encrypt / decrypt key | Page 13 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 4.1a - Critical Security Parameters | 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 | 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. | ###### 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-90 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. Table 4.1b - Public Keys Page 14 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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-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. Page 15 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 5 Roles, Authentication and Services The Module implements the required User and Crypto Officer roles and requires authentication for those roles. Only one role may be active at a time and the Module does not allow concurrent operators. The User or Crypto Officer role is assumed by passing the appropriate password to the FIPS_module_mode_set() function. The password values may be specified at build time and must have a minimum length of 16 characters. Any attempt to authenticate with an invalid password will result in an immediate and permanent failure condition rendering the Module unable to enter the FIPS mode of operation, even with subsequent use of a correct password. Authentication data is loaded into the Module during the Module build process, performed by the Crypto Officer, and otherwise cannot be accessed. Since minimum password length is 16 characters, the probability of a random successful authentication attempt in one try is a maximum of 1/256 16 , or less than 1/10 38 . The Module permanently disables further authentication attempts after a single failure, so this probability is independent of time. Both roles have access to all of the services provided by the Module. - User Role (User): Loading the Module and calling any of the API functions. - Crypto Officer Role (CO): Installation of the Module on the host computer system and calling of any API functions. All services implemented by the Module are listed below, along with a description of service CSP access. | Service | Role | Description | |-------------|----------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Initialize | User, CO | Module initialization. Does not access CSPs. | | Self-test | User, CO | Perform self tests (FIPS_selftest). Does not access CSPs. | | Show status | User, CO | Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. | | Zeroize | User, CO | Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. | | Random | User, CO | Used for random number and symmetric key generation. | Page 16 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table 5 - Services and CSP Access | Service | Role | Description | |---------------------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | number generation | | Seed or reseed a DRBG instance Determine security strength of a DRBG instance Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. | | Asymmetric key generation | User, CO | Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP800-90 | | 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 transport 3 | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | | Key agreement | User, CO | Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). | | Digital signature | User, CO | Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). | | Utility | User, CO | Miscellaneous helper functions. Does not access CSPs. | 3 "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 Digi ConnectCore Security Module . Page 17 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 6 Self-test The Module performs the self-tests listed below on invocation of Initialize or Self-test. Table 6a - Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency 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 | | 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 | | DRBG | KAT | CTR_DRBG: AES, 256 bit with and without derivation function 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.1). | | ECC CDH | KAT | Shared secret calculation per SP 800-56A §5.7.1.2, IG 9.6 | The Module is installed using 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() 4 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() 4 succeeds. 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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 Module also implements the following conditional tests: Table 6b - Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Tested as required by [SP800-90] 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 | 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 Module can do itself. Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. Page 19 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 140-2 requirement for a single user mode of operation. Page 20 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. Page 21 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix A Installation and Usage Guidance 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 digi-fips-1.0.tar.gz . The command sets are: ``` ./config make make install ``` ####### Installation instructions 1. Download and copy the distribution file to the build system. 2. Verify the HMAC-SHA-1 digest of the distribution file; see Appendix B. An independently acquired FIPS 140-2 validated implemention 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 4. Execute the installation command sets as shown above. No other command sets shall be used. 5. The resulting fi pscanister.o file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 5 function. ``` gunzip -c digi-fips-1.0.tar.gz | tar xf - ``` 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 Module are outside of the cryptographic boundary. When linking the application with the Module two steps are necessary: 1. The HMAC-SHA-1 digest of the Module file must be calculated and verified against the installed digest to ensure the integrity of the Module. 5 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 22 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 2. A HMAC-SHA1 digest of the Module must be generated and embedded in the Module for use by the FIPS_mode_set() 5 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the 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() 5 function compares the embedded HMAC-SHA-1 digest with a digest generated from the Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. Page 23 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix B Controlled Distribution File Fingerprint The Digi ConnectCore Security Module v1.0 consists of the Module (the fi pscanister.o contiguous unit of binary object code) generated from the specific source files. The source files are in the specific special distribution file digi-fips-1.0.tar.gz with HMACSHA-1 digest of e8dbfa6cb9e22a049ec625ffb7ccaf33e6116598 The distribution is obtained by directly contacting Digi International, Inc. 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 distribution file (and patch file if used) shall be verified using the above HMAC-SHA-1 digest. Page 24 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy ## Appendix C Compilers This appendix lists the specific compilers used to generate the Module for the respective Operational Environments. Note this list does not imply that use of the Module is restricted to only the listed compiler versions, only that the use of other versions has not been confirmed to produce a correct result. Table C - Compilers | # | Operational Environment | Compiler | |-----|---------------------------|------------| | 1 | Yocto Linux 2.4 | gcc 7.3.0 | | 2 | Yocto Linux 2.4 | gcc 7.3.0 | Page 25 of 25': 1}, '__update__': {'AES 128/192/256': 2}, '__delete__': ['HMAC SHA-1', 'platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON']}}}} data.
21.09.2026

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The following values were inserted: {'module_algorithms': {'_type': 'Set', 'elements': ['RSA#2851', 'DRBG#2053', 'SHS#4275', 'AES#5323', 'Triple-DES#2686', 'HMAC#3521', 'DSA#1375', 'CVL#1788', 'ECDSA#1397']}, 'policy_algorithms': {'_type': 'Set', 'elements': ['#4275', '#1397', '#2686', '#5323', '#1375', '#2053', '#2851', '#3521']}}.

The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'HMACSHA-1': 1, 'DRBG 1': 1, 'platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON': 1}, '__update__': {'SHA-1': 19, 'AES 128/192/256': 3}, '__delete__': ['HMAC- SHA-1', 'AES 128/ 192/256', 'DRBG1', 'platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON Page 3 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy References Reference Full Specification Name [ANS X9.31] Digital Signatures Using Reversible Public Key Cryptography for the Financial 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) [SP 800-38B] Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication [SP 800-38C] Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality [SP 800-38D] Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC [SP 800-56A] Recommendation for Pair-Wise Key Establishment Schemes Using Discrete 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 [SP 800-90] Recommendation for Random Number Generation Using Deterministic Random Bit Generators [SP 800- 131A] Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths Page 4 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table of Contents 1 Introduction.........................................................................................................................6 2 Tested Configurations.........................................................................................................8 2.1 Tested Environments...................................................................................................8 2.2 Vendor Affirmed Environments..................................................................................8 3 Ports and Interfaces.............................................................................................................9 4 Modes of Operation and Cryptographic Functionality.......................................................10 4.1 Critical Security Parameters and Public Keys.............................................................13 5 Roles, Authentication and Services....................................................................................16 6 Self-test...............................................................................................................................18 7 Operational Environment....................................................................................................20 8 Mitigation of other Attacks.................................................................................................21 Appendix A Installation and Usage Guidance.......................................................................22 Appendix B Controlled Distribution File Fingerprint...........................................................24 Appendix C Compilers..........................................................................................................25 Page 5 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 1 Introduction This document is the non-proprietary security policy for the Digi ConnectCore Security Module, hereafter referred to as the Module. The Module is based on the OpenSSL FIPS Object Module v2.0. 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. The Module performs no communications other than with the calling application (the process that invokes the Module services). Note that the Digi ConnectCore Security Module v1.0 is fully backwards compatible with all earlier revisions of the Digi ConnectCore Security Module. The v1.0 Module incorporates support for new platforms without disturbing functionality for any previously tested platforms. The v1.0 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 Page 6 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy The Module’s software version for this validation is 1.0. Page 7 of 25 Figure 1 - Module Block Diagram Digi ConnectCore Security Module - FIPS 140-2 Security Policy 2 Tested Configurations 2.1 Tested Environments # Operational Environment Processor Optimiz-ations (Target) 1 Yocto Linux 2.4 ConnectCore 6/6UL SoM (ARMv7) None 2 Yocto Linux 2.4 ConnectCore 6/6UL SoM (ARMv7) NEON Table 2.1 - Tested Configurations See Appendix A for additional information on build method. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. 2.2 Vendor Affirmed Environments The following platforms have not been tested as part of this FIPS 140-2 level 1 validation. However Digi International “vendor affirms” that these platforms are equivalent to the tested and validated platforms and the Module will function the same way and provide the same security services on any of the systems listed below. # Operational Environment Processor Optimiz-ations (Target) 1 Yocto Linux 2.4 ConnectCore 6 SoM (ARMv7) None 2 Yocto Linux 2.4 ConnectCore 6 SoM (ARMv7) NEON Table 2.2 - Vendor Affirmed Configurations Page 8 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 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 module is performing self-tests, or is in an error state, all output on the logical data output interface is inhibited. The module is single-threaded and in error scenarios returns only an error value (no data output is returned). Page 9 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 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-90] DRBG1 Prediction resistance supported for all variations Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function 2053 Encryption, Decryption and CMAC [SP 800-67] 3-Key TDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify 2686 [FIPS 197] AES 128/ 192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify 5323 [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM [SP 800-38E] XTS Message Digests [FIPS 180-3] SHA-1, SHA-2 (224, 256, 384, 512) 4275 Keyed Hash [FIPS 198] HMAC SHA-1, SHA-2 (224, 256, 384, 512) 3521 Digital Signature and Asymmetric Key Generation [FIPS 186-2] RSA GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS, SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072/4096 with all SHA-2 sizes) 2851 [FIPS 186-4] DSA PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA-2 sizes) 1375 [FIPS 186-2] ECDSA PKG: CURVES( P-224 P-384 P-521 K-233 K- 283 K-409 K-571 B-233 B-283 B-409 B-571 ) PKV: 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 ) 1397 PKG: CURVES( P-224 P-384 P-521 ) PKV: CURVES( P-192 P-224 P-256 P-384 P-521 ) 1397 1 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP800-90] and [SP800-57]. Page 10 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy [FIPS 186-4] ECDSA PKG: CURVES( P-224 P-256 P-384 P-521 K- 224 K-256 K-384 K-521 B-224 B-256 B-384 B- 521 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) ) 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) ) PKG: CURVES( P-224 P-256 P-384 P-521 ) PKV: CURVES( ALL-P ) 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) ) 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) ) ECC CDH (KAS) [SP 800-56A] (§5.7.1.2) All NIST defined B, K and P curves except sizes 163 and 192 1788 Table 4a – FIPS Approved Cryptographic Functions The Module supports only NIST defined curves for use with ECDSA and ECC CDH. Page 11 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Category Algorithm Description Key Agreement EC DH Non-compliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. Key Encryption, Decryption RSA The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. Table 4b – Non-FIPS Approved But Allowed Cryptographic Functions The Module implements the following services which are Non-Approved per the SP 800-131A transition: Function Algorithm Options Cert # Random Number Generation; Symmetric key generation [ANS X9.31] RNG AES 128/192/256 Random Number Generation; Symmetric key generation [SP 800-90] 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, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/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) ) Page 12 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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()2 , 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 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 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) 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 (3-Key) encrypt / decrypt key 2 The function call in the Module is FIPS_module_mode_set() which is typically used by an application via the FIPS_mode_set() wrapper function. Page 13 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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-90 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. Page 14 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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 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 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-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. Page 15 of 25 Digi ConnectCore Security Module - FIPS 140-2 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. Self-test User, CO Perform self tests (FIPS_selftest). Does not access CSPs. Show status User, CO Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. Zeroize User, CO Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. Random User, CO Used for random number and symmetric key generation. Page 16 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Service Role Description number generation Seed or reseed a DRBG instance Determine security strength of a DRBG instance Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. Asymmetric key generation User, CO Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP800-90 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 transport3 User, CO Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). Key agreement User, CO Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). Digital signature User, CO Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). Utility User, CO Miscellaneous helper functions. Does not access CSPs. Table 5 - Services and CSP Access 3 "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 Digi ConnectCore Security Module. Page 17 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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 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 DRBG KAT CTR_DRBG: AES, 256 bit with and without derivation function 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.1). 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 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()4 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 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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()4 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 Module also implements the following conditional tests: Algorithm Test DRBG Tested as required by [SP800-90] 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 uninstantiate and re- instantiate the DRBG per the requirements of [SP 800-90]; 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. Page 19 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 140-2 requirement for a single user mode of operation. Page 20 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. Page 21 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Appendix A Installation and Usage Guidance 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 digi-fips-1.0.tar.gz. The command sets are: ./config make make install Installation instructions 1. Download and copy the distribution file to the build system. 2. Verify the HMAC-SHA-1 digest of the distribution file; see Appendix B. An independently acquired FIPS 140-2 validated implemention 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 digi-fips-1.0.tar.gz | tar xf - 4. Execute the installation command sets as shown above. No other command sets shall be used. 5. The resulting fipscanister.o file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 5 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 Module are outside of the cryptographic boundary. When linking the application with the Module two steps are necessary: 1. The HMAC-SHA-1 digest of the Module file must be calculated and verified against the installed digest to ensure the integrity of the Module. 5 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 22 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 2. A HMAC-SHA1 digest of the Module must be generated and embedded in the Module for use by the FIPS_mode_set()5 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the 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()5 function compares the embedded HMAC-SHA-1 digest with a digest generated from the Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. Page 23 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Appendix B Controlled Distribution File Fingerprint The Digi ConnectCore Security Module v1.0 consists of the Module (the fipscanister.o contiguous unit of binary object code) generated from the specific source files. The source files are in the specific special distribution file digi-fips-1.0.tar.gz with HMAC- SHA-1 digest of e8dbfa6cb9e22a049ec625ffb7ccaf33e6116598 The distribution is obtained by directly contacting Digi International, Inc. 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 distribution file (and patch file if used) shall be verified using the above HMAC-SHA-1 digest. Page 24 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 Yocto Linux 2.4 gcc 7.3.0 2 Yocto Linux 2.4 gcc 7.3.0 Table C - Compilers Page 25 of 25']}}}, 'symmetric_crypto': {'__update__': {'constructions': {'__update__': {'MAC': {'__update__': {'CMAC': 16}}}}}}, 'asymmetric_crypto': {'__update__': {'ECC': {'__update__': {'ECDSA': {'__update__': {'ECDSA': 18}}}}}}, 'hash_function': {'__update__': {'SHA': {'__update__': {'SHA1': {'__update__': {'SHA-1': 39}}}}}}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 20}}}}, 'cipher_mode': {'__update__': {'ECB': {'__update__': {'ECB': 4}}, 'CBC': {'__update__': {'CBC': 4}}, 'CTR': {'__update__': {'CTR': 3}}, 'CFB': {'__update__': {'CFB': 6}}, 'OFB': {'__update__': {'OFB': 2}}, 'GCM': {'__update__': {'GCM': 6}}, 'CCM': {'__update__': {'CCM': 5}}, 'XTS': {'__update__': {'XTS': 5}}}}, 'standard_id': {'__update__': {'FIPS': {'__update__': {'FIPS 186-4': 8}}}}} data.

The computed heuristics were updated.

The algorithms property was updated, with the {'_type': 'Set', 'elements': ['#4275', '#1397', '#2686', '#5323', '#1375', '#2053', '#2851', '#3521']} values added.

The state was updated.

The policy property was updated, with the {'txt_hash': '2ba3dd1238306d0ba71ef61d99371d6b4a1f2b7780ea225faa5b196167a922e4', 'json_hash': '6ad1769e2bd3faccce5bdcaf803c4904f59f5c06565fb05a8508b35341c5c780'} data.
15.12.2025

The certificate data changed.
Certificate changed

The state was updated.

The following values were inserted: {'policy_json_hash': None}.

The following properties were deleted: ['policy_convert_garbage'].
08.09.2025

The certificate data changed.
Certificate changed

The web extraction data was updated.

The validation_history property was updated.
09.02.2023

The certificate data changed.
Certificate changed

The cert_id was updated.

The new value is 3176.

The web extraction data was updated.

The following values were inserted: {'validation_history': [{'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2018-04-26', 'validation_type': 'Initial', 'lab': 'ACUMEN SECURITY, LLC'}, {'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2018-06-12', 'validation_type': 'Update', 'lab': 'ACUMEN SECURITY, LLC'}], 'vendor_url': 'http://www.digi.com', 'certificate_pdf_url': 'https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/certificates/AprilConsolidated2018.pdf', 'hw_versions': None, 'fw_versions': None}.

The standard property was set to FIPS 140-2.

The status property was set to historical.

The level property was set to 1.

The embodiment property was set to Multi-Chip Stand Alone.

The mentioned_certs property was updated, with the {'2398': 1} data.

The following properties were deleted: ['date_validation', 'algorithms', 'vendor_www', 'lab', 'lab_nvlap', 'security_policy_www', 'certificate_www', 'hw_version', 'fw_version', 'product_url'].

The PDF extraction data was updated.

The following values were inserted: {'policy_metadata': {'pdf_file_size_bytes': 236048, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 25, '/Author': 'CPUBuilders Customer', '/Creator': 'Writer', '/Producer': 'LibreOffice 5.1', '/CreationDate': "D:20180330153146-04'00'", 'pdf_hyperlinks': {'_type': 'Set', 'elements': ['http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-89/SP-800-89_November2006.pdf', 'http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf', 'http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-90/SP800-90revised_March2007.pdf', 'http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-56A/SP800-56A_Revision1_Mar08-2007.pdf', 'http://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1_final.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-38C/SP800-38C_updated-July20_2007.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-67/SP800-67.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf']}}}.

The following properties were deleted: ['cert_id', 'algorithms', 'clean_cert_ids', 'st_metadata'].

The computed heuristics were updated.

The following values were inserted: {'policy_prunned_references': {'_type': 'Set', 'elements': []}, 'module_prunned_references': {'_type': 'Set', 'elements': ['2398']}, 'policy_processed_references': {'_type': 'sec_certs.sample.certificate.References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': None, 'indirectly_referencing': None}, 'module_processed_references': {'_type': 'sec_certs.sample.certificate.References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': {'_type': 'Set', 'elements': ['2398']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['2398']}}, 'direct_transitive_cves': None, 'indirect_transitive_cves': None}.

The algorithms property was set to {'_type': 'Set', 'elements': ['RSA#2851', 'DRBG#2053', 'SHS#4275', 'AES#5323', 'Triple-DES#2686', 'HMAC#3521', 'DSA#1375', 'CVL#1788', 'ECDSA#1397']}.

The following properties were deleted: ['keywords', 'unmatched_algs', 'clean_cert_ids', 'st_references', 'web_references'].

The state was updated.

The following values were inserted: {'module_download_ok': True, 'policy_download_ok': True, 'policy_convert_garbage': False, 'policy_convert_ok': True, 'module_extract_ok': True, 'policy_extract_ok': True, 'policy_pdf_hash': '3c4d11b0edd0c7d2535b2afc732be3cd3d9090a023e5421c120ea365745722fc', 'policy_txt_hash': '46152aef1b1c4c7fb4c98873840615973cdc39bfcf6ccf6581e4f63df4a57633'}.

The following properties were deleted: ['sp_path', 'html_path', 'tables_done', 'file_status', 'txt_state'].
10.12.2022

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The keywords property was set to {'fips_cert_id': {'Cert': {'#1': 1, '#2': 1}}, 'fips_security_level': {'Level': {'level 1': 1}}, 'fips_certlike': {'Certlike': {'HMAC SHA-1': 1, 'HMAC-SHA-1': 16, 'HMAC-SHA1': 4, 'HMAC- SHA-1': 1, 'SHA-1': 20, 'SHA-2 (224': 2, 'SHA-2': 3, 'SHA-224': 15, 'SHA- 224': 1, 'SHA-1, 224': 20, 'SHA- 1, 224': 3, 'SHA1': 1, 'SHA224': 1, 'SHA256': 4, 'SHA384': 1, 'SHA512': 2, 'SHA-256': 1, 'SHA-384': 1, 'PKCS#1': 2, 'AES 128/ 192/256': 1, 'AES 128/192/256': 2, 'AES, 256': 1, 'DRBG1': 1, 'DSA (1024': 2, 'platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON Page 3 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy References Reference Full Specification Name [ANS X9.31] Digital Signatures Using Reversible Public Key Cryptography for the Financial 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) [SP 800-38B] Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication [SP 800-38C] Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality [SP 800-38D] Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC [SP 800-56A] Recommendation for Pair-Wise Key Establishment Schemes Using Discrete 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 [SP 800-90] Recommendation for Random Number Generation Using Deterministic Random Bit Generators [SP 800- 131A] Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths Page 4 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table of Contents 1 Introduction.........................................................................................................................6 2 Tested Configurations.........................................................................................................8 2.1 Tested Environments...................................................................................................8 2.2 Vendor Affirmed Environments..................................................................................8 3 Ports and Interfaces.............................................................................................................9 4 Modes of Operation and Cryptographic Functionality.......................................................10 4.1 Critical Security Parameters and Public Keys.............................................................13 5 Roles, Authentication and Services....................................................................................16 6 Self-test...............................................................................................................................18 7 Operational Environment....................................................................................................20 8 Mitigation of other Attacks.................................................................................................21 Appendix A Installation and Usage Guidance.......................................................................22 Appendix B Controlled Distribution File Fingerprint...........................................................24 Appendix C Compilers..........................................................................................................25 Page 5 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 1 Introduction This document is the non-proprietary security policy for the Digi ConnectCore Security Module, hereafter referred to as the Module. The Module is based on the OpenSSL FIPS Object Module v2.0. 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. The Module performs no communications other than with the calling application (the process that invokes the Module services). Note that the Digi ConnectCore Security Module v1.0 is fully backwards compatible with all earlier revisions of the Digi ConnectCore Security Module. The v1.0 Module incorporates support for new platforms without disturbing functionality for any previously tested platforms. The v1.0 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 Page 6 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy The Module’s software version for this validation is 1.0. Page 7 of 25 Figure 1 - Module Block Diagram Digi ConnectCore Security Module - FIPS 140-2 Security Policy 2 Tested Configurations 2.1 Tested Environments # Operational Environment Processor Optimiz-ations (Target) 1 Yocto Linux 2.4 ConnectCore 6/6UL SoM (ARMv7) None 2 Yocto Linux 2.4 ConnectCore 6/6UL SoM (ARMv7) NEON Table 2.1 - Tested Configurations See Appendix A for additional information on build method. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. 2.2 Vendor Affirmed Environments The following platforms have not been tested as part of this FIPS 140-2 level 1 validation. However Digi International “vendor affirms” that these platforms are equivalent to the tested and validated platforms and the Module will function the same way and provide the same security services on any of the systems listed below. # Operational Environment Processor Optimiz-ations (Target) 1 Yocto Linux 2.4 ConnectCore 6 SoM (ARMv7) None 2 Yocto Linux 2.4 ConnectCore 6 SoM (ARMv7) NEON Table 2.2 - Vendor Affirmed Configurations Page 8 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 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 module is performing self-tests, or is in an error state, all output on the logical data output interface is inhibited. The module is single-threaded and in error scenarios returns only an error value (no data output is returned). Page 9 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 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-90] DRBG1 Prediction resistance supported for all variations Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function 2053 Encryption, Decryption and CMAC [SP 800-67] 3-Key TDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify 2686 [FIPS 197] AES 128/ 192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify 5323 [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM [SP 800-38E] XTS Message Digests [FIPS 180-3] SHA-1, SHA-2 (224, 256, 384, 512) 4275 Keyed Hash [FIPS 198] HMAC SHA-1, SHA-2 (224, 256, 384, 512) 3521 Digital Signature and Asymmetric Key Generation [FIPS 186-2] RSA GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS, SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072/4096 with all SHA-2 sizes) 2851 [FIPS 186-4] DSA PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA-2 sizes) 1375 [FIPS 186-2] ECDSA PKG: CURVES( P-224 P-384 P-521 K-233 K- 283 K-409 K-571 B-233 B-283 B-409 B-571 ) PKV: 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 ) 1397 PKG: CURVES( P-224 P-384 P-521 ) PKV: CURVES( P-192 P-224 P-256 P-384 P-521 ) 1397 1 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP800-90] and [SP800-57]. Page 10 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy [FIPS 186-4] ECDSA PKG: CURVES( P-224 P-256 P-384 P-521 K- 224 K-256 K-384 K-521 B-224 B-256 B-384 B- 521 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) ) 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) ) PKG: CURVES( P-224 P-256 P-384 P-521 ) PKV: CURVES( ALL-P ) 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) ) 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) ) ECC CDH (KAS) [SP 800-56A] (§5.7.1.2) All NIST defined B, K and P curves except sizes 163 and 192 1788 Table 4a – FIPS Approved Cryptographic Functions The Module supports only NIST defined curves for use with ECDSA and ECC CDH. Page 11 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Category Algorithm Description Key Agreement EC DH Non-compliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. Key Encryption, Decryption RSA The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. Table 4b – Non-FIPS Approved But Allowed Cryptographic Functions The Module implements the following services which are Non-Approved per the SP 800-131A transition: Function Algorithm Options Cert # Random Number Generation; Symmetric key generation [ANS X9.31] RNG AES 128/192/256 Random Number Generation; Symmetric key generation [SP 800-90] 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, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/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) ) Page 12 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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()2 , 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 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 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) 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 (3-Key) encrypt / decrypt key 2 The function call in the Module is FIPS_module_mode_set() which is typically used by an application via the FIPS_mode_set() wrapper function. Page 13 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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-90 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. Page 14 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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 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 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-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. Page 15 of 25 Digi ConnectCore Security Module - FIPS 140-2 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. Self-test User, CO Perform self tests (FIPS_selftest). Does not access CSPs. Show status User, CO Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. Zeroize User, CO Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. Random User, CO Used for random number and symmetric key generation. Page 16 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Service Role Description number generation Seed or reseed a DRBG instance Determine security strength of a DRBG instance Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. Asymmetric key generation User, CO Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP800-90 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 transport3 User, CO Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). Key agreement User, CO Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). Digital signature User, CO Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). Utility User, CO Miscellaneous helper functions. Does not access CSPs. Table 5 - Services and CSP Access 3 "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 Digi ConnectCore Security Module. Page 17 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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 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 DRBG KAT CTR_DRBG: AES, 256 bit with and without derivation function 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.1). 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 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()4 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 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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()4 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 Module also implements the following conditional tests: Algorithm Test DRBG Tested as required by [SP800-90] 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 uninstantiate and re- instantiate the DRBG per the requirements of [SP 800-90]; 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. Page 19 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 140-2 requirement for a single user mode of operation. Page 20 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. Page 21 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Appendix A Installation and Usage Guidance 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 digi-fips-1.0.tar.gz. The command sets are: ./config make make install Installation instructions 1. Download and copy the distribution file to the build system. 2. Verify the HMAC-SHA-1 digest of the distribution file; see Appendix B. An independently acquired FIPS 140-2 validated implemention 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 digi-fips-1.0.tar.gz | tar xf - 4. Execute the installation command sets as shown above. No other command sets shall be used. 5. The resulting fipscanister.o file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 5 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 Module are outside of the cryptographic boundary. When linking the application with the Module two steps are necessary: 1. The HMAC-SHA-1 digest of the Module file must be calculated and verified against the installed digest to ensure the integrity of the Module. 5 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 22 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 2. A HMAC-SHA1 digest of the Module must be generated and embedded in the Module for use by the FIPS_mode_set()5 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the 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()5 function compares the embedded HMAC-SHA-1 digest with a digest generated from the Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. Page 23 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Appendix B Controlled Distribution File Fingerprint The Digi ConnectCore Security Module v1.0 consists of the Module (the fipscanister.o contiguous unit of binary object code) generated from the specific source files. The source files are in the specific special distribution file digi-fips-1.0.tar.gz with HMAC- SHA-1 digest of e8dbfa6cb9e22a049ec625ffb7ccaf33e6116598 The distribution is obtained by directly contacting Digi International, Inc. 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 distribution file (and patch file if used) shall be verified using the above HMAC-SHA-1 digest. Page 24 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 Yocto Linux 2.4 gcc 7.3.0 2 Yocto Linux 2.4 gcc 7.3.0 Table C - Compilers Page 25 of 25': 1}}, 'vendor': {}, 'eval_facility': {}, 'symmetric_crypto': {'AES_competition': {'AES': {'AES': 19}}, 'DES': {'3DES': {'TDEA': 1, 'TDES': 9}}, 'constructions': {'MAC': {'HMAC': 8, 'CMAC': 15}}}, 'asymmetric_crypto': {'ECC': {'ECDSA': {'ECDSA': 17}, 'ECC': {'ECC': 4}}, 'FF': {'DH': {'DH': 9}, 'DSA': {'DSA': 18}}}, 'pq_crypto': {}, 'hash_function': {'SHA': {'SHA1': {'SHA-1': 40, 'SHA1': 1}, 'SHA2': {'SHA-224': 15, 'SHA224': 1, 'SHA256': 4, 'SHA384': 1, 'SHA512': 2, 'SHA-256': 1, 'SHA-384': 1, 'SHA-2': 5}}}, 'crypto_scheme': {'KA': {'Key Agreement': 2, 'Key agreement': 2}}, 'crypto_protocol': {}, 'randomness': {'PRNG': {'DRBG': 19}, 'RNG': {'RNG': 3}}, 'cipher_mode': {'ECB': {'ECB': 3}, 'CBC': {'CBC': 3}, 'CTR': {'CTR': 2}, 'CFB': {'CFB': 3}, 'OFB': {'OFB': 1}, 'GCM': {'GCM': 5}, 'CCM': {'CCM': 4}, 'XTS': {'XTS': 4}}, 'ecc_curve': {'NIST': {'P-224': 10, 'P-521': 10, 'P-192': 10, 'P-256': 8, 'P-384': 4, 'K-409': 3, 'B-233': 1, 'B-409': 1, 'K-233': 4, 'B-163': 4, 'B-283': 2, 'B-571': 2, 'K-256': 1, 'K-521': 1, 'B-256': 1}}, 'crypto_engine': {}, 'tls_cipher_suite': {}, 'crypto_library': {'OpenSSL': {'OpenSSL': 1}}, 'vulnerability': {}, 'side_channel_analysis': {}, 'device_model': {}, 'tee_name': {}, 'os_name': {}, 'cplc_data': {}, 'ic_data_group': {}, 'standard_id': {'FIPS': {'FIPS 140-2': 35, 'FIPS 180-3': 2, 'FIPS 186-4': 7, 'FIPS 197': 2, 'FIPS 198-1': 1, 'FIPS 198': 1, 'FIPS 186-2': 7, 'FIPS 186-3': 1}, 'NIST': {'SP 800-38B': 2, 'SP 800-38C': 2, 'SP 800-38D': 2, 'SP 800-56A': 4, 'SP 800-89': 1, 'SP 800-90': 6, 'SP 800-67': 1, 'SP 800-38E': 1, 'SP 800-56B': 1, 'SP 800-131A': 1}, 'PKCS': {'PKCS#1': 1}}, 'javacard_version': {}, 'javacard_api_const': {}, 'javacard_packages': {}, 'certification_process': {}}.

The algorithms property was set to {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 11', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '283', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '140', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2053', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '131', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '571', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '440', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '57', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '89', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2686', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'c 7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '56', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 19', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1397', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '67', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '90', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4275', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4096', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'C1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 140', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 12', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '\n1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1536', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 25', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 5323', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3072', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1375', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2001', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 18', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1788', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 17', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '888', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 10', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '521', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 186', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 14', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '31', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 198', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1024', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '409', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '233', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1038', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 180', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2851', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 197', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '160', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '25616', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 8', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '38', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3521', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}]}.

The st_metadata property was set to {'pdf_file_size_bytes': 236048, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 25, '/Author': 'CPUBuilders Customer', '/Creator': 'Writer', '/Producer': 'LibreOffice 5.1', '/CreationDate': "D:20180330153146-04'00'", 'pdf_hyperlinks': {'_type': 'Set', 'elements': ['http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-89/SP-800-89_November2006.pdf', 'http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf', 'http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-90/SP800-90revised_March2007.pdf', 'http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-56A/SP800-56A_Revision1_Mar08-2007.pdf', 'http://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1_final.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-38C/SP800-38C_updated-July20_2007.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-67/SP800-67.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf']}}.

The computed heuristics were updated.

The algorithms property was set to {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 11', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '283', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '140', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2053', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '131', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '571', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '440', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '57', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '89', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2686', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'c 7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '56', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 19', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1397', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '67', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '90', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4275', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4096', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'C1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 140', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 12', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '\n1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1536', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 25', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 5323', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3072', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1375', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2001', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 18', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1788', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 17', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '888', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 10', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '521', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 186', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 14', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '31', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 198', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1024', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '409', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '233', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1038', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 180', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2851', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 197', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '160', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '25616', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 8', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '38', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3521', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}]}.

The state was updated.

The tables_done property was set to True.

The txt_state property was set to True.
09.12.2022

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The keywords property was set to None.

The algorithms property was set to {'_type': 'Set', 'elements': []}.

The st_metadata property was set to None.

The computed heuristics were updated.

The algorithms property was set to {'_type': 'Set', 'elements': []}.

The state was updated.

The tables_done property was set to False.

The txt_state property was set to False.
05.11.2022

The certificate data changed.
Certificate changed

The web extraction data was updated.

The algorithms property was set to {'_type': 'Set', 'elements': []}.

The computed heuristics were updated.

The algorithms property was updated, with the {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#4275', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#3521', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#5323', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1375', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2053', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2851', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1397', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2686', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1788', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}]} values discarded.
25.10.2022

The certificate data changed.
Certificate changed

The PDF extraction data was updated.

The keywords property was updated, with the {'fips_cert_id': {'__update__': {'Cert': {'__update__': {'#1': 1}}}}, 'fips_certlike': {'__update__': {'Certlike': {'__update__': {'SHA-1': 20, 'SHA1': 1, 'DSA (1024': 2}, '__delete__': ['PKCS1', 'AES (128', 'AES (256', 'AES KAT 128', 'AES-128', 'AES-256', 'DES (3']}}}, 'symmetric_crypto': {'__update__': {'AES_competition': {'__update__': {'AES': {'__update__': {'AES': 19}, '__delete__': ['AES-', 'AES-128', 'AES-256']}}}, 'DES': {'__delete__': ['DES']}, 'constructions': {'__update__': {'MAC': {'__update__': {'HMAC': 8}}}}}}, 'asymmetric_crypto': {'__update__': {'FF': {'__update__': {'DH': {'__update__': {'DH': 9}}, 'DSA': {'__update__': {'DSA': 18}}}}}}, 'hash_function': {'__update__': {'SHA': {'__update__': {'SHA1': {'__update__': {'SHA-1': 40, 'SHA1': 1}}, 'SHA2': {'__update__': {'SHA-2': 5}, '__delete__': ['SHA2']}}, '__delete__': ['SHA3']}}}, 'crypto_scheme': {'__update__': {'KA': {'__delete__': ['KA']}}, '__delete__': ['MAC']}, 'crypto_protocol': {}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 19}}, 'RNG': {'__delete__': ['RBG']}}}, 'cipher_mode': {'__update__': {'ECB': {'__update__': {'ECB': 3}}, 'CBC': {'__update__': {'CBC': 3}}, 'CTR': {'__update__': {'CTR': 2}}, 'CFB': {'__update__': {'CFB': 3}}, 'OFB': {'__update__': {'OFB': 1}}, 'GCM': {'__update__': {'GCM': 5}}, 'XTS': {'__update__': {'XTS': 4}}}}, 'ecc_curve': {'__update__': {'NIST': {'__update__': {'P-224': 10, 'P-384': 4, 'P-521': 10, 'P-192': 10, 'P-256': 8, 'K-233': 4, 'K-409': 3, 'B-233': 1, 'B-283': 2, 'B-409': 1, 'B-571': 2, 'B-163': 4}, '__delete__': ['K-571', 'K-163', 'K-283', 'K-384', 'B-224', 'B-384']}}}, 'standard_id': {'__update__': {'NIST': {'SP 800-38B': 2, 'SP 800-38C': 2, 'SP 800-38D': 2, 'SP 800-56A': 4, 'SP 800-89': 1, 'SP 800-90': 6, 'SP 800-67': 1, 'SP 800-38E': 1, 'SP 800-56B': 1, 'SP 800-131A': 1}, 'PKCS': {'__delete__': ['PKCS1']}}}} data.

The algorithms property was set to {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 11', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '283', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '140', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2053', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '131', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '571', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '440', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '57', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '89', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2686', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'c 7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '56', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 19', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1397', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '67', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '90', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4275', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'C1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4096', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 140', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 12', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '\n1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1536', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 25', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 5323', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3072', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1375', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2001', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 18', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1788', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 17', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '888', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 10', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '521', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 186', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 14', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '31', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 198', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1024', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '409', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '233', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1038', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 180', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2851', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 197', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '160', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '25616', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 8', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '38', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3521', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}]}.

The clean_cert_ids property was set to {}.

The computed heuristics were updated.

The algorithms property was updated, with the {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 11', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '283', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '140', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2053', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '131', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '571', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '440', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '57', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '89', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2686', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'c 7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '56', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 19', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1397', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '67', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '90', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4275', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4096', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'C1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '9', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 140', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '128', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 12', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '\n1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1536', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 25', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 5323', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3072', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1375', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '800', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2001', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 18', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1788', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 17', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '888', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 10', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '521', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 186', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 192', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 14', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 163', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '31', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 198', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1024', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 16', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '409', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '233', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '1038', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 180', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 1', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '6', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2851', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 197', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '160', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '25616', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 0', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 8', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '38', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 3521', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'A512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 2048', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}]} values added.

The web_references property was updated, with the {'directly_referencing': {'_type': 'Set', 'elements': ['2398']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['2398']}} data.

The state was updated.

The tables_done property was set to True.
08.10.2022

The certificate data changed.
Certificate changed

The computed heuristics were updated.

The cpe_matches property was set to None.

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

The certificate data changed.
Certificate changed

The web extraction data was updated.

This property was added with value {'_type': 'sec_certs.sample.fips.FIPSCertificate.WebData', 'module_name': 'Digi ConnectCore Security Module', 'standard': 'FIPS140-2', 'status': 'Historical', 'date_sunset': None, 'date_validation': ['2018-04-26', '2018-06-12'], 'level': '1', 'caveat': 'When built, installed, protected and initialized as assumed by the Crypto Officer role and as specified in the provided Security Policy. Appendix A of the provided Security Policy specifies the actual distribution tar file containing the source code of this module. There shall be no additions, deletions or alterations to the tar file contents as used during module build. The distribution tar file shall be verified as specified in Appendix A of the provided Security Policy. Installation and protection shall be completed as specified in Appendix A of the provided Security Policy. Initialization shall be invoked as per Section 4 of the provided Security Policy. Any deviation from specified verification, protection, installation and initialization procedures will result in a non FIPS 140-2 compliant module. This validation entry is a non-security relevant modification to Cert. #2398', 'exceptions': ['Roles, Services, and Authentication: Level 2', 'Physical Security: N/A', 'Design Assurance: Level 3', 'Mitigation of Other Attacks: N/A'], 'module_type': 'Software', 'embodiment': 'Multi Chip Standalone', 'algorithms': {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#4275', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#3521', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#5323', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1375', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2053', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2851', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1397', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2686', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1788', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}]}, 'tested_conf': ['Yocto Linux 2.4 running on ConnectCore 6/6UL SoM (ARMv7) without PAA (gcc Compiler Version 7.3.0), Yocto Linux 2.4 running on ConnectCore 6/6UL SoM (ARMv7) with PAA (gcc Compiler Version 7.3.0) (single-user mode)'], 'description': 'The Digi ConnectCore Security Module provides cryptographic services for Digi International Inc. products.', 'mentioned_certs': {'2398': {'count': 1}}, 'vendor': 'Digi International, Inc.', 'vendor_www': 'http://www.digi.com', 'lab': None, 'lab_nvlap': None, 'historical_reason': '186-2 transition', 'security_policy_www': 'https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp3176.pdf', 'certificate_www': 'https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/certificates/AprilConsolidated2018.pdf', 'hw_version': None, 'fw_version': None, 'revoked_reason': None, 'revoked_link': None, 'sw_versions': '1.0', 'product_url': None}.

The PDF extraction data was updated.

This property was added with value {'_type': 'sec_certs.sample.fips.FIPSCertificate.PdfData', 'cert_id': 3176, 'keywords': {'fips_cert_id': {'Cert': {'#1': 2, '#2': 1}}, 'fips_security_level': {'Level': {'level 1': 1}}, 'fips_certlike': {'Certlike': {'HMAC SHA-1': 1, 'HMAC-SHA-1': 16, 'HMAC-SHA1': 4, 'HMAC- SHA-1': 1, 'SHA-1': 28, 'SHA-2 (224': 2, 'SHA-2': 3, 'SHA-224': 15, 'SHA- 224': 1, 'SHA-1, 224': 20, 'SHA- 1, 224': 3, 'SHA1': 3, 'SHA224': 1, 'SHA256': 4, 'SHA384': 1, 'SHA512': 2, 'SHA-256': 1, 'SHA-384': 1, 'PKCS1': 6, 'PKCS#1': 2, 'AES 128/ 192/256': 1, 'AES 128/192/256': 2, 'AES (128': 3, 'AES (256': 1, 'AES KAT 128': 1, 'AES-128': 1, 'AES-256': 1, 'AES, 256': 1, 'DRBG1': 1, 'DES (3': 2, 'DSA (1024': 4, 'platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON Page 3 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy References Reference Full Specification Name [ANS X9.31] Digital Signatures Using Reversible Public Key Cryptography for the Financial 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) [SP 800-38B] Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication [SP 800-38C] Recommendation for Block Cipher Modes of Operation: The CCM Mode for Authentication and Confidentiality [SP 800-38D] Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC [SP 800-56A] Recommendation for Pair-Wise Key Establishment Schemes Using Discrete 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 [SP 800-90] Recommendation for Random Number Generation Using Deterministic Random Bit Generators [SP 800- 131A] Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths Page 4 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Table of Contents 1 Introduction.........................................................................................................................6 2 Tested Configurations.........................................................................................................8 2.1 Tested Environments...................................................................................................8 2.2 Vendor Affirmed Environments..................................................................................8 3 Ports and Interfaces.............................................................................................................9 4 Modes of Operation and Cryptographic Functionality.......................................................10 4.1 Critical Security Parameters and Public Keys.............................................................13 5 Roles, Authentication and Services....................................................................................16 6 Self-test...............................................................................................................................18 7 Operational Environment....................................................................................................20 8 Mitigation of other Attacks.................................................................................................21 Appendix A Installation and Usage Guidance.......................................................................22 Appendix B Controlled Distribution File Fingerprint...........................................................24 Appendix C Compilers..........................................................................................................25 Page 5 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 1 Introduction This document is the non-proprietary security policy for the Digi ConnectCore Security Module, hereafter referred to as the Module. The Module is based on the OpenSSL FIPS Object Module v2.0. 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. The Module performs no communications other than with the calling application (the process that invokes the Module services). Note that the Digi ConnectCore Security Module v1.0 is fully backwards compatible with all earlier revisions of the Digi ConnectCore Security Module. The v1.0 Module incorporates support for new platforms without disturbing functionality for any previously tested platforms. The v1.0 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 Page 6 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy The Module’s software version for this validation is 1.0. Page 7 of 25 Figure 1 - Module Block Diagram Digi ConnectCore Security Module - FIPS 140-2 Security Policy 2 Tested Configurations 2.1 Tested Environments # Operational Environment Processor Optimiz-ations (Target) 1 Yocto Linux 2.4 ConnectCore 6/6UL SoM (ARMv7) None 2 Yocto Linux 2.4 ConnectCore 6/6UL SoM (ARMv7) NEON Table 2.1 - Tested Configurations See Appendix A for additional information on build method. See Appendix C for a list of the specific compilers used to generate the Module for the respective operational environments. 2.2 Vendor Affirmed Environments The following platforms have not been tested as part of this FIPS 140-2 level 1 validation. However Digi International “vendor affirms” that these platforms are equivalent to the tested and validated platforms and the Module will function the same way and provide the same security services on any of the systems listed below. # Operational Environment Processor Optimiz-ations (Target) 1 Yocto Linux 2.4 ConnectCore 6 SoM (ARMv7) None 2 Yocto Linux 2.4 ConnectCore 6 SoM (ARMv7) NEON Table 2.2 - Vendor Affirmed Configurations Page 8 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 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 module is performing self-tests, or is in an error state, all output on the logical data output interface is inhibited. The module is single-threaded and in error scenarios returns only an error value (no data output is returned). Page 9 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 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-90] DRBG1 Prediction resistance supported for all variations Hash DRBG HMAC DRBG, no reseed CTR DRBG (AES), no derivation function 2053 Encryption, Decryption and CMAC [SP 800-67] 3-Key TDES TECB, TCBC, TCFB, TOFB; CMAC generate and verify 2686 [FIPS 197] AES 128/ 192/256 ECB, CBC, OFB, CFB 1, CFB 8, CFB 128, CTR, XTS; CCM; GCM; CMAC generate and verify 5323 [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM [SP 800-38E] XTS Message Digests [FIPS 180-3] SHA-1, SHA-2 (224, 256, 384, 512) 4275 Keyed Hash [FIPS 198] HMAC SHA-1, SHA-2 (224, 256, 384, 512) 3521 Digital Signature and Asymmetric Key Generation [FIPS 186-2] RSA GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS, SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072/4096 with all SHA-2 sizes) 2851 [FIPS 186-4] DSA PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (1024/2048/3072 with all SHA-2 sizes) 1375 [FIPS 186-2] ECDSA PKG: CURVES( P-224 P-384 P-521 K-233 K- 283 K-409 K-571 B-233 B-283 B-409 B-571 ) PKV: 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 ) 1397 PKG: CURVES( P-224 P-384 P-521 ) PKV: CURVES( P-192 P-224 P-256 P-384 P-521 ) 1397 1 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP800-90] and [SP800-57]. Page 10 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy [FIPS 186-4] ECDSA PKG: CURVES( P-224 P-256 P-384 P-521 K- 224 K-256 K-384 K-521 B-224 B-256 B-384 B- 521 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) ) 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) ) PKG: CURVES( P-224 P-256 P-384 P-521 ) PKV: CURVES( ALL-P ) 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) ) 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) ) ECC CDH (KAS) [SP 800-56A] (§5.7.1.2) All NIST defined B, K and P curves except sizes 163 and 192 1788 Table 4a – FIPS Approved Cryptographic Functions The Module supports only NIST defined curves for use with ECDSA and ECC CDH. Page 11 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Category Algorithm Description Key Agreement EC DH Non-compliant (untested) DH scheme using elliptic curve, supporting all NIST defined B, K and P curves. Key agreement is a service provided for calling process use, but is not used to establish keys into the Module. Key Encryption, Decryption RSA The RSA algorithm may be used by the calling application for encryption or decryption of keys. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. Table 4b – Non-FIPS Approved But Allowed Cryptographic Functions The Module implements the following services which are Non-Approved per the SP 800-131A transition: Function Algorithm Options Cert # Random Number Generation; Symmetric key generation [ANS X9.31] RNG AES 128/192/256 Random Number Generation; Symmetric key generation [SP 800-90] 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, SigGen9.31, SigGenPKCS1.5, SigGenPSS (1024/1536 with all SHA sizes, 2048/3072/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) ) Page 12 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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()2 , 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 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 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) 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 (3-Key) encrypt / decrypt key 2 The function call in the Module is FIPS_module_mode_set() which is typically used by an application via the FIPS_mode_set() wrapper function. Page 13 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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-90 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. Page 14 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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 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 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-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. Page 15 of 25 Digi ConnectCore Security Module - FIPS 140-2 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. Self-test User, CO Perform self tests (FIPS_selftest). Does not access CSPs. Show status User, CO Functions that provide module status information: Version (as unsigned long or const char *) FIPS Mode (Boolean) Does not access CSPs. Zeroize User, CO Functions that destroy CSPs: fips_drbg_uninstantiate: for a given DRBG context, overwrites DRBG CSPs (Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs) All other services automatically overwrite CSPs stored in allocated memory. Stack cleanup is the responsibility of the calling application. Random User, CO Used for random number and symmetric key generation. Page 16 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Service Role Description number generation Seed or reseed a DRBG instance Determine security strength of a DRBG instance Obtain random data Uses and updates Hash_DRBG CSPs, HMAC_DRBG CSPs, CTR_DRBG CSPs. Asymmetric key generation User, CO Used to generate DSA, ECDSA and RSA keys: RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK There is one supported entropy strength for each mechanism and algorithm type, the maximum specified in SP800-90 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 transport3 User, CO Used to encrypt or decrypt a key value on behalf of the calling process (does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). Key agreement User, CO Used to perform key agreement primitives on behalf of the calling process (does not establish keys into the module). Executes using EC DH Private, EC DH Public (passed in by the calling process). Digital signature User, CO Used to generate or verify RSA, DSA or ECDSA digital signatures. Executes using RSA SGK, RSA SVK; DSA SGK, DSA SVK; ECDSA SGK, ECDSA SVK (passed in by the calling process). Utility User, CO Miscellaneous helper functions. Does not access CSPs. Table 5 - Services and CSP Access 3 "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 Digi ConnectCore Security Module. Page 17 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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 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 DRBG KAT CTR_DRBG: AES, 256 bit with and without derivation function 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.1). 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 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()4 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 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 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()4 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 Module also implements the following conditional tests: Algorithm Test DRBG Tested as required by [SP800-90] 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 uninstantiate and re- instantiate the DRBG per the requirements of [SP 800-90]; 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. Page 19 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 140-2 requirement for a single user mode of operation. Page 20 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. Page 21 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Appendix A Installation and Usage Guidance 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 digi-fips-1.0.tar.gz. The command sets are: ./config make make install Installation instructions 1. Download and copy the distribution file to the build system. 2. Verify the HMAC-SHA-1 digest of the distribution file; see Appendix B. An independently acquired FIPS 140-2 validated implemention 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 digi-fips-1.0.tar.gz | tar xf - 4. Execute the installation command sets as shown above. No other command sets shall be used. 5. The resulting fipscanister.o file is now available for use. 6. The calling application enables FIPS mode by calling the FIPS_mode_set() 5 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 Module are outside of the cryptographic boundary. When linking the application with the Module two steps are necessary: 1. The HMAC-SHA-1 digest of the Module file must be calculated and verified against the installed digest to ensure the integrity of the Module. 5 FIPS_mode_set() calls the Module function FIPS_module_mode_set() Page 22 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy 2. A HMAC-SHA1 digest of the Module must be generated and embedded in the Module for use by the FIPS_mode_set()5 function at runtime initialization. The fips_standalone_sha1 command can be used to perform the verification of the 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()5 function compares the embedded HMAC-SHA-1 digest with a digest generated from the Module object code. This digest is the final link in the chain of validation from the original source to the runtime executable application file. Page 23 of 25 Digi ConnectCore Security Module - FIPS 140-2 Security Policy Appendix B Controlled Distribution File Fingerprint The Digi ConnectCore Security Module v1.0 consists of the Module (the fipscanister.o contiguous unit of binary object code) generated from the specific source files. The source files are in the specific special distribution file digi-fips-1.0.tar.gz with HMAC- SHA-1 digest of e8dbfa6cb9e22a049ec625ffb7ccaf33e6116598 The distribution is obtained by directly contacting Digi International, Inc. 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 distribution file (and patch file if used) shall be verified using the above HMAC-SHA-1 digest. Page 24 of 25 Digi ConnectCore Security Module - FIPS 140-2 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 Yocto Linux 2.4 gcc 7.3.0 2 Yocto Linux 2.4 gcc 7.3.0 Table C - Compilers Page 25 of 25': 1}}, 'vendor': {}, 'eval_facility': {}, 'symmetric_crypto': {'AES_competition': {'AES': {'AES': 20, 'AES-': 1, 'AES-128': 1, 'AES-256': 1}}, 'DES': {'DES': {'DEA': 1, 'DES': 9}, '3DES': {'TDEA': 1, 'TDES': 9}}, 'constructions': {'MAC': {'HMAC': 24, 'CMAC': 15}}}, 'asymmetric_crypto': {'ECC': {'ECDSA': {'ECDSA': 17}, 'ECC': {'ECC': 4}}, 'FF': {'DH': {'DH': 13}, 'DSA': {'DSA': 36}}}, 'pq_crypto': {}, 'hash_function': {'SHA': {'SHA1': {'SHA-1': 48, 'SHA1': 3}, 'SHA2': {'SHA-224': 15, 'SHA224': 1, 'SHA256': 4, 'SHA384': 1, 'SHA512': 2, 'SHA-256': 1, 'SHA-384': 1, 'SHA-2': 21, 'SHA2': 5}, 'SHA3': {'SHA3': 1, 'SHA-3': 1}}}, 'crypto_scheme': {'MAC': {'MAC': 40}, 'KA': {'KA': 15, 'Key Agreement': 2, 'Key agreement': 2}}, 'crypto_protocol': {'TLS': {'SSL': {'SSL': 1}}}, 'randomness': {'PRNG': {'DRBG': 38}, 'RNG': {'RNG': 3, 'RBG': 38}}, 'cipher_mode': {'ECB': {'ECB': 4}, 'CBC': {'CBC': 4}, 'CTR': {'CTR': 7}, 'CFB': {'CFB': 4}, 'OFB': {'OFB': 2}, 'GCM': {'GCM': 6}, 'CCM': {'CCM': 4}, 'XTS': {'XTS': 7}}, 'ecc_curve': {'NIST': {'P-224': 26, 'P-384': 24, 'P-521': 24, 'P-192': 16, 'P-256': 18, 'K-233': 8, 'K-409': 6, 'K-571': 6, 'B-233': 5, 'B-283': 6, 'B-409': 6, 'B-571': 6, 'K-163': 6, 'K-283': 5, 'B-163': 6, 'K-256': 1, 'K-384': 1, 'K-521': 1, 'B-224': 1, 'B-256': 1, 'B-384': 1}}, 'crypto_engine': {}, 'tls_cipher_suite': {}, 'crypto_library': {'OpenSSL': {'OpenSSL': 1}}, 'vulnerability': {}, 'side_channel_analysis': {}, 'device_model': {}, 'tee_name': {}, 'os_name': {}, 'cplc_data': {}, 'ic_data_group': {}, 'standard_id': {'FIPS': {'FIPS 140-2': 35, 'FIPS 180-3': 2, 'FIPS 186-4': 7, 'FIPS 197': 2, 'FIPS 198-1': 1, 'FIPS 198': 1, 'FIPS 186-2': 7, 'FIPS 186-3': 1}, 'NIST': {'SP 800-3': 7, 'SP 800-5': 5, 'SP 800-8': 1, 'SP 800-9': 6, 'SP 800-6': 1, 'SP 800-1': 1}, 'PKCS': {'PKCS1': 3, 'PKCS#1': 1}}, 'javacard_version': {}, 'javacard_api_const': {}, 'javacard_packages': {}, 'certification_process': {}}, 'algorithms': {'_type': 'Set', 'elements': []}, 'clean_cert_ids': {'#2': 1}, 'st_metadata': {'pdf_file_size_bytes': 236048, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 25, '/Author': 'CPUBuilders Customer', '/Creator': 'Writer', '/Producer': 'LibreOffice 5.1', '/CreationDate': "D:20180330153146-04'00'", 'pdf_hyperlinks': {'_type': 'Set', 'elements': ['http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-89/SP-800-89_November2006.pdf', 'http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf', 'http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-90/SP800-90revised_March2007.pdf', 'http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-56A/SP800-56A_Revision1_Mar08-2007.pdf', 'http://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1_final.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-38C/SP800-38C_updated-July20_2007.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-67/SP800-67.pdf', 'http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf']}}}.

The _type was updated.

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

The computed heuristics were updated.

The following values were inserted: {'clean_cert_ids': {}}.

The _type property was set to sec_certs.sample.fips.FIPSCertificate.Heuristics.

The keywords property was set to {}.

The algorithms property was set to {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#4275', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#3521', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#5323', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1375', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2053', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2851', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1397', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2686', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1788', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}]}.

The st_references property was updated, with the {'_type': 'sec_certs.sample.certificate.References', 'directly_referencing': None, 'indirectly_referencing': None} data.

The web_references property was updated, with the {'_type': 'sec_certs.sample.certificate.References'} data.

The state was updated.

The _type property was set to sec_certs.sample.fips.FIPSCertificate.InternalState.

The following properties were deleted: ['fragment_path'].

The web_scan was updated.

This property was removed.

The pdf_scan was updated.

This property was removed.
14.06.2022

The certificate data changed.
Certificate changed

The pdf_scan was updated.

The keywords property was updated, with the {'rules_standard_id': {'__update__': {'FIPS ?(?:PUB )?[0-9]+-[0-9]+?': {'__update__': {'FIPS 140-2': {'__update__': {'count': 1}}}, '__delete__': ['FIPS 180-3', 'FIPS 186-4', 'FIPS 198-1', 'FIPS 186-2', 'FIPS 186-3']}, 'FIPS ?(?:PUB )?[0-9]+?': {'__delete__': ['FIPS 197']}}}, 'rules_block_cipher_modes': {'__insert__': {'CCM': {'CCM': {'count': 1}}, 'XTS': {'XTS': {'count': 1}}}, '__update__': {'ECB': {'__update__': {'ECB': {'__update__': {'count': 1}}}}, 'CBC': {'__update__': {'CBC': {'__update__': {'count': 1}}}}, 'CTR': {'__update__': {'CTR': {'__update__': {'count': 1}}}}, 'CFB': {'__update__': {'CFB': {'__update__': {'count': 1}}}}, 'OFB': {'__update__': {'OFB': {'__update__': {'count': 1}}}}, 'GCM': {'__update__': {'GCM': {'__update__': {'count': 1}}}}}}, 'rules_ecc_curves': {'__insert__': {'(NIST)? ?[PBK]-[0-9]{3}': {'K-233': {'count': 1}}}, '__update__': {'(?:Curve |curve |)P-(192|224|256|384|521)': {'__update__': {'P-224': {'__update__': {'count': 1}}}, '__delete__': ['P-384', 'P-521', 'P-192', 'P-256']}}}, 'rules_other': {'__update__': {'library': {'__update__': {'library': {'__update__': {'count': 1}}}}}}} data.

The computed heuristics were updated.

The keywords property was updated, with the {'rules_standard_id': {'__update__': {'FIPS ?(?:PUB )?[0-9]+-[0-9]+?': {'__update__': {'FIPS 140-2': {'__update__': {'count': 1}}}, '__delete__': ['FIPS 180-3', 'FIPS 186-4', 'FIPS 198-1', 'FIPS 186-2', 'FIPS 186-3']}, 'FIPS ?(?:PUB )?[0-9]+?': {'__delete__': ['FIPS 197']}}}, 'rules_block_cipher_modes': {'__insert__': {'CCM': {'CCM': {'count': 1}}, 'XTS': {'XTS': {'count': 1}}}, '__update__': {'ECB': {'__update__': {'ECB': {'__update__': {'count': 1}}}}, 'CBC': {'__update__': {'CBC': {'__update__': {'count': 1}}}}, 'CTR': {'__update__': {'CTR': {'__update__': {'count': 1}}}}, 'CFB': {'__update__': {'CFB': {'__update__': {'count': 1}}}}, 'OFB': {'__update__': {'OFB': {'__update__': {'count': 1}}}}, 'GCM': {'__update__': {'GCM': {'__update__': {'count': 1}}}}}}, 'rules_ecc_curves': {'__insert__': {'(NIST)? ?[PBK]-[0-9]{3}': {'K-233': {'count': 1}}}, '__update__': {'(?:Curve |curve |)P-(192|224|256|384|521)': {'__update__': {'P-224': {'__update__': {'count': 1}}}, '__delete__': ['P-384', 'P-521', 'P-192', 'P-256']}}}, 'rules_other': {'__update__': {'library': {'__update__': {'library': {'__update__': {'count': 1}}}}}}} data.
22.05.2022

The certificate data changed.
Certificate changed

The computed heuristics were updated.

The cpe_matches property was set to {'_type': 'Set', 'elements': ['cpe:2.3:h:digi:connectcore_8x:-:*:*:*:*:*:*:*']}.
08.03.2022

The certificate data changed.
Certificate changed

The web_scan was updated.

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

The pdf_scan was updated.

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

The computed heuristics were updated.

The following values were inserted: {'st_references': {'_type': 'References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': {'_type': 'Set', 'elements': ['2398']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['2398']}}, 'web_references': {'_type': 'References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': {'_type': 'Set', 'elements': ['2398']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['2398']}}}.

The following properties were deleted: ['connections', 'directly_affected_by', 'indirectly_affected_by', 'directly_affecting', 'indirectly_affecting'].
18.02.2022

The certificate data changed.
Certificate changed

The computed heuristics were updated.

The extracted_versions property was set to {'_type': 'Set', 'elements': ['-']}.
02.02.2022

The certificate data changed.
Certificate changed

The web_scan was updated.

The module_type property was set to Software.
30.01.2022

The certificate was first processed.

Raw data

{
  "_type": "sec_certs.sample.fips.FIPSCertificate",
  "cert_id": 3176,
  "dgst": "73e7f3f802b0e919",
  "heuristics": {
    "_type": "sec_certs.sample.fips.FIPSCertificate.Heuristics",
    "algorithms": {
      "_type": "Set",
      "elements": [
        "#2053",
        "#1397",
        "ECDSA#1397",
        "AES#5323",
        "#2851",
        "#3521",
        "DSA#1375",
        "#4275",
        "SHS#4275",
        "#2686",
        "#1375",
        "RSA#2851",
        "#5323",
        "CVL#1788",
        "Triple-DES#2686",
        "DRBG#2053",
        "HMAC#3521"
      ]
    },
    "cpe_matches": null,
    "direct_transitive_cves": null,
    "extracted_versions": {
      "_type": "Set",
      "elements": [
        "-"
      ]
    },
    "indirect_transitive_cves": null,
    "module_processed_references": {
      "_type": "sec_certs.sample.certificate.References",
      "directly_referenced_by": null,
      "directly_referencing": {
        "_type": "Set",
        "elements": [
          "2398"
        ]
      },
      "indirectly_referenced_by": null,
      "indirectly_referencing": {
        "_type": "Set",
        "elements": [
          "2398"
        ]
      }
    },
    "module_prunned_references": {
      "_type": "Set",
      "elements": [
        "2398"
      ]
    },
    "policy_processed_references": {
      "_type": "sec_certs.sample.certificate.References",
      "directly_referenced_by": null,
      "directly_referencing": null,
      "indirectly_referenced_by": null,
      "indirectly_referencing": null
    },
    "policy_prunned_references": {
      "_type": "Set",
      "elements": []
    },
    "related_cves": null,
    "verified_cpe_matches": null
  },
  "pdf_data": {
    "_type": "sec_certs.sample.fips.FIPSCertificate.PdfData",
    "br1_deviations": 43,
    "br1_tables": null,
    "is_br1_format": false,
    "keywords": {
      "asymmetric_crypto": {
        "ECC": {
          "ECC": {
            "ECC": 4
          },
          "ECDSA": {
            "ECDSA": 18
          }
        },
        "FF": {
          "DH": {
            "DH": 9
          },
          "DSA": {
            "DSA": 18
          }
        }
      },
      "certification_process": {},
      "cipher_mode": {
        "CBC": {
          "CBC": 4
        },
        "CCM": {
          "CCM": 5
        },
        "CFB": {
          "CFB": 6
        },
        "CTR": {
          "CTR": 3
        },
        "ECB": {
          "ECB": 4
        },
        "GCM": {
          "GCM": 6
        },
        "OFB": {
          "OFB": 2
        },
        "XTS": {
          "XTS": 5
        }
      },
      "cplc_data": {},
      "crypto_engine": {},
      "crypto_library": {
        "OpenSSL": {
          "OpenSSL": 1
        }
      },
      "crypto_protocol": {},
      "crypto_scheme": {
        "KA": {
          "Key Agreement": 2,
          "Key agreement": 2
        }
      },
      "device_model": {},
      "ecc_curve": {
        "NIST": {
          "B-163": 4,
          "B-233": 1,
          "B-256": 1,
          "B-283": 2,
          "B-409": 1,
          "B-571": 2,
          "K-233": 4,
          "K-256": 1,
          "K-409": 3,
          "K-521": 1,
          "P-192": 10,
          "P-224": 10,
          "P-256": 8,
          "P-384": 4,
          "P-521": 10
        }
      },
      "eval_facility": {},
      "fips_cert_id": {
        "Cert": {
          "#1": 1,
          "#2": 1
        }
      },
      "fips_certlike": {
        "Certlike": {
          "AES 128/192/256": 3,
          "AES, 256": 1,
          "DRBG 1": 1,
          "DSA (1024": 2,
          "HMAC SHA-1": 1,
          "HMAC-SHA-1": 16,
          "HMAC-SHA1": 4,
          "HMACSHA-1": 1,
          "PKCS#1": 2,
          "SHA- 1, 224": 3,
          "SHA- 224": 1,
          "SHA-1": 19,
          "SHA-1, 224": 20,
          "SHA-2": 3,
          "SHA-2 (224": 2,
          "SHA-224": 15,
          "SHA-256": 1,
          "SHA-384": 1,
          "SHA1": 1,
          "SHA224": 1,
          "SHA256": 4,
          "SHA384": 1,
          "SHA512": 2,
          "platforms #1, #2; Yocto Linux 2.4 on ConnectCore 6/6UL SoM (ARMv7) with/without NEON": 1
        }
      },
      "fips_security_level": {
        "Level": {
          "level 1": 1
        }
      },
      "hash_function": {
        "SHA": {
          "SHA1": {
            "SHA-1": 39,
            "SHA1": 1
          },
          "SHA2": {
            "SHA-2": 5,
            "SHA-224": 15,
            "SHA-256": 1,
            "SHA-384": 1,
            "SHA224": 1,
            "SHA256": 4,
            "SHA384": 1,
            "SHA512": 2
          }
        }
      },
      "ic_data_group": {},
      "javacard_api_const": {},
      "javacard_packages": {},
      "javacard_version": {},
      "os_name": {},
      "pq_crypto": {},
      "randomness": {
        "PRNG": {
          "DRBG": 20
        },
        "RNG": {
          "RNG": 3
        }
      },
      "side_channel_analysis": {},
      "standard_id": {
        "FIPS": {
          "FIPS 140-2": 35,
          "FIPS 180-3": 2,
          "FIPS 186-2": 7,
          "FIPS 186-3": 1,
          "FIPS 186-4": 8,
          "FIPS 197": 2,
          "FIPS 198": 1,
          "FIPS 198-1": 1
        },
        "NIST": {
          "SP 800-131A": 1,
          "SP 800-38B": 2,
          "SP 800-38C": 2,
          "SP 800-38D": 2,
          "SP 800-38E": 1,
          "SP 800-56A": 4,
          "SP 800-56B": 1,
          "SP 800-67": 1,
          "SP 800-89": 1,
          "SP 800-90": 6
        },
        "PKCS": {
          "PKCS#1": 1
        }
      },
      "symmetric_crypto": {
        "AES_competition": {
          "AES": {
            "AES": 19
          }
        },
        "DES": {
          "3DES": {
            "TDEA": 1,
            "TDES": 9
          }
        },
        "constructions": {
          "MAC": {
            "CMAC": 16,
            "HMAC": 8
          }
        }
      },
      "tee_name": {},
      "tls_cipher_suite": {},
      "vendor": {},
      "vulnerability": {}
    },
    "module_algorithms": {
      "_type": "Set",
      "elements": [
        "AES#5323",
        "ECDSA#1397",
        "DRBG#2053",
        "DSA#1375",
        "RSA#2851",
        "CVL#1788",
        "Triple-DES#2686",
        "SHS#4275",
        "HMAC#3521"
      ]
    },
    "policy_algorithms": {
      "_type": "Set",
      "elements": [
        "#2053",
        "#1397",
        "#3521",
        "#4275",
        "#2686",
        "#1375",
        "#5323",
        "#2851"
      ]
    },
    "policy_metadata": {
      "/Author": "CPUBuilders Customer",
      "/CreationDate": "D:20180330153146-04\u002700\u0027",
      "/Creator": "Writer",
      "/Producer": "LibreOffice 5.1",
      "pdf_file_size_bytes": 236048,
      "pdf_hyperlinks": {
        "_type": "Set",
        "elements": [
          "http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf",
          "http://csrc.nist.gov/publications/nistpubs/800-38C/SP800-38C_updated-July20_2007.pdf",
          "http://csrc.nist.gov/publications/nistpubs/800-38D/SP-800-38D.pdf",
          "http://csrc.nist.gov/publications/nistpubs/800-90/SP800-90revised_March2007.pdf",
          "http://csrc.nist.gov/publications/nistpubs/800-56A/SP800-56A_Revision1_Mar08-2007.pdf",
          "http://csrc.nist.gov/publications/fips/fips186-3/fips_186-3.pdf",
          "http://csrc.nist.gov/publications/fips/fips180-3/fips180-3_final.pdf",
          "http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf",
          "http://csrc.nist.gov/publications/nistpubs/800-89/SP-800-89_November2006.pdf",
          "http://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1_final.pdf",
          "http://csrc.nist.gov/publications/nistpubs/800-67/SP800-67.pdf",
          "http://csrc.nist.gov/publications/fips/fips140-2/fips1402.pdf"
        ]
      },
      "pdf_is_encrypted": false,
      "pdf_number_of_pages": 25
    }
  },
  "state": {
    "_type": "sec_certs.sample.fips.InternalState",
    "module": {
      "_type": "sec_certs.sample.document_state.DocumentState",
      "convert_ok": true,
      "download_ok": true,
      "extract_ok": true,
      "json_hash": null,
      "source_hash": null,
      "txt_hash": null
    },
    "policy": {
      "_type": "sec_certs.sample.document_state.DocumentState",
      "convert_ok": true,
      "download_ok": true,
      "extract_ok": true,
      "json_hash": "6ad1769e2bd3faccce5bdcaf803c4904f59f5c06565fb05a8508b35341c5c780",
      "source_hash": "3c4d11b0edd0c7d2535b2afc732be3cd3d9090a023e5421c120ea365745722fc",
      "txt_hash": "2ba3dd1238306d0ba71ef61d99371d6b4a1f2b7780ea225faa5b196167a922e4"
    }
  },
  "web_data": {
    "_type": "sec_certs.sample.fips.FIPSCertificate.WebData",
    "caveat": "When built, installed, protected and initialized as assumed by the Crypto Officer role and as specified in the provided Security Policy. Appendix A of the provided Security Policy specifies the actual distribution tar file containing the source code of this module. There shall be no additions, deletions or alterations to the tar file contents as used during module build. The distribution tar file shall be verified as specified in Appendix A of the provided Security Policy. Installation and protection shall be completed as specified in Appendix A of the provided Security Policy. Initialization shall be invoked as per Section 4 of the provided Security Policy. Any deviation from specified verification, protection, installation and initialization procedures will result in a non FIPS 140-2 compliant module. This validation entry is a non-security relevant modification to Cert. #2398",
    "certificate_pdf_url": "https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/certificates/AprilConsolidated2018.pdf",
    "date_sunset": null,
    "description": "The Digi ConnectCore Security Module provides cryptographic services for Digi International Inc. products.",
    "embodiment": "Multi-Chip Stand Alone",
    "exceptions": [
      "Roles, Services, and Authentication: Level 2",
      "Physical Security: N/A",
      "Design Assurance: Level 3",
      "Mitigation of Other Attacks: N/A"
    ],
    "fw_versions": null,
    "historical_reason": "186-2 transition",
    "hw_versions": null,
    "level": 1,
    "mentioned_certs": {
      "2398": 1
    },
    "module_name": "Digi ConnectCore Security Module",
    "module_type": "Software",
    "revoked_link": null,
    "revoked_reason": null,
    "standard": "FIPS 140-2",
    "status": "historical",
    "sw_versions": "1.0",
    "tested_conf": [
      "Yocto Linux 2.4 running on ConnectCore 6/6UL SoM (ARMv7) without PAA (gcc Compiler Version 7.3.0), Yocto Linux 2.4 running on ConnectCore 6/6UL SoM (ARMv7) with PAA (gcc Compiler Version 7.3.0) (single-user mode)"
    ],
    "validation_history": [
      {
        "_type": "sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry",
        "date": "2018-04-26",
        "lab": "Acumen Security",
        "validation_type": "Initial"
      },
      {
        "_type": "sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry",
        "date": "2018-06-12",
        "lab": "Acumen Security",
        "validation_type": "Update"
      }
    ],
    "vendor": "Digi International, Inc.",
    "vendor_url": "http://www.digi.com"
  }
}

Sections