Arista EOS Crypto Module v1.0

Extracted keywords

• 06.10.2026

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'HMAC SHA-1': 1, 'SHA-1 128': 1, 'SHA-512 256': 1, 'AES-128 128': 1, 'AES-192 192': 1, 'AES-256 256': 1, 'platform #102, TS-Linux 2.4 on ARMv4': 1, 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4': 1, 'platform #96, FreeBSD 8.4 on x86 without AES-NI': 1, 'platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG': 1, 'platforms #90, #91': 1, 'platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86': 1, 'platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5': 1, 'platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition': 1, 'platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI': 1, 'platforms #77, #78 iOS 6.0 with/without NEON': 1}, '__update__': {'SHA-1': 4, 'SHA-512': 2, 'AES-256': 1}, '__delete__': ['AES-128', 'AES-192', 'platform #102, TS-Linux 2.4 on ARMv4 | | 2014-11-25 | (2.0.9) Addition of new platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 | | 2014-01-04 | Addition of new platform #96, FreeBSD 8.4 on x86 without AES-NI | | 2014-07-30 | Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG | | 2014-07-28 | Changed processor names for platforms #90, #91 | | 2014-07-11 | Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86 | | 2014-06-12 | Temporarily remove misplaced platform, move Dual EC DRBG to the Non- Approved Table 4c | | 2014-05-29 | Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) | | 2014-05-12 | Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition | | 2013-11-08 | Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI | | 2013-11-01 | Added two platforms #77, #78 iOS 6.0 with/without NEON | | 2013-10-02 | Added six platforms (Linux 3.4 x86 virtualized under XenSource/VMware/Hyper- V, with/without AES-NI) Updated URL in Appendix A footnote | | 2013-08-29 | Added new sponsor acknowledgment | Page 4 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy | 2013-08-14 | Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms | |--------------|-----------------------------------------------------------------------------------------------------| | 2013-07-24 | Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 | | 2013-06-09 | Added QNX, iOS 6.1, eCos for revision 2.0.5 | | 2013-05-01 | Added OpenWRT 2.6 for revision 2.0.4 | | 2013-03-01 | Added VMware Horizon Mobile 1.3, Apple OS X 10.7, Apple iOS 5.0 | | 2013-02-23 | Added WinEC7 and Android 4.0 for revision 2.0.3 | | 2013-02-14 | Table 5: Removed references to non-existent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM | | 2013-01-28 | Added four platforms: Android 4.1 and Android 4.2 with and without NEON | | 2013-01-08 | Reworded section 8 | | 2013-01-03 | Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AES-NI. | | 2012-12-08 | Note EC DH Key Agreement and RSA Key Wrapping strength. | | 2012-10-10 | Added NetBSD 5.1 on PowerPC-e500, NetBSD 5.1 on Intel Xeon 5500 (x86-64) for revision 2.0.2 | | 2011-07-02 | Added DSP Media Framework, Linux 2.6/Freescale PowerPC-e500, Android 4.0 | | 2011-06-15 | Added iOS, WinCE 5, WinCE 6 OEs | Page 5 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy References | Reference | Full Specification Name | |---------------|---------------------------------------------------------------------------------------------------------| | [FIPS 140-2] | Security Requirements for Cryptographic modules, May 25, 2001 | | [FIPS 180-4] | 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-90A] | 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 6 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### Table of Contents | 1 | Introduction | |-----|----------------------------------------------------| | 2 | Tested Configurations | | 3 | Ports and Interfaces | | 4 | Modes of Operation and Cryptographic Functionality | | | 4.1 Critical Security Parameters and Public Keys | | 5 | Roles, Authentication, and Services | | 6 | Self-Tests | | 7 | Operational Environment | | 8 | Mitigation of other Attacks | | 9 | Operator Guidance | Page 7 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 1 Introduction This document is the non-proprietary security policy for the Arista EOS Crypto Module v1.0, hereafter referred to as the Module. The Module is a software library providing a C-language application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 140-2 as a software module, multi-chip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the OpenSSL API file. The Module performs no communications other than with the calling application (the process that invokes the Module services). The FIPS 140-2 security levels for the Module are as follows: Table 1 - Security Level of Security Requirements | Security Requirement | Security Level | |-------------------------------------------|------------------| | Cryptographic Module Specification | 1 | | Cryptographic Module Ports and Interfaces | 1 | | Roles, Services, and Authentication | 1 | | Finite State Model | 1 | | Physical Security | NA | | Operational Environment | 1 | | Cryptographic Key Management | 1 | | EMI/EMC | 1 | | Self-Tests | 1 | | Design Assurance | 1 | | Mitigation of Other Attacks | NA | The Module\'s software version for this validation is: v1.0. This is a fork of the OpenSSL FIPS Object Module version 2.0.10. Page 8 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy Arista Networks; Inc: FIPS 140-2 Security Policy Figure 1 - Module Block Diagram Page 9 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 2 Module Configurations The following configurations were operationally tested. Table 2a - Tested Configurations | # | Operational Environment | Processor | Optimizations (Target) | |-----|-----------------------------------------------------------------------|----------------------------|--------------------------| | 1 | EOS v4 on Arista 7150S-24 | AMD Athlon NEO X2 | None | | 2 | EOS v4 on Arista 7300 (DCS-7300-SUP supervisor, DCS-7308 chassis) | Intel Sandy Bridge EN | None | | 3 | EOS v4 on Arista 7500R (DCS-7500- SUP2 supervisor, DCS-7508 chassis ) | Intel Broadwell-DE | None | | 4 | EOS v4 on Arista 7050SX-72 | AMD G Series: eKabini | None | | 5 | EOS v4 on Arista 7060CX-32S | AMD G Series: Steppe Eagle | None | The following configurations have the same operating system and processors as the above configurations and are vendor affirmed to behave in the same manner. (As these have only been affirmed by the vendor, CMVP itself does not provide assurances to the correct operation of the module or the strength of generated keys.) Table 2b - Vendor Affirmed Configurations | # | Operational Environment | Processor | Optimizations (Target) | |-----|-------------------------------------------------------------------------------------------|----------------------------|--------------------------| | 1 | EOS v4 on Arista 7050QX, 7150 | AMD Athlon NEO X2 | None | | 2 | EOS v4 on Arista 7500R, 7320X, 7300X, 7300X3, 7250QX, 7260X, 7280CR, 7050SX, 7050TX | Intel Sandy Bridge EN | None | | 3 | EOS v4 on Arista 7500R, 7260X3, 7170, 7060X4 | Intel Broadwell-DE | None | | 4 | EOS v4 on Arista 7260, 7260X, 7050SX, 7050TX, 7050QX, 7160, 7010T | AMD G Series: eKabini | None | | 5 | EOS v4 on Arista 7280QR, 7280SR, 7280TR, 7060, 7050SX, 7050TX, 7160, 7060X, 7050X3, 7020R | AMD G Series: Steppe Eagle | None | Page 10 of 19 Arista Networks, Inc. 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 11 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 Approved mode and a non-Approved mode. The Approved mode is invoked by calling FIPS_mode_set() and using only Approved and allowed algorithms. Tables 4a and 4b list the Approved and non-approved but allowed algorithms, respectively. Table 4a - FIPS Approved Cryptographic Functions | Function | Algorithm | Options | Cert # | |-------------------------------------------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| | Random number generation | [SP 800-90] DRBG 1 Prediction resistance supported for all variations | Hash DRBG (SHA-1, all SHA-2 sizes) HMAC DRBG (SHA-1, all SHA-2 sizes) CTR DRBG (AES-128/192/256) | DRBG #1340 | | Encryption, Decryption and CMAC | [FIPS 197] AES [SP 800-38A] CBC, etc. [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM | 128/192/256 ECB, CBC, OFB, CFB-1, CFB-8, CFB-128, CTR; CCM; GCM; CMAC | AES #4280 | | Encryption, Decryption and CMAC | [SP 800-67] Triple-DES | 3-Key Triple-DES TECB, TCBC, TCFB-1, TCFB-8, TCFB-64, TOFB; CMAC | Triple- DES #2309 | | Message Digests | [FIPS 180-3] SHA-1/2 | SHA-1, SHA-2 (224, 256, 384, 512) | SHS #3516 | | Keyed Hash | [FIPS 198] HMAC | SHA-1, SHA-2 (224, 256, 384, 512) | HMAC #2816 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] RSA | GenKey9.31 (2048/3072) SigGen9.31, SigGenPKCS1.5, SigGenPSS (2048/3072 with all SHA2 sizes) SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072 with all SHA-2 sizes) | RSA #2301 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] Legacy RSA | SigVer9.31, SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA sizes) | RSA #2301 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (2048/3072) PQG Ver, Sig Ver (1024) | DSA #1141 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] ECDSA | Functions: PKG, PKV, SigGen, SigGen Component, SigVer Curves: P-256, P-384, P-521 Hashes: SHA-1*, SHA-224, SHA-256, SHA- 384, SHA-512 *SHA-1 signature generation is allowed for protocol usage only. | ECDSA #998 | | Key Derivation | [SP800-135] KDF, Application Specific 2 | TLS KDF (v1.0/v1.1 and v1.2) SSH KDF | CVL #1012 | 1 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP800-90A] and [SP800-57]. 2 Only the KDFs to these protocols have been tested by CAVP. Page 12 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy Table 4b - Non-FIPS Approved But Allowed Cryptographic Functions | Category | Algorithm | Description | |----------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC Diffie-Hellman | Non-compliant (untested to SP800-56A) Diffie-Hellman scheme using elliptic curve, supporting curves P-256, P-384, and P-512. This key agreement scheme provides between 128 and 256 bits of encryption strength; however, it is only a service provided for calling process use. It 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. It provides 112 or 128 bits of encryption strength. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. | | Hashing | MD5 within TLS | Component of TLS KDF | The Module implements the following NIST-specified algorithms, which are non-Approved, either from algorithm transitions (e.g., SP800-131A) or from not being tested: Table 4c - Untested and Transition-Disallowed Cryptographic Functions | Function | Algorithm | Options | |-------------------------------------------------|----------------------------------|----------------------------------------------------------| | Encryption and Decryption | AES-XTS 128/256 (Untested) | Encrypt, decrypt | | Digital Signature and Asymmetric Key Generation | RSA key size < 2048 (Disallowed) | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (<2048) | | | DSA key size <2048 (Disallowed) | PQG Gen, Key Pair Gen, Sig Gen (<2048) | | Key Encryption, Decryption | RSA key size < 2048 (Disallowed) | RSA key encryption/decryption (<2048) | The algorithms in Table 4c must not be used when operating in the FIPS mode of operation. The Module also implements the following algorithms, which are non-Approved: Table 4d - Other non-Approved Cryptographic Functions | Function | Algorithm | Function | Algorithm | |---------------------------|-----------------------------------|---------------------------|-------------| | Encryption and Decryption | AES/Triple-DES KW (non-compliant) | Encryption and Decryption | RC4 | | Encryption and Decryption | Blowfish | Encryption and Decryption | RC5 | | Encryption and Decryption | Camellia 128/192/256 | Encryption and Decryption | SEED | | Encryption and Decryption | CAST5 | Message Digests | MD4 | | Encryption and Decryption | DES | Message Digests | MD5 | | Encryption and Decryption | DES-X | Message Digests | RIPEMD-160 | | Encryption and Decryption | IDEA | Message Digests | Whirlpool | | Encryption and Decryption | RC2 | Keyed Hash | HMAC-MD5 | The algorithms in Table 4d are automatically disabled when in the FIPS mode of operation. 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 assurances are outside the scope of the Module, and are the responsibility of the calling process. Page 13 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ## 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. Table 4.1a - Critical Security Parameters | CSP Name | Description | |---------------------------|-----------------------------------------------------------------| | AES EDK | AES encrypt / decrypt key | | AES CMAC | AES CMAC generate / verify key | | AES CCM | AES encrypt / decrypt / generate / verify key for CCM | | AES GCM | AES encrypt / decrypt / generate / verify key for GCM | | DRBG Seed | Entropy input for Hash, HMAC, or CTR DRBG. | | Hash_DRBG CSPs | V (440/888 bits) and C (440/888 bits) | | HMAC_DRBG CSPs | V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits) | | CTR_DRBG CSPs | V (128 bits) and Key (AES 128/192/256) | | DSA SGK | DSA signature generation key | | ECDSA SGK | ECDSA signature generation key | | EC Diffie-Hellman Private | EC Diffie-Hellman private key agreement key | | HMAC Key | Keyed hash key (160/224/256/384/512) | | RSA SGK | RSA signature generation key | | RSA KDK | RSA key decryption (private key transport) key | | Triple-DES EDK | Triple-DES (3-Key) encrypt / decrypt key | | Triple-DES CMAC | Triple-DES (3-Key) CMAC generate / verify key | The module does not output intermediate key generation values. Table 4.1b - Public Keys | Public Key Name | Description | |--------------------------|-----------------------------------------------| | DSA SVK | DSA signature verification key | | ECDSA SVK | ECDSA signature verification key | | EC Diffie-Hellman Public | EC Diffie-Hellman public key agreement key | | RSA SVK | RSA signature verification public key | | RSA KEK | RSA key encryption (public key transport) key | ####### For all CSPs and Public Keys: Storage: RAM, associated to entities by memory location. The Module stores RNG and DRBG state values for the lifetime of the RNG or DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of RNG and DRBG state values used for the Module\'s default key generation service. Generation: The Module implements SP 800-90A DRBG (Hash, HMAC, or CTR) services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry: All CSPs enter the Module\'s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output: The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Page 14 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy 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 (Cryptographic 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. For operation in the Approved mode, Module users (the calling applications) shall use entropy sources that contain at least 112 bits of entropy. To ensure full DRBG strength, the entropy sources must meet or exceed the security strengths shown in the table below. Table 5 - DRBG Entropy Requirements | DRBG Type | Underlying Algorithm | Minimum Seed Entropy | |------------------------|------------------------|------------------------| | Hash_DRBG or HMAC_DRBG | SHA-1 | 128 | | Hash_DRBG or HMAC_DRBG | SHA-224 | 192 | | Hash_DRBG or HMAC_DRBG | SHA-256 | 256 | | Hash_DRBG or HMAC_DRBG | SHA-384 | 256 | | Hash_DRBG or HMAC_DRBG | SHA-512 | 256 | | CTR_DRBG | AES-128 | 128 | | | AES-192 | 192 | | | AES-256 | 256 | This entropy is supplied by means of callback functions. Those functions must return an error if the requested entropy strength cannot be met. Page 15 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 5 Roles, Authentication, and Services The Module implements the required User and Cryptographic Officer roles and does not perform operator authentication. 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. - Cryptographic 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. All services are available in both the Approved mode and the non-Approved mode. In the Approved mode, these services are restricted to the algorithms listed in Tables 4a and 4b. In the non-Approved mode, the algorithms listed in Tables 4c and 4d may also be used. | 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 number generation | User, CO | Used for random number and symmetric key 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 security 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 any symmetric encryption key from Table 4.1a: AES EDK, AES CCM, AES GCM, Triple-DES EDK (passed in by the calling process). | | Symmetric digest | User, CO | Used to generate or verify data integrity with CMAC. Executes using AES CMAC, Triple-DES 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). | Page 16 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy Table 6 - Services and CSP Access | Key transport 3 (algorithms only) | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (the key is treated as payload data; this service does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | |-------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key agreement (algorithms only) | User, CO | Used to perform key agreement primitives on behalf of the calling process (this service does not establish keys into the module). Executes using EC Diffie-Hellman Private, EC Diffie-Hellman Public (passed in by the calling process). | | Key derivation | User, CO | Used to perform key derivation primitives as per SP800-135: TLS KDF and SSH KDF (this service does not establish keys into the module). | | 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 OpenSSL FIPS Object Module. Page 17 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 6 Self-Tests The Module performs the self-tests listed below on invocation of Initialize or Self-Test. Table 7a - 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 | | AES CMAC | KAT | CMAC generate and verify, 128, 192, 256 key lengths | | Triple-DES | KAT | Separate encrypt and decrypt, ECB mode, 3-Key | | Triple-DES CMAC | KAT | CMAC generate and verify, 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 with and without derivation function Hash_DRBG: SHA-256 HMAC_DRBG: SHA-256 | | ECDSA | PCT | Keygen, sign, verify using P-256 with SHA-512. | The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMAC-SHA-1 of the Module distribution file as tested by the CST 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() 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. 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy The Module also implements the following conditional tests: Table 7b - Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Health Tests as required by [SP800-90A] Section 11.3 | | DRBG | FIPS 140-2 continuous test (CRNGT) 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 | Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. Failure of conditional self-tests is handled in the same manner as failure of power-on self-tests. ##### 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. ##### 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. ##### 9 Operator Guidance User must ensure that the use of Triple-DES is compliant with IG A.13 SP 800-67rev1 Transition. User is responsible to enforce the limit of 2 20 64-bit data block encryptions with the same three-key Triple-DES key applies when keys are generated as part of one of the recognized IETF protocols and to enforce the limit of 2 16 64-bit data block encryptions when key is not generated as part of a recognized IETF protocol. Page 19 of 19']}}}} data.

  The computed heuristics were updated.

  • The policy_prunned_references property was updated, with the {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '81', '77', '86']} values discarded.
  • The policy_processed_references property was updated, with the {'directly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '81', '77', '86']}}, 'indirectly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '81', '77', '86']}}} data.
• 05.10.2026

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'AES-128': 1, 'AES-192': 1, 'platform #102, TS-Linux 2.4 on ARMv4 | | 2014-11-25 | (2.0.9) Addition of new platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 | | 2014-01-04 | Addition of new platform #96, FreeBSD 8.4 on x86 without AES-NI | | 2014-07-30 | Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG | | 2014-07-28 | Changed processor names for platforms #90, #91 | | 2014-07-11 | Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86 | | 2014-06-12 | Temporarily remove misplaced platform, move Dual EC DRBG to the Non- Approved Table 4c | | 2014-05-29 | Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) | | 2014-05-12 | Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition | | 2013-11-08 | Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI | | 2013-11-01 | Added two platforms #77, #78 iOS 6.0 with/without NEON | | 2013-10-02 | Added six platforms (Linux 3.4 x86 virtualized under XenSource/VMware/Hyper- V, with/without AES-NI) Updated URL in Appendix A footnote | | 2013-08-29 | Added new sponsor acknowledgment | Page 4 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy | 2013-08-14 | Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms | |--------------|-----------------------------------------------------------------------------------------------------| | 2013-07-24 | Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 | | 2013-06-09 | Added QNX, iOS 6.1, eCos for revision 2.0.5 | | 2013-05-01 | Added OpenWRT 2.6 for revision 2.0.4 | | 2013-03-01 | Added VMware Horizon Mobile 1.3, Apple OS X 10.7, Apple iOS 5.0 | | 2013-02-23 | Added WinEC7 and Android 4.0 for revision 2.0.3 | | 2013-02-14 | Table 5: Removed references to non-existent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM | | 2013-01-28 | Added four platforms: Android 4.1 and Android 4.2 with and without NEON | | 2013-01-08 | Reworded section 8 | | 2013-01-03 | Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AES-NI. | | 2012-12-08 | Note EC DH Key Agreement and RSA Key Wrapping strength. | | 2012-10-10 | Added NetBSD 5.1 on PowerPC-e500, NetBSD 5.1 on Intel Xeon 5500 (x86-64) for revision 2.0.2 | | 2011-07-02 | Added DSP Media Framework, Linux 2.6/Freescale PowerPC-e500, Android 4.0 | | 2011-06-15 | Added iOS, WinCE 5, WinCE 6 OEs | Page 5 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy References | Reference | Full Specification Name | |---------------|---------------------------------------------------------------------------------------------------------| | [FIPS 140-2] | Security Requirements for Cryptographic modules, May 25, 2001 | | [FIPS 180-4] | 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-90A] | 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 6 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### Table of Contents | 1 | Introduction | |-----|----------------------------------------------------| | 2 | Tested Configurations | | 3 | Ports and Interfaces | | 4 | Modes of Operation and Cryptographic Functionality | | | 4.1 Critical Security Parameters and Public Keys | | 5 | Roles, Authentication, and Services | | 6 | Self-Tests | | 7 | Operational Environment | | 8 | Mitigation of other Attacks | | 9 | Operator Guidance | Page 7 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 1 Introduction This document is the non-proprietary security policy for the Arista EOS Crypto Module v1.0, hereafter referred to as the Module. The Module is a software library providing a C-language application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 140-2 as a software module, multi-chip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the OpenSSL API file. The Module performs no communications other than with the calling application (the process that invokes the Module services). The FIPS 140-2 security levels for the Module are as follows: Table 1 - Security Level of Security Requirements | Security Requirement | Security Level | |-------------------------------------------|------------------| | Cryptographic Module Specification | 1 | | Cryptographic Module Ports and Interfaces | 1 | | Roles, Services, and Authentication | 1 | | Finite State Model | 1 | | Physical Security | NA | | Operational Environment | 1 | | Cryptographic Key Management | 1 | | EMI/EMC | 1 | | Self-Tests | 1 | | Design Assurance | 1 | | Mitigation of Other Attacks | NA | The Module\'s software version for this validation is: v1.0. This is a fork of the OpenSSL FIPS Object Module version 2.0.10. Page 8 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy Arista Networks; Inc: FIPS 140-2 Security Policy Figure 1 - Module Block Diagram Page 9 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 2 Module Configurations The following configurations were operationally tested. Table 2a - Tested Configurations | # | Operational Environment | Processor | Optimizations (Target) | |-----|-----------------------------------------------------------------------|----------------------------|--------------------------| | 1 | EOS v4 on Arista 7150S-24 | AMD Athlon NEO X2 | None | | 2 | EOS v4 on Arista 7300 (DCS-7300-SUP supervisor, DCS-7308 chassis) | Intel Sandy Bridge EN | None | | 3 | EOS v4 on Arista 7500R (DCS-7500- SUP2 supervisor, DCS-7508 chassis ) | Intel Broadwell-DE | None | | 4 | EOS v4 on Arista 7050SX-72 | AMD G Series: eKabini | None | | 5 | EOS v4 on Arista 7060CX-32S | AMD G Series: Steppe Eagle | None | The following configurations have the same operating system and processors as the above configurations and are vendor affirmed to behave in the same manner. (As these have only been affirmed by the vendor, CMVP itself does not provide assurances to the correct operation of the module or the strength of generated keys.) Table 2b - Vendor Affirmed Configurations | # | Operational Environment | Processor | Optimizations (Target) | |-----|-------------------------------------------------------------------------------------------|----------------------------|--------------------------| | 1 | EOS v4 on Arista 7050QX, 7150 | AMD Athlon NEO X2 | None | | 2 | EOS v4 on Arista 7500R, 7320X, 7300X, 7300X3, 7250QX, 7260X, 7280CR, 7050SX, 7050TX | Intel Sandy Bridge EN | None | | 3 | EOS v4 on Arista 7500R, 7260X3, 7170, 7060X4 | Intel Broadwell-DE | None | | 4 | EOS v4 on Arista 7260, 7260X, 7050SX, 7050TX, 7050QX, 7160, 7010T | AMD G Series: eKabini | None | | 5 | EOS v4 on Arista 7280QR, 7280SR, 7280TR, 7060, 7050SX, 7050TX, 7160, 7060X, 7050X3, 7020R | AMD G Series: Steppe Eagle | None | Page 10 of 19 Arista Networks, Inc. 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 11 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 Approved mode and a non-Approved mode. The Approved mode is invoked by calling FIPS_mode_set() and using only Approved and allowed algorithms. Tables 4a and 4b list the Approved and non-approved but allowed algorithms, respectively. Table 4a - FIPS Approved Cryptographic Functions | Function | Algorithm | Options | Cert # | |-------------------------------------------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| | Random number generation | [SP 800-90] DRBG 1 Prediction resistance supported for all variations | Hash DRBG (SHA-1, all SHA-2 sizes) HMAC DRBG (SHA-1, all SHA-2 sizes) CTR DRBG (AES-128/192/256) | DRBG #1340 | | Encryption, Decryption and CMAC | [FIPS 197] AES [SP 800-38A] CBC, etc. [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM | 128/192/256 ECB, CBC, OFB, CFB-1, CFB-8, CFB-128, CTR; CCM; GCM; CMAC | AES #4280 | | Encryption, Decryption and CMAC | [SP 800-67] Triple-DES | 3-Key Triple-DES TECB, TCBC, TCFB-1, TCFB-8, TCFB-64, TOFB; CMAC | Triple- DES #2309 | | Message Digests | [FIPS 180-3] SHA-1/2 | SHA-1, SHA-2 (224, 256, 384, 512) | SHS #3516 | | Keyed Hash | [FIPS 198] HMAC | SHA-1, SHA-2 (224, 256, 384, 512) | HMAC #2816 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] RSA | GenKey9.31 (2048/3072) SigGen9.31, SigGenPKCS1.5, SigGenPSS (2048/3072 with all SHA2 sizes) SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072 with all SHA-2 sizes) | RSA #2301 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] Legacy RSA | SigVer9.31, SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA sizes) | RSA #2301 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (2048/3072) PQG Ver, Sig Ver (1024) | DSA #1141 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] ECDSA | Functions: PKG, PKV, SigGen, SigGen Component, SigVer Curves: P-256, P-384, P-521 Hashes: SHA-1*, SHA-224, SHA-256, SHA- 384, SHA-512 *SHA-1 signature generation is allowed for protocol usage only. | ECDSA #998 | | Key Derivation | [SP800-135] KDF, Application Specific 2 | TLS KDF (v1.0/v1.1 and v1.2) SSH KDF | CVL #1012 | 1 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP800-90A] and [SP800-57]. 2 Only the KDFs to these protocols have been tested by CAVP. Page 12 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy Table 4b - Non-FIPS Approved But Allowed Cryptographic Functions | Category | Algorithm | Description | |----------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC Diffie-Hellman | Non-compliant (untested to SP800-56A) Diffie-Hellman scheme using elliptic curve, supporting curves P-256, P-384, and P-512. This key agreement scheme provides between 128 and 256 bits of encryption strength; however, it is only a service provided for calling process use. It 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. It provides 112 or 128 bits of encryption strength. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. | | Hashing | MD5 within TLS | Component of TLS KDF | The Module implements the following NIST-specified algorithms, which are non-Approved, either from algorithm transitions (e.g., SP800-131A) or from not being tested: Table 4c - Untested and Transition-Disallowed Cryptographic Functions | Function | Algorithm | Options | |-------------------------------------------------|----------------------------------|----------------------------------------------------------| | Encryption and Decryption | AES-XTS 128/256 (Untested) | Encrypt, decrypt | | Digital Signature and Asymmetric Key Generation | RSA key size < 2048 (Disallowed) | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (<2048) | | | DSA key size <2048 (Disallowed) | PQG Gen, Key Pair Gen, Sig Gen (<2048) | | Key Encryption, Decryption | RSA key size < 2048 (Disallowed) | RSA key encryption/decryption (<2048) | The algorithms in Table 4c must not be used when operating in the FIPS mode of operation. The Module also implements the following algorithms, which are non-Approved: Table 4d - Other non-Approved Cryptographic Functions | Function | Algorithm | Function | Algorithm | |---------------------------|-----------------------------------|---------------------------|-------------| | Encryption and Decryption | AES/Triple-DES KW (non-compliant) | Encryption and Decryption | RC4 | | Encryption and Decryption | Blowfish | Encryption and Decryption | RC5 | | Encryption and Decryption | Camellia 128/192/256 | Encryption and Decryption | SEED | | Encryption and Decryption | CAST5 | Message Digests | MD4 | | Encryption and Decryption | DES | Message Digests | MD5 | | Encryption and Decryption | DES-X | Message Digests | RIPEMD-160 | | Encryption and Decryption | IDEA | Message Digests | Whirlpool | | Encryption and Decryption | RC2 | Keyed Hash | HMAC-MD5 | The algorithms in Table 4d are automatically disabled when in the FIPS mode of operation. 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 assurances are outside the scope of the Module, and are the responsibility of the calling process. Page 13 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ## 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. Table 4.1a - Critical Security Parameters | CSP Name | Description | |---------------------------|-----------------------------------------------------------------| | AES EDK | AES encrypt / decrypt key | | AES CMAC | AES CMAC generate / verify key | | AES CCM | AES encrypt / decrypt / generate / verify key for CCM | | AES GCM | AES encrypt / decrypt / generate / verify key for GCM | | DRBG Seed | Entropy input for Hash, HMAC, or CTR DRBG. | | Hash_DRBG CSPs | V (440/888 bits) and C (440/888 bits) | | HMAC_DRBG CSPs | V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits) | | CTR_DRBG CSPs | V (128 bits) and Key (AES 128/192/256) | | DSA SGK | DSA signature generation key | | ECDSA SGK | ECDSA signature generation key | | EC Diffie-Hellman Private | EC Diffie-Hellman private key agreement key | | HMAC Key | Keyed hash key (160/224/256/384/512) | | RSA SGK | RSA signature generation key | | RSA KDK | RSA key decryption (private key transport) key | | Triple-DES EDK | Triple-DES (3-Key) encrypt / decrypt key | | Triple-DES CMAC | Triple-DES (3-Key) CMAC generate / verify key | The module does not output intermediate key generation values. Table 4.1b - Public Keys | Public Key Name | Description | |--------------------------|-----------------------------------------------| | DSA SVK | DSA signature verification key | | ECDSA SVK | ECDSA signature verification key | | EC Diffie-Hellman Public | EC Diffie-Hellman public key agreement key | | RSA SVK | RSA signature verification public key | | RSA KEK | RSA key encryption (public key transport) key | ####### For all CSPs and Public Keys: Storage: RAM, associated to entities by memory location. The Module stores RNG and DRBG state values for the lifetime of the RNG or DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of RNG and DRBG state values used for the Module\'s default key generation service. Generation: The Module implements SP 800-90A DRBG (Hash, HMAC, or CTR) services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry: All CSPs enter the Module\'s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output: The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Page 14 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy 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 (Cryptographic 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. For operation in the Approved mode, Module users (the calling applications) shall use entropy sources that contain at least 112 bits of entropy. To ensure full DRBG strength, the entropy sources must meet or exceed the security strengths shown in the table below. Table 5 - DRBG Entropy Requirements | DRBG Type | Underlying Algorithm | Minimum Seed Entropy | |------------------------|------------------------|------------------------| | Hash_DRBG or HMAC_DRBG | SHA-1 | 128 | | Hash_DRBG or HMAC_DRBG | SHA-224 | 192 | | Hash_DRBG or HMAC_DRBG | SHA-256 | 256 | | Hash_DRBG or HMAC_DRBG | SHA-384 | 256 | | Hash_DRBG or HMAC_DRBG | SHA-512 | 256 | | CTR_DRBG | AES-128 | 128 | | | AES-192 | 192 | | | AES-256 | 256 | This entropy is supplied by means of callback functions. Those functions must return an error if the requested entropy strength cannot be met. Page 15 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 5 Roles, Authentication, and Services The Module implements the required User and Cryptographic Officer roles and does not perform operator authentication. 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. - Cryptographic 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. All services are available in both the Approved mode and the non-Approved mode. In the Approved mode, these services are restricted to the algorithms listed in Tables 4a and 4b. In the non-Approved mode, the algorithms listed in Tables 4c and 4d may also be used. | 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 number generation | User, CO | Used for random number and symmetric key 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 security 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 any symmetric encryption key from Table 4.1a: AES EDK, AES CCM, AES GCM, Triple-DES EDK (passed in by the calling process). | | Symmetric digest | User, CO | Used to generate or verify data integrity with CMAC. Executes using AES CMAC, Triple-DES 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). | Page 16 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy Table 6 - Services and CSP Access | Key transport 3 (algorithms only) | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (the key is treated as payload data; this service does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | |-------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key agreement (algorithms only) | User, CO | Used to perform key agreement primitives on behalf of the calling process (this service does not establish keys into the module). Executes using EC Diffie-Hellman Private, EC Diffie-Hellman Public (passed in by the calling process). | | Key derivation | User, CO | Used to perform key derivation primitives as per SP800-135: TLS KDF and SSH KDF (this service does not establish keys into the module). | | 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 OpenSSL FIPS Object Module. Page 17 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 6 Self-Tests The Module performs the self-tests listed below on invocation of Initialize or Self-Test. Table 7a - 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 | | AES CMAC | KAT | CMAC generate and verify, 128, 192, 256 key lengths | | Triple-DES | KAT | Separate encrypt and decrypt, ECB mode, 3-Key | | Triple-DES CMAC | KAT | CMAC generate and verify, 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 with and without derivation function Hash_DRBG: SHA-256 HMAC_DRBG: SHA-256 | | ECDSA | PCT | Keygen, sign, verify using P-256 with SHA-512. | The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMAC-SHA-1 of the Module distribution file as tested by the CST 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() 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. 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy The Module also implements the following conditional tests: Table 7b - Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Health Tests as required by [SP800-90A] Section 11.3 | | DRBG | FIPS 140-2 continuous test (CRNGT) 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 | Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. Failure of conditional self-tests is handled in the same manner as failure of power-on self-tests. ##### 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. ##### 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. ##### 9 Operator Guidance User must ensure that the use of Triple-DES is compliant with IG A.13 SP 800-67rev1 Transition. User is responsible to enforce the limit of 2 20 64-bit data block encryptions with the same three-key Triple-DES key applies when keys are generated as part of one of the recognized IETF protocols and to enforce the limit of 2 16 64-bit data block encryptions when key is not generated as part of a recognized IETF protocol. Page 19 of 19': 1}, '__update__': {'SHA-1': 6, 'SHA-512': 3, 'AES-256': 2}, '__delete__': ['HMAC SHA-1', 'SHA-1 128', 'SHA-512 256', 'AES-128 128', 'AES-192 192', 'AES-256 256', 'platform #102, TS-Linux 2.4 on ARMv4', 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4', 'platform #96, FreeBSD 8.4 on x86 without AES-NI', 'platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG', 'platforms #90, #91', 'platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86', 'platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5', 'platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition', 'platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI', 'platforms #77, #78 iOS 6.0 with/without NEON']}}}} data.

  The computed heuristics were updated.

  • The policy_prunned_references property was updated, with the {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '77', '81', '86']} values added.
  • The policy_processed_references property was updated, with the {'directly_referencing': {'__add__': {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '77', '81', '86']}}, 'indirectly_referencing': {'__add__': {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '77', '81', '86']}}} data.
• 24.09.2026

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The keywords property was updated, with the {'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'HMAC SHA-1': 1, 'SHA-1 128': 1, 'SHA-512 256': 1, 'AES-128 128': 1, 'AES-192 192': 1, 'AES-256 256': 1, 'platform #102, TS-Linux 2.4 on ARMv4': 1, 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4': 1, 'platform #96, FreeBSD 8.4 on x86 without AES-NI': 1, 'platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG': 1, 'platforms #90, #91': 1, 'platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86': 1, 'platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5': 1, 'platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition': 1, 'platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI': 1, 'platforms #77, #78 iOS 6.0 with/without NEON': 1}, '__update__': {'SHA-1': 4, 'SHA-512': 2, 'AES-256': 1}, '__delete__': ['AES-128', 'AES-192', 'platform #102, TS-Linux 2.4 on ARMv4 | | 2014-11-25 | (2.0.9) Addition of new platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 | | 2014-01-04 | Addition of new platform #96, FreeBSD 8.4 on x86 without AES-NI | | 2014-07-30 | Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG | | 2014-07-28 | Changed processor names for platforms #90, #91 | | 2014-07-11 | Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86 | | 2014-06-12 | Temporarily remove misplaced platform, move Dual EC DRBG to the Non- Approved Table 4c | | 2014-05-29 | Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) | | 2014-05-12 | Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition | | 2013-11-08 | Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI | | 2013-11-01 | Added two platforms #77, #78 iOS 6.0 with/without NEON | | 2013-10-02 | Added six platforms (Linux 3.4 x86 virtualized under XenSource/VMware/Hyper- V, with/without AES-NI) Updated URL in Appendix A footnote | | 2013-08-29 | Added new sponsor acknowledgment | Page 4 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy | 2013-08-14 | Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms | |--------------|-----------------------------------------------------------------------------------------------------| | 2013-07-24 | Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 | | 2013-06-09 | Added QNX, iOS 6.1, eCos for revision 2.0.5 | | 2013-05-01 | Added OpenWRT 2.6 for revision 2.0.4 | | 2013-03-01 | Added VMware Horizon Mobile 1.3, Apple OS X 10.7, Apple iOS 5.0 | | 2013-02-23 | Added WinEC7 and Android 4.0 for revision 2.0.3 | | 2013-02-14 | Table 5: Removed references to non-existent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM | | 2013-01-28 | Added four platforms: Android 4.1 and Android 4.2 with and without NEON | | 2013-01-08 | Reworded section 8 | | 2013-01-03 | Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AES-NI. | | 2012-12-08 | Note EC DH Key Agreement and RSA Key Wrapping strength. | | 2012-10-10 | Added NetBSD 5.1 on PowerPC-e500, NetBSD 5.1 on Intel Xeon 5500 (x86-64) for revision 2.0.2 | | 2011-07-02 | Added DSP Media Framework, Linux 2.6/Freescale PowerPC-e500, Android 4.0 | | 2011-06-15 | Added iOS, WinCE 5, WinCE 6 OEs | Page 5 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy References | Reference | Full Specification Name | |---------------|---------------------------------------------------------------------------------------------------------| | [FIPS 140-2] | Security Requirements for Cryptographic modules, May 25, 2001 | | [FIPS 180-4] | 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-90A] | 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 6 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### Table of Contents | 1 | Introduction | |-----|----------------------------------------------------| | 2 | Tested Configurations | | 3 | Ports and Interfaces | | 4 | Modes of Operation and Cryptographic Functionality | | | 4.1 Critical Security Parameters and Public Keys | | 5 | Roles, Authentication, and Services | | 6 | Self-Tests | | 7 | Operational Environment | | 8 | Mitigation of other Attacks | | 9 | Operator Guidance | Page 7 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 1 Introduction This document is the non-proprietary security policy for the Arista EOS Crypto Module v1.0, hereafter referred to as the Module. The Module is a software library providing a C-language application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 140-2 as a software module, multi-chip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the OpenSSL API file. The Module performs no communications other than with the calling application (the process that invokes the Module services). The FIPS 140-2 security levels for the Module are as follows: Table 1 - Security Level of Security Requirements | Security Requirement | Security Level | |-------------------------------------------|------------------| | Cryptographic Module Specification | 1 | | Cryptographic Module Ports and Interfaces | 1 | | Roles, Services, and Authentication | 1 | | Finite State Model | 1 | | Physical Security | NA | | Operational Environment | 1 | | Cryptographic Key Management | 1 | | EMI/EMC | 1 | | Self-Tests | 1 | | Design Assurance | 1 | | Mitigation of Other Attacks | NA | The Module\'s software version for this validation is: v1.0. This is a fork of the OpenSSL FIPS Object Module version 2.0.10. Page 8 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy Arista Networks; Inc: FIPS 140-2 Security Policy Figure 1 - Module Block Diagram Page 9 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 2 Module Configurations The following configurations were operationally tested. Table 2a - Tested Configurations | # | Operational Environment | Processor | Optimizations (Target) | |-----|-----------------------------------------------------------------------|----------------------------|--------------------------| | 1 | EOS v4 on Arista 7150S-24 | AMD Athlon NEO X2 | None | | 2 | EOS v4 on Arista 7300 (DCS-7300-SUP supervisor, DCS-7308 chassis) | Intel Sandy Bridge EN | None | | 3 | EOS v4 on Arista 7500R (DCS-7500- SUP2 supervisor, DCS-7508 chassis ) | Intel Broadwell-DE | None | | 4 | EOS v4 on Arista 7050SX-72 | AMD G Series: eKabini | None | | 5 | EOS v4 on Arista 7060CX-32S | AMD G Series: Steppe Eagle | None | The following configurations have the same operating system and processors as the above configurations and are vendor affirmed to behave in the same manner. (As these have only been affirmed by the vendor, CMVP itself does not provide assurances to the correct operation of the module or the strength of generated keys.) Table 2b - Vendor Affirmed Configurations | # | Operational Environment | Processor | Optimizations (Target) | |-----|-------------------------------------------------------------------------------------------|----------------------------|--------------------------| | 1 | EOS v4 on Arista 7050QX, 7150 | AMD Athlon NEO X2 | None | | 2 | EOS v4 on Arista 7500R, 7320X, 7300X, 7300X3, 7250QX, 7260X, 7280CR, 7050SX, 7050TX | Intel Sandy Bridge EN | None | | 3 | EOS v4 on Arista 7500R, 7260X3, 7170, 7060X4 | Intel Broadwell-DE | None | | 4 | EOS v4 on Arista 7260, 7260X, 7050SX, 7050TX, 7050QX, 7160, 7010T | AMD G Series: eKabini | None | | 5 | EOS v4 on Arista 7280QR, 7280SR, 7280TR, 7060, 7050SX, 7050TX, 7160, 7060X, 7050X3, 7020R | AMD G Series: Steppe Eagle | None | Page 10 of 19 Arista Networks, Inc. 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 11 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 Approved mode and a non-Approved mode. The Approved mode is invoked by calling FIPS_mode_set() and using only Approved and allowed algorithms. Tables 4a and 4b list the Approved and non-approved but allowed algorithms, respectively. Table 4a - FIPS Approved Cryptographic Functions | Function | Algorithm | Options | Cert # | |-------------------------------------------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| | Random number generation | [SP 800-90] DRBG 1 Prediction resistance supported for all variations | Hash DRBG (SHA-1, all SHA-2 sizes) HMAC DRBG (SHA-1, all SHA-2 sizes) CTR DRBG (AES-128/192/256) | DRBG #1340 | | Encryption, Decryption and CMAC | [FIPS 197] AES [SP 800-38A] CBC, etc. [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM | 128/192/256 ECB, CBC, OFB, CFB-1, CFB-8, CFB-128, CTR; CCM; GCM; CMAC | AES #4280 | | Encryption, Decryption and CMAC | [SP 800-67] Triple-DES | 3-Key Triple-DES TECB, TCBC, TCFB-1, TCFB-8, TCFB-64, TOFB; CMAC | Triple- DES #2309 | | Message Digests | [FIPS 180-3] SHA-1/2 | SHA-1, SHA-2 (224, 256, 384, 512) | SHS #3516 | | Keyed Hash | [FIPS 198] HMAC | SHA-1, SHA-2 (224, 256, 384, 512) | HMAC #2816 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] RSA | GenKey9.31 (2048/3072) SigGen9.31, SigGenPKCS1.5, SigGenPSS (2048/3072 with all SHA2 sizes) SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072 with all SHA-2 sizes) | RSA #2301 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] Legacy RSA | SigVer9.31, SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA sizes) | RSA #2301 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (2048/3072) PQG Ver, Sig Ver (1024) | DSA #1141 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] ECDSA | Functions: PKG, PKV, SigGen, SigGen Component, SigVer Curves: P-256, P-384, P-521 Hashes: SHA-1*, SHA-224, SHA-256, SHA- 384, SHA-512 *SHA-1 signature generation is allowed for protocol usage only. | ECDSA #998 | | Key Derivation | [SP800-135] KDF, Application Specific 2 | TLS KDF (v1.0/v1.1 and v1.2) SSH KDF | CVL #1012 | 1 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP800-90A] and [SP800-57]. 2 Only the KDFs to these protocols have been tested by CAVP. Page 12 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy Table 4b - Non-FIPS Approved But Allowed Cryptographic Functions | Category | Algorithm | Description | |----------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC Diffie-Hellman | Non-compliant (untested to SP800-56A) Diffie-Hellman scheme using elliptic curve, supporting curves P-256, P-384, and P-512. This key agreement scheme provides between 128 and 256 bits of encryption strength; however, it is only a service provided for calling process use. It 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. It provides 112 or 128 bits of encryption strength. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. | | Hashing | MD5 within TLS | Component of TLS KDF | The Module implements the following NIST-specified algorithms, which are non-Approved, either from algorithm transitions (e.g., SP800-131A) or from not being tested: Table 4c - Untested and Transition-Disallowed Cryptographic Functions | Function | Algorithm | Options | |-------------------------------------------------|----------------------------------|----------------------------------------------------------| | Encryption and Decryption | AES-XTS 128/256 (Untested) | Encrypt, decrypt | | Digital Signature and Asymmetric Key Generation | RSA key size < 2048 (Disallowed) | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (<2048) | | | DSA key size <2048 (Disallowed) | PQG Gen, Key Pair Gen, Sig Gen (<2048) | | Key Encryption, Decryption | RSA key size < 2048 (Disallowed) | RSA key encryption/decryption (<2048) | The algorithms in Table 4c must not be used when operating in the FIPS mode of operation. The Module also implements the following algorithms, which are non-Approved: Table 4d - Other non-Approved Cryptographic Functions | Function | Algorithm | Function | Algorithm | |---------------------------|-----------------------------------|---------------------------|-------------| | Encryption and Decryption | AES/Triple-DES KW (non-compliant) | Encryption and Decryption | RC4 | | Encryption and Decryption | Blowfish | Encryption and Decryption | RC5 | | Encryption and Decryption | Camellia 128/192/256 | Encryption and Decryption | SEED | | Encryption and Decryption | CAST5 | Message Digests | MD4 | | Encryption and Decryption | DES | Message Digests | MD5 | | Encryption and Decryption | DES-X | Message Digests | RIPEMD-160 | | Encryption and Decryption | IDEA | Message Digests | Whirlpool | | Encryption and Decryption | RC2 | Keyed Hash | HMAC-MD5 | The algorithms in Table 4d are automatically disabled when in the FIPS mode of operation. 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 assurances are outside the scope of the Module, and are the responsibility of the calling process. Page 13 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ## 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. Table 4.1a - Critical Security Parameters | CSP Name | Description | |---------------------------|-----------------------------------------------------------------| | AES EDK | AES encrypt / decrypt key | | AES CMAC | AES CMAC generate / verify key | | AES CCM | AES encrypt / decrypt / generate / verify key for CCM | | AES GCM | AES encrypt / decrypt / generate / verify key for GCM | | DRBG Seed | Entropy input for Hash, HMAC, or CTR DRBG. | | Hash_DRBG CSPs | V (440/888 bits) and C (440/888 bits) | | HMAC_DRBG CSPs | V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits) | | CTR_DRBG CSPs | V (128 bits) and Key (AES 128/192/256) | | DSA SGK | DSA signature generation key | | ECDSA SGK | ECDSA signature generation key | | EC Diffie-Hellman Private | EC Diffie-Hellman private key agreement key | | HMAC Key | Keyed hash key (160/224/256/384/512) | | RSA SGK | RSA signature generation key | | RSA KDK | RSA key decryption (private key transport) key | | Triple-DES EDK | Triple-DES (3-Key) encrypt / decrypt key | | Triple-DES CMAC | Triple-DES (3-Key) CMAC generate / verify key | The module does not output intermediate key generation values. Table 4.1b - Public Keys | Public Key Name | Description | |--------------------------|-----------------------------------------------| | DSA SVK | DSA signature verification key | | ECDSA SVK | ECDSA signature verification key | | EC Diffie-Hellman Public | EC Diffie-Hellman public key agreement key | | RSA SVK | RSA signature verification public key | | RSA KEK | RSA key encryption (public key transport) key | ####### For all CSPs and Public Keys: Storage: RAM, associated to entities by memory location. The Module stores RNG and DRBG state values for the lifetime of the RNG or DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of RNG and DRBG state values used for the Module\'s default key generation service. Generation: The Module implements SP 800-90A DRBG (Hash, HMAC, or CTR) services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry: All CSPs enter the Module\'s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output: The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Page 14 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy 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 (Cryptographic 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. For operation in the Approved mode, Module users (the calling applications) shall use entropy sources that contain at least 112 bits of entropy. To ensure full DRBG strength, the entropy sources must meet or exceed the security strengths shown in the table below. Table 5 - DRBG Entropy Requirements | DRBG Type | Underlying Algorithm | Minimum Seed Entropy | |------------------------|------------------------|------------------------| | Hash_DRBG or HMAC_DRBG | SHA-1 | 128 | | Hash_DRBG or HMAC_DRBG | SHA-224 | 192 | | Hash_DRBG or HMAC_DRBG | SHA-256 | 256 | | Hash_DRBG or HMAC_DRBG | SHA-384 | 256 | | Hash_DRBG or HMAC_DRBG | SHA-512 | 256 | | CTR_DRBG | AES-128 | 128 | | | AES-192 | 192 | | | AES-256 | 256 | This entropy is supplied by means of callback functions. Those functions must return an error if the requested entropy strength cannot be met. Page 15 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 5 Roles, Authentication, and Services The Module implements the required User and Cryptographic Officer roles and does not perform operator authentication. 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. - Cryptographic 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. All services are available in both the Approved mode and the non-Approved mode. In the Approved mode, these services are restricted to the algorithms listed in Tables 4a and 4b. In the non-Approved mode, the algorithms listed in Tables 4c and 4d may also be used. | 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 number generation | User, CO | Used for random number and symmetric key 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 security 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 any symmetric encryption key from Table 4.1a: AES EDK, AES CCM, AES GCM, Triple-DES EDK (passed in by the calling process). | | Symmetric digest | User, CO | Used to generate or verify data integrity with CMAC. Executes using AES CMAC, Triple-DES 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). | Page 16 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy Table 6 - Services and CSP Access | Key transport 3 (algorithms only) | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (the key is treated as payload data; this service does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | |-------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key agreement (algorithms only) | User, CO | Used to perform key agreement primitives on behalf of the calling process (this service does not establish keys into the module). Executes using EC Diffie-Hellman Private, EC Diffie-Hellman Public (passed in by the calling process). | | Key derivation | User, CO | Used to perform key derivation primitives as per SP800-135: TLS KDF and SSH KDF (this service does not establish keys into the module). | | 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 OpenSSL FIPS Object Module. Page 17 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 6 Self-Tests The Module performs the self-tests listed below on invocation of Initialize or Self-Test. Table 7a - 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 | | AES CMAC | KAT | CMAC generate and verify, 128, 192, 256 key lengths | | Triple-DES | KAT | Separate encrypt and decrypt, ECB mode, 3-Key | | Triple-DES CMAC | KAT | CMAC generate and verify, 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 with and without derivation function Hash_DRBG: SHA-256 HMAC_DRBG: SHA-256 | | ECDSA | PCT | Keygen, sign, verify using P-256 with SHA-512. | The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMAC-SHA-1 of the Module distribution file as tested by the CST 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() 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. 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy The Module also implements the following conditional tests: Table 7b - Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Health Tests as required by [SP800-90A] Section 11.3 | | DRBG | FIPS 140-2 continuous test (CRNGT) 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 | Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. Failure of conditional self-tests is handled in the same manner as failure of power-on self-tests. ##### 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. ##### 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. ##### 9 Operator Guidance User must ensure that the use of Triple-DES is compliant with IG A.13 SP 800-67rev1 Transition. User is responsible to enforce the limit of 2 20 64-bit data block encryptions with the same three-key Triple-DES key applies when keys are generated as part of one of the recognized IETF protocols and to enforce the limit of 2 16 64-bit data block encryptions when key is not generated as part of a recognized IETF protocol. Page 19 of 19']}}}} data.
  • The br1_deviations property was set to 43.

  The computed heuristics were updated.

  • The policy_prunned_references property was updated, with the {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '77', '81', '86']} values discarded.
  • The policy_processed_references property was updated, with the {'directly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '77', '81', '86']}}, 'indirectly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '77', '81', '86']}}} data.
• 23.09.2026

  Changed

  The certificate data changed.

  Show diff

  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__': {'AES-128': 1, 'AES-192': 1, 'platform #102, TS-Linux 2.4 on ARMv4 | | 2014-11-25 | (2.0.9) Addition of new platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 | | 2014-01-04 | Addition of new platform #96, FreeBSD 8.4 on x86 without AES-NI | | 2014-07-30 | Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG | | 2014-07-28 | Changed processor names for platforms #90, #91 | | 2014-07-11 | Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86 | | 2014-06-12 | Temporarily remove misplaced platform, move Dual EC DRBG to the Non- Approved Table 4c | | 2014-05-29 | Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) | | 2014-05-12 | Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition | | 2013-11-08 | Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI | | 2013-11-01 | Added two platforms #77, #78 iOS 6.0 with/without NEON | | 2013-10-02 | Added six platforms (Linux 3.4 x86 virtualized under XenSource/VMware/Hyper- V, with/without AES-NI) Updated URL in Appendix A footnote | | 2013-08-29 | Added new sponsor acknowledgment | Page 4 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy | 2013-08-14 | Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms | |--------------|-----------------------------------------------------------------------------------------------------| | 2013-07-24 | Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 | | 2013-06-09 | Added QNX, iOS 6.1, eCos for revision 2.0.5 | | 2013-05-01 | Added OpenWRT 2.6 for revision 2.0.4 | | 2013-03-01 | Added VMware Horizon Mobile 1.3, Apple OS X 10.7, Apple iOS 5.0 | | 2013-02-23 | Added WinEC7 and Android 4.0 for revision 2.0.3 | | 2013-02-14 | Table 5: Removed references to non-existent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM | | 2013-01-28 | Added four platforms: Android 4.1 and Android 4.2 with and without NEON | | 2013-01-08 | Reworded section 8 | | 2013-01-03 | Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AES-NI. | | 2012-12-08 | Note EC DH Key Agreement and RSA Key Wrapping strength. | | 2012-10-10 | Added NetBSD 5.1 on PowerPC-e500, NetBSD 5.1 on Intel Xeon 5500 (x86-64) for revision 2.0.2 | | 2011-07-02 | Added DSP Media Framework, Linux 2.6/Freescale PowerPC-e500, Android 4.0 | | 2011-06-15 | Added iOS, WinCE 5, WinCE 6 OEs | Page 5 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy References | Reference | Full Specification Name | |---------------|---------------------------------------------------------------------------------------------------------| | [FIPS 140-2] | Security Requirements for Cryptographic modules, May 25, 2001 | | [FIPS 180-4] | 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-90A] | 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 6 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### Table of Contents | 1 | Introduction | |-----|----------------------------------------------------| | 2 | Tested Configurations | | 3 | Ports and Interfaces | | 4 | Modes of Operation and Cryptographic Functionality | | | 4.1 Critical Security Parameters and Public Keys | | 5 | Roles, Authentication, and Services | | 6 | Self-Tests | | 7 | Operational Environment | | 8 | Mitigation of other Attacks | | 9 | Operator Guidance | Page 7 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 1 Introduction This document is the non-proprietary security policy for the Arista EOS Crypto Module v1.0, hereafter referred to as the Module. The Module is a software library providing a C-language application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 140-2 as a software module, multi-chip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the OpenSSL API file. The Module performs no communications other than with the calling application (the process that invokes the Module services). The FIPS 140-2 security levels for the Module are as follows: Table 1 - Security Level of Security Requirements | Security Requirement | Security Level | |-------------------------------------------|------------------| | Cryptographic Module Specification | 1 | | Cryptographic Module Ports and Interfaces | 1 | | Roles, Services, and Authentication | 1 | | Finite State Model | 1 | | Physical Security | NA | | Operational Environment | 1 | | Cryptographic Key Management | 1 | | EMI/EMC | 1 | | Self-Tests | 1 | | Design Assurance | 1 | | Mitigation of Other Attacks | NA | The Module\'s software version for this validation is: v1.0. This is a fork of the OpenSSL FIPS Object Module version 2.0.10. Page 8 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy Arista Networks; Inc: FIPS 140-2 Security Policy Figure 1 - Module Block Diagram Page 9 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 2 Module Configurations The following configurations were operationally tested. Table 2a - Tested Configurations | # | Operational Environment | Processor | Optimizations (Target) | |-----|-----------------------------------------------------------------------|----------------------------|--------------------------| | 1 | EOS v4 on Arista 7150S-24 | AMD Athlon NEO X2 | None | | 2 | EOS v4 on Arista 7300 (DCS-7300-SUP supervisor, DCS-7308 chassis) | Intel Sandy Bridge EN | None | | 3 | EOS v4 on Arista 7500R (DCS-7500- SUP2 supervisor, DCS-7508 chassis ) | Intel Broadwell-DE | None | | 4 | EOS v4 on Arista 7050SX-72 | AMD G Series: eKabini | None | | 5 | EOS v4 on Arista 7060CX-32S | AMD G Series: Steppe Eagle | None | The following configurations have the same operating system and processors as the above configurations and are vendor affirmed to behave in the same manner. (As these have only been affirmed by the vendor, CMVP itself does not provide assurances to the correct operation of the module or the strength of generated keys.) Table 2b - Vendor Affirmed Configurations | # | Operational Environment | Processor | Optimizations (Target) | |-----|-------------------------------------------------------------------------------------------|----------------------------|--------------------------| | 1 | EOS v4 on Arista 7050QX, 7150 | AMD Athlon NEO X2 | None | | 2 | EOS v4 on Arista 7500R, 7320X, 7300X, 7300X3, 7250QX, 7260X, 7280CR, 7050SX, 7050TX | Intel Sandy Bridge EN | None | | 3 | EOS v4 on Arista 7500R, 7260X3, 7170, 7060X4 | Intel Broadwell-DE | None | | 4 | EOS v4 on Arista 7260, 7260X, 7050SX, 7050TX, 7050QX, 7160, 7010T | AMD G Series: eKabini | None | | 5 | EOS v4 on Arista 7280QR, 7280SR, 7280TR, 7060, 7050SX, 7050TX, 7160, 7060X, 7050X3, 7020R | AMD G Series: Steppe Eagle | None | Page 10 of 19 Arista Networks, Inc. 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 11 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 Approved mode and a non-Approved mode. The Approved mode is invoked by calling FIPS_mode_set() and using only Approved and allowed algorithms. Tables 4a and 4b list the Approved and non-approved but allowed algorithms, respectively. Table 4a - FIPS Approved Cryptographic Functions | Function | Algorithm | Options | Cert # | |-------------------------------------------------|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------| | Random number generation | [SP 800-90] DRBG 1 Prediction resistance supported for all variations | Hash DRBG (SHA-1, all SHA-2 sizes) HMAC DRBG (SHA-1, all SHA-2 sizes) CTR DRBG (AES-128/192/256) | DRBG #1340 | | Encryption, Decryption and CMAC | [FIPS 197] AES [SP 800-38A] CBC, etc. [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM | 128/192/256 ECB, CBC, OFB, CFB-1, CFB-8, CFB-128, CTR; CCM; GCM; CMAC | AES #4280 | | Encryption, Decryption and CMAC | [SP 800-67] Triple-DES | 3-Key Triple-DES TECB, TCBC, TCFB-1, TCFB-8, TCFB-64, TOFB; CMAC | Triple- DES #2309 | | Message Digests | [FIPS 180-3] SHA-1/2 | SHA-1, SHA-2 (224, 256, 384, 512) | SHS #3516 | | Keyed Hash | [FIPS 198] HMAC | SHA-1, SHA-2 (224, 256, 384, 512) | HMAC #2816 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] RSA | GenKey9.31 (2048/3072) SigGen9.31, SigGenPKCS1.5, SigGenPSS (2048/3072 with all SHA2 sizes) SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072 with all SHA-2 sizes) | RSA #2301 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-2] Legacy RSA | SigVer9.31, SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA sizes) | RSA #2301 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] DSA | PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (2048/3072) PQG Ver, Sig Ver (1024) | DSA #1141 | | Digital Signature and Asymmetric Key Generation | [FIPS 186-4] ECDSA | Functions: PKG, PKV, SigGen, SigGen Component, SigVer Curves: P-256, P-384, P-521 Hashes: SHA-1*, SHA-224, SHA-256, SHA- 384, SHA-512 *SHA-1 signature generation is allowed for protocol usage only. | ECDSA #998 | | Key Derivation | [SP800-135] KDF, Application Specific 2 | TLS KDF (v1.0/v1.1 and v1.2) SSH KDF | CVL #1012 | 1 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP800-90A] and [SP800-57]. 2 Only the KDFs to these protocols have been tested by CAVP. Page 12 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy Table 4b - Non-FIPS Approved But Allowed Cryptographic Functions | Category | Algorithm | Description | |----------------------------|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key Agreement | EC Diffie-Hellman | Non-compliant (untested to SP800-56A) Diffie-Hellman scheme using elliptic curve, supporting curves P-256, P-384, and P-512. This key agreement scheme provides between 128 and 256 bits of encryption strength; however, it is only a service provided for calling process use. It 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. It provides 112 or 128 bits of encryption strength. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. | | Hashing | MD5 within TLS | Component of TLS KDF | The Module implements the following NIST-specified algorithms, which are non-Approved, either from algorithm transitions (e.g., SP800-131A) or from not being tested: Table 4c - Untested and Transition-Disallowed Cryptographic Functions | Function | Algorithm | Options | |-------------------------------------------------|----------------------------------|----------------------------------------------------------| | Encryption and Decryption | AES-XTS 128/256 (Untested) | Encrypt, decrypt | | Digital Signature and Asymmetric Key Generation | RSA key size < 2048 (Disallowed) | GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (<2048) | | | DSA key size <2048 (Disallowed) | PQG Gen, Key Pair Gen, Sig Gen (<2048) | | Key Encryption, Decryption | RSA key size < 2048 (Disallowed) | RSA key encryption/decryption (<2048) | The algorithms in Table 4c must not be used when operating in the FIPS mode of operation. The Module also implements the following algorithms, which are non-Approved: Table 4d - Other non-Approved Cryptographic Functions | Function | Algorithm | Function | Algorithm | |---------------------------|-----------------------------------|---------------------------|-------------| | Encryption and Decryption | AES/Triple-DES KW (non-compliant) | Encryption and Decryption | RC4 | | Encryption and Decryption | Blowfish | Encryption and Decryption | RC5 | | Encryption and Decryption | Camellia 128/192/256 | Encryption and Decryption | SEED | | Encryption and Decryption | CAST5 | Message Digests | MD4 | | Encryption and Decryption | DES | Message Digests | MD5 | | Encryption and Decryption | DES-X | Message Digests | RIPEMD-160 | | Encryption and Decryption | IDEA | Message Digests | Whirlpool | | Encryption and Decryption | RC2 | Keyed Hash | HMAC-MD5 | The algorithms in Table 4d are automatically disabled when in the FIPS mode of operation. 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 assurances are outside the scope of the Module, and are the responsibility of the calling process. Page 13 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ## 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. Table 4.1a - Critical Security Parameters | CSP Name | Description | |---------------------------|-----------------------------------------------------------------| | AES EDK | AES encrypt / decrypt key | | AES CMAC | AES CMAC generate / verify key | | AES CCM | AES encrypt / decrypt / generate / verify key for CCM | | AES GCM | AES encrypt / decrypt / generate / verify key for GCM | | DRBG Seed | Entropy input for Hash, HMAC, or CTR DRBG. | | Hash_DRBG CSPs | V (440/888 bits) and C (440/888 bits) | | HMAC_DRBG CSPs | V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits) | | CTR_DRBG CSPs | V (128 bits) and Key (AES 128/192/256) | | DSA SGK | DSA signature generation key | | ECDSA SGK | ECDSA signature generation key | | EC Diffie-Hellman Private | EC Diffie-Hellman private key agreement key | | HMAC Key | Keyed hash key (160/224/256/384/512) | | RSA SGK | RSA signature generation key | | RSA KDK | RSA key decryption (private key transport) key | | Triple-DES EDK | Triple-DES (3-Key) encrypt / decrypt key | | Triple-DES CMAC | Triple-DES (3-Key) CMAC generate / verify key | The module does not output intermediate key generation values. Table 4.1b - Public Keys | Public Key Name | Description | |--------------------------|-----------------------------------------------| | DSA SVK | DSA signature verification key | | ECDSA SVK | ECDSA signature verification key | | EC Diffie-Hellman Public | EC Diffie-Hellman public key agreement key | | RSA SVK | RSA signature verification public key | | RSA KEK | RSA key encryption (public key transport) key | ####### For all CSPs and Public Keys: Storage: RAM, associated to entities by memory location. The Module stores RNG and DRBG state values for the lifetime of the RNG or DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of RNG and DRBG state values used for the Module\'s default key generation service. Generation: The Module implements SP 800-90A DRBG (Hash, HMAC, or CTR) services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry: All CSPs enter the Module\'s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output: The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Page 14 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy 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 (Cryptographic 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. For operation in the Approved mode, Module users (the calling applications) shall use entropy sources that contain at least 112 bits of entropy. To ensure full DRBG strength, the entropy sources must meet or exceed the security strengths shown in the table below. Table 5 - DRBG Entropy Requirements | DRBG Type | Underlying Algorithm | Minimum Seed Entropy | |------------------------|------------------------|------------------------| | Hash_DRBG or HMAC_DRBG | SHA-1 | 128 | | Hash_DRBG or HMAC_DRBG | SHA-224 | 192 | | Hash_DRBG or HMAC_DRBG | SHA-256 | 256 | | Hash_DRBG or HMAC_DRBG | SHA-384 | 256 | | Hash_DRBG or HMAC_DRBG | SHA-512 | 256 | | CTR_DRBG | AES-128 | 128 | | | AES-192 | 192 | | | AES-256 | 256 | This entropy is supplied by means of callback functions. Those functions must return an error if the requested entropy strength cannot be met. Page 15 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 5 Roles, Authentication, and Services The Module implements the required User and Cryptographic Officer roles and does not perform operator authentication. 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. - Cryptographic 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. All services are available in both the Approved mode and the non-Approved mode. In the Approved mode, these services are restricted to the algorithms listed in Tables 4a and 4b. In the non-Approved mode, the algorithms listed in Tables 4c and 4d may also be used. | 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 number generation | User, CO | Used for random number and symmetric key 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 security 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 any symmetric encryption key from Table 4.1a: AES EDK, AES CCM, AES GCM, Triple-DES EDK (passed in by the calling process). | | Symmetric digest | User, CO | Used to generate or verify data integrity with CMAC. Executes using AES CMAC, Triple-DES 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). | Page 16 of 19 ####### Arista Networks, Inc. FIPS 140-2 Security Policy Table 6 - Services and CSP Access | Key transport 3 (algorithms only) | User, CO | Used to encrypt or decrypt a key value on behalf of the calling process (the key is treated as payload data; this service does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). | |-------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Key agreement (algorithms only) | User, CO | Used to perform key agreement primitives on behalf of the calling process (this service does not establish keys into the module). Executes using EC Diffie-Hellman Private, EC Diffie-Hellman Public (passed in by the calling process). | | Key derivation | User, CO | Used to perform key derivation primitives as per SP800-135: TLS KDF and SSH KDF (this service does not establish keys into the module). | | 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 OpenSSL FIPS Object Module. Page 17 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy ##### 6 Self-Tests The Module performs the self-tests listed below on invocation of Initialize or Self-Test. Table 7a - 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 | | AES CMAC | KAT | CMAC generate and verify, 128, 192, 256 key lengths | | Triple-DES | KAT | Separate encrypt and decrypt, ECB mode, 3-Key | | Triple-DES CMAC | KAT | CMAC generate and verify, 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 with and without derivation function Hash_DRBG: SHA-256 HMAC_DRBG: SHA-256 | | ECDSA | PCT | Keygen, sign, verify using P-256 with SHA-512. | The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMAC-SHA-1 of the Module distribution file as tested by the CST 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() 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. 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Page 18 of 19 Arista Networks, Inc. FIPS 140-2 Security Policy The Module also implements the following conditional tests: Table 7b - Conditional Tests | Algorithm | Test | |-------------|------------------------------------------------------------| | DRBG | Health Tests as required by [SP800-90A] Section 11.3 | | DRBG | FIPS 140-2 continuous test (CRNGT) 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 | Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. Failure of conditional self-tests is handled in the same manner as failure of power-on self-tests. ##### 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. ##### 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. ##### 9 Operator Guidance User must ensure that the use of Triple-DES is compliant with IG A.13 SP 800-67rev1 Transition. User is responsible to enforce the limit of 2 20 64-bit data block encryptions with the same three-key Triple-DES key applies when keys are generated as part of one of the recognized IETF protocols and to enforce the limit of 2 16 64-bit data block encryptions when key is not generated as part of a recognized IETF protocol. Page 19 of 19': 1}, '__update__': {'SHA-1': 6, 'SHA-512': 3, 'AES-256': 2}, '__delete__': ['HMAC SHA-1', 'SHA-1 128', 'SHA-512 256', 'AES-128 128', 'AES-192 192', 'AES-256 256', 'platform #102, TS-Linux 2.4 on ARMv4', 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4', 'platform #96, FreeBSD 8.4 on x86 without AES-NI', 'platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG', 'platforms #90, #91', 'platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86', 'platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5', 'platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition', 'platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI', 'platforms #77, #78 iOS 6.0 with/without NEON']}}}} data.

  The computed heuristics were updated.

  • The policy_prunned_references property was updated, with the {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '77', '81', '86']} values added.
  • The policy_processed_references property was updated, with the {'directly_referencing': {'__add__': {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '81', '77', '86']}}, 'indirectly_referencing': {'__add__': {'_type': 'Set', 'elements': ['94', '79', '88', '97', '96', '90', '81', '77', '86']}}} data.
• 21.09.2026

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The following values were inserted: {'module_algorithms': {'_type': 'Set', 'elements': ['DRBG#1340', 'DSA#1141', 'CVL#1012', 'AES#4280', 'HMAC#2816', 'Triple-DES#2309', 'RSA#2301', 'SHS#3516', 'ECDSA#998']}, 'policy_algorithms': {'_type': 'Set', 'elements': ['#1012', '#4280', '#1141', '#3516', '#998', '#2816', '#1340', '#2301', '#2309']}}.
  • The keywords property was updated, with the {'fips_cert_id': {'__update__': {'Cert': {'__delete__': ['#100', '#101']}}}, 'fips_certlike': {'__update__': {'Certlike': {'__insert__': {'AES-192 192': 1, 'DRBG 1': 1, 'platform #102, TS-Linux 2.4 on ARMv4': 1, 'platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4': 1, 'platform #96, FreeBSD 8.4 on x86 without AES-NI': 1, 'platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG': 1, 'platforms #90, #91': 1, 'platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2 on x86': 1, 'platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5': 1, 'platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition': 1, 'platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI': 1, 'platforms #77, #78 iOS 6.0 with/without NEON': 1}, '__update__': {'SHA-224': 2}, '__delete__': ['DRBG1', 'platform #102, TS-Linux 2.4 on ARMv4 2014-11-25 (2.0.9) Addition of new platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64-bit on ARMv8 2014-01-04 Addition of new platform #96, FreeBSD 8.4 on x86 without AES-NI 2014-07-30 Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG 2014-07-28 Changed processor names for platforms #90, #91 2014-07-11 Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2on x86 2014-06-12 Temporarily remove misplaced platform, move Dual EC DRBG to the Non- Approved Table 4c 2014-05-29 Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) 2014-05-12 Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition 2013-11-08 Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI 2013-11-01 Added two platforms #77, #78 iOS 6.0 with/without NEON 2013-10-02 Added six platforms (Linux 3.4 x86 virtualized under XenSource/VMware/Hyper- V, with/without AES-NI) Updated URL in Appendix A footnote 2013-08-29 Added new sponsor acknowledgment Arista Networks, Inc. FIPS 140-2 Security Policy Page 5 of 19 2013-08-14 Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms 2013-07-24 Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 2013-06-09 Added QNX, iOS 6.1, eCos for revision 2.0.5 2013-05-01 Added OpenWRT 2.6 for revision 2.0.4 2013-03-01 Added VMware Horizon Mobile 1.3, Apple OS X 10.7, Apple iOS 5.0 2013-02-23 Added WinEC7 and Android 4.0 for revision 2.0.3 2013-02-14 Table 5: Removed references to non-existent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM 2013-01-28 Added four platforms: Android 4.1 and Android 4.2 with and without NEON 2013-01-08 Reworded section 8 2013-01-03 Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AES-NI. 2012-12-08 Note EC DH Key Agreement and RSA Key Wrapping strength. 2012-10-10 Added NetBSD 5.1 on PowerPC-e500, NetBSD 5.1 on Intel Xeon 5500 (x86-64) for revision 2.0.2 2011-07-02 Added DSP Media Framework, Linux 2.6/Freescale PowerPC-e500, Android 4.0 2011-06-15 Added iOS, WinCE 5, WinCE 6 OEs Arista Networks, Inc. FIPS 140-2 Security Policy Page 6 of 19 References Reference Full Specification Name [FIPS 140-2] Security Requirements for Cryptographic modules, May 25, 2001 [FIPS 180-4] 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-90A] 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 Arista Networks, Inc. FIPS 140-2 Security Policy Page 7 of 19 Table of Contents 1 Introduction 2 Tested Configurations 3 Ports and Interfaces 4 Modes of Operation and Cryptographic Functionality 4.1 Critical Security Parameters and Public Keys 5 Roles, Authentication, and Services 6 Self-Tests 7 Operational Environment 8 Mitigation of other Attacks 9 Operator Guidance Arista Networks, Inc. FIPS 140-2 Security Policy Page 8 of 19 1 Introduction This document is the non-proprietary security policy for the Arista EOS Crypto Module v1.0, hereafter referred to as the Module. The Module is a software library providing a C-language application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 140-2 as a software module, multi-chip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the OpenSSL API file. The Module performs no communications other than with the calling application (the process that invokes the Module services). 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 1 Finite State Model 1 Physical Security NA Operational Environment 1 Cryptographic Key Management 1 EMI/EMC 1 Self-Tests 1 Design Assurance 1 Mitigation of Other Attacks NA Table 1 – Security Level of Security Requirements The Module’s software version for this validation is: v1.0. This is a fork of the OpenSSL FIPS Object Module version 2.0.10. Arista Networks, Inc. FIPS 140-2 Security Policy Page 9 of 19 Figure 1 - Module Block Diagram Arista Networks, Inc. FIPS 140-2 Security Policy Page 10 of 19 2 Module Configurations The following configurations were operationally tested. # Operational Environment Processor Optimizations (Target) 1 EOS v4 on Arista 7150S-24 AMD Athlon NEO X2 None 2 EOS v4 on Arista 7300 (DCS-7300-SUP supervisor, DCS-7308 chassis) Intel Sandy Bridge EN None 3 EOS v4 on Arista 7500R (DCS-7500- SUP2 supervisor, DCS-7508 chassis ) Intel Broadwell-DE None 4 EOS v4 on Arista 7050SX-72 AMD G Series: eKabini None 5 EOS v4 on Arista 7060CX-32S AMD G Series: Steppe Eagle None Table 2a - Tested Configurations The following configurations have the same operating system and processors as the above configurations and are vendor affirmed to behave in the same manner. (As these have only been affirmed by the vendor, CMVP itself does not provide assurances to the correct operation of the module or the strength of generated keys.) # Operational Environment Processor Optimizations (Target) 1 EOS v4 on Arista 7050QX, 7150 AMD Athlon NEO X2 None 2 EOS v4 on Arista 7500R, 7320X, 7300X, 7300X3, 7250QX, 7260X, 7280CR, 7050SX, 7050TX Intel Sandy Bridge EN None 3 EOS v4 on Arista 7500R, 7260X3, 7170, 7060X4 Intel Broadwell-DE None 4 EOS v4 on Arista 7260, 7260X, 7050SX, 7050TX, 7050QX, 7160, 7010T AMD G Series: eKabini None 5 EOS v4 on Arista 7280QR, 7280SR, 7280TR, 7060, 7050SX, 7050TX, 7160, 7060X, 7050X3, 7020R AMD G Series: Steppe Eagle None Table 2b – Vendor Affirmed Configurations Arista Networks, Inc. FIPS 140-2 Security Policy Page 11 of 19 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). Arista Networks, Inc. FIPS 140-2 Security Policy Page 12 of 19 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 Approved mode and a non-Approved mode. The Approved mode is invoked by calling FIPS_mode_set() and using only Approved and allowed algorithms. Tables 4a and 4b list the Approved and non-approved but allowed algorithms, respectively. Function Algorithm Options Cert # Random number generation [SP 800-90] DRBG1 Prediction resistance supported for all variations Hash DRBG (SHA-1, all SHA-2 sizes) HMAC DRBG (SHA-1, all SHA-2 sizes) CTR DRBG (AES-128/192/256) DRBG #1340 Encryption, Decryption and CMAC [FIPS 197] AES [SP 800-38A] CBC, etc. [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM 128/192/256 ECB, CBC, OFB, CFB-1, CFB-8, CFB-128, CTR; CCM; GCM; CMAC AES #4280 [SP 800-67] Triple-DES 3-Key Triple-DES TECB, TCBC, TCFB-1, TCFB-8, TCFB-64, TOFB; CMAC Triple- DES #2309 Message Digests [FIPS 180-3] SHA-1/2 SHA-1, SHA-2 (224, 256, 384, 512) SHS #3516 Keyed Hash [FIPS 198] HMAC SHA-1, SHA-2 (224, 256, 384, 512) HMAC #2816 Digital Signature and Asymmetric Key Generation [FIPS 186-4] RSA GenKey9.31 (2048/3072) SigGen9.31, SigGenPKCS1.5, SigGenPSS (2048/3072 with all SHA2 sizes) SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072 with all SHA-2 sizes) RSA #2301 [FIPS 186-2] Legacy RSA SigVer9.31, SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA sizes) RSA #2301 [FIPS 186-4] DSA PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (2048/3072) PQG Ver, Sig Ver (1024) DSA #1141 [FIPS 186-4] ECDSA Functions: PKG, PKV, SigGen, SigGen Component, SigVer Curves: P-256, P-384, P-521 Hashes: SHA-1*, SHA-224, SHA-256, SHA- 384, SHA-512 ECDSA #998 *SHA-1 signature generation is allowed for protocol usage only. Key Derivation [SP800-135] KDF, Application Specific2 TLS KDF (v1.0/v1.1 and v1.2) SSH KDF CVL #1012 Table 4a – FIPS Approved Cryptographic Functions 1 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP800-90A] and [SP800-57]. 2 Only the KDFs to these protocols have been tested by CAVP. Arista Networks, Inc. FIPS 140-2 Security Policy Page 13 of 19 Category Algorithm Description Key Agreement EC Diffie-Hellman Non-compliant (untested to SP800-56A) Diffie-Hellman scheme using elliptic curve, supporting curves P-256, P-384, and P-512. This key agreement scheme provides between 128 and 256 bits of encryption strength; however, it is only a service provided forcalling process use. It 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. It provides 112 or 128 bits of encryption strength. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. Hashing MD5 within TLS Component of TLS KDF Table 4b – Non-FIPS Approved But Allowed CryptographicFunctions The Module implements the following NIST-specified algorithms, which are non-Approved, either from algorithm transitions (e.g., SP800-131A) or from not being tested: Function Algorithm Options Encryption and Decryption AES-XTS 128/256 (Untested) Encrypt, decrypt Digital Signature and Asymmetric Key Generation RSA key size < 2048 (Disallowed) GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (<2048) DSA key size <2048 (Disallowed) PQG Gen, Key Pair Gen, Sig Gen (<2048) Key Encryption, Decryption RSA key size < 2048 (Disallowed) RSA key encryption/decryption (<2048) Table 4c – Untested and Transition-Disallowed Cryptographic Functions The algorithms in Table 4c must not be used when operating in the FIPS mode of operation. The Module also implements the following algorithms, which are non-Approved: Function Algorithm Function Algorithm Encryption and Decryption AES/Triple-DES KW (non-compliant) Encryption and Decryption RC4 Blowfish RC5 Camellia 128/192/256 SEED CAST5 Message Digests MD4 DES MD5 DES-X RIPEMD-160 IDEA Whirlpool RC2 Keyed Hash HMAC-MD5 Table 4d – Other non-Approved Cryptographic Functions The algorithms in Table 4d are automatically disabled when in the FIPS mode of operation. 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 assurances are outside the scope of the Module, and are the responsibility of the calling process. Arista Networks, Inc. FIPS 140-2 Security Policy Page 14 of 19 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 AES EDK AES encrypt / decrypt key AES CMAC AES CMAC generate / verify key AES CCM AES encrypt / decrypt / generate / verify key for CCM AES GCM AES encrypt / decrypt / generate / verify key for GCM DRBG Seed Entropy input for Hash, HMAC, or CTR DRBG. Hash_DRBG CSPs V (440/888 bits) and C (440/888 bits) HMAC_DRBG CSPs V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits) CTR_DRBG CSPs V (128 bits) and Key (AES 128/192/256) DSA SGK DSA signature generation key ECDSA SGK ECDSA signature generation key EC Diffie-Hellman Private EC Diffie-Hellman private key agreement key HMAC Key Keyed hash key (160/224/256/384/512) RSA SGK RSA signature generation key RSA KDK RSA key decryption (private key transport) key Triple-DES EDK Triple-DES (3-Key) encrypt / decrypt key Triple-DES CMAC Triple-DES (3-Key) CMAC generate / verify key Table 4.1a – Critical Security Parameters The module does not output intermediate key generation values. Public Key Name Description DSA SVK DSA signature verification key ECDSA SVK ECDSA signature verification key EC Diffie-Hellman Public EC Diffie-Hellman public key agreement key RSA SVK RSA signature verification public key RSA KEK RSA key encryption (public key transport) key Table 4.1b – Public Keys For all CSPs and Public Keys: Storage: RAM, associated to entities by memory location. The Module stores RNG and DRBG state values for the lifetime of the RNG or DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of RNG and DRBG state values used for the Module’s default key generation service. Generation: The Module implements SP 800-90A DRBG (Hash, HMAC, or CTR) services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry: All CSPs enter the Module’s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output: The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Arista Networks, Inc. FIPS 140-2 Security Policy Page 15 of 19 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 (Cryptographic 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. For operation in the Approved mode, Module users (the calling applications) shall use entropy sources that contain at least 112 bits of entropy. To ensure full DRBG strength, the entropy sources must meet or exceed the security strengths shown in the table below. DRBG Type Underlying Algorithm Minimum Seed Entropy Hash_DRBG or HMAC_DRBG SHA-1 128 SHA-224 192 SHA-256 256 SHA-384 256 SHA-512 256 CTR_DRBG AES-128 128 AES-192 192 AES-256 256 Table 5 – DRBG Entropy Requirements This entropy is supplied by means of callback functions. Those functions must return an error if the requested entropy strength cannot be met. Arista Networks, Inc. FIPS 140-2 Security Policy Page 16 of 19 5 Roles, Authentication, and Services The Module implements the required User and Cryptographic Officer roles and does not perform operator authentication. 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. Cryptographic 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. All services are available in both the Approved mode and the non-Approved mode. In the Approved mode, these services are restricted to the algorithms listed in Tables 4a and 4b. In the non-Approved mode, the algorithms listed in Tables 4c and 4d may also be used. 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 number generation User, CO Used for random number and symmetric key 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 security 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 any symmetric encryption key from Table 4.1a: AES EDK, AES CCM, AES GCM, Triple-DES EDK (passed in by the calling process). Symmetric digest User, CO Used to generate or verify data integrity with CMAC. Executes using AES CMAC, Triple-DES 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). Arista Networks, Inc. FIPS 140-2 Security Policy Page 17 of 19 Key transport3 (algorithms only) User, CO Used to encrypt or decrypt a key value on behalf of the calling process (the key is treated as payload data; this service does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). Key agreement (algorithms only) User, CO Used to perform key agreement primitives on behalf of the calling process (this service does not establish keys into the module). Executes using EC Diffie-Hellman Private, EC Diffie-Hellman Public (passed in by the calling process). Key derivation User, CO Used to perform key derivation primitives as per SP800-135: TLS KDF and SSH KDF (this service does not establish keys into the module). 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 6 - 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 OpenSSL FIPS Object Module. Arista Networks, Inc. FIPS 140-2 Security Policy Page 18 of 19 6 Self-Tests 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 AES CMAC KAT CMAC generate and verify, 128, 192, 256 key lengths Triple-DES KAT Separate encrypt and decrypt, ECB mode, 3-Key Triple-DES CMAC KAT CMAC generate and verify, 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 with and without derivation function Hash_DRBG: SHA-256 HMAC_DRBG: SHA-256 ECDSA PCT Keygen, sign, verify using P-256 with SHA-512. Table 7a - Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency test) The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMAC-SHA-1 of the Module distribution file as tested by the CST 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() 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. 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Arista Networks, Inc. FIPS 140-2 Security Policy Page 19 of 19 The Module also implements the following conditional tests: Algorithm Test DRBG Health Tests as required by [SP800-90A] Section 11.3 DRBG FIPS 140-2 continuous test (CRNGT) 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 7b - Conditional Tests Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. Failure of conditional self-tests is handled in the same manner as failure of power-on self-tests. 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. 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. 9 Operator Guidance User must ensure that the use of Triple-DES is compliant with IG A.13 SP 800-67rev1 Transition. User is responsible to enforce the limit of 220 64-bit data block encryptions with the same three-key Triple-DES key applies when keys are generated as part of one of the recognized IETF protocols and to enforce the limit of 216 64-bit data block encryptions when key is not generated as part of a recognized IETF protocol']}}}, 'symmetric_crypto': {'__update__': {'constructions': {'__update__': {'MAC': {'__update__': {'CMAC': 17}}}}}}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 23}}}}, 'crypto_library': {'__update__': {'OpenSSL': {'__update__': {'OpenSSL': 8}}}}, 'standard_id': {'__update__': {'FIPS': {'__update__': {'FIPS 140-2': 28}}}}} data.

  The computed heuristics were updated.

  • The algorithms property was updated, with the {'_type': 'Set', 'elements': ['#1012', '#4280', '#1141', '#3516', '#998', '#2816', '#1340', '#2301', '#2309']} values added.
  • The policy_prunned_references property was updated, with the {'_type': 'Set', 'elements': ['94', '79', '88', '97', '101', '96', '90', '81', '77', '100', '86']} values discarded.
  • The policy_processed_references property was updated, with the {'directly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '97', '101', '96', '90', '81', '77', '100', '86']}}, 'indirectly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['94', '79', '88', '97', '101', '96', '90', '81', '77', '100', '86']}}} data.

  The state was updated.

  • The policy property was updated, with the {'txt_hash': '9c867c39f80aa3895487cdcc48a502faa432010ac24d005ae5efde8a96ae7487', 'json_hash': 'ad04f6c82ec9890c9cc623614383c235f54f38f6ead167c07733b6c1f4c2dab5'} data.
• 15.12.2025

  Changed

  The certificate data changed.

  Show diff

  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

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web extraction data was updated.

  • The validation_history property was updated.
• 09.02.2023

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The cert_id was updated.

  • The new value is 2909.

  The web extraction data was updated.

  • The following values were inserted: {'validation_history': [{'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2017-05-15', 'validation_type': 'Initial', 'lab': 'UL VERIFICATION SERVICES INC'}, {'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2019-01-28', 'validation_type': 'Update', 'lab': 'UL VERIFICATION SERVICES INC'}, {'_type': 'sec_certs.sample.fips.FIPSCertificate.ValidationHistoryEntry', 'date': '2020-07-10', 'validation_type': 'Update', 'lab': 'CYGNACOM SOLUTIONS INC'}], 'vendor_url': 'http://www.arista.com', 'certificate_pdf_url': 'https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/certificates/FIPS140ConsolidatedCertMay2017.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 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': 509022, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 19, '/Title': 'Microsoft Word - 1g - Arista_SP_140sp2909 V1.3_1_8_2019.docx', '/Author': 'lgarcia', '/Creator': 'Microsoft® Word 2013', '/CreationDate': "D:20200623151917-04'00'", '/ModDate': "D:20200623151917-04'00'", '/Producer': 'Microsoft® Word 2013', 'pdf_hyperlinks': {'_type': 'Set', 'elements': ['http://www.openssl.org/', 'http://www.drh-consultancy.co.uk/', 'http://www.cryptsoft.com/', 'mailto:[email protected]', 'mailto:[email protected]', 'mailto:[email protected]', 'mailto:[email protected]', 'http://www.infogard.com/', 'mailto:[email protected]', 'mailto:[email protected]', 'mailto:[email protected]', 'mailto:[email protected]']}}}.
  • 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': ['99', '98', '93', '86', '105', '80', '84', '97', '77', '81', '100', '87', '78', '91', '96', '85', '101', '89', '92', '94', '79', '83', '88', '95', '90', '82']}, 'module_prunned_references': {'_type': 'Set', 'elements': []}, 'policy_processed_references': {'_type': 'sec_certs.sample.certificate.References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': {'_type': 'Set', 'elements': ['99', '98', '93', '86', '105', '80', '84', '97', '77', '81', '100', '87', '78', '91', '96', '85', '101', '89', '92', '94', '79', '83', '88', '95', '90', '82']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['99', '98', '93', '86', '105', '80', '84', '97', '77', '81', '100', '87', '78', '91', '96', '85', '101', '89', '92', '94', '79', '83', '88', '95', '90', '82']}}, 'module_processed_references': {'_type': 'sec_certs.sample.certificate.References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': None, 'indirectly_referencing': None}, 'direct_transitive_cves': None, 'indirect_transitive_cves': None}.
  • The algorithms property was set to {'_type': 'Set', 'elements': ['DRBG#1340', 'DSA#1141', 'CVL#1012', 'AES#4280', 'HMAC#2816', 'Triple-DES#2309', 'RSA#2301', 'SHS#3516', 'ECDSA#998']}.
  • 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': 'c36f15e3a5fad001d122212b6f749e69211e6f469ebeb1d29bf16007652f24e0', 'policy_txt_hash': '47be60823bcdbf9f10290aa21c69814a6bba9d73e5b95954cbd9d9ea32fdccea'}.
  • The following properties were deleted: ['sp_path', 'html_path', 'tables_done', 'file_status', 'txt_state'].
• 05.11.2022

  Changed

  The certificate data changed.

  Show diff

  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': '#2309', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#4280', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2816', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#998', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#3516', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1141', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2301', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1340', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1012', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}]} values discarded.
• 25.10.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The PDF extraction data was updated.

  • The keywords property was updated, with the {'fips_cert_id': {'__update__': {'Cert': {'__delete__': ['#103', '#106', '#108', '#110', '#1']}}}, 'fips_certlike': {'__update__': {'Certlike': {'__update__': {'SHA-1': 4, 'SHA-224': 1, 'SHA1': 1}, '__delete__': ['PKCS1', 'AES GCM 2013', 'AES-192 192', 'DRBG 2014', 'DES 3', 'DES (3', 'DSA #998']}}}, 'symmetric_crypto': {'__update__': {'AES_competition': {'__update__': {'AES': {'__update__': {'AES': 21, 'AES-128': 1}, '__delete__': ['AES-']}}}, 'DES': {'__update__': {'DES': {'__update__': {'DES': 2}, '__delete__': ['DEA']}, '3DES': {'__update__': {'Triple-DES': 13}}}}, 'constructions': {'__update__': {'MAC': {'__update__': {'HMAC': 10}}}}}}, 'asymmetric_crypto': {'__update__': {'FF': {'__update__': {'DSA': {'__update__': {'DSA': 16}}}}}}, 'hash_function': {'__update__': {'SHA': {'__update__': {'SHA1': {'__update__': {'SHA-1': 6, 'SHA1': 1}}, 'SHA2': {'__update__': {'SHA-2': 6, 'SHA2': 1}}}, '__delete__': ['SHA3']}, 'MD': {'__update__': {'MD5': {'__update__': {'MD5': 2}}}}}}, 'crypto_scheme': {'__update__': {'KA': {'__delete__': ['KA']}}, '__delete__': ['MAC']}, 'crypto_protocol': {'__update__': {'TLS': {'__delete__': ['SSL']}}}, 'randomness': {'__update__': {'PRNG': {'__update__': {'DRBG': 22}}, 'RNG': {'__update__': {'RNG': 3}, '__delete__': ['RBG']}}}, 'cipher_mode': {'__update__': {'ECB': {'__update__': {'ECB': 3}}, 'CBC': {'__update__': {'CBC': 2}}, 'CTR': {'__update__': {'CTR': 4}}, 'OFB': {'__update__': {'OFB': 1}}}, '__delete__': ['CFB', 'XTS']}, 'ecc_curve': {'__update__': {'NIST': {'__delete__': ['B-128']}}}, 'tee_name': {}, 'standard_id': {'__update__': {'NIST': {'SP 800-131A': 2, 'SP 800-38B': 2, 'SP 800-38C': 2, 'SP 800-38D': 2, 'SP 800-56A': 1, 'SP 800-89': 1, 'SP 800-90A': 2, 'SP 800-90': 1, 'SP 800-38A': 1, 'SP 800-67': 1, 'SP 800-56B': 1}, 'PKCS': {'__delete__': ['PKCS1']}}}} data.
  • The algorithms property was set to {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '\n 5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7260', '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': '#2301', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7500', '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': '#998', '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': ' 7280', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7150', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7280', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7050', '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': '#3516', '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': '64', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7020', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7060', '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': '72', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 112', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7170', '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': ' 512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '32', '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': ' 7300', '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': ' 192', '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': '5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7150', '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': ' 7010', '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': ' 256', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7050', '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': '\n 1', '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': '\n 4', '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': 'c2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7300', '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': '7050', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#4280', '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': '#1141', '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': ' 7160', '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': 'a 7060', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2309', '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': 'A224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7500', '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': '\n 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7260', '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': ' 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '135', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'C5', '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': 'A2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '\n 2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7508', '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': ' 7320', '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': '7300', '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': 'C2', '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': '#1340', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'C4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2816', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 128', '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': '24', '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': ' 7250', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7060', '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': ' 384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7280', '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': '38', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1012', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7308', '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': '8', '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 updated.

  The computed heuristics were updated.

  • The algorithms property was updated, with the {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '\n 5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7260', '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': '#2301', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7500', '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': '#998', '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': ' 7280', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7150', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7280', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7050', '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': '#3516', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '64', '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': ' 7020', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7060', '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': '72', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 112', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': ' 7170', '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': ' 512', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '32', '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': ' 7300', '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': ' 192', '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': '5', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7150', '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': ' 7010', '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': '512', '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': 'a 7050', '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': '\n 1', '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': '\n 4', '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': 'c2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7300', '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': '7050', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#4280', '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': '#1141', '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': ' 7160', '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': 'a 7060', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2309', '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': 'A224', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7500', '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': '\n 3', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 7260', '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': ' 4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '135', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'C5', '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': 'A2', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7508', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '\n 2', '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': ' 7320', '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': '7300', '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': 'C2', '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': '#1340', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'C4', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2816', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': 'a 128', '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': '24', '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': ' 7250', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7060', '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': ' 384', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7280', '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': '38', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1012', 'algorithm_type': None, 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '7308', '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': '8', '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 clean_cert_ids property was updated.
  • The st_references property was updated, with the {'directly_referencing': {'_type': 'Set', 'elements': ['93', '95', '85', '100']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['93', '95', '85', '100']}} data.

  The state was updated.

  • The tables_done property was set to True.
• 08.10.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The computed heuristics were updated.

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

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web extraction data was updated.

  • This property was added with value {'_type': 'sec_certs.sample.fips.FIPSCertificate.WebData', 'module_name': 'Arista EOS Crypto Module v1.0', 'standard': 'FIPS140-2', 'status': 'Historical', 'date_sunset': None, 'date_validation': ['2017-05-15', '2019-01-28', '2020-07-10'], 'level': '1', 'caveat': 'When operated in FIPS mode. No assurance of the minimum strength of generated keys. The module generates cryptographic keys whose strengths are modified by available entropy', 'exceptions': ['Physical Security: N/A', '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': '#2309', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#4280', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2816', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#998', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1141', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#3516', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2301', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1340', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1012', 'algorithm_type': 'CVL', 'vendor': None, 'implementation': None, 'date': None}]}, 'tested_conf': ['EOS v4 running on Arista 7050SX-72 with AMD G Series: eKabini', 'EOS v4 running on Arista 7060CX-32S with AMD G Series: Steppe Eagle', 'EOS v4 running on Arista 7150S-24 with AMD Athlon NEO X2', 'EOS v4 running on Arista 7300 (DCS-7300-SUP supervisor, DCS-7308 chassis) with Intel Sandy Bridge EN', 'EOS v4 running on Arista 7500R (DCS-7500-SUP2 supervisor, DCS-7508 chassis) with Intel Broadwell-DE (single-user mode)'], 'description': 'Arista’s crypto library is a comprehensive suite of FIPS Approved algorithms. Many key sizes and modes have been implemented to allow flexibility and efficiency.', 'mentioned_certs': {}, 'vendor': 'Arista Networks, Inc.', 'vendor_www': 'http://www.arista.com', 'lab': None, 'lab_nvlap': None, 'historical_reason': 'Moved to historical list due to sunsetting', 'security_policy_www': 'https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/security-policies/140sp2909.pdf', 'certificate_www': 'https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation-program/documents/certificates/FIPS140ConsolidatedCertMay2017.pdf', 'hw_version': None, 'fw_version': None, 'revoked_reason': None, 'revoked_link': None, 'sw_versions': 'v1.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': 2909, 'keywords': {'fips_cert_id': {'Cert': {'#103': 1, '#105': 1, '#106': 1, '#108': 1, '#110': 1, '#102': 1, '#97': 1, '#98': 1, '#99': 1, '#100': 1, '#101': 1, '#96': 1, '#94': 1, '#95': 1, '#90': 2, '#91': 2, '#88': 1, '#89': 1, '#92': 1, '#93': 1, '#86': 1, '#87': 1, '#81': 1, '#82': 1, '#83': 1, '#84': 1, '#85': 1, '#79': 1, '#80': 1, '#77': 1, '#78': 1, '#1340': 1, '#4280': 1, '#2309': 1, '#3516': 1, '#2816': 1, '#2301': 2, '#1141': 1, '#998': 1, '#1012': 1, '#1': 1}}, 'fips_security_level': {}, 'fips_certlike': {'Certlike': {'HMAC SHA-1': 1, 'HMAC #2816': 2, 'HMAC-SHA1': 2, 'HMAC-SHA-1': 2, 'SHA-1': 8, 'SHA-2': 4, 'SHA-1/2': 1, 'SHA-2 (224': 2, 'SHS #3516': 1, 'SHA2': 1, 'SHA-224': 2, 'SHA-256': 5, 'SHA- 384': 1, 'SHA-512': 2, 'SHA-1 128': 1, 'SHA-384': 2, 'SHA-512 256': 1, 'SHA1': 2, 'SHA224': 1, 'SHA256': 1, 'SHA384': 1, 'SHA512': 1, 'RSA #2301': 2, 'PKCS1': 8, 'PKCS#1': 2, 'AES GCM 2013': 1, 'AES-128/192/256': 1, 'AES #4280': 1, 'AES 128/192/256': 1, 'AES-128 128': 1, 'AES-192 192': 1, 'AES-256 256': 1, 'AES-256': 1, 'DRBG 2014': 1, 'DRBG1': 1, 'DRBG #1340': 1, 'DES 3': 1, 'DES #2309': 1, 'DES (3': 2, 'DSA #1141': 1, 'DSA #998': 1, 'platform #102, TS-Linux 2.4 on ARMv4 2014-11-25 (2.0.9) Addition of new platforms #97, #98, VMware Horizon Workspace 2.1 x86 under vSphere Addition of new platform #99, QNX on ARMv4 Addition of new platforms #100, #101, Apple iOS 7.1 64-bit on ARMv8 2014-01-04 Addition of new platform #96, FreeBSD 8.4 on x86 without AES-NI 2014-07-30 Addition of two platforms #94, #95, FreeBSD 10.0 on x86, and re-removal of Dual EC DRBG 2014-07-28 Changed processor names for platforms #90, #91 2014-07-11 Added new platforms #88, #89, ArbOS 5.3 on x86 and #92, #93 FreeBSD 9.2on x86 2014-06-12 Temporarily remove misplaced platform, move Dual EC DRBG to the Non- Approved Table 4c 2014-05-29 Added platforms #86, #87 FreeBSD 9.1 on x86, #90 Linux ORACLESP 2.6 on ASPEED AST-Series (ARMv5) , #91 ORACLESP 2.6 on Emulex PILOT 3 (ARMv5) 2014-05-12 Added platforms #81 Linux 2.6 on PPC, #82, #83 AcanOS 1.0 on x86, #84 AcanOS 1.0 on ARMv5, #85 FreeBSD 8.4 on x86 Multiple changes to separate the Approved services from those that are non Approved per the SP 800-131A transition 2013-11-08 Added two platforms #79, #80 PexOS 1.0 under vSphere with/without AES-NI 2013-11-01 Added two platforms #77, #78 iOS 6.0 with/without NEON 2013-10-02 Added six platforms (Linux 3.4 x86 virtualized under XenSource/VMware/Hyper- V, with/without AES-NI) Updated URL in Appendix A footnote 2013-08-29 Added new sponsor acknowledgment Arista Networks, Inc. FIPS 140-2 Security Policy Page 5 of 19 2013-08-14 Added two Ubuntu 13.04 on ARMv7 (Beaglebone Black) and one Linux 3.8 on ARMv5TEJ platforms 2013-07-24 Added two VMware Horizon Workspace platforms Fixed typo in Table 4.1a, Hash DRBGs 888 bits not 880 2013-06-09 Added QNX, iOS 6.1, eCos for revision 2.0.5 2013-05-01 Added OpenWRT 2.6 for revision 2.0.4 2013-03-01 Added VMware Horizon Mobile 1.3, Apple OS X 10.7, Apple iOS 5.0 2013-02-23 Added WinEC7 and Android 4.0 for revision 2.0.3 2013-02-14 Table 5: Removed references to non-existent Table 9 Table 4a: added certs Table 4.1a: Added AES GCM 2013-01-28 Added four platforms: Android 4.1 and Android 4.2 with and without NEON 2013-01-08 Reworded section 8 2013-01-03 Added Win2008, RHEL 32/64 bit under vSphere and Win7 with AES-NI. 2012-12-08 Note EC DH Key Agreement and RSA Key Wrapping strength. 2012-10-10 Added NetBSD 5.1 on PowerPC-e500, NetBSD 5.1 on Intel Xeon 5500 (x86-64) for revision 2.0.2 2011-07-02 Added DSP Media Framework, Linux 2.6/Freescale PowerPC-e500, Android 4.0 2011-06-15 Added iOS, WinCE 5, WinCE 6 OEs Arista Networks, Inc. FIPS 140-2 Security Policy Page 6 of 19 References Reference Full Specification Name [FIPS 140-2] Security Requirements for Cryptographic modules, May 25, 2001 [FIPS 180-4] 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-90A] 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 Arista Networks, Inc. FIPS 140-2 Security Policy Page 7 of 19 Table of Contents 1 Introduction 2 Tested Configurations 3 Ports and Interfaces 4 Modes of Operation and Cryptographic Functionality 4.1 Critical Security Parameters and Public Keys 5 Roles, Authentication, and Services 6 Self-Tests 7 Operational Environment 8 Mitigation of other Attacks 9 Operator Guidance Arista Networks, Inc. FIPS 140-2 Security Policy Page 8 of 19 1 Introduction This document is the non-proprietary security policy for the Arista EOS Crypto Module v1.0, hereafter referred to as the Module. The Module is a software library providing a C-language application program interface (API) for use by other processes that require cryptographic functionality. The Module is classified by FIPS 140-2 as a software module, multi-chip standalone module embodiment. The physical cryptographic boundary is the general purpose computer on which the module is installed. The logical cryptographic boundary of the Module is the OpenSSL API file. The Module performs no communications other than with the calling application (the process that invokes the Module services). 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 1 Finite State Model 1 Physical Security NA Operational Environment 1 Cryptographic Key Management 1 EMI/EMC 1 Self-Tests 1 Design Assurance 1 Mitigation of Other Attacks NA Table 1 – Security Level of Security Requirements The Module’s software version for this validation is: v1.0. This is a fork of the OpenSSL FIPS Object Module version 2.0.10. Arista Networks, Inc. FIPS 140-2 Security Policy Page 9 of 19 Figure 1 - Module Block Diagram Arista Networks, Inc. FIPS 140-2 Security Policy Page 10 of 19 2 Module Configurations The following configurations were operationally tested. # Operational Environment Processor Optimizations (Target) 1 EOS v4 on Arista 7150S-24 AMD Athlon NEO X2 None 2 EOS v4 on Arista 7300 (DCS-7300-SUP supervisor, DCS-7308 chassis) Intel Sandy Bridge EN None 3 EOS v4 on Arista 7500R (DCS-7500- SUP2 supervisor, DCS-7508 chassis ) Intel Broadwell-DE None 4 EOS v4 on Arista 7050SX-72 AMD G Series: eKabini None 5 EOS v4 on Arista 7060CX-32S AMD G Series: Steppe Eagle None Table 2a - Tested Configurations The following configurations have the same operating system and processors as the above configurations and are vendor affirmed to behave in the same manner. (As these have only been affirmed by the vendor, CMVP itself does not provide assurances to the correct operation of the module or the strength of generated keys.) # Operational Environment Processor Optimizations (Target) 1 EOS v4 on Arista 7050QX, 7150 AMD Athlon NEO X2 None 2 EOS v4 on Arista 7500R, 7320X, 7300X, 7300X3, 7250QX, 7260X, 7280CR, 7050SX, 7050TX Intel Sandy Bridge EN None 3 EOS v4 on Arista 7500R, 7260X3, 7170, 7060X4 Intel Broadwell-DE None 4 EOS v4 on Arista 7260, 7260X, 7050SX, 7050TX, 7050QX, 7160, 7010T AMD G Series: eKabini None 5 EOS v4 on Arista 7280QR, 7280SR, 7280TR, 7060, 7050SX, 7050TX, 7160, 7060X, 7050X3, 7020R AMD G Series: Steppe Eagle None Table 2b – Vendor Affirmed Configurations Arista Networks, Inc. FIPS 140-2 Security Policy Page 11 of 19 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). Arista Networks, Inc. FIPS 140-2 Security Policy Page 12 of 19 4 Modes of Operation and Cryptographic Functionality The Module supports only a FIPS 140-2 Approved mode and a non-Approved mode. The Approved mode is invoked by calling FIPS_mode_set() and using only Approved and allowed algorithms. Tables 4a and 4b list the Approved and non-approved but allowed algorithms, respectively. Function Algorithm Options Cert # Random number generation [SP 800-90] DRBG1 Prediction resistance supported for all variations Hash DRBG (SHA-1, all SHA-2 sizes) HMAC DRBG (SHA-1, all SHA-2 sizes) CTR DRBG (AES-128/192/256) DRBG #1340 Encryption, Decryption and CMAC [FIPS 197] AES [SP 800-38A] CBC, etc. [SP 800-38B] CMAC [SP 800-38C] CCM [SP 800-38D] GCM 128/192/256 ECB, CBC, OFB, CFB-1, CFB-8, CFB-128, CTR; CCM; GCM; CMAC AES #4280 [SP 800-67] Triple-DES 3-Key Triple-DES TECB, TCBC, TCFB-1, TCFB-8, TCFB-64, TOFB; CMAC Triple- DES #2309 Message Digests [FIPS 180-3] SHA-1/2 SHA-1, SHA-2 (224, 256, 384, 512) SHS #3516 Keyed Hash [FIPS 198] HMAC SHA-1, SHA-2 (224, 256, 384, 512) HMAC #2816 Digital Signature and Asymmetric Key Generation [FIPS 186-4] RSA GenKey9.31 (2048/3072) SigGen9.31, SigGenPKCS1.5, SigGenPSS (2048/3072 with all SHA2 sizes) SigVer9.31, SigVerPKCS1.5, SigVerPSS (2048/3072 with all SHA-2 sizes) RSA #2301 [FIPS 186-2] Legacy RSA SigVer9.31, SigVerPKCS1.5, SigVerPSS (1024/1536/2048/3072/4096 with all SHA sizes) RSA #2301 [FIPS 186-4] DSA PQG Gen, PQG Ver, Key Pair Gen, Sig Gen, Sig Ver (2048/3072) PQG Ver, Sig Ver (1024) DSA #1141 [FIPS 186-4] ECDSA Functions: PKG, PKV, SigGen, SigGen Component, SigVer Curves: P-256, P-384, P-521 Hashes: SHA-1*, SHA-224, SHA-256, SHA- 384, SHA-512 ECDSA #998 *SHA-1 signature generation is allowed for protocol usage only. Key Derivation [SP800-135] KDF, Application Specific2 TLS KDF (v1.0/v1.1 and v1.2) SSH KDF CVL #1012 Table 4a – FIPS Approved Cryptographic Functions 1 For all DRBGs the "supported security strengths" is just the highest supported security strength per [SP800-90A] and [SP800-57]. 2 Only the KDFs to these protocols have been tested by CAVP. Arista Networks, Inc. FIPS 140-2 Security Policy Page 13 of 19 Category Algorithm Description Key Agreement EC Diffie-Hellman Non-compliant (untested to SP800-56A) Diffie-Hellman scheme using elliptic curve, supporting curves P-256, P-384, and P-512. This key agreement scheme provides between 128 and 256 bits of encryption strength; however, it is only a service provided forcalling process use. It 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. It provides 112 or 128 bits of encryption strength. No claim is made for SP 800-56B compliance, and no CSPs are established into or exported out of the module using these services. Hashing MD5 within TLS Component of TLS KDF Table 4b – Non-FIPS Approved But Allowed CryptographicFunctions The Module implements the following NIST-specified algorithms, which are non-Approved, either from algorithm transitions (e.g., SP800-131A) or from not being tested: Function Algorithm Options Encryption and Decryption AES-XTS 128/256 (Untested) Encrypt, decrypt Digital Signature and Asymmetric Key Generation RSA key size < 2048 (Disallowed) GenKey9.31, SigGen9.31, SigGenPKCS1.5, SigGenPSS (<2048) DSA key size <2048 (Disallowed) PQG Gen, Key Pair Gen, Sig Gen (<2048) Key Encryption, Decryption RSA key size < 2048 (Disallowed) RSA key encryption/decryption (<2048) Table 4c – Untested and Transition-Disallowed Cryptographic Functions The algorithms in Table 4c must not be used when operating in the FIPS mode of operation. The Module also implements the following algorithms, which are non-Approved: Function Algorithm Function Algorithm Encryption and Decryption AES/Triple-DES KW (non-compliant) Encryption and Decryption RC4 Blowfish RC5 Camellia 128/192/256 SEED CAST5 Message Digests MD4 DES MD5 DES-X RIPEMD-160 IDEA Whirlpool RC2 Keyed Hash HMAC-MD5 Table 4d – Other non-Approved Cryptographic Functions The algorithms in Table 4d are automatically disabled when in the FIPS mode of operation. 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 assurances are outside the scope of the Module, and are the responsibility of the calling process. Arista Networks, Inc. FIPS 140-2 Security Policy Page 14 of 19 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 AES EDK AES encrypt / decrypt key AES CMAC AES CMAC generate / verify key AES CCM AES encrypt / decrypt / generate / verify key for CCM AES GCM AES encrypt / decrypt / generate / verify key for GCM DRBG Seed Entropy input for Hash, HMAC, or CTR DRBG. Hash_DRBG CSPs V (440/888 bits) and C (440/888 bits) HMAC_DRBG CSPs V (160/224/256/384/512 bits) and Key (160/224/256/384/512 bits) CTR_DRBG CSPs V (128 bits) and Key (AES 128/192/256) DSA SGK DSA signature generation key ECDSA SGK ECDSA signature generation key EC Diffie-Hellman Private EC Diffie-Hellman private key agreement key HMAC Key Keyed hash key (160/224/256/384/512) RSA SGK RSA signature generation key RSA KDK RSA key decryption (private key transport) key Triple-DES EDK Triple-DES (3-Key) encrypt / decrypt key Triple-DES CMAC Triple-DES (3-Key) CMAC generate / verify key Table 4.1a – Critical Security Parameters The module does not output intermediate key generation values. Public Key Name Description DSA SVK DSA signature verification key ECDSA SVK ECDSA signature verification key EC Diffie-Hellman Public EC Diffie-Hellman public key agreement key RSA SVK RSA signature verification public key RSA KEK RSA key encryption (public key transport) key Table 4.1b – Public Keys For all CSPs and Public Keys: Storage: RAM, associated to entities by memory location. The Module stores RNG and DRBG state values for the lifetime of the RNG or DRBG instance. The module uses CSPs passed in by the calling application on the stack. The Module does not store any CSP persistently (beyond the lifetime of an API call), with the exception of RNG and DRBG state values used for the Module’s default key generation service. Generation: The Module implements SP 800-90A DRBG (Hash, HMAC, or CTR) services for creation of symmetric keys, and for generation of DSA, elliptic curve, and RSA keys as shown in Table 4a. The calling application is responsible for storage of generated keys returned by the module. Entry: All CSPs enter the Module’s logical boundary in plaintext as API parameters, associated by memory location. However, none cross the physical boundary. Output: The Module does not output CSPs, other than as explicit results of key generation services. However, none cross the physical boundary. Arista Networks, Inc. FIPS 140-2 Security Policy Page 15 of 19 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 (Cryptographic 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. For operation in the Approved mode, Module users (the calling applications) shall use entropy sources that contain at least 112 bits of entropy. To ensure full DRBG strength, the entropy sources must meet or exceed the security strengths shown in the table below. DRBG Type Underlying Algorithm Minimum Seed Entropy Hash_DRBG or HMAC_DRBG SHA-1 128 SHA-224 192 SHA-256 256 SHA-384 256 SHA-512 256 CTR_DRBG AES-128 128 AES-192 192 AES-256 256 Table 5 – DRBG Entropy Requirements This entropy is supplied by means of callback functions. Those functions must return an error if the requested entropy strength cannot be met. Arista Networks, Inc. FIPS 140-2 Security Policy Page 16 of 19 5 Roles, Authentication, and Services The Module implements the required User and Cryptographic Officer roles and does not perform operator authentication. 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. Cryptographic 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. All services are available in both the Approved mode and the non-Approved mode. In the Approved mode, these services are restricted to the algorithms listed in Tables 4a and 4b. In the non-Approved mode, the algorithms listed in Tables 4c and 4d may also be used. 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 number generation User, CO Used for random number and symmetric key 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 security 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 any symmetric encryption key from Table 4.1a: AES EDK, AES CCM, AES GCM, Triple-DES EDK (passed in by the calling process). Symmetric digest User, CO Used to generate or verify data integrity with CMAC. Executes using AES CMAC, Triple-DES 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). Arista Networks, Inc. FIPS 140-2 Security Policy Page 17 of 19 Key transport3 (algorithms only) User, CO Used to encrypt or decrypt a key value on behalf of the calling process (the key is treated as payload data; this service does not establish keys into the module). Executes using RSA KDK, RSA KEK (passed in by the calling process). Key agreement (algorithms only) User, CO Used to perform key agreement primitives on behalf of the calling process (this service does not establish keys into the module). Executes using EC Diffie-Hellman Private, EC Diffie-Hellman Public (passed in by the calling process). Key derivation User, CO Used to perform key derivation primitives as per SP800-135: TLS KDF and SSH KDF (this service does not establish keys into the module). 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 6 - 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 OpenSSL FIPS Object Module. Arista Networks, Inc. FIPS 140-2 Security Policy Page 18 of 19 6 Self-Tests 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 AES CMAC KAT CMAC generate and verify, 128, 192, 256 key lengths Triple-DES KAT Separate encrypt and decrypt, ECB mode, 3-Key Triple-DES CMAC KAT CMAC generate and verify, 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 with and without derivation function Hash_DRBG: SHA-256 HMAC_DRBG: SHA-256 ECDSA PCT Keygen, sign, verify using P-256 with SHA-512. Table 7a - Power On Self Tests (KAT = Known answer test; PCT = Pairwise consistency test) The Module is installed using one of the set of instructions in Appendix A, as appropriate for the target system. The HMAC-SHA-1 of the Module distribution file as tested by the CST 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() 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. 4 FIPS_mode_set() calls Module function FIPS_module_mode_set() Arista Networks, Inc. FIPS 140-2 Security Policy Page 19 of 19 The Module also implements the following conditional tests: Algorithm Test DRBG Health Tests as required by [SP800-90A] Section 11.3 DRBG FIPS 140-2 continuous test (CRNGT) 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 7b - Conditional Tests Pairwise consistency tests are performed for both possible modes of use, e.g. Sign/Verify and Encrypt/Decrypt. Failure of conditional self-tests is handled in the same manner as failure of power-on self-tests. 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. 8 Mitigation of other Attacks The module is not designed to mitigate against attacks which are outside of the scope of FIPS 140-2. 9 Operator Guidance User must ensure that the use of Triple-DES is compliant with IG A.13 SP 800-67rev1 Transition. User is responsible to enforce the limit of 220 64-bit data block encryptions with the same three-key Triple-DES key applies when keys are generated as part of one of the recognized IETF protocols and to enforce the limit of 216 64-bit data block encryptions when key is not generated as part of a recognized IETF protocol': 1, 'CVL #1012': 1}}, 'vendor': {'Qualcomm': {'Qualcomm': 1}}, 'eval_facility': {}, 'symmetric_crypto': {'AES_competition': {'AES': {'AES-': 5, 'AES': 22, 'AES-128': 2, 'AES-192': 1, 'AES-256': 2}, 'CAST': {'CAST5': 1}, 'RC': {'RC4': 1, 'RC5': 1, 'RC2': 1}}, 'DES': {'DES': {'DES': 17, 'DEA': 2}, '3DES': {'Triple-DES': 14, 'TDEA': 1}}, 'miscellaneous': {'IDEA': {'IDEA': 1}, 'Blowfish': {'Blowfish': 1}, 'Camellia': {'Camellia': 1}, 'SEED': {'SEED': 1}}, 'constructions': {'MAC': {'HMAC': 18, 'CMAC': 16}}}, 'asymmetric_crypto': {'ECC': {'ECDSA': {'ECDSA': 14}}, 'FF': {'DH': {'DH': 1, 'Diffie-Hellman': 8}, 'DSA': {'DSA': 30}}}, 'pq_crypto': {}, 'hash_function': {'SHA': {'SHA1': {'SHA-1': 10, 'SHA1': 2}, 'SHA2': {'SHA-224': 2, 'SHA-256': 5, 'SHA-512': 3, 'SHA-384': 2, 'SHA224': 1, 'SHA256': 1, 'SHA384': 1, 'SHA512': 1, 'SHA-2': 13, 'SHA2': 3}, 'SHA3': {'SHA-3': 2, 'SHA3': 1}}, 'MD': {'MD4': {'MD4': 1}, 'MD5': {'MD5': 3}}, 'RIPEMD': {'RIPEMD-160': 1}}, 'crypto_scheme': {'MAC': {'MAC': 35}, 'KA': {'Key Agreement': 2, 'Key agreement': 1, 'KA': 12}}, 'crypto_protocol': {'SSH': {'SSH': 2}, 'TLS': {'SSL': {'SSL': 7}, 'TLS': {'TLS': 4}}}, 'randomness': {'PRNG': {'DRBG': 40}, 'RNG': {'RNG': 4, 'RBG': 40}}, 'cipher_mode': {'ECB': {'ECB': 4}, 'CBC': {'CBC': 3}, 'CTR': {'CTR': 9}, 'CFB': {'CFB': 6}, 'OFB': {'OFB': 2}, 'GCM': {'GCM': 9}, 'CCM': {'CCM': 7}, 'XTS': {'XTS': 1}}, 'ecc_curve': {'NIST': {'P-256': 6, 'P-384': 4, 'P-521': 2, 'B-128': 1, 'P-512': 1}}, 'crypto_engine': {}, 'tls_cipher_suite': {}, 'crypto_library': {'OpenSSL': {'OpenSSL': 7}}, 'vulnerability': {}, 'side_channel_analysis': {}, 'device_model': {}, 'tee_name': {'IBM': {'SE': 2}}, 'os_name': {}, 'cplc_data': {}, 'ic_data_group': {}, 'standard_id': {'FIPS': {'FIPS 140-2': 27, 'FIPS 186-4': 5, 'FIPS 180-4': 1, 'FIPS 197': 2, 'FIPS 198-1': 1, 'FIPS 180-3': 1, 'FIPS 198': 1, 'FIPS 186-2': 1, 'FIPS 186': 1}, 'NIST': {'SP 805-7': 1, 'SP 800-6': 4, 'SP 800-1': 2, 'SP 800-3': 7, 'SP 800-5': 2, 'SP 800-8': 1, 'SP 800-9': 3}, 'PKCS': {'PKCS1': 4, 'PKCS#1': 1}}, 'javacard_version': {}, 'javacard_api_const': {}, 'javacard_packages': {}, 'certification_process': {}}, 'algorithms': {'_type': 'Set', 'elements': []}, 'clean_cert_ids': {'#103': 1, '#105': 1, '#106': 1, '#108': 1, '#110': 1, '#97': 1, '#98': 1, '#99': 1, '#100': 1, '#101': 1, '#96': 1, '#94': 1, '#95': 1, '#90': 2, '#91': 2, '#88': 1, '#89': 1, '#92': 1, '#93': 1, '#86': 1, '#87': 1, '#81': 1, '#82': 1, '#83': 1, '#84': 1, '#85': 1, '#79': 1, '#80': 1, '#77': 1, '#78': 1}, 'st_metadata': {'pdf_file_size_bytes': 509022, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 19, '/Title': 'Microsoft Word - 1g - Arista_SP_140sp2909 V1.3_1_8_2019.docx', '/Author': 'lgarcia', '/Creator': 'Microsoft® Word 2013', '/CreationDate': "D:20200623151917-04'00'", '/ModDate': "D:20200623151917-04'00'", '/Producer': 'Microsoft® Word 2013', 'pdf_hyperlinks': {'_type': 'Set', 'elements': ['http://www.openssl.org/', 'http://www.drh-consultancy.co.uk/', 'http://www.cryptsoft.com/', 'mailto:[email protected]', 'mailto:[email protected]', 'mailto:[email protected]', 'mailto:[email protected]', 'http://www.infogard.com/', 'mailto:[email protected]', 'mailto:[email protected]', 'mailto:[email protected]', 'mailto:[email protected]']}}}.

  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': {'#100': 1, '#95': 1, '#89': 1, '#93': 1, '#85': 1}}.
  • 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': '#2309', 'algorithm_type': 'Triple-DES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#4280', 'algorithm_type': 'AES', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2816', 'algorithm_type': 'HMAC', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#998', 'algorithm_type': 'ECDSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1141', 'algorithm_type': 'DSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#3516', 'algorithm_type': 'SHS', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#2301', 'algorithm_type': 'RSA', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1340', 'algorithm_type': 'DRBG', 'vendor': None, 'implementation': None, 'date': None}, {'_type': 'sec_certs.sample.fips_algorithm.FIPSAlgorithm', 'cert_id': '#1012', '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': {'_type': 'Set', 'elements': ['95', '93', '85', '100', '89']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['95', '93', '85', '100', '89']}} 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

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The pdf_scan was updated.

  • The keywords property was updated, with the {'rules_cert_id': {}, 'rules_standard_id': {'__update__': {'FIPS ?(?:PUB )?[0-9]+-[0-9]+?': {'__update__': {'FIPS 140-2': {'__update__': {'count': 1}}}, '__delete__': ['FIPS 186-4', 'FIPS 180-4', 'FIPS 198-1', 'FIPS 180-3', 'FIPS 186-2']}, 'FIPS ?(?:PUB )?[0-9]+?': {'__delete__': ['FIPS 197', 'FIPS 198']}}}, '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}}}}, 'OFB': {'__update__': {'OFB': {'__update__': {'count': 1}}}}, 'GCM': {'__update__': {'GCM': {'__update__': {'count': 1}}}}}}, 'rules_ecc_curves': {'__insert__': {'(NIST)? ?[PBK]-[0-9]{3}': {'P-256': {'count': 1}}}, '__update__': {'(?:Curve |curve |)P-(192|224|256|384|521)': {'__update__': {'P-256': {'__update__': {'count': 1}}}, '__delete__': ['P-384']}}}, 'rules_crypto_libs': {'__update__': {'OpenSSL': {'__update__': {'OpenSSL': {'__update__': {'count': 1}}}}}}, 'rules_other': {'__update__': {'library': {'__update__': {'library': {'__update__': {'count': 1}}}}}}} data.

  The computed heuristics were updated.

  • The keywords property was updated, with the {'rules_cert_id': {}, 'rules_standard_id': {'__update__': {'FIPS ?(?:PUB )?[0-9]+-[0-9]+?': {'__update__': {'FIPS 140-2': {'__update__': {'count': 1}}}, '__delete__': ['FIPS 186-4', 'FIPS 180-4', 'FIPS 198-1', 'FIPS 180-3', 'FIPS 186-2']}, 'FIPS ?(?:PUB )?[0-9]+?': {'__delete__': ['FIPS 197', 'FIPS 198']}}}, '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}}}}, 'OFB': {'__update__': {'OFB': {'__update__': {'count': 1}}}}, 'GCM': {'__update__': {'GCM': {'__update__': {'count': 1}}}}}}, 'rules_ecc_curves': {'__insert__': {'(NIST)? ?[PBK]-[0-9]{3}': {'P-256': {'count': 1}}}, '__update__': {'(?:Curve |curve |)P-(192|224|256|384|521)': {'__update__': {'P-256': {'__update__': {'count': 1}}}, '__delete__': ['P-384']}}}, 'rules_crypto_libs': {'__update__': {'OpenSSL': {'__update__': {'OpenSSL': {'__update__': {'count': 1}}}}}}, 'rules_other': {'__update__': {'library': {'__update__': {'library': {'__update__': {'count': 1}}}}}}} data.
• 15.05.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The status property was set to Historical.
  • The date_sunset property was set to None.
  • The historical_reason property was set to Moved to historical list due to sunsetting.
• 08.03.2022

  Changed

  The certificate data changed.

  Show diff

  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': None, 'indirectly_referencing': None}, 'web_references': {'_type': 'References', 'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': None, 'indirectly_referencing': None}}.
  • The following properties were deleted: ['connections', 'directly_affected_by', 'indirectly_affected_by', 'directly_affecting', 'indirectly_affecting'].
• 18.02.2022

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The computed heuristics were updated.

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

  Changed

  The certificate data changed.

  Show diff

  Certificate changed

  The web_scan was updated.

  • The module_type property was set to Software.
• 30.01.2022

  New

  The certificate was first processed.

  Show diff

  New certificate

  A new FIPS 140 certificate with the product name Arista EOS Crypto Module v1.0 was processed.