Copyright Juniper, 2016 Version 1.1 Page 1 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). Juniper Networks LN1000 Mobile Secure Router Non-Proprietary FIPS 140-2 Cryptographic Module Security Policy Version: 1.2 Date: August 23, 2016 Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408.745.2000 1.888 JUNIPER www.juniper.net Copyright Juniper, 2016 Version 1.1 Page 2 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). Table of Contents 1 Introduction ....................................................................................................................3 1.1 Hardware and Physical Cryptographic Boundary.........................................................................5 1.2 Mode of Operation.......................................................................................................................6 1.3 Firmware Load..............................................................................................................................7 1.4 Zeroization....................................................................................................................................8 2 Cryptographic Functionality.............................................................................................8 2.1 Disallowed Algorithms............................................................................................................... 11 2.2 Critical Security Parameters...................................................................................................... 11 3 Roles, Authentication and Services................................................................................12 3.1 Roles and Authentication of Operators to Roles ...................................................................... 12 3.2 Authentication Methods ........................................................................................................... 12 3.3 Services...................................................................................................................................... 13 4 Self-tests........................................................................................................................14 5 Physical Security Policy..................................................................................................15 5.1 General Tamper Seal Placement and Application Instructions................................................. 16 6 Security Rules and Guidance..........................................................................................17 7 References and Definitions............................................................................................17 List of Tables Table 1 – Cryptographic Module Configurations..........................................................................................3 Table 2 - Security Level of Security Requirements........................................................................................3 Table 3 - Ports and Interfaces ...................................................................................................................... 6 Table 4 - Approved and CAVP Validated Cryptographic Functions ..............................................................8 Table 5 - Non-Approved but Allowed Cryptographic Functions.................................................................10 Table 6 - Protocols Allowed in FIPS Mode ..................................................................................................10 Table 7 - Critical Security Parameters (CSPs)..............................................................................................11 Table 8 - Public Keys.................................................................................................................................... 12 Table 9 - Authenticated Services ................................................................................................................13 Table 10 - Unauthenticated traffic..............................................................................................................13 Table 11 - CSP Access Rights within Services..............................................................................................14 Table 12 – Physical Security Inspection Guidelines ....................................................................................16 Table 13 – References................................................................................................................................. 17 Table 14 – Acronyms and Definitions .........................................................................................................17 Table 15 – Datasheet .................................................................................................................................. 18 Copyright Juniper, 2016 Version 1.1 Page 3 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). List of Figures Figure 1 – LN1000 Top View ......................................................................................................................... 5 Figure 2 – LN1000 Bottom View ................................................................................................................... 5 Figure 3 – Tamper-Evident Seal Placement ................................................................................................16 1 Introduction The Juniper Networks LN1000 Mobile Secure Router is a secure router that provides essential capabilities to connect, secure, and manage work force locations sized from handfuls to hundreds of users. The LN1000 provides high-performance network routing, next-generation firewall and intrusion prevention system (IPS) capabilities, and unified threat management in a standard VPX form factor. The LN1000 runs Juniper’s JUNOS firmware – in this case, a specific FIPS-compliant version called JUNOS- FIPS, version 12.1X46-D40. The firmware image is junos-ln-12.1X46-D40.4-fips.tgz and the firmware Status service identifies itself as in the “Junos 12.1X46-D40.4 (FIPS edition)”. The cryptographic module is defined as multiple-chip embedded module that execute JUNOS-FIPS firmware on the LN1000 hardware. Table 1 – Cryptographic Module Configurations Model Hardware Version Firmware Description LN1000 LN1000-V JUNOS-FIPS 12.1X46- D40 VPX Form Factor, supports 8 x 1GbE interfaces LN1000 JNPR-FIPS-TAMPER- LBLS N/A Tamper-Evident Seals The module is designed to meet FIPS 140-2 Level 2 overall: Table 2 - Security Level of Security Requirements Area Description Level 1 Module Specification 2 2 Ports and Interfaces 2 3 Roles and Services 3 4 Finite State Model 2 5 Physical Security 2 6 Operational Environment N/A 7 Key Management 2 8 EMI/EMC 2 9 Self-test 2 10 Design Assurance 3 11 Mitigation of Other Attacks N/A Overall 2 Copyright Juniper, 2016 Version 1.1 Page 4 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). The module has a limited operational environment as per the FIPS 140-2 definitions. It includes a firmware load service to support necessary updates. New firmware versions within the scope of this validation must be validated through the FIPS 140-2 CMVP. Any other firmware loaded into the module is out of the scope of this validation and require a separate FIPS 140-2 validation. The module does not implement any mitigations of other attacks as defined by FIPS 140-2. Copyright Juniper, 2016 Version 1.1 Page 5 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). 1.1 Hardware and Physical Cryptographic Boundary The physical forms of the module are depicted in Figures 1-2 below. The cryptographic boundary is defined as the outer edge of the device, with the exception of the protective plate over the RJ-45 console port. The module requires a third party chassis with a 3U VPX (VITA 46.0) compatible peripheral slot for input, output, and power. Figure 1 – LN1000 Top View Figure 2 – LN1000 Bottom View Copyright Juniper, 2016 Version 1.1 Page 6 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). Table 3 - Ports and Interfaces Port Description Logical Interface Type Backplane LAN Communications Control in, Data in, Data out, Status out, Power in Serial RJ-45 Console serial port Control in, Status out LED Status indicator lighting Status out 1.2 Mode of Operation Follow the instructions in Section 5 to apply the tamper seals to the module. Once the tamper seals have been applied as shown in this document, the JUNOS-FIPS firmware image is installed on the device, integrity and self-tests have run successfully on initial power-on, and the approved algorithms have been configured, the module is operating in the approved mode. The Crypto-Officer must ensure that the backup image of the firmware is also a JUNOS-FIPS image by issuing the request system snapshot command. If the module was previously in a non-Approved mode of operation, the Cryptographic Officer must zeroize the CSPs by following the instructions in Section 1.4. Then, the CO must run the following commands to configure SSH to use FIPS approved and FIPS allowed algorithms: co@fips-ln# set system services ssh hostkey-algorithm ssh-ecdsa co@fips-ln# set system services ssh hostkey-algorithm no-ssh-rsa co@fips-ln# set system services ssh hostkey-algorithm no-ssh-dss co@fips-ln# set system services ssh hostkey-algorithm no-ssh-ed25519 co@fips-ln# commit The module always enables the following algorithms for SSH: dh-group14-sha1, ecdh-sha2-nistp256, ecdh-sha2-nistp384, group-exchange-sha1, group-exchange-sha2, hmac-sha1, hmac-sha1-96, and 3des- cbc, aes128-cbc, aes128-ctr, aes192-cbc, aes192-ctr, aes256-cbc, aes256-ctr. The CO can change the preference of SSH key exchange and cipher algorithms using the following commands: co@fips-ln# set system services ssh key-exchange - dh-group14-sha1, ecdh-sha2-nistp256, ecdh-sha2-nistp384, group-exchange-sha1, or group-exchange-sha2 co@fips-ln# set system services ssh ciphers - 3des-cbc, aes128-cbc, aes128-ctr, aes192-cbc, aes192-ctr, aes256-cbc, aes256-ctr Note: These algorithms are always proposed during SSH session negotiation. Explicitly specifying an algorithm moves the algorithm up in the list of proposed algorithms during the SSH session establishment. Copyright Juniper, 2016 Version 1.1 Page 7 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). The CO can change the preference of SSH MAC algorithms or enable additional Approved algorithms using the following command: co@fips-ln# set system services ssh macs - hmac-sha1, hmac-sha1-96, hmac-sha2-256, hmac-sha2-512, hmac-sha1-96-etm@openssh.com, hmac-sha1-etm@openssh.com, hmac-sha2-256- etm@openssh.com, hmac-sha2-512-etm@openssh.com Note: hmac-sha1 and hmac-sha1-96 are always proposed during SSH session negotiation. Explicitly specifying either algorithm moves it up in the list of proposed algorithms during the SSH session establishment. Specifying any other MAC algorithm adds it to the list of algorithms proposed. For each IPsec tunnel configured, the CO must run the following command to configure the algorithms: co@fips-ln# set system security ipsec authentication-algorithm - hmac-sha-256-128, hmac-sha1-96 co@fips-ln# set system security ipsec encryption-algorithm - 3des-cbc, aes-128-cbc, aes-128-gcm, aes-192-cbc, aes-192- gcm, aes-256-cbc, aes-256-gcm Note: Use of AES-GCM is only FIPS approved when it is configured for use in conjunction with IKEv2. The “show version” command will indicate if the module is operating in FIPS mode (e.g. JUNOS Software Release [12.1X46-D40] (FIPS edition)), run “show system services ssh”, and run “show security ipsec” to verify that only the FIPS approved and FIPS allowed algorithms are configured for SSH and IPsec as specified above. 1.3 Firmware Load The cryptographic module implements a firmware load service which allows the loading of legacy firmware (legacy-use of digital signature verification using SHA-1 as defined by SP800-131Ar1). To comply with SP 800-131Ar1, the Crypto Officer must manually determine when a legacy firmware load is being performed and determine if the correct type of signature is being verified. When newer firmware is being loaded, the Crypto Officer must verify the presence of an ECDSA signature for the junos and junos-boot portions of the image by running: % tar ztf .tgz | grep esig The Crypto Officer must verify the output show presence of an esig file for both the junos and junos- boot portions of the image. For example: % tar ztf junos-ln-12.1X46-D40.4-fips.tgz | grep esig junos-boot-ln-12.1X46-D40.4-fips.esig junos-ln-12.1X46-D40.4-fips.esig If the two esig files are not present, the Crypto Officer must not install the image. If the two esig files are present or the Crypto Officer is installing a legacy image, installation may continue using the following command: co@fips-ln> request system software add [no-validate] [no-copy] .tgz [reboot] The module will automatically verify that the image signature(s) are valid. Copyright Juniper, 2016 Version 1.1 Page 8 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). 1.4 Zeroization The cryptographic module provides a non-Approved mode of operation in which non-approved cryptographic algorithms are supported. When transitioning between the non-Approved mode of operation and the Approved mode of operation, the Cryptographic Officer must run the following commands to zeroize the Approved mode CSPs: co@fips-ln> start shell co@fips-ln% rm –P - each persistent private or secret key other than the SSH host keys and the X.509 keys for IKE. co@fips-ln% rm –P /var/db/certs/common/certificate-request/* co@fips-ln% exit co@fips-ln> request system zeroize Note: The Cryptographic Officer must retain control of the module while zeroization is in process. 2 Cryptographic Functionality The module implements the FIPS Approved and Non-Approved but Allowed cryptographic functions listed in Tables 4 and 5 below. Table 6 summarizes the high level protocol algorithm support. The module does not implement algorithms that require vendor affirmation. Table 4 - Approved and CAVP Validated Cryptographic Functions Implementation Reference Mode Functions Strength Cert IPsec Triple-DES SP 800-20 TCBC Encrypt and decrypt 112 (3-Key) 2042 IPsec AES FIPS 197 SP 800-38A SP 800-38D CBC GCM Encrypt and decrypt 128, 192, 256 3660 IPsec SHA FIPS 180-4 Hash generation 80 (SHA-1) 128 (SHA-256) 3078 IPsec HMAC FIPS 198-1 HMAC Gen, Ver 128 (HMAC-SHA-1) 256 (HMAC-SHA- 256) 2410 IKE Triple-DES SP 800-20 TCBC Encrypt and decrypt 112 (3-key) 2035 IKE AES FIPS 197 SP 800-38A CBC Encrypt and decrypt 128, 192, 256 3656 IKE SHA FIPS 180-4 Hash generation 80 (SHA-1) 128 (SHA-256) 192 (SHA-384) 3074 IKE HMAC FIPS 198-1 HMAC Gen, Ver 128 (HMAC-SHA-1) 256 (HMAC-SHA- 256, HMAC-SHA- 384) 2406 IKE KDF SP 800-135 IKE v1/v2 KDF 112-256 CVL 659 IKE ECDSA FIPS 186-4 KeyGen, SigGen, SigVer 128 (P-256) 192 (P-384) 767 Copyright Juniper, 2016 Version 1.1 Page 9 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). IKE RSA FIPS 186-4 SigGen, SigVer 112 (2048 bit) 1893 IKE DSA FIPS 186-4 KeyGen 112 (2048 bit) 1030 SSH Triple-DES SP 800-20 TCBC Encrypt and decrypt 112 (3-Key) 2036 SSH AES FIPS 197 SP 800-38A CBC CTR Encrypt and decrypt 128, 192, 256 3650 SSH SHA FIPS 180-4 Hash generation 80 (SHA-1) 128 (SHA-256) 256 (SHA-512) 3068 SSH HMAC FIPS 198-1 HMAC Gen, Ver 128 (HMAC-SHA-1) 256 (HMAC-SHA- 256, HMAC-SHA- 512) 2400 SSH RSA FIPS 186-4 KeyGen, SigVer 112 (2048 bit) 1885 SigVer 128 (3072 bit) SSH ECDSA FIPS 186-4 KeyGen, SigGen, SigVer 112 (P-224) 128 (P-256) 192 (P-384) 758 SSH DSA FIPS 186-4 KeyGen 112 (2048 bit) 1022 DRBG SP 800-90A HMAC Random generation 256 (HMAC-SHA- 256) 981 SSH KDF SP 800-135 SSHv2 KDF 112-256 CVL 660 Copyright Juniper, 2016 Version 1.1 Page 10 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). Table 5 - Non-Approved but Allowed Cryptographic Functions Algorithm Reference Non-SP 800-56A Compliant Diffie-Hellman [IG] D.8 Diffie-Hellman (key agreement; key establishment methodology provides between 112 and 192 bits of encryption strength). Non-SP 800-56A Compliant Elliptic Curve Diffie-Hellman [IG] D.8 EC Diffie-Hellman (key agreement; key establishment methodology provides 128 or 192 bits of encryption strength). NDRNG [IG] 7.11 Hardware Non-Deterministic RNG used to seed the FIPS Approved DRBG. HMAC-SHA-1-96 [IG] A.8 Hash Message Authentication Code truncated to 96-bits. Allowed for use in FIPS mode. Table 6 - Protocols Allowed in FIPS Mode Protocol Key Exchange Auth Cipher Integrity IKEv1/v2 Oakley Group 14 (DH 2048) Oakley Group 19 (P-256) Oakley Group 20 (P-384) Oakley Group 24 (DH 2048) RSA 2048 Pre-Shared Secret ECDSA P-256 ECDSA P-384 3 Key Triple-DES AES CBC 128/192/256 HMAC-SHA- 1-96 HMAC-SHA- 256 HMAC-SHA- 384 IPsec ESP IKEv1 with optional: • Oakley Group 14 (DH 2048) • Oakley Group 19 (P-256) • Oakley Group 20 (P-384) • Oakley Group 24 (DH 2048) IKEv1 3 Key Triple-DES AES CBC 128/192/256 HMAC-SHA- 1-96 HMAC-SHA- 256-128 IKEv2 with optional: • Oakley Group 14 (DH 2048) • Oakley Group 19 (P-256) • Oakley Group 20 (P-384) • Oakley Group 24 (DH 2048) IKEv2 3 Key Triple-DES AES CBC 128/192/256 AES GCM 128/192/256 16 octet ICV SSHv2 Diffie-hellman-group- exchange-sha1 (2048 bit, 3072 bit, 4096 bit, 6144 bit, 7680 bit, or 8192 bit) Diffie-hellman-group- exchange-sha2 (2048 bit, 3072 bit, 4096 bit, 6144 bit, 7680 bit, or 8192 bit) Diffie-hellman-group14-sha1 (2048 bit) ECDSA P-256 3 Key Triple-DES AES CBC 128/192/256 AES CTR 128/192/256 HMAC-SHA- 1-96 HMAC-SHA-1 HMAC-SHA- 256 HMAC-SHA- 512 Copyright Juniper, 2016 Version 1.1 Page 11 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). ECDH-sha2-nistp256 ECDH-sha2-nistp384 These protocols have not been reviewed or tested by the CAVP and CMVP. The IKE and SSH algorithms allow independent selection of key exchange, authentication, cipher and integrity. In Table 6 above, each column of options for a given protocol is independent, and may be used in any viable combination. 2.1 Disallowed Algorithms These algorithms are non-Approved algorithms that are disabled when the module is operated in an Approved mode of operation. • ssh-dss (DSA non-compliant) • dh-group1-sha1 (Diffie-Hellman (non-compliant key agreement; key establishment methodology provides less than 112 bits of encryption strength) • hmac-md5 • hmac-ripemd160 • umac-128 • umac-64 • arcfour • blowfish • cast128 • DES 2.2 Critical Security Parameters All CSPs and public keys used by the module are described in this section. Table 7 - Critical Security Parameters (CSPs) Name Description and usage DRBG_Seed Seed material used to seed or reseed the DRBG DRBG_State V and Key values for the HMAC_DRBG SSH PHK SSH-2 Private host key. The first time SSH is configured, the keys are generated. ECDSA P- 256. Used to identify the host. SSH DH SSH Diffie-Hellman private component. Ephemeral Diffie-Hellman private key used in SSH. DH (2048 bit, 3072 bit, 4096 bit, 6144 bit, 7680 bit, or 8192 bit), ECDH P-256, or ECDH P- 384 SSH-SEK SSH Session Key; Session keys used with SSH. TDES (3key), AES, HMAC. ESP-SEK IPSec ESP Session Keys. TDES (3 key), AES, HMAC. IKE-PSK Pre-Shared Key used to authenticate IKE connections. IKE-Priv IKE Private Key. RSA 2048, ECDSA P-256, or ECDSA P-384 IKE-SKEYID IKE secret used to derive IKE and IPsec ESP session keys. IKE-SEK IKE Session Keys. TDES (3 key), AES, HMAC. IKE-DH-PRI IKE Diffie-Hellman private component. Ephemeral Diffie-Hellman private key used in IKE. Copyright Juniper, 2016 Version 1.1 Page 12 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). DH 2048 bit), ECDH P-256, or ECDH P-384 CO-PW ASCII Text used to authenticate the CO. User-PW ASCII Text used to authenticate the User. Table 8 - Public Keys Name Description and usage SSH-PUB SSH-2 Public Host Key used to identify the host. ECDSA P-256. SSH-DH-PUB Diffie-Hellman public component. Ephemeral Diffie-Hellman public key used in SSH key establishment. DH (2048 bit, 3072 bit, 4096 bit, 6144 bit, 7680 bit, 8192 bit), ECDH P-256, or ECDH P-384. IKE-PUB IKE Public Key RSA 2048, ECDSA P-256, or ECDSA P-384. IKE-DH-PUB Diffie-Hellman public component. Ephemeral Diffie-Hellman public key used in IKE key establishment. DH 2048 bit, ECDH P-256, or ECDH P-384. Auth-UPub User Authentication Public Keys. Used to authenticate users to the module. ECDSA P256 or P- 384. Auth-COPub CO Authentication Public Keys. Used to authenticate CO to the module. ECDSA P256 or P-384. Root-CA JuniperRootCA. RSA 2048 X.509 Certificate; Used to verify the validity of the Juniper Package- CA at software load. RootEC-CA JuniperRootEC CA. ECDSA P-256 X.509 Certificate; Used to verify the validity of the Juniper Package CA at software load and also at runtime for integrity. Package-CA PackageCA. RSA 2048 X.509 Certificate; Used to verify the validity of legacy Juniper Images at software load. PackageEC- CA PackageEC CA. ECDSA P-256 X.509 Certificate; Used to verify the validity the Juniper Image at software load and also at runtime for integrity. 3 Roles, Authentication and Services 3.1 Roles and Authentication of Operators to Roles The module supports two roles: Cryptographic Officer (CO) and User. The module supports concurrent operators, but does not support a maintenance role and/or bypass capability. The module enforces the separation of roles using identity-based operator authentication. The Cryptographic Officer role configures and monitors the module via a console or SSH connection. As root or super-user, the Cryptographic Officer has permission to view and edit secrets within the module. The User role monitors the router via the console or SSH. The user role may not change the configuration. 3.2 Authentication Methods The module implements two forms of Identity-Based authentication, Username and password over the Console and SSH as well as Username and public key over SSH. Password authentication: The module enforces 10-character passwords (at minimum) chosen from the 96 human readable ASCII characters. The maximum password length is 20-characters. Copyright Juniper, 2016 Version 1.1 Page 13 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). The module enforces a timed access mechanism as follows: For the first two failed attempts (assuming 0 time to process), no timed access is enforced. Upon the third attempt, the module enforces a 5-second delay. Each failed attempt thereafter results in an additional 5-second delay above the previous (e.g. 4th failed attempt = 10-second delay, 5th failed attempt = 15-second delay, 6th failed attempt = 20-second delay, 7th failed attempt = 25-second delay). This leads to a maximum of nine (9) possible attempts in a one-minute period for each getty. The best approach for the attacker would be to disconnect after 4 failed attempts, and wait for a new getty to be spawned. This would allow the attacker to perform roughly 9.6 attempts per minute (576 attempts per hour/60 mins); this would be rounded down to 9 per minute, because there is no such thing as 0.6 attempts. Thus the probability of a successful random attempt is 1/9610 , which is less than 1/1 million. The probability of a success with multiple consecutive attempts in a one-minute period is 9/(9610 ), which is less than 1/100,000. ECDSA signature verification: SSH public-key authentication. Processing constraints allow for a maximum of 5.6e7 ECDSA attempts per minute. The module supports ECDSA (P-256 and P-384). The probability of a random authentication attempt succeeding is 1/2128 . The probability of a success with multiple consecutive attempts in a one-minute period is 5.6e7/(2128 ). 3.3 Services All services implemented by the module are listed in the tables below. Table 11 lists the access to CSPs by each service. The services offered in the Approved and Non-Approved modes of operation are identical, however Non-Approved algorithms are available in the Non-Approved mode. Table 9 - Authenticated Services Service Description CO User Configure security Security relevant configuration x Configure Non-security relevant configuration x Secure Traffic IPsec protected connection (ESP) x Status Show status x x Zeroize Destroy all CSPs x SSH connect Initiate SSH connection for SSH monitoring and control (CLI) x x IPsec connect Initiate IPsec connection (IKE) x Console access Console monitoring and control (CLI) x x Remote reset Software initiated reset x Table 10 - Unauthenticated traffic Service Description Local reset Hardware reset or power cycle Traffic Traffic requiring no cryptographic services Copyright Juniper, 2016 Version 1.1 Page 14 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). Table 11 - CSP Access Rights within Services Service CSPs DRBG_Seed DRBG_State SSH PHK SSH DH SSH-SEK ESP-SEK IKE-PSK IKE-Priv IKE-SKEYID IKE-SEK IKE-DH-PRI CO-PW User-PW Configure security -- E GW -- -- -- W GW -- -- -- W W Configure -- -- -- -- -- -- -- -- -- -- -- -- -- Secure traffic -- -- -- -- -- E -- -- -- E -- -- -- Status -- -- -- -- -- -- -- -- -- -- -- -- -- Zeroize -- Z Z -- -- -- Z Z -- -- -- Z Z SSH connect -- E E GE GE -- -- -- -- -- -- E E IPsec connect -- E -- -- -- G E E G G G -- -- Console access -- -- -- -- -- -- -- -- -- -- -- E E Remote reset GEZ G -- Z Z Z -- -- Z Z Z Z Z Local reset GEZ G -- Z Z Z -- -- Z Z Z Z Z Traffic -- -- -- -- -- -- -- -- -- -- -- -- -- G = Generate: The module generates the CSP R = Read: The CSP is read from the module (e.g. the CSP is output) E = Execute: The module executes using the CSP W = Write: The CSP is updated or written to the module Z = Zeroize: The module zeroizes the CSP. 4 Self-tests Each time the module is powered up, it tests that the cryptographic algorithms still operate correctly and that sensitive data have not been damaged. Power-up self-tests are available on demand by power cycling the module. On power up or reset, the module performs the self-tests described below. All KATs must be completed successfully prior to any other use of cryptography by the module. If one of the KATs fails, the module enters the Critical Failure error state. The module performs the following power-up self-tests: • Firmware Integrity check using ECDSA P-256 with SHA-256 • QuickSec JSF Hardware Accelerated KATs o AES-CBC Encrypt & Decrypt KATs o AES-GCM Encrypt & Decrypt KATs o RSA 2048 w/ SHA-256 Sign/Verify KATs o ECDSA P-256 w/ SHA-256 Sign/Verify PCT • QuickSec Hardware Accelerated KATs o 3DES-CBC Encrypt & Decrypt KATs o HMAC-SHA-1 KAT Copyright Juniper, 2016 Version 1.1 Page 15 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). o HMAC-SHA-256 KAT • OpenSSL KATs o SP 800-90A HMAC DRBG KAT  Health-tests initialize, re-seed, and generate. o ECDSA P-256 Sign/Verify PCT o ECDH P-256 KAT  Derivation of the expected shared secret. o RSA 2048 w/ SHA-256 Sign and Verify KATs o DES3-CBC Encrypt & Decrypt KATs o HMAC-SHA-1 KAT o HMAC-SHA-256 KAT o HMAC-SHA-384 KAT o HMAC-SHA-512 KAT o SHA-256 KAT o AES-CBC Encrypt & Decrypt Known Answer Test o KDF-SSH KAT • QuickSec KATs o 3DES-CBC Encrypt & Decrypt KATs o HMAC-SHA1 KAT o HMAC-SHA-256 KAT o HMAC-SHA-384 KAT o AES-CBC Encrypt & Decrypt KATs o KDF-IKE-V1 KAT o KDF-IKE-V2 KAT • Critical Function Test o The cryptographic module performs a verification of a limited operational environment, and verification of optional non-critical packages. The module also performs the following conditional self-tests: • Continuous RNG Test on the SP 800-90A HMAC-DRBG • Continuous RNG test on the NDRNG • Pairwise consistency test when generating DSA, ECDSA, and RSA key pairs. • Firmware Load Test (ECDSA P-256 with SHA-256 or RSA 2048 with SHA-1 signature verification) 5 Physical Security Policy The module’s physical embodiment is that of a multi-chip embedded device that meets Level 2 Physical Security requirements. The module is completely enclosed in a rectangular brushed aluminum enclosure. There are no ventilation holes, gaps, slits, cracks, slots, or crevices that would allow for any sort of observation of any component contained within the cryptographic boundary. Tamper-evident seals allow the operator to tell if the enclosure has been breached. These seals are not factory-installed and must be applied by the Cryptographic Officer. (Seals are available for order from Juniper using part number JNPR-FIPS-TAMPER-LBLS.) The tamper-evident seals shall be installed for the module to operate in a FIPS mode of operation. Copyright Juniper, 2016 Version 1.1 Page 16 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). The Cryptographic Officer is responsible for securing and having control at all times of any unused seals and the direct control and observation of any changes to the module such as reconfigurations where the tamper-evident seals or security appliances are removed or installed to ensure the security of the module is maintained during such changes and the module is returned to a FIPS Approved state. Table 12 – Physical Security Inspection Guidelines Physical Security Mechanism Recommended Frequency of Inspection/Test Inspection/Test Guidance Details Tamper seals, opaque metal enclosure. Once per month by the Cryptographic Officer. Seals should be free of any tamper evidence. 5.1 General Tamper Seal Placement and Application Instructions For all seal applications, the Cryptographic Officer should observe the following instructions: • Handle the seals with care. Do not touch the adhesive side. • Before applying a seal, ensure the location of application is clean, dry, and clear of any residue. • Place the seal on the module, applying firm pressure across it to ensure adhesion. Allow at least 1 hour for the adhesive to cure. Four (4) tamper seals must be applied as depicted below. Figure 3: Tamper-Evident Seal Placement Copyright Juniper, 2016 Version 1.1 Page 17 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). 6 Security Rules and Guidance The module design corresponds to the security rules below. The term must in this context specifically refers to a requirement for correct usage of the module in the Approved mode; all other statements indicate a security rule implemented by the module. 1. The module clears previous authentications on power cycle. 2. When the module has not been placed in a valid role, the operator does not have access to any cryptographic services. 3. Power up self-tests do not require any operator action. 4. Data output is inhibited during key generation, self-tests, zeroization, and error states. 5. Status information does not contain CSPs or sensitive data that if misused could lead to a compromise of the module. 6. There are no restrictions on which keys or CSPs are zeroized by the zeroization service. 7. The module does not support a maintenance interface or role. 8. The module does not support manual key entry. 9. The module does not output intermediate key values. 10. The module requires two independent internal actions to be performed prior to outputting plaintext CSPs. 11. The cryptographic officer must determine whether firmware being loaded is a legacy use of the firmware load service. 12. The cryptographic officer must retain control of the module while zeroization is in process. 7 References and Definitions The following standards are referred to in this Security Policy. Table 13 – References Abbreviation Full Specification Name [FIPS140-2] Security Requirements for Cryptographic Modules, May 25, 2001 [SP800-131A] Transitions: Recommendation for Transitioning the Use of Cryptographic Algorithms and Key Lengths, January 2011 [IG] Implementation Guidance for FIPS PUB 140-2 and the Cryptographic Module Validation Program Table 14 – Acronyms and Definitions Acronym Definition AES Advanced Encryption Standard DH Diffie-Hellman DSA Digital Signature Algorithm Copyright Juniper, 2016 Version 1.1 Page 18 of 18 Juniper Networks Public Material – May be reproduced only in its original entirety (without revision). Acronym Definition ECDH Elliptic Curve Diffie-Hellman ECDSA Elliptic Curve Digital Signature Algorithm EMC Electromagnetic Compatibility ESP Encapsulating Security Payload FIPS Federal Information Processing Standard HMAC Keyed-Hash Message Authentication Code ICV Integrity Check Value (i.e. Tag) IKE Internet Key Exchange Protocol IOC Input/Output Card IPsec Internet Protocol Security MD5 Message Digest 5 NPC Network Processing Card RE Routing Engine RSA Public-key encryption technology developed by RSA Data Security, Inc. SHA Secure Hash Algorithms SPC Services Processing Card SSH Secure Shell Triple-DES Triple - Data Encryption Standard Table 15 – Datasheet Model Title URL LN1000- V LN1000 Mobile Secure Router https://www.juniper.net/assets/us/en/local/pdf/datasheets/1000285- en.pdf