Juniper EX4300 Admin Guide

Verifying Secure Delivery of the Product on page 6

•

•

Applying Tamper-Evident Seals to Switch Management Ports for FIPS Mode on page 7

•

Understanding FIPS Mode Terminology and Supported Cryptographic

Algorithms on page 10

•

Understanding Zeroization to Clear System Data for FIPS Mode on page 13

•

Understanding FIPS Self-Tests on page 14

•

Understanding FIPS Error States and System Panic on page 15

•

Understanding Roles and Services for Junos OS in FIPS Mode on page 17

•

Understanding the Operational Environment for Junos OS in FIPS Mode on page 19

•

Understanding Requirements for Secure Communication Between Routing Engines in

Understanding Password Specifications and Guidelines for Junos OS in FIPS

•

Mode on page 24

•

Understanding Remote Access for Junos OS in FIPS Mode on page 25

•

Understanding Event Logging for Junos OS in FIPS Mode on page 25

•

Understanding Configuration Limitations and Restrictions on Junos OS in FIPS

Mode on page 26

•

How to Enable and Configure Junos OS in FIPS Mode—Overview on page 28

Understanding Junos OS in FIPS Mode

Federal Information Processing Standards (FIPS) 140-2 defines security levels for hardware and software that perform cryptographic functions. By meeting the applicable overall requirements within the FIPS standard, Juniper Networks EX Series Ethernet switches running the Juniper Networks Junos operating system (Junos OS) in FIPS mode comply with the FIPS 140-2 Level 1 standard.

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

Operating EX Series Ethernet switches in a FIPS 140-2 Level 1 environment requires enabling and configuring FIPS mode on the switches from the Junos OS CLI.

The Crypto Officer enables FIPS mode in Junos OS and sets up keys and passwords for the system and other FIPS users who can view the configuration. Both user types can also perform normal configuration tasks on the switch (such as modify interface types) as individual user configuration allows.

BEST PRACTICE: Be sure to verify the secure delivery of your switch and apply tamper-evident seals to its vulnerable ports.

•

About the Cryptographic Boundary on Your EX Series Switch on page 4

•

Validated Version of Junos OS in FIPS Mode

Juniper Networks submits one Junos OS release per year—Junos OS Release 14.1X53-D30, for example—to the National Institute of Standards and Technology (NIST) for validation.

To determine whether a Junos OS release is NIST-validated, see the software download page on the Juniper Networks Web site ( http://www.juniper.net/ ) or the National Institute of Standards and Technology site.

How to Use FIPS Documentation

For configuration and operational tasks that are specific to FIPS mode on EX Series switches, be sure to use the documentation for Junos OS in FIPS mode. Do not use the documentation for Junos-FIPS statements and commands because the syntax and options might not apply to FIPS mode.

For Junos OS configuration and operational tasks that are not specific to FIPS mode, see other EX Series hardware and software documentation at http://www.juniper.net/techpubs/en_US/release-independent/information-products/pathway-pages/ex-series/product/index.html

Documentation

•

Verifying Secure Delivery of the Product on page 6

•

Applying Tamper-Evident Seals to Switch Management Ports for FIPS Mode on page 7

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

Verifying Secure Delivery of the Product

Use the following checklists to verify the secure delivery of your Juniper Networks product:

•

Verifying Product Integrity on page 6

•

Verifying Product Authenticity on page 6

Verifying Product Integrity

To ensure that you received a product that was not tampered with, perform the following checks upon receipt of your Juniper Networks product to verify its integrity:

• Shipping label—Ensure that the shipping label correctly identifies your correct customer name and address as well as the Juniper Networks product you ordered.

• Outside packaging—Inspect the outside shipping box and tape. Ensure that the shipping tape has not been cut or otherwise compromised. Ensure that the box has not been cut or damaged to allow access to the product.

• Inside packaging—Inspect the plastic bag and seal. Ensure that the bag is not cut or removed. Ensure that the seal is intact.

If you identify a problem during the inspection, immediately contact the supplier and provide the order number, tracking number, and a description of the problem.

Verifying Product Authenticity

Perform the following checks upon receipt of your Juniper Networks product to verify its authenticity:

• Verify that the product was ordered using a purchase order. Juniper Networks products are never shipped without a purchase order.

• When a product is shipped, a shipment notification is sent to the e-mail address provided by the customer when the order is taken. Verify that this e-mail notification was received. Verify that the e-mail contains the following information:

• Purchase order number

• Juniper Networks order number used to track the shipment

• Carrier tracking number used to track the shipment

• List of items shipped, including serial numbers

• Address and contacts of both the supplier and the customer

• Perform the following additional checks to ensure that the box you received was sent by Juniper Networks and not a different company masquerading as Juniper Networks.

To verify that a shipment was initiated by Juniper Networks:

• Compare the carrier tracking number of the Juniper Networks order number listed in the Juniper Networks shipping notification with the tracking number on the package you received.

Chapter 1: Junos OS in FIPS Mode Overview—Environment and Requirements

• Log in to the Juniper Networks online customer support portal at https://www.juniper.net/customers/csc/management to view the order status.

Documentation

•

Applying Tamper-Evident Seals to Switch Management Ports for FIPS Mode on page 7

Applying Tamper-Evident Seals to Switch Management Ports for FIPS Mode

Adhesive seals applied to management ports and Virtual Chassis ports (VCPs) help secure an EX Series switch. Any damage to a seal provides evidence of physical tampering with the FIPS cryptographic module. Tamper-evident seals are shipped with your switch.

As Crypto Officer, you are responsible for applying the seals to secure the cryptographic module, controlling any unused seals, and directly controlling and observing any changes—such as repairs or booting from an external USB drive—to the cryptographic module that require removing or replacing the seals to maintain the security of the module.

•

General Tamper-Evident Seal Instructions on page 7

•

EX4300 Switch Tamper-Evident Seal Application on page 7

General Tamper-Evident Seal Instructions

All FIPS-certified switches require tamper-evident seals on USB ports. In addition, ports that are pre-configured as VCP ports also require tamper-evident seals. (For details, see the specific instructions for your switch.) While applying seals, follow these general instructions:

• Handle the seals with care. Do not touch the adhesive side. Do not cut or otherwise resize a seal to make it fit.

• Make sure all surfaces to which the seals are applied are clean and dry and clear of any residue.

• Apply the seals with firm pressure across the seal to ensure adhesion. Allow at least

1 hour for the adhesive to cure.

EX4300 Switch Tamper-Evident Seal Application

Apply tamper-evident seals to all USB and mini-USB ports to secure the EX4300 cryptographic module. USB ports are located on the front panel of the chassis, and mini-USB ports are located on the rear panel of the chassis.

See

Figure 1 on page 8

for placement of tamper-evident seals on the USB port of an

EX4300 switch with 24 ports.

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

Figure 1: EX4300 Tamper-Evident Seal Location—Front Panel of a 24-Port

EX4300 Switch

See

Figure 2 on page 8

for placement of tamper-evident seals on the mini-USB port of an EX4300 switch with 24 ports.

NOTE: For EX4300 switches with 4 QSFP+ ports, continue the procedure until all ports are converted.

Documentation

•

Understanding the Operational Environment for Junos OS in FIPS Mode on page 19

•

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

Understanding FIPS Mode Terminology and Supported Cryptographic Algorithms

Use the definitions of FIPS terms and supported algorithms to help you understand Junos

OS in FIPS mode.

•

FIPS Terminology on page 10

•

Supported Cryptographic Algorithms on page 12

FIPS Terminology

Critical security parameter (CSP) —Security-related information—for example, secret and private cryptographic keys and authentication data such as passwords and personal identification numbers (PINs)—whose disclosure or modification can compromise the security of a cryptographic module or the information it protects. For details, see

“Understanding the Operational Environment for Junos OS in FIPS Mode” on page 19 .

Cryptographic module —The set of hardware, software, and firmware that implements approved security functions (including cryptographic algorithms and key generation) and is contained within the cryptographic boundary. EX Series switches are certified at FIPS 140-2 Level 1. For fixed-configuration switches, the cryptographic module is the switch case. For modular switches, the cryptographic module is the Routing

Engine.

Crypto Officer —Person with appropriate permissions who is responsible for securely enabling, configuring, monitoring, and maintaining Junos OS in FIPS mode on a switch.

For details, see

“Understanding Roles and Services for Junos OS in FIPS Mode” on page 17

ESP —Encapsulating Security Payload (ESP) protocol. The part of the IPsec protocol that guarantees the confidentiality of packets through encryption. The protocol ensures that if an ESP packet is successfully decrypted, and no other party knows the secret key the peers share, the packet was not wiretapped in transit.

FIPS —Federal Information Processing Standards. FIPS 140-2 specifies requirements for security and cryptographic modules. Junos OS in FIPS mode complies with FIPS

140-2 Level 1.

FIPS maintenance role —The role the Crypto Officer assumes to perform physical maintenance or logical maintenance services such as hardware or software diagnostics. For FIPS 140-2 compliance, the Crypto Officer zeroizes the Routing

Engine on entry to and exit from the FIPS maintenance role to erase all plain-text secret and private keys and unprotected CSPs.

NOTE: The FIPS maintenance role is not supported on Junos OS in FIPS mode.

Chapter 1: Junos OS in FIPS Mode Overview—Environment and Requirements

Hashing —A message authentication method that applies a cryptographic technique iteratively to a message of arbitrary length and produces a hash “message digest” or “signature” of fixed length that is appended to the message when sent.

IKE —The Internet Key Exchange (IKE) is part of IPsec and provides ways to securely negotiate the shared private keys that the AH and ESP portions of IPsec need to function properly. IKE employs Diffie-Hellman key-exchange methods and is optional in IPsec. (The shared keys can be entered manually at the endpoints.)

IPsec —The IP Security (IPsec) protocol. A standard way to add security to Internet communications. IPsec security association (SA) is required on the switch to enable internal communication between the Routing Engine and PFE.

An IPsec SA is required for fixed-configuration switches running Junos OS in FIPS mode because the Routing Engine communicates with system processes through logical connections; therefore, the switch requires an internal, manual IPsec SA to protect those logical communications when the switch is running in FIPS mode. By default design, the switch has some innate characteristics of a master switch in a

Virtual Chassis, and this use of logical communications is one such characteristic.

In a multimember Virtual Chassis, the master switch’s Routing Engine would send control messages to the Routing Engines of the other member switches by using those built-in logical communications. Do not configure a Virtual Chassis in FIPS mode. Note, however, that the IPsec SA is required on your single switch to protect the built-in logical connections.

NOTE: Virtual Chassis features are not supported in FIPS mode—they have not been tested by Juniper Networks. Do not configure a Virtual

Chassis in FIPS mode.

For more information, see

“Understanding Requirements for Secure Communication

Between Routing Engines in FIPS Mode” on page 22 .

KATs —Known answer tests. System self-tests that validate the output of cryptographic algorithms approved for FIPS and test the integrity of some Junos OS modules. For details, see

“Understanding FIPS Self-Tests” on page 14 .

SA —Security association (SA). A connection between hosts that allows them to communicate securely by defining, for example, how they exchange private keys. As

Crypto Officer, you must manually configure an internal SA on switches running

Junos OS in FIPS mode. All values, including the keys, must be statically specified in the configuration. On switches with more than one Routing Engine, the configuration must match on both ends of the connection between the Routing Engines. For communication to take place, each Routing Engine must have the same configured options, which need no negotiation and do not expire. For more information, see

“Understanding Requirements for Secure Communication Between Routing Engines in FIPS Mode” on page 22

SPI —Security parameter index (SPI). A numeric identifier used with the destination address and security protocol in IPsec to identify an SA. Because you manually

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS configure the SA for Junos OS in FIPS mode, the SPI must be entered as a parameter rather than derived randomly.

SSH —A protocol that uses strong authentication and encryption for remote access across a nonsecure network. SSH provides remote login, remote program execution, file copy, and other functions. It is intended as a secure replacement for rlogin , rsh , and rcp in a UNIX environment. To secure the information sent over administrative connections, use SSHv2 for CLI configuration. In Junos OS, SSHv2 is enabled by default, and SSHv1, which is not considered secure, is disabled.

Zeroization —Erasure of all CSPs and other user-created data on a switch before its operation as a FIPS cryptographic module—or in preparation for repurposing the switch for non-FIPS operation. The Crypto Officer can zeroize the system with a CLI operational command. For details, see

“Understanding Zeroization to Clear System

Data for FIPS Mode” on page 13

Supported Cryptographic Algorithms

Each implementation of an algorithm is checked by a series of known answer test (KAT) self-tests. Any self-test failure results in a FIPS error state.

BEST PRACTICE: For FIPS 140-2 compliance, use only FIPS-approved cryptographic algorithms In Junos OS in FIPS mode.

The following cryptographic algorithms are supported in FIPS mode. Symmetric methods use the same key for encryption and decryption, while asymmetric methods (preferred) use different keys for encryption and decryption.

AES —The Advanced Encryption Standard (AES), defined in FIPS PUB 197. The AES algorithm uses keys of 128, 192, or 256 bits to encrypt and decrypt data in blocks of

128 bits.

Diffie-Hellman —A method of key exchange across a nonsecure environment (such as the

Internet). The Diffie-Hellman algorithm negotiates a session key without sending the key itself across the network by allowing each party to pick a partial key independently and send part of that key to the other. Each side then calculates a common key value. This is a symmetrical method—keys are typically used only for a short time, discarded, and regenerated.

ECDH —Elliptic Curve Diffie-Hellman. A variant of the Diffie-Hellman key exchange algorithm that uses cryptography based on the algebraic structure of elliptic curves over finite fields. ECDH allows two parties, each having an elliptic curve public-private key pair, to establish a shared secret over an insecure channel. The shared secret can be used either as a key or to derive another key for encrypting subsequent communications using a symmetric key cipher.

ECDSA —Elliptic Curve Digital Signature Algorithm. A variant of the Digital Signature

Algorithm (DSA) that uses cryptography based on the algebraic structure of elliptic curves over finite fields. The bit size of the elliptic curve determines the difficulty of decrypting the key. The public key believed to be needed for ECDSA is about twice

Chapter 1: Junos OS in FIPS Mode Overview—Environment and Requirements the size of the security level, in bits. ECDSA using the P-256 curve can be configured under OpenSSH.

HMAC —Defined as “Keyed-Hashing for Message Authentication” in RFC 2104, HMAC combines hashing algorithms with cryptographic keys for message authentication.

For Junos OS in FIPS mode, HMAC uses the iterated cryptographic hash functions

SHA-1, SHA-256, and SHA-512 along with a secret key.

SHA-256 and SHA-512 —Secure hash algorithms (SHA) belonging to the SHA-2 standard defined in FIPS PUB 180-2. Developed by NIST, SHA-256 produces a 256-bit hash digest, and SHA-512 produces a 512-bit hash digest.

3DES ( 3des-cbc ) —Encryption standard based on the original Data Encryption Standard

(DES) from the 1970s that used a 56-bit key and was cracked in 1997. The more secure 3DES is DES enhanced with three multiple stages and effective key lengths of about 112 bits. For Junos OS in FIPS mode, 3DES is implemented with cipher block chaining (CBC).

Documentation

•

Understanding FIPS Self-Tests on page 14

•

Understanding Zeroization to Clear System Data for FIPS Mode on page 13

•

Understanding Requirements for Secure Communication Between Routing Engines in

When to Zeroize? on page 14

Understanding Zeroization to Clear System Data for FIPS Mode

Zeroization completely erases all configuration information on the Routing Engines, including all plain-text passwords, secrets, and private keys for SSH, local encryption, local authentication, and IPsec.

The Crypto Officer initiates the zeroization process by entering the request system zeroize

(FIPS) operational command from the CLI after enabling FIPS mode. Use of this command is restricted to the Crypto Officer. (To zeroize the system before enabling FIPS mode, use the request system zeroize media command.)

CAUTION: Perform system zeroization with care. After the zeroization process is complete, no data is left on the Routing Engine. The switch is returned to the factory default state, without any configured users or configuration files.

Zeroization can be time-consuming. Although all configurations are removed in a few seconds, the zeroization process goes on to overwrite all media, which can take considerable time depending on the size of the media.

•

Why Zeroize? on page 14

•

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

Why Zeroize?

Your switch is not considered a valid FIPS cryptographic module until all critical security parameters (CSPs) have been entered—or reentered—while the switch is in FIPS mode.

BEST PRACTICE: For FIPS 140-2 compliance, you must zeroize the system to remove sensitive information before disabling FIPS mode on the switch.

When to Zeroize?

As Crypto Officer, perform zeroization in the following situations:

• Before FIPS operation.

To prepare your switch for operation as a FIPS cryptographic module, perform zeroization after enabling FIPS mode and before FIPS operation.

• Before non-FIPS operation.

To begin repurposing your switch for non-FIPS operation, perform zeroization before disabling FIPS mode on the switch or loading Junos OS packages that do not include FIPS mode.

NOTE: Juniper Networks does not support installing non-FIPS software in a FIPS environment, but doing so might be necessary in certain test environments. Be sure to zeroize the system first.

• When a tamper-evident seal is disturbed.

If the seal on an insecure port has been tampered with, the system is considered to be compromised. After applying new tamper-evident seals to the appropriate locations, zeroize the system and set up new passwords and CSPs.

Documentation

•

•

•

Applying Tamper-Evident Seals to Switch Management Ports for FIPS Mode on page 7

•

Understanding FIPS Self-Tests

The cryptographic module enforces security rules to ensure that a switch running the

Juniper Networks Junos operating system (Junos OS) in FIPS mode meets the security requirements of FIPS 140-2 Level 1. To validate the output of cryptographic algorithms approved for FIPS and test the integrity of some system modules, the system performs the following series of known answer test (KAT) self-tests:

• kernel_kats —KAT for kernel cryptographic routines

• md_kats —KAT for libmd and libc

• openssl_kats —KAT for OpenSSL cryptographic implementation

Chapter 1: Junos OS in FIPS Mode Overview—Environment and Requirements

• quicksec_kats —KAT for QuickSec Toolkit cryptographic implementation

• ssh_ipsec_kats —KAT for SSH IPsec Toolkit cryptographic implementation

The KAT self-tests are performed automatically at startup and reboot, regardless of whether FIPS mode is enabled on the switch. Conditional self-tests are also performed automatically to verify digitally signed software packages, generated random numbers,

RSA and DSA key pairs, and manually entered keys.

If the KATs are completed successfully, the system log (syslog) file is updated to display the tests that were executed.

If the system fails a KAT, it writes the details to a system log file, enters FIPS error state

(panic), and reboots the switch.

The file show /var/log/messages command displays the system log.

Documentation

•

Understanding FIPS Error States and System Panic on page 15

Understanding FIPS Error States and System Panic

A switch operating Junos OS in FIPS mode has certain operational restrictions such as the ability to load only integrity-checked software files and use only FIPS-approved cryptographic algorithms. To ensure correct operation, the switch performs a series of

FIPS self-tests.

The switch performs additional tests as needed—for example, to ensure that randomly generated numbers are truly random and to verify manually entered keys (passwords).

If it fails a test, the switch enters a FIPS error state known as system panic .

When a low-level cryptographic function cannot complete for lack of memory or another resource, a memory allocation error occurs. This error does not result in system panic.

FIPS errors that occur early in the boot cycle can prevent the system from successfully starting up. For this reason, keep alternate boot media up to date.

For details, see:

•

FIPS System Panic on page 15

•

Memory Allocation Error on page 16

•

Error Recovery from Alternate Boot Media on page 16

FIPS System Panic

If a switch fails a FIPS self-test, the switch enters a FIPS error state known as system panic . The panic condition halts all cryptographic processing and stops all data output from the switch. To clear the FIPS error, the switch reboots, runs the FIPS self-tests, and if it passes all the tests, returns to normal operation.

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

If the switch fails a self-test during a reboot from panic mode, the system stops booting and attempts to reboot. If the reboot is unsuccessful, the switch attempts again to reboot, this time from available boot media.

During a system panic, only status messages are displayed on the console. For example, a FIPS error is logged as follows: panic: pid 5090 (fips-error), uid 0, FIPS error 5: cannot verify certificate

PackageCA

The reboot after panic displays the following error message on the console: savecore: reboot after panic: pid 5090 (fips-error), uid 0, FIPS error 5: cannot

verify certificate PackageCA

The following error states create a system panic:

NOTE: These errors have only an extremely small chance of occurring.

• The switch failed a known answer test (KAT).

• The random number is not random.

• Signature generation failed.

• Signature verification failed.

• Certificate verification failed.

• Encryption or decryption failed.

• An environment error occurred.

• An error occurred in a pair-wise conditional test.

Memory Allocation Error

A FIPS memory allocation error occurs when a low-level cryptographic function cannot finish processing for lack of memory or of another resource. This error causes the affected process to be terminated, but does not result in system panic.

FIPS memory failures are logged as follows:

Apr 15 23:08:15 shmoo /kernel: pid 6374 (fips-error), uid 0, FIPS error 9: RSA verify memory allocation failed

Terminating the process clears the error so that the process can be run again.

Error Recovery from Alternate Boot Media

An EX Series switch running Junos OS in FIPS mode performs KATs self-tests at startup.

If the switch fails a KAT, the boot process stops and the switch attempts to reboot. If the reboot is unsuccessful, the switch attempts again to reboot, this time from available boot media.

If the alternate media are not functional, the switch might not be able to start up at all.

In that case, the Crypto Officer must remove the tamper-evident seal from the USB port

Chapter 1: Junos OS in FIPS Mode Overview—Environment and Requirements and insert the removable boot media so that the system can boot normally and install

Junos OS.

However, if the seal is broken, the switch is no longer a FIPS cryptographic module. You as Crypto Officer must reinstall and reconfigure Junos OS and enable FIPS mode.

For this reason, be sure to keep the alternate media on the switch in a functional state by running the request system snapshot command after a successful upgrade.

Documentation

• Understanding System Snapshot on EX Series Switches

•

Applying Tamper-Evident Seals to Switch Management Ports for FIPS Mode on page 7

• request system snapshot

Understanding Roles and Services for Junos OS in FIPS Mode

The Juniper Networks Junos operating system (Junos OS) running in non-FIPS mode allows a wide range of capabilities for users, and authentication is identity-based. In contrast, the FIPS 140-2 standard defines two user roles: Crypto Officer and FIPS user .

These roles are defined in terms of Junos OS user capabilities.

All other user types defined for Junos OS in FIPS mode (operator, administrative user, and so on) must fall into one of the two categories: Crypto Officer or FIPS user. For this reason, user authentication in FIPS mode is role-based rather than identity-based.

In addition to their FIPS roles, both user types can perform normal configuration tasks on the switch as individual user configuration allows.

Crypto Officers and FIPS users perform all FIPS-mode-related configuration tasks and issue all statements and commands for Junos OS in FIPS mode. Crypto Officer and FIPS user configurations must follow the guidelines for Junos OS in FIPS mode.

For details, see:

•

Crypto Officer Role and Responsibilities on page 17

•

FIPS User Role and Responsibilities on page 18

•

What Is Expected of All FIPS Users on page 18

Crypto Officer Role and Responsibilities

The Crypto Officer is the person responsible for enabling, configuring, monitoring, and maintaining Junos OS in FIPS mode on a switch. The Crypto Officer securely installs Junos

OS on the switch, enables FIPS mode, establishes keys and passwords for other users and software modules, and initializes the switch before network connection.

BEST PRACTICE: We recommend that the Crypto Officer administer the system in a secure manner by keeping passwords secure and checking audit files.

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

The permissions that distinguish the Crypto Officer from other FIPS users are secret , security , maintenance , and control . For FIPS compliance, assign the Crypto Officer to a login class that contains all of these permissions. A user with the Junos OS maintenance permission can read files containing critical security parameters (CSPs).

NOTE: Junos OS in FIPS mode does not support the FIPS 140-2 maintenance

role, which is different from the Junos OS maintenance permission.

Among the tasks related to Junos OS in FIPS mode, the Crypto Officer is expected to:

• Set the initial root password.

• Reset user passwords for FIPS-approved algorithms during upgrades from Junos OS.

• Examine log and audit files for events of interest.

• Erase user-generated files and data on (zeroize) the switch.

FIPS User Role and Responsibilities

All FIPS users, including the Crypto Officer, can view the configuration. Only the user assigned as the Crypto Officer can modify the configuration.

The permissions that distinguish Crypto Officers from other FIPS users are secret , security , maintenance , and control . For FIPS compliance, assign the FIPS user to a class that contains none of these permissions.

FIPS users configure networking features on the switch and perform other tasks that are not specific to FIPS mode. FIPS users who are not Crypto Officers can perform reboots and view status output.

What Is Expected of All FIPS Users

All FIPS users, including the Crypto Officer, must observe security guidelines at all times.

All FIPS users must:

• Keep all passwords confidential.

• Store switches and documentation in a secure area.

• Deploy switches in secure areas.

• Check audit files periodically.

• Conform to all other FIPS 140-2 security rules.

• Follow these guidelines:

• Users are trusted.

• Users abide by all security guidelines.

• Users do not deliberately compromise security.

• Users behave responsibly at all times.

Chapter 1: Junos OS in FIPS Mode Overview—Environment and Requirements

Documentation

•

Configuring Crypto Officer and FIPS User Identification and Access on page 38

•

Understanding the Operational Environment for Junos OS in FIPS Mode

A Juniper Networks EX Series Ethernet Switch running the Juniper Networks Junos operating system (Junos OS) in FIPS mode forms a special type of hardware and software operational environment that is different from the environment of a switch in non-FIPS mode:

•

Hardware Environment for Junos OS in FIPS Mode on page 19

•

Software Environment for Junos OS in FIPS Mode on page 19

•

Critical Security Parameters on page 20

Hardware Environment for Junos OS in FIPS Mode

Junos OS in FIPS mode establishes a cryptographic boundary in the switch that no critical security parameters (CSPs) can cross using plain text. Each hardware component of the switch that requires a cryptographic boundary for FIPS 140-2 compliance is a separate cryptographic module.

For more information about the cryptographic boundary on your switch, see

“Understanding Junos OS in FIPS Mode” on page 3 .

An EX Series switch with redundant Routing Engines contains two separate cryptographic modules. Communications involving CSPs between these secure environments must take place using encryption.

BEST PRACTICE: We recommend that you, as Crypto Officer, apply tamper-evident seals to the USB port on all switches to adequately secure the cryptographic module. For details, see

“Applying Tamper-Evident Seals to Switch Management Ports for FIPS Mode” on page 7 .

If a seal is tampered with, the cryptographic module is considered to be compromised. To restore the module, we recommend that you apply new tamper-evident seals, zeroize the system, and set up new passwords and

CSPs.

Cryptographic methods are not a substitute for physical security. The hardware must be located in a secure physical environment. Users of all types must not reveal keys or passwords, or allow written records or notes to be seen by unauthorized personnel.

Software Environment for Junos OS in FIPS Mode

An EX Series switch running Junos OS in FIPS mode forms a special type of nonmodifiable operational environment. To achieve this environment on the switch, the system prevents the execution of any binary file that was not part of the certified Junos OS distribution.

When a switch is in FIPS mode, it can run only Junos OS.

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

FIPS mode on EX Series switches is available starting with Junos OS Release 14.1X53-D30.

The Junos OS in FIPS mode software environment is established after the Crypto Officer successfully enables FIPS mode on an EX Series switch. The Junos OS Release

14.1X53-D30 image that includes FIPS mode is available on the Juniper Networks website and can be installed on an EX Series switch.

For FIPS 140-2 compliance, we recommend deleting all user-created files and data from

( zeroizing ) the system immediately after enabling FIPS mode.

NOTE: Do not attach the switch to a network until you, the Crypto Officer, complete the configuration from the local console connection.

Critical Security Parameters

Critical security parameters (CSPs) are security-related information such as cryptographic keys and passwords that can compromise the security of the cryptographic module or the security of the information protected by the module if they are disclosed or modified.

Zeroization of the system erases all traces of CSPs in preparation for operating the switch or Routing Engine as a cryptographic module.

Table 5 on page 21

lists CSPs on switches running Junos OS.

Chapter 1: Junos OS in FIPS Mode Overview—Environment and Requirements

Table 5: Critical Security Parameters

CSP Description Zeroize

SSH-2 private host key

ECDSA key used to identify the host, generated the first time SSH is configured.

Zeroize command.

SSH-2 session key Session key used with SSH-2. and as a

Diffie-Hellman private key.

Encryption: 3DES, AES-128, AES-192,

AES-256.

MACs: HMAC-SHA-1, HMAC SHA1-96, HMAC

SHA-256, HMAC SHA-512.

Key exchange: DH Group exchange (2048 ≤ key ≤ 8192), ECDH Prime curve NID_secp521r1

(NIST Curve P-521).

Power cycle and terminate session.

User authentication key

Hash of the user’s password: SHA-1, SHA-256,

SHA-512.

Zeroize command.

Crypto Officer authentication key

Hash of the Crypto Officer’s password: SHA-1,

SHA-256, SHA-512.

Zeroize command.

Use

Used to identify the host.

Symmetric key used to encrypt data between host and client.

Used to authenticate a user to the cryptographic module.

Used to authenticate the

Crypto Officer to the cryptographic module.

Used to authenticate the

RE-to-RE IPSec connection.

RE-to-RE authentication key

HMAC key (manual IPsec SA):

HMAC-SHA1-96 (20 bit), HMAC-SHA-256

(32-bit).

RE-to-RE encryption key

TDES key (manual IPsec SA).

Zeroize/explicitly delete command.

Used in IPSec connection between REs.

HMAC DRBG seed Seed for deterministic random bit generator

(DRBG).

Seed is not stored by the cryptographic module.

Used for seeding DRBG.

A critical value of the internal state of DRBG.

HMAC DRBG V value The value (V) of output block length (outlen) in bits, which is updated each time another outlen bits of output are produced.

Power cycle.

HMAC DRBG key value

NDRNG entropy

The current value of the outlen-bit key, which is updated at least once each time that the

DRBG mechanism generates pseudorandom bits.

Power cycle.

Used as entropy input string to the HMAC

DRBG.

Power cycle.

A critical value of the internal state of DRBG.

In Junos OS in FIPS mode, all CSPs must enter and leave the cryptographic module in encrypted form. Any CSP encrypted with a non-approved algorithm is considered plain text by FIPS. However, as the Crypto Officer, you can enter user authentication data in plain text. During initial configuration, you can also enter the IP Security (IPsec) keys for communication between internal Routing Engines or for logical communications between

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS the Routing Engine and system processes in plain text on the console port (under manual key entry rules).

BEST PRACTICE: For FIPS compliance, configure the switch over SSH connections because they are encrypted connections.

Local passwords are encrypted with the secure hash algorithm SHA-1, SHA-256, or

SHA-512. Password recovery is not possible in Junos OS in FIPS mode. Junos OS in FIPS mode cannot boot into single-user mode without the correct root password.

Documentation

•

Understanding Requirements for Secure Communication Between Routing Engines in

Understanding FIPS Mode Terminology and Supported Cryptographic Algorithms on page 10

•

•

Understanding Password Specifications and Guidelines for Junos OS in FIPS Mode on page 24

•

Understanding Zeroization to Clear System Data for FIPS Mode on page 13

•

Understanding Configuration Limitations and Restrictions on Junos OS in FIPS Mode on page 26

•

Applying Tamper-Evident Seals to Switch Management Ports for FIPS Mode on page 7

Understanding Requirements for Secure Communication Between Routing Engines in

FIPS Mode

The internal IPsec SA provides a secure way to mutually authenticate and encrypt communications between Routing Engines.

The cryptographic boundary on a modular switch is the Routing Engine. For this reason,

EX9204, EX9208, and EX9214 switches with dual (redundant) Routing Engines require an internal, manual IP Security (IPsec) security association (SA) configured on each

Routing Engine for the Routing Engines to communicate with each other. The Crypto

Officer must use the console of each Routing Engine to configure the IPsec SA. Only four parameters are required: SA direction, security parameter index (SPI), a key value for authentication, and a key value for encryption. The SAs must be identical. All values, including the keys, must be statically specified in the configuration and must match on both ends of the connection. For communication to take place, each Routing Engine must have the same configured options.

For details, see:

•

SA Direction on page 23

•

SPI on page 23

•

IPsec Keys on page 23

•

IPsec Limitations on page 23

Chapter 1: Junos OS in FIPS Mode Overview—Environment and Requirements

SA Direction

The internal, manual IPsec security association (SA) established by you, the Crypto

Officer, on a Routing Engine can have the same SPI, authentication key, and encryption key for inbound and outbound communication, or one set of values for the inbound tunnel and another set for the outbound tunnel:

• Bidirectional—Apply the same SA values in both directions between Routing Engines.

• Inbound—Apply the SA values only to the inbound IPsec tunnel.

• Outbound—Apply the SA values only to the outbound IPsec tunnel.

If you do not configure the SA to be bidirectional, you must configure two unidirectional

IPsec tunnels, one in each direction.

NOTE: We do not recommend the use of unidirectional IPsec tunnels.

SPI

The security parameter index (SPI) is an arbitrary value between 256 and 16639 that uniquely identifies the SA to use at the receiving Routing Engine. The sending Routing

Engine uses the SPI to identify and select the SA it uses to secure every packet. The receiving Routing Engine uses the SPI to identify and select the encryption algorithm and key it uses to decrypt packets.

IPsec Keys

The internal, manual IPsec SA established by you, the Crypto Officer, on a Routing Engine requires an authentication key with a minimum message digest length of 20 bytes, as well as an encryption key. For this type of SA, we recommend you create preshared keys in hexadecimal format, for maximum key strength. Each key requires a specific cryptographic algorithm:

• Authentication algorithm

• HMAC-SHA-256 (64 hexadecimal characters)

• Encryption algorithm

• 3DES-CBC (48 hexadecimal characters)

You use the configuration mode command prompt to enter the value for each key twice.

If the two entries do not match, the key is not set.

IPsec Limitations

On a switch with Junos OS in FIPS mode enabled, you cannot configure IPsec SAs to use the IPsec Authentication Header (AH) protocol or the Data Encryption Standard (DES) encryption algorithm. Instead, you must use the Encapsulating Security Payload (ESP) protocol for both encryption and authentication and the 3DES-CBC algorithm for encryption.

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

Documentation

•

Understanding FIPS Mode Terminology and Supported Cryptographic Algorithms on page 10

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

• For more information about IPsec, see the Junos OS System Basics Configuration Guide.

Understanding Password Specifications and Guidelines for Junos OS in FIPS Mode

Ensure that the switch is in FIPS mode before you configure the Crypto Officer or any users. All passwords established for users by the Crypto Officer must conform to the following Junos OS in FIPS mode requirements. Attempts to configure passwords that do not conform to the following specifications result in an error.

• Length.

Passwords must contain between 10 and 20 characters.

• Character set requirements.

Passwords must contain at least three of the following five defined character sets:

• Uppercase letters

• Lowercase letters

• Digits

• Punctuation marks

• Keyboard characters not included in the other four sets—such as the percent sign

(%) and the ampersand (&)

• Authentication requirements.

All passwords and keys used to authenticate peers must contain at least 10 characters, and in some cases the number of characters must match the digest size—for example, 20 characters for SHA-1 authentication. For a list of supported cryptographic algorithms (ciphers), see

“Understanding FIPS Mode

Terminology and Supported Cryptographic Algorithms” on page 10

Guidelines for strong passwords.

Strong, reusable passwords can be based on letters from a favorite phrase or word and then concatenated with other unrelated words, along with added digits and punctuation. In general, a strong password is:

• Easy to remember so that users are not tempted to write it down.

• Made up of mixed alphanumeric characters and punctuation. For FIPS compliance include at least one change of case, one or more digits, and one or more punctuation marks.

• Changed periodically.

• Not divulged to anyone.

Characteristics of weak passwords.

Do not use the following weak passwords:

• Words that might be found in or exist as a permuted form in a system files such as

/etc/passwd .

• The hostname of the system (always a first guess).

Chapter 1: Junos OS in FIPS Mode Overview—Environment and Requirements

• Any word or phrase that appears in a dictionary or other well-known source, including dictionaries and thesauruses in languages other than English; works by classical or popular writers; or common words and phrases from sports, sayings, movies or television shows.

• Permutations on any of the above—for example, a dictionary word with letters replaced with digits ( root ) or with digits added to the end.

• Any machine-generated password. Algorithms reduce the search space of password-guessing programs and so must not be used.

Documentation

•

Understanding FIPS Mode Terminology and Supported Cryptographic Algorithms on page 10

•

Understanding the Operational Environment for Junos OS in FIPS Mode on page 19

Understanding Remote Access for Junos OS in FIPS Mode

When the switch is in Junos OS in FIPS mode, only SSH is available as a remote access service. To secure the information sent on administrative connections, use SSHv2 for CLI configuration. For SSH configuration information, see the Junos OS System Basics

Configuration Guide.

BEST PRACTICE: For FIPS compliance, configure the switch over SSH connections because they are encrypted connections.

The Ethernet management (MGMT) port on the switch is disabled by default. To use the

MGMT port, you must enable the me0 interface and assign it an IP address if you have not already done so. For more information, see the Junos OS System Basics Configuration

Guide.

In Junos OS in FIPS mode, all critical security parameters (CSPs) must enter and leave the cryptographic module in encrypted form. Any CSP encrypted with a non-approved algorithm is considered plain text by FIPS. However, as the Crypto Officer, you can enter user authentication data in plain text. During initial configuration, you can also enter the

IP Security (IPsec) keys for communication between internal Routing Engines in plain text on the console port (under manual key entry rules).

Documentation

•

Understanding Configuration Limitations and Restrictions on Junos OS in FIPS Mode on page 26

• Junos OS System Basics and Services Command Reference

Understanding Event Logging for Junos OS in FIPS Mode

A secure Juniper Networks Junos operating system (Junos OS) environment requires the auditing of configuration changes through the system log (syslog).

In addition, if configuration changes are audited, Junos OS can:

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

• Send automated responses to audit events (system log entry creation).

• Allow the Crypto Officer to examine audit logs.

• Send audit files to external servers.

• Allow the Crypto Officer to return the system to a known state.

Event logging for Junos OS in FIPS mode must capture the following events:

• Changes to secret data in the configuration

• Committed changes

• Login and logout of users

• System startup and shutdown

BEST PRACTICE: We recommend that FIPS logging also include:

• Capturing all changes to the configuration

• Storing logging information remotely

Documentation

•

Configuring Event Logging for Junos OS in FIPS Mode on page 44

Understanding Configuration Limitations and Restrictions on Junos OS in FIPS Mode

In FIPS mode, an EX Series switch operates as a nonmodifiable operational environment in which only files shipped as part of Junos OS can be executed.

In contrast to non-FIPS mode, Junos OS in FIPS mode:

• Conforms to FIPS 140-2.

• Establishes a cryptographic boundary depending on the switch chassis type. On fixed-configuration chassis, the boundary is the switch case. On modular chassis, the boundary is the Routing Engine.

• Requires special installation procedures.

• Mandates the use of internal, manual IPsec tunnels with specific requirements.

• Limits services used for remote access.

• Allows only the use of approved ciphers.

• Requires user logout on disconnect at the console.

• Sets strict requirements for passwords.

• Requires special system logging considerations.

Chapter 1: Junos OS in FIPS Mode Overview—Environment and Requirements

• Disables the following Junos OS protocols and services so that you cannot configure them. Attempts to configure these services or to load configurations with these services configured result in a configuration syntax error.

• finger

• FTP

• rlogin

• rsh

• Telnet

• Trivial File Transfer Protocol (TFTP)

• Transport Layer Security (TLS) protocol

• xnm-clear-text

If you try to load a configuration that includes statements not supported by Junos OS in FIPS mode, you see a warning message. For example, suppose you attempt to configure Telnet for remote access:

[edit] crypto-officer@switch:fips# set system services telnet

You receive the following warning and cannot add the system services telnet statement to the loaded configuration:

[edit]

'telnet' warning: not allowed in JUNOS-FIPS; ignored

Documentation

•

Understanding Requirements for Secure Communication Between Routing Engines in

•

Understanding Remote Access for Junos OS in FIPS Mode on page 25

•

•

Understanding FIPS Mode Terminology and Supported Cryptographic Algorithms on page 10

•

Understanding Password Specifications and Guidelines for Junos OS in FIPS Mode on page 24

•

Understanding Event Logging for Junos OS in FIPS Mode on page 25

•

Understanding FIPS Error States and System Panic on page 15

•

Configuring the Console Port for FIPS Mode on page 43

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

How to Enable and Configure Junos OS in FIPS Mode—Overview

You, as Crypto Officer, can enable and configure Junos OS in FIPS mode on your EX Series switch.

Before you begin enabling and configuring FIPS mode on the switch:

• Verify the secure delivery of your switch. See

“Verifying Secure Delivery of the Product” on page 6

• Apply tamper-evident seals. See

“Applying Tamper-Evident Seals to Switch

Management Ports for FIPS Mode” on page 7

To enable and configure Junos OS in FIPS mode, perform the following tasks. Follow the links for instructions.

Install the Junos OS Release 14.1X53-D30 image, if you have not already done so. See

“Downloading and Installing Junos Software Packages (FIPS Mode)” on page 29 .

Disable non-CLI user interfaces.

Erase old passwords and rollback configurations and otherwise zeroize the system.

See

“Zeroizing the System (FIPS Mode)” on page 33 .

Establish root password access according to FIPS guidelines. See

“Establishing Root

Password Access (FIPS Mode)” on page 36

Enable FIPS mode, and commit. See

“Setting a Switch to FIPS Mode” on page 34

NOTE: On switches with multiple Routing Engines, ensure that you always use the commit synchronize command to commit configuration changes.

Set IPsec security association (SA) algorithms and keys. See

“Enabling Internal

Communications Between the RE and PFE (FIPS Mode)” on page 40 .

Configure local login authentication for Crypto Officer access and other FIPS users.

See

“Configuring Crypto Officer and FIPS User Identification and Access” on page 38 .

Configure the console port to log out automatically when you unplug the cable and require the root password for single-user mode. See

“Configuring the Console Port for FIPS Mode” on page 43 .

Configure FIPS logging to record events. See

“Configuring Event Logging for Junos OS in FIPS Mode” on page 44

After you as the Crypto Officer complete Junos OS in FIPS mode configuration, you can connect the switch to the network and proceed with normal configuration.

Documentation

•

Downloading and Installing Junos Software Packages (FIPS Mode) on page 29

CHAPTER 2

Enabling and Configuring Junos OS in FIPS

Mode

•

•

Downloading Software Packages from Juniper Networks (FIPS Mode) on page 30

•

Installing Software on an EX Series Switch with a Single Routing Engine (FIPS

Mode) on page 31

•

•

Establishing Root Password Access (FIPS Mode) on page 36

•

•

Configuring Crypto Officer and FIPS User Identification and Access on page 38

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

•

Configuring the Console Port for FIPS Mode on page 43

•

Configuring Event Logging for Junos OS in FIPS Mode on page 44

•

“Downloading Software Packages from Juniper Networks

Downloading and Installing Junos Software Packages (FIPS Mode)

EX Series Ethernet switches can provide the security defined by Federal Information

Processing Standards (FIPS) 140-2 Level 1 if these switches are operated in the Junos

OS in FIPS mode. To operate in Junos OS in FIPS mode, the switch must have the following software packages installed:

• Junos OS for EX Series switches, Release 14.1X53-D30

• Junos FIPS mode, Release 14.1X53-D30

To install these software packages, perform the following tasks:

Download the Junos OS package and the Junos FIPS mode package from http://www.juniper.net/ . See

(FIPS Mode)” on page 30 .

Connect locally to the console port of the active Routing Engine on the switch.

Copy the Junos OS and Junos FIPS mode software packages to the Routing Engine or Routing Engines. See the instructions that are appropriate for your switch:

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

•

Installing Software on an EX Series Switch with a Single Routing Engine (FIPS Mode) on page 31

Documentation

•

Installing Software on an EX Series Switch with a Single Routing Engine (FIPS Mode) on page 31

Downloading Software Packages from Juniper Networks (FIPS Mode)

You can download the following Junos OS software packages from the Juniper Networks website:

• Junos OS for EX Series switches, Release 14.1X53-D30

• Junos FIPS mode, Release 14.1X53-D30

Before you begin to download the software, ensure that you have a Juniper Networks

Web account and a valid support contract. To obtain an account, complete the registration form at the Juniper Networks website: https://www.juniper.net/registration/Register.jsp

To download software packages from Juniper Networks:

Using a Web browser, follow the links to the download URL on the Juniper Networks webpage. For EX Series, because separate software packages are not provided for different locations, select Canada and U.S. Version regardless of your location: https://www.juniper.net/support/downloads/junos.html

Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.

Select the appropriate software package:

• For Junos OS package, ensure that the name contains the correct switch name and number of the Junos OS release that is FIPS-certified on the switches.

For example, jinstall-ex-4300-14.1X53-D30.3-domestic-signed.tgz

NOTE: domestic-signed is appended to all EX Series package names.

Although other Juniper Networks platforms use a domestic package for the United States and Canada and an export package for worldwide distribution, EX Series switches use domestic for both domestic and worldwide distribution.

• For the Junos FIPS mode package, select fips-mode-i386-14.1X53-D30.2-signed.tgz

Download the software to a local host or to an internal software distribution site.

Install the Junos OS and Junos FIPS mode packages. See

“Installing Software on an

EX Series Switch with a Single Routing Engine (FIPS Mode)” on page 31 .

Documentation

•

Installing Software on an EX Series Switch with a Single Routing Engine (FIPS Mode) on page 31

Chapter 2: Enabling and Configuring Junos OS in FIPS Mode

Installing Software on an EX Series Switch with a Single Routing Engine (FIPS Mode)

You can use this procedure to upgrade Junos OS on an EX Series switch with a single

Routing Engine.

To install software upgrades on a switch with a single Routing Engine:

Download the software package as described in

“Downloading Software Packages from Juniper Networks (FIPS Mode)” on page 30

If you have not already done so, connect to the console port on the switch from your management device, and log in to the Junos OS CLI. (For instructions, see Connecting and Configuring an EX Series Switch (CLI Procedure) .)

(Optional) Back up the current software configuration to a second storage option.

See the Junos OS Installation and Upgrade Guide for instructions on performing this task.

(Optional) Copy the software package to the switch. We recommend that you use

FTP to copy the file to the /var/tmp/ directory.

This step is optional because Junos OS can also be upgraded when the software image is stored at a remote location. These instructions describe the software upgrade process for both scenarios.

Install the new package on the switch: user@switch> request system software add package

Replace package with one of the following paths:

• For a software package in a local directory on the switch, use /var/tmp/ package .tgz

• For a software package on a remote server, use one of the following paths, replacing package with the software package name—for example, jinstall-ex-4300-14.1X53-D30.3-domestic-signed.tgz

(see

“Downloading Software

Packages from Juniper Networks (FIPS Mode)” on page 30

• ftp:// hostname / pathname / package .tgz

• http:// hostname / pathname / package .tgz

NOTE: If you need to terminate the installation, do not reboot your switch; instead, finish the installation and then issue the request system software delete package .tgz

command, where package .tgz

is, for example, jinstall-ex-4300-14.1X53-D30.3-domestic-signed.tgz

. This is your last chance to stop the installation.

Reboot the switch to load the installation and start the new software: user@switch> request system reboot

After the reboot has completed, log in and use the show version command to verify that the new version of the software is successfully installed. If you installed the Junos

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

FIPS mode package, verify that the FIPS mode utilities are present—as shown in the following example: user@switch> show version fpc0:

--------------------------------------------------------------------------

Hostname: switch

Model: ex4300

Junos: 14.1X53-D30

JUNOS Base OS boot [14.1X53-D30]

JUNOS Base OS Software Suite [14.1X53-D30]

JUNOS 64-bit Kernel Software Suite [14.1X53-D30]

JUNOS Crypto Software Suite [14.1X53-D30]

JUNOS Packet Forwarding Engine Support (M/T/EX Common) [14.1X53-D30]

JUNOS Packet Forwarding Engine Support (EX4300) [14.1X53-D30]

JUNOS Online Documentation [14.1X53-D30]

JUNOS Services AACL Container package [14.1X53-D30]

JUNOS Services Application Level Gateways [14.1X53-D30]

JUNOS AppId Services [14.1X53-D30]

JUNOS Border Gateway Function package [14.1X53-D30]

JUNOS Services Captive Portal and Content Delivery Container package

[14.1X53-D30]

JUNOS Services HTTP Content Management package [14.1X53-D30]

JUNOS IDP Services [14.1X53-D30]

JUNOS Services Jflow Container package [14.1X53-D30]

JUNOS Services LL-PDF Container package [14.1X53-D30]

JUNOS Services MobileNext Software package [14.1X53-D30]

JUNOS Services Mobile Subscriber Service Container package [14.1X53-D30]

JUNOS Services NAT [14.1X53-D30]

JUNOS Services PTSP Container package [14.1X53-D30]

JUNOS Services RPM [14.1X53-D30]

JUNOS Services Stateful Firewall [14.1X53-D30]

JUNOS Voice Services Container package [14.1X53-D30]

JUNOS Services Crypto [14.1X53-D30]

JUNOS Services SSL [14.1X53-D30]

JUNOS Services IPSec [14.1X53-D30]

JUNOS platform Software Suite [14.1X53-D30]

JUNOS Routing Software Suite [14.1X53-D30]

JUNOS Runtime Software Suite [14.1X53-D30]

JUNOS 64-bit Runtime Software Suite [14.1X53-D30]

JUNOS py-base-i386 [14.1X53-D30]

JUNOS FIPS mode utilities [14.1X53-D30]

Documentation

• Troubleshooting Software Installation

• Understanding Software Installation on EX Series Switches

Chapter 2: Enabling and Configuring Junos OS in FIPS Mode

Zeroizing the System (FIPS Mode)

Your switch is not considered a valid FIPS cryptographic module until all critical security parameters (CSPs) have been entered—or reentered—while the switch is in FIPS mode.

For FIPS 140-2 compliance, you must zeroize the system to remove sensitive information before disabling FIPS mode on the switch.

As Crypto Officer, you run the request system zeroize command to remove all user-created files from a switch and replace the user data with zeros. This command completely erases all configuration information on the Routing Engines, including all rollback configuration files and plain-text passwords, secrets, and private keys for SSH, local encryption, local authentication, and IPsec.

To zeroize your switch:

From the CLI, enter root@switch> request system zeroize warning: System will be rebooted and may not boot without configuration

Erase all data, including configuration and log files? [yes, no] (no)

To initiate the zeroization process, type yes at the prompt:

Erase all data, including configuration and log files? [yes, no] (no) yes re1:

-------------------------------------------------------------------------warning: zeroizing re1 warning: zeroizing re0

...

Rebooting after scrubbing memory...

...

The entire operation can take considerable time depending on the size of the media, but all critical security parameters (CSPs) are removed within a few seconds. The physical environment must remain secure until the zeroization process is complete.

When the system finishes rebooting and performing FIPS self-tests, proceed with

FIPS configuration.

• Go on to

“Establishing Root Password Access (FIPS Mode)” on page 36 .

Documentation

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

•

•

Understanding Zeroization to Clear System Data for FIPS Mode on page 13

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

Setting a Switch to FIPS Mode

FIPS mode is not automatically enabled when you install Junos OS on the switch.

As Crypto Officer, you must explicitly enable FIPS mode on the switch by setting the FIPS level to 1 (one), the FIPS 140-2 level at which EX Series switches are certified. A switch on which FIPS mode is not enabled has a FIPS level of 0 (zero).

NOTE: To transition to FIPS mode, passwords must be encrypted with a

FIPS-compliant hash algorithm. The encryption format must be SHA-1 or higher. Passwords that do not meet this requirement, such as passwords that are hashed with MD5, must be reconfigured or removed from the configuration before FIPS mode can be enabled.

To enable FIPS mode in Junos OS on the switch:

Enter configuration mode: root@switch> configure

Entering configuration mode

[edit] root@switch#

Enable FIPS mode on the switch by setting the FIPS level to 1, and verify the level:

[edit] root@switch# set system

fips level

[edit] root@switch# show system fips level level 1;

Commit the configuration:

NOTE: If the switch terminal displays error messages about the presence of critical security parameters (CSPs), delete those CSPs, and then commit the configuration.

For switches with multiple Routing Engines:

{master:0[edit security] root@switch# delete ipsec

{master:0}[edit security] root@switch# commit synchronize configuration check succeeds

[edit]

'system'

reboot is required to transition to FIPS level 1 commit complete

For switches with a single Routing Engine:

{master:0}[edit security] root@switch# delete ipsec

Chapter 2: Enabling and Configuring Junos OS in FIPS Mode

{master:0}[edit security] root@switch# commit configuration check succeeds

[edit]

'system'

reboot is required to transition to FIPS level 1 commit complete

Reboot the switch:

For switches with multiple Routing Engines:

[edit] root@switch# run request system reboot other-routing-engine

Reboot the system ? [yes,no] (no) yes

[edit] root@switch# run request system reboot

Reboot the system ? [yes,no] (no) yes

For switches with a single Routing Engine:

[edit] root@switch# run request system reboot

Reboot the system ? [yes,no] (no) yes

During the reboot, the switch runs Known Answer Tests (KATS). It returns a login prompt:

Verified jkernel-ex-14.1X53-D30-20141229.0 signed by PackageProduction_12_1_0

Mounted jpfe-ex42x package on /dev/md9...

...

Creating initial configuration...mgd: Running FIPS Self-tests mgd: Testing file integrity: mgd: File integrity Known Answer Test: Passed mgd: Testing crypto integrity: mgd: Crypto integrity Known Answer Test: Passed mgd: Testing kernel KATS: mgd: DES3-CBC Known Answer Test: Passed

...

mgd: FIPS Self-tests Passed mgd: commit complete

[edit system services]

'ftp'

warning: not allowed in FIPS mode; ignored

[edit system services]

'telnet'

warning: not allowed in FIPS mode; ignored

[edit system services]

'tftp'

warning: not allowed in FIPS mode; ignored mgd: commit complete

...

clean, 28550 free (22 frags, 3566 blocks, 0.0% fragmentation) switch (ttyu0) login:

--- JUNOS 14.1X53-D30-20141229.0 built 2014-12-29 04:12:22 UTC

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS root@switch:fips>

Documentation

•

•

“Understanding Password Specifications and Guidelines for Junos OS in FIPS Mode” on page 24

Establishing Root Password Access (FIPS Mode)

When Junos OS is installed on a switch and the switch is powered on, it is ready to be configured. Initially, you log in as the user root with no password. When you log in as root , your SSH connection is enabled by default.

As Crypto Officer, you must establish a root password conforming to the FIPS password requirements in

. When you enable FIPS mode in Junos OS on the switch, you cannot configure passwords unless they meet this standard.

Local passwords are encrypted with the secure hash algorithm SHA-1, SHA-256 or

SHA-512. Password recovery is not possible in Junos OS in FIPS mode. Junos OS in FIPS mode cannot boot into single-user mode without the correct root password.

After you log in, configure the root (superuser) password to be used to access the switch as follows:

% cli

— JUNOS 14.1X53-D30-20141229.0 built 2014-12-29 04:12:22 UTC root@switch:fips> configure

Entering configuration mode

[edit] root@switch:fips#

Chapter 2: Enabling and Configuring Junos OS in FIPS Mode

Change the password format to a FIPS-compliant hash algorithm:

NOTE: When establishing root password access after zeroization, the password format must be changed from the default of md5 . MD5 is not a FIPS-compliant hash algorithm.

Configure the FIPS-compliant hash algorithm for plain-text passwords by including the format statement at the [edit system login] hierarchy level and selecting sha1 , sha256 , or sha512 :

[edit] root@switch:fips# set system login format (sha1 | sha256 | sha512) b.

Configure a temporary root password in order to commit the password format change. This password will be hashed in the default format of MD5, and must be reset in Step 3.

Commit the configuration:

[edit] root@switch:fips# commit commit complete

Configure the root password by including the root-authentication statement at the

[edit system] hierarchy level and selecting one of the password options.

• To configure a plain-text password, select the plain-text-password option. Enter and confirm the password at the prompts.

[edit] root@switch:fips# set system root-authentication plain-text-password

New password: type password here

Retype new password: retype password here

Ensure that you follow the password guidelines in

“Understanding Password

Specifications and Guidelines for Junos OS in FIPS Mode” on page 24

• To configure public keys for SSH authentication of root logins, use the ssh-ecdsa option. You can configure more than one public key for SSH authentication of root logins and for user accounts. When a user logs in as root , the public keys are referenced to determine whether the private key matches any of them.

If you are finished configuring the switch, commit the configuration and exit:

[edit] root@switch:fips# commit commit complete root@switch:fips# exit root@switch:fips> exit

Otherwise, go on to

“Setting a Switch to FIPS Mode” on page 34 .

Documentation

•

Understanding Password Specifications and Guidelines for Junos OS in FIPS Mode on page 24

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

• For more information about the root password and root logins, see the Junos OS System

Basics Configuration Guide .

•

Understanding Remote Access for Junos OS in FIPS Mode on page 25

Configuring Crypto Officer and FIPS User Identification and Access

Crypto Officers and FIPS users perform all configuration tasks for Junos OS in FIPS mode and issue all Junos OS in FIPS mode statements and commands. Crypto Officer and FIPS user configurations must follow Junos OS in FIPS mode guidelines.

•

Configuring Crypto Officer Login Access on page 38

•

Configuring FIPS User Login Access on page 39

Configuring Crypto Officer Login Access

Junos OS in FIPS mode offers a finer granularity of user permissions than those mandated by FIPS 140-2.

For FIPS 140-2 compliance, any FIPS user with the secret , security , maintenance , and control permission bits set is a Crypto Officer. In most cases the super-user class suffices for the Crypto Officer.

To configure login access for a Crypto Officer:

Log in to the switch with the root password if you have not already done so, and enter configuration mode: root@switch:fips> configure

Entering configuration mode

[edit] root@switch:fips#

Name the user “crypto-officer” and assign the Crypto Officer a user ID (for example,

6400 ) and a class (for example, super-user ). When you assign the class, you assign the permissions—for example, secret , security , maintenance , and control .

For a list of permissions, see Understanding Junos OS Access Privilege Levels .

[edit] root@switch:fips# set system login user crypto-officer uid 6400 class super-user

Following the guidelines in

“Understanding Password Specifications and Guidelines for Junos OS in FIPS Mode” on page 24 , assign the Crypto Officer a plain-text password

for login authentication. Set the password by typing a password after the prompts

New password and Retype new password .

[edit] root@switch:fips# set system login user crypto-officer class super-user authentication plain-text-password

Optionally, display the configuration:

[edit] root@switch:fips# edit system

Chapter 2: Enabling and Configuring Junos OS in FIPS Mode

[edit system] root@switch:fips# show login { user crypto-officer { uid 6400; authentication { encrypted-password "$ABC123"; ## SECRET-DATA

} class super-user;

}

If you are finished configuring the switch, commit the configuration and exit:

[edit] root@switch:fips# commit commit complete root@switch:fips# exit root@switch:fips> exit

Otherwise, go on to

“Configuring FIPS User Login Access” on page 39

Configuring FIPS User Login Access

A fips-user is defined as any FIPS user that does not have the secret , security , maintenance , and control permission bits set.

As the Crypto Officer you set up FIPS users. FIPS users can be granted permissions normally reserved for the Crypto Officer—for example, permission to zeroize the system.

To configure login access for a FIPS user:

Log in to the switch with your Crypto Officer password if you have not already done so, and enter configuration mode: crypto-officer@switch:fips> configure

Entering configuration mode

[edit] crypto-officer@switch:fips#

Give the user a username, assign the FIPS user a user ID (for example, 6401 ) and a class (for example, operator ). When you assign the class, you assign the permissions—for example, clear , configure , network , reset , view , and view-configuration .

For a list of permissions, see Understanding Junos OS Access Privilege Levels .

[edit] crypto-officer@switch:fips# set system login user fips-user1 uid 6401 class operator

Following the guidelines in

“Understanding Password Specifications and Guidelines for Junos OS in FIPS Mode” on page 24

, assign the FIPS a plain-text password for login authentication. Set the password by typing a password after the prompts New password and Retype new password .

[edit] crypto-officer@switch:fips# set system login user fips-user1 class operator authentication plain-text-password

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

Optionally, display the configuration:

[edit] crypto-officer@switch:fips# edit system

[edit system] crypto-officer@switch:fips# show login { user fips-user1 { uid 6401; authentication { encrypted-password "$ABC123"; ## SECRET-DATA

} class operator;

}

If you are finished configuring the switch, commit the configuration and exit:

[edit] crypto-officer@switch:fips# commit crypto-officer@switch:fips> exit

Otherwise, go on to

“Configuring the Console Port for FIPS Mode” on page 43

Documentation

•

Understanding Roles and Services for Junos OS in FIPS Mode on page 17

Enabling Internal Communications Between the RE and PFE (FIPS Mode)

A switch in FIPS mode must have an internal IPsec security association (SA) manually configured to enable communications between the Routing Engine (RE) and Packet

Forwarding Engine (PFE). As Crypto Officer, you configure an IPsec SA. Only four parameters are required: SA direction, Security Parameter Index (SPI) value, a key value for authentication, and a key value for encryption.

NOTE: You cannot configure DES-based IPsec SAs in Junos OS in FIPS mode.

The internal IPsec SAs use HMAC-SHA2-256 authentication and 3DES-CBC encryption.

Manual SAs require no negotiation. All values, including the keys, are static and specified in the configuration. Manual SAs statically define the SPI values, algorithms, and keys to be used, and require matching configurations on both ends of the tunnel. Each peer must have the same configured options for communication to take place.

NOTE: When the switch is in FIPS mode, you cannot use the commit synchronize command until you have established an IPsec SA.

As Crypto Officer, you configure an internal IPsec SA with the following statements at the [edit security] hierarchy level:

Chapter 2: Enabling and Configuring Junos OS in FIPS Mode

[edit

{

{

{

(bidirectional | inbound | outbound) {

;

spi-value;

{

(hmac-sha2-256);

(ascii-text ascii-text-string | hexadecimal hexadecimal-number);

}

{

3des-cbc;

Configuring the IPsec SA on a Switch with a Single Routing Engine on page 41

(ascii-text ascii-text-string |hexadecimal hexadecimal-number);

}

The SA you configure can have two unidirectional tunnels—an inbound and outbound tunnel—or a single tunnel for bidirectional communication.

NOTE: We do not recommend the use of unidirectional IPsec tunnels.

If you do not configure the SA to be bidirectional, you must configure SA parameters for

IPsec tunnels in both directions. The following instructions show how to configure a bidirectional IPsec SA on a Routing Engine:

•

Configuring the IPsec SA on a Switch with a Single Routing Engine

If you are configuring the IPsec SA on a switch with a single Routing Engine, you have to configure the SA only once, on this single, master Routing Engine. You do not have to create the SA on any other Routing Engine.

To configure an internal, manual IPsec SA on the master Routing Engine:

% cli

— JUNOS 14.1-20141229.0 built 2014-12-29 04:12:22 UTC

{master} root@switch:fips> configure

Entering configuration mode

{master} [edit] root@switch:fips#

Specify the direction of the IPsec SA as bidirectional:

{master} [edit]

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

42 root@switch:fips# set

security ipsec internal security-association manual direction

bidirectional

For the SA, specify the protocol (ESP is required) and an SPI between 256 and

16639—for example, 512:

{master} [edit security ipsec internal security-association manual direction

bidirectional] root@switch:fips# set

protocol esp spi

512

Specify the authentication algorithm (HMAC-SHA2-256):

{master} [edit security ipsec internal security-association manual direction

bidirectional] root@switch:fips# set

authentication algorithm

hmac-sha2-256

Specify the encryption algorithm (3DES-CBC is required):

{master} [edit security ipsec internal security-association manual direction

bidirectional] root@switch:fips# set

encryption algorithm

3des-cbc

In configuration mode, use the prompt command to enter a secret key value of

40 hexadecimal characters for authentication —for example,

309fc4be20f04e53e011b00744642d3fe66c2c7c:

{master} [edit] root@switch:fips# prompt

security ipsec internal security-association manual direction

bidirectional

authentication key

hexadecimal

New hexadecimal (secret):

Retype new hexadecimal (secret):

Use prompt again to enter a secret key value of 48 hexadecimal characters for encryption —for example, b0344c61d8db38535ca8afceaf0bf12b881dc200c9833da7:

{master} [edit] root@switch:fips# prompt

security ipsec internal security-association manual direction

bidirectional

encryption key

hexadecimal

New hexadecimal (secret):

Retype new hexadecimal (secret):

Use show security to verify that the key values for both authentication and encryption—and other required IPsec SA values—have been configured on the master

Routing Engine. The key hexadecimal values are never displayed.

{master} [edit] root@switch:fips# show security ipsec { internal { security-association { manual { direction bidirectional { protocol esp; spi 512; authentication { algorithm hmac-sha2-256; key hexadecimal "<cipher-text>"; ## SECRET- DATA

} encryption { algorithm 3des-cbc;

Chapter 2: Enabling and Configuring Junos OS in FIPS Mode

}

} key hexadecimal "<cipher-text>"; ## SECRET- DATA

Commit the changes on the master Routing Engine:

{master} [edit] root@switch:fips# commit

Documentation

• For information about IP Security (IPsec) monitoring and troubleshooting, see the

Junos OS System Basics and Services Command Reference .

•

Understanding Requirements for Secure Communication Between Routing Engines in

“Configuring Event Logging for Junos OS in FIPS Mode” on page 44 .

Configuring the Console Port for FIPS Mode

You initially connect to your switch through an RJ-45 serial cable plugged into the console port. From the console port, you can use the CLI to configure the switch. By default, the console port is enabled.

For FIPS compliance, your user account must be automatically logged out when you unplug the serial console cable from a switch running Junos OS in FIPS mode. Junos OS in FIPS mode automatically logs out of your user account when you disconnect because the log-out-on-disconnect configuration statement is enabled by default. Also, Junos OS in FIPS mode does not automatically disable root password recovery, so you must explicitly configure that by specifying the insecure configuration statement.

CAUTION: If you disable root password recovery by setting the insecure statement, the root password can be recovered only if the Crypto Officer logs in to the system and modifies the configuration by removing that setting.

To configure automatic logout on disconnection:

Log in to the switch with your Crypto Officer password if you have not already done so, and enter configuration mode: crypto-officer@switch:fips> configure

Entering configuration mode

[edit] crypto-officer@switch:fips#

Configure the switch to automatically log out of a user session when the console port cable is unplugged:

[edit] crypto-officer@switch:fips# set system ports console log-out-on-disconnect

Configure the switch to disable root password recovery:

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

[edit] crypto-officer@switch:fips# set system ports console insecure

Optionally, display the configuration:

[edit] crypto-officer@switch:fips# edit system

[edit system] ports { console { log-out-on-disconnect; insecure;

}

If you are finished configuring the switch, commit the configuration and exit:

[edit] crypto-officer@switch:fips# commit commit complete crypto-officer@switch:fips# exit crypto-officer@switch:fips> exit

Otherwise, go on to

Documentation

• For information about local console configuration and more information about console port options, see the Junos OS System Basics Configuration Guide.

Configuring Event Logging for Junos OS in FIPS Mode

The system log (syslog) files record system events in Junos OS.

BEST PRACTICE: Because of the sensitive nature of information used to configure and operate a system running Junos OS in FIPS mode, we recommend that you as Crypto Officer log certain events and examine the logs frequently.

For Junos OS in FIPS mode, we recommend that you as Crypto Officer configure the system log to record the following events. You can log more types of information, but these events are particularly important to the Junos OS in FIPS mode environment.

• All authorization events—stored in /var/log/authlog and /var/log/auditlog

• All interactive commands and configuration change events, including secrets—stored in /var/log/auditlog

• All events of moderate severity—stored in /var/log/messages

In Junos OS in FIPS mode, the actual secrets themselves are not logged. When Junos OS encounters secret information that it would ordinarily log, it replaces the secrets with

Chapter 2: Enabling and Configuring Junos OS in FIPS Mode the token /* SECRET-DATA */ . For example, a secret string entered as part of the command line is not logged, but is replaced with the following token:

Feb 10 23:57:01 shmoo mgd[15558]: UI_CFG_AUDIT_SET_SECRET: User 'root' set: [system

tacplus-server 172.17.12.120 secret]

Feb 10 23:57:01 shmoo mgd[15558]: UI_CMDLINE_READ_LINE: User 'root', command 'set

system tacplus-server frodo secret /* SECRET-DATA */ '

The following system log configuration is recommended for Junos OS in FIPS mode:

[edit] system { syslog { file authlog { authorization info;

} file messages { any any;

} file auditlog { authorization info; change-log any; interactive-commands any;

}

You can configure the system to log events to a local file or to a remote server:

•

Configuring Event Logging to a Local File on page 45

•

Configuring Event Logging to a Remote Server on page 46

Configuring Event Logging to a Local File

To configure the system to store the recommended information for Junos OS in FIPS mode, you create log files on the switch called authlog , audit-log , and messages .

(You can also store event logs on a secure, remote server. For details, see

“Configuring

Event Logging to a Remote Server” on page 46 .)

To configure the system to log the recommended events to local files on the switch in the /var/log/ directory:

Log in to the switch with your Crypto Officer password if you have not already done so, and enter configuration mode: crypto-officer@switch:fips> configure

[edit] crypto-officer@switch:fips#

Configure a file named authlog to store informational messages from the authorization system in /var/log/authlog on the switch:

[edit] crypto-officer@switch:fips# set system syslog file authlog authorization info

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

Configure a file named auditlog to store informational messages from the authorization system, all configuration changes, and all commands entered through the

CLI—including secrets—in /var/log/auditlog on the switch:

[edit] crypto-officer@switch:fips# set system syslog file auditlog authorization info

[edit] crypto-officer@switch:fips# set system syslog file auditlog change-log any

[edit] crypto-officer@switch:fips# set system syslog file auditlog interactive-commands any

Configure a file named messages to store notices of all events of moderate severity in /var/log/messages on the switch:

[edit] crypto-officer@switch:fips# set system syslog file messages any any

If you are finished configuring the switch, commit the configuration and exit:

[edit] crypto-officer@switch:fips# commit commit complete crypto-officer@switch:fips# exit crypto-officer@switch:fips> exit

To view the contents of the log files, enter the following operational mode commands: crypto-officer@switch:fips> file show /var/log/authlog crypto-officer@switch:fips> file show /var/log/auditlog crypto-officer@switch:fips> file show /var/log/messages

Configuring Event Logging to a Remote Server

In addition to storing log files in the local /var/log/ directory on the switch (see

“Configuring

Event Logging to a Local File” on page 45

), you can export the information in system log files to a secure, remote server.

BEST PRACTICE: We recommend that you store system log files remotely.

To configure the system to log the recommended events to a remote host:

Log in to the switch with your Crypto Officer password if you have not already done so, and enter configuration mode: crypto-officer@switch:fips> configure

[edit] crypto-officer@switch:fips#

Configure the system to import informational messages from the authorization system and store them on a remote host—for example, a host named Secure-Audit-Server :

[edit] crypto-officer@switch:fips# set system syslog host Secure-Audit-Server authorization info

Chapter 2: Enabling and Configuring Junos OS in FIPS Mode

Configure the system to import all configuration changes and all commands entered through the CLI—including secrets—and store them on the remote host

Secure-Audit-Server :

[edit] crypto-officer@switch:fips# set system syslog host Secure-Audit-Server change-log any

[edit] crypto-officer@switch:fips# set system syslog host Secure-Audit-Server interactive-commands any

Configure the system to import all notices of events of moderate severity and store them on the remote host Secure-Audit-Server :

[edit] crypto-officer@switch:fips# set system syslog host Secure-Audit-Server any

notice

If you are finished configuring the switch, commit the configuration and exit:

[edit] crypto-officer@switch:fips# commit commit complete crypto-officer@switch:fips# exit crypto-officer@switch:fips> exit

Documentation

•

Understanding Event Logging for Junos OS in FIPS Mode on page 25

• For more information about system logging, see the Junos OS System Basics Configuration

Guide.

• To configure features on the switch that are not specific to FIPS mode, see the EX

Series hardware and software documentation at http://www.juniper.net/techpubs/en_US/release-independent/information-products/ pathway-pages/ex-series/product/index.html

Disabling FIPS Mode

As Crypto Officer, you might need to disable FIPS mode on your switch to return it to non-FIPS operation.

BEST PRACTICE: For FIPS 140-2 compliance, you must zeroize the system to remove sensitive information before disabling FIPS mode on the switch.

To disable FIPS mode in Junos OS:

Follow the instructions in

“Zeroizing the System (FIPS Mode)” on page 33

to zeroize the switch.

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

When the system finishes rebooting, log in to the switch again with your Crypto Officer password and enter configuration mode:

— JUNOS 14.1-20141229.0 built 2014-12-29 04:12:22 UTC crypto-officer@switch> configure

Entering configuration mode

[edit] crypto-officer@switch#

Commit the configuration change:

[edit] crypto-officer@switch:fips# commit configuration check succeeds commit complete

Documentation

•

Verifying That FIPS Self-Tests Are Taking Place on page 49

CHAPTER 3

Administering Junos OS in FIPS Mode on an EX Series Switch

•

Verifying That FIPS Self-Tests Are Taking Place

Purpose Verify that FIPS self-tests are taking place on the switch.

Action You can run FIPS self-tests manually by issuing the request system reboot command.

After a self-test is run on the switch, the system log (syslog) file is updated to display the known answer tests (KATs) that are executed. To view the system log file, issue the command file show /var/log/messages : user@switch:fips> file show /var/log/messages

Oct 25 22:28:50 host kernel_kats[5358]: DES3-CBC Known Answer Test: Passed

Oct 25 22:28:50 host kernel_kats[5358]: HMAC-SHA1 Known Answer Test: Passed

Oct 25 22:28:50 host kernel_kats[5358]: HMAC-SHA2-256 Known Answer Test: Passed

Oct 25 22:28:50 host kernel_kats[5358]: SHA-2 Known Answer Test: Passed

Oct 25 22:28:50 host kernel_kats[5358]: AES128-CMAC Known Answer Test: Passed

Oct 25 22:28:50 host kernel_kats[5358]: AES-CBC Known Answer Test: Passed

Oct 25 22:28:50 host kernel_kats[5358]: FIPS Known Answer Tests passed

Oct 25 22:28:50 host md_kats[5360]: HMAC-SHA1 Known Answer Test: Passed

Oct 25 22:28:50 host md_kats[5360]: HMAC-SHA2-256 Known Answer Test: Passed

Oct 25 22:28:50 host md_kats[5360]: FIPS Known Answer Tests passed

Oct 25 22:28:50 host openssl_kats[5362]: FIPS RNG Known Answer Test: Passed

Oct 25 22:28:57 host openssl_kats[5362]: FIPS DSA Known Answer Test: Passed

Oct 25 22:28:57 host openssl_kats[5362]: FIPS ECDSA Known Answer Test: Passed

Oct 25 22:28:58 host openssl_kats[5362]: FIPS ECDH Known Answer Test: Passed

Oct 25 22:29:00 host openssl_kats[5362]: FIPS RSA Known Answer Test: Passed

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

Oct 25 22:29:00 host openssl_kats[5362]: DES3-CBC Known Answer Test: Passed

Oct 25 22:29:00 host openssl_kats[5362]: HMAC-SHA1 Known Answer Test: Passed

Oct 25 22:29:00 host openssl_kats[5362]: SHA-2 Known Answer Test: Passed

Oct 25 22:29:00 host openssl_kats[5362]: AES-CBC Known Answer Test: Passed

Oct 25 22:29:00 host openssl_kats[5362]: ECDSA-SIGN Known Answer Test: Passed

Oct 25 22:29:00 host openssl_kats[5362]: KDF-IKE-V1 Known Answer Test: Passed

Oct 25 22:29:00 host openssl_kats[5362]: FIPS Known Answer Tests passed

Oct 25 22:29:00 host ssh_ipsec_kats[5364]: DES3-CBC Known Answer Test: Passed

Oct 25 22:29:00 host ssh_ipsec_kats[5364]: HMAC-SHA1 Known Answer Test: Passed

Oct 25 22:29:00 host ssh_ipsec_kats[5364]: HMAC-SHA2-256 Known Answer Test:

Passed

Oct 25 22:29:00 host ssh_ipsec_kats[5364]: SHA-2 Known Answer Test: Passed

Oct 25 22:29:00 host ssh_ipsec_kats[5364]: AES-CBC Known Answer Test: Passed

Oct 25 22:29:01 host ssh_ipsec_kats[5364]: SSH-RSA-ENC Known Answer Test: Passed

Oct 25 22:29:03 host ssh_ipsec_kats[5364]: SSH-RSA-SIGN Known Answer Test: Passed

Oct 25 22:29:03 host ssh_ipsec_kats[5364]: KDF-IKE-V1 Known Answer Test: Passed

Oct 25 22:29:03 host ssh_ipsec_kats[5364]: FIPS Known Answer Tests passed

Meaning The system log file displays the date and time at which each KAT was executed, the name of the test, and its status.

Documentation

•

Understanding FIPS Self-Tests on page 14

CHAPTER 4

Configuration Statements for Junos OS in

FIPS Mode

•

algorithm (FIPS) on page 52

•

authentication (FIPS) on page 52

•

direction (FIPS) on page 53

•

encryption (FIPS) on page 54

•

fips (FIPS) on page 54

•

internal (FIPS) on page 55

•

ipsec (FIPS) on page 56

•

key (FIPS) on page 57

•

level (FIPS) on page 58

•

manual (FIPS) on page 59

•

protocol esp (FIPS) on page 59

•

security (FIPS) on page 60

•

security-association (FIPS) on page 61

•

spi (FIPS) on page 62

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

algorithm (FIPS)

Syntax algorithm <name>;

Hierarchy Level [edit

security ipsec internal security-association manual direction authentication

[edit

security ipsec internal security-association manual direction encryption

]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Select the authentication and encryption algorithm for an IPsec security association (SA) between internal Routing Engines.

Options hmac-sha2-256 —Use a 256-bit Hash Message Authentication Code (HMAC) based on

Secure Hash Algorithm 2 (SHA2) as the authentication algorithm.

3des-cbc —Use a triple-Data Encryption Standard (3DES) cyclical block check (CBC) as the encryption algorithm.

Required Privilege

Level maintenance—To add and view this statement in the configuration.

Documentation

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

authentication (FIPS)

Syntax authentication {

(hmac-sha2-256);

security ipsec internal security-association manual direction

(ascii-text ascii-text-string | hexadecimal key-value);

}

Hierarchy Level [edit

]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Define the authentication parameters for communication between internal Routing

Engines.

NOTE: We recommend using the hexadecimal format for maximum key strength.

The remaining statements are explained separately.

Required Privilege

Level maintenance—To view and add this statement in the configuration.

Documentation

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

Chapter 4: Configuration Statements for Junos OS in FIPS Mode

direction (FIPS)

Syntax direction (bidirectional | inbound | outbound) {

;

spi-value;

{

(hmac-sha2-256);

(ascii-text ascii-text-string| hexadecimal key-value);

}

{

3des-cbc;

security ipsec internal security-association manual

(ascii-text ascii-text-string| hexadecimal key-value);

}

Hierarchy Level [edit

]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Establish a manual security association (SA) for communication between internal Routing

Engines.

Options bidirectional —Apply the same SA values in both directions between Routing Engines.

inbound —Apply these SA properties only to the inbound IPsec tunnel.

outbound —Apply these SA properties only to the outbound IPsec tunnel.

The remaining statements are explained separately.

Required Privilege

Level maintenance—To view and add this statement in the configuration.

Documentation

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

encryption (FIPS)

Syntax encryption {

3des-cbc;

security ipsec internal security-association manual direction

(ascii-text ascii-text-string| hexadecimal key-value);

}

Hierarchy Level [edit

]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Define the encryption parameters for communication between internal Routing Engines.

NOTE: We recommend using the hexadecimal format for maximum key strength.

The remaining statements are explained separately.

Required Privilege

Level maintenance—To view and add this statement in the configuration.

Documentation

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

fips (FIPS)

Syntax fips {

level

level;

Hierarchy Level [edit system]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Configure Junos OS Federal Information Processing Standard (FIPS) mode features on a switch.

The remaining statements are explained separately.

Required Privilege

Level system—To view this statement in the configuration.

system-control—To add this statement to the configuration.

Documentation

•

•

Chapter 4: Configuration Statements for Junos OS in FIPS Mode

internal (FIPS)

Syntax internal {

security-association

{

manual

direction

(bidirectional | inbound | outbound) {

;

spi-value;

{

(hmac-sha2-256);

(ascii-text ascii-text-string| hexadecimal key-value);

}

{

3des-cbc;

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

(ascii-text ascii-text-string| hexadecimal key-value);

}

Hierarchy Level [edit

security ipsec ]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Define an internal security association (SA) for communication between internal Routing

Engines.

The remaining statements are explained separately.

Required Privilege

Level maintenance—To view and add this statement in the configuration.

Documentation

•

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

ipsec (FIPS)

Syntax ipsec {

{

{

(bidirectional | inbound | outbound) {

;

spi-value;

{

(hmac-sha2-256);

(ascii-text ascii-text-string| hexadecimal key-value);

}

{

3des-cbc;

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

(ascii-text ascii-text-string| hexadecimal key-value);

}

Hierarchy Level [edit

security ]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Set up an Internet Protocol Security (IPsec) hierarchy in which you can define a manual internal security association (SA) for communication between internal Routing Engines.

The remaining statements are explained separately.

Required Privilege

Level maintenance—To view and add this statement in the configuration.

Documentation

•

Chapter 4: Configuration Statements for Junos OS in FIPS Mode

key (FIPS)

Syntax key (ascii-text ascii-text-string | hexadecimal key-value);

Hierarchy Level [edit

security ipsec internal security-association manual direction authentication

[edit

security ipsec internal security-association manual direction encryption

]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Following FIPS password guidelines, use the prompt command, in configuration mode, to specify one key (password) value each for the authentication algorithm and the encryption algorithm in an internal IPsec security association (SA) between internal

Routing Engines. You must specify a value for each algorithm.

NOTE: We recommend using the hexadecimal format for maximum key strength.

You must enter the hexadecimal value for each key twice, and the strings entered must match; otherwise, the key is not set. The hexadecimal key value is never displayed in plain text.

Options hexadecimal key-value —The encrypted hexadecimal key value:

• For the authentication algorithm (HMAC-SHA-256), enter a key consisting of

64 hexadecimal characters.

• For the encryption algorithm (3DES-CBC), enter a key consisting of 48 hexadecimal characters.

Required Privilege

Level maintenance—To add and view this statement in the configuration.

Documentation

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

•

Understanding Password Specifications and Guidelines for Junos OS in FIPS Mode on page 24

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

level (FIPS)

Syntax level level;

Hierarchy Level [edit system

fips ]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Set the level for the Junos OS Federal Information Processing Standards (FIPS) mode on the device. Setting the FIPS level to a value other than the default, 0 (zero), enables

FIPS mode on the device.

Compared to non-FIPS mode, Junos OS in FIPS mode is a nonmodifiable operational environment with limitations. (See

“Understanding Configuration Limitations and

Restrictions on Junos OS in FIPS Mode” on page 26 .)

Options level —FIPS level on a device, from level 1 (lowest) through level 4 (highest). At level 0

(the default), the device is in non-FIPS mode.

Range: 0 through 4

NOTE: To enable Junos OS in FIPS mode on an EX Series switch, set level to

1. Only level 1 is supported on the switches.

Required Privilege

Level system—To view this statement in the configuration.

system-control—To add this statement to the configuration.

Documentation

•

•

Chapter 4: Configuration Statements for Junos OS in FIPS Mode

manual (FIPS)

Syntax manual {

direction

(bidirectional | inbound | outbound) {

;

spi-value;

{

(hmac-sha2-256);

(ascii-text ascii-text-string| hexadecimal key-value);

}

{

3des-cbc;

security ipsec internal security-association

(ascii-text ascii-text-string| hexadecimal key-value);

}

Hierarchy Level [edit

]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Define a manual security association (SA) for communication between internal Routing

Engines.

The remaining statements are explained separately.

Required Privilege

Level maintenance—To view and add this statement in the configuration.

Documentation

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

protocol esp (FIPS)

Syntax protocol esp;

Hierarchy Level [edit

security ipsec internal security-association manual direction

]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Specify the protocol (esp) used for an internal IPsec security association (SA) between internal Routing Engines.

Options esp —Use the TCP/IP Encapsulating Security Protocol (ESP).

Required Privilege

Level maintenance—To add and view this statement in the configuration.

Documentation

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

security (FIPS)

Syntax security {

{

{

{

{

(bidirectional | inbound | outbound) {

;

spi-value;

{

(hmac-sha2-256);

(ascii-text ascii-text-string| hexadecimal key-value);

}

{

3des-cbc;

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

(ascii-text ascii-text-string| hexadecimal key-value);

}

Hierarchy Level [edit]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Define security parameters for communication between internal Routing Engines.

The remaining statements are explained separately.

Required Privilege

Level security—To view and add this statement in the configuration.

Documentation

•

Chapter 4: Configuration Statements for Junos OS in FIPS Mode

security-association (FIPS)

Syntax security-association {

manual

{

direction

(bidirectional | inbound | outbound) {

;

spi-value;

{

(hmac-sha2-256);

(ascii-text ascii-text-string| hexadecimal key-value);

}

{

3des-cbc;

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

(ascii-text ascii-text-string| hexadecimal key-value);

}

Hierarchy Level [edit

security ipsec internal

]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Define an IPsec security association (SA) for communication between internal Routing

Engines.

The remaining statements are explained separately.

Required Privilege

Level maintenance—To view and add this statement in the configuration.

Documentation

•

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

spi (FIPS)

Syntax spi spi-value;

Hierarchy Level [edit

security ipsec internal security-association manual direction

]

Release Information Statement introduced in Junos OS Release 12.1 for EX Series switches.

Description Specify the security parameter index (SPI) value for the internal IPsec security association

(SA) between internal Routing Engines. The SPI is an arbitrary value that uniquely identifies the SA to use at the receiving Routing Engine. The sending Routing Engine uses the SPI to identify and select the SA it uses to secure every packet. The receiving Routing Engine uses the SPI to identify and select the encryption algorithm and key it uses to decrypt packets.

Options spi-value —Integer to use for this SPI.

Range: 256 through 16639

Required Privilege

Level maintenance—To add and view this statement in the configuration.

Documentation

•

Enabling Internal Communications Between the RE and PFE (FIPS Mode) on page 40

CHAPTER 5

Operational Commands for Junos OS in

FIPS Mode

•

request system zeroize (FIPS)

Junos

OS for EX Series Ethernet Switches, Release 14.1X53-D30: FIPS

request system zeroize (FIPS)

Syntax request system zeroize

Release Information Command introduced in Junos OS Release 12.1 for EX Series switches.

Description Erase and replace with zeros all user-created data from Routing Engines.

Options none—Zeroize all Routing Engines in Junos OS in FIPS mode. You must verify the request by typing yes to proceed. This command is restricted to Crypto Officers because the maintenance permission bit is one of the permission bits, along with secret and control , that distinguishes Crypto Officers from other FIPS users.

Required Privilege

Level maintenance

Documentation

•

Understanding Zeroization to Clear System Data for FIPS Mode on page 13

•