- play_arrow Configuring Administrative Credentials and Privileges
- play_arrow Configuring Roles and Authentication Methods
- Understanding Roles and Services for Junos OS
- Understanding the Operational Environment for Junos OS in FIPS Mode
- Understanding Password Specifications and Guidelines for Junos OS in FIPS Mode
- Downloading Software Packages from Juniper Networks
- Installing Software on a Device with Single Routing Engine
- Understanding Zeroization to Clear System Data for FIPS Mode
- Zeroizing the System
- Enabling FIPS Mode
- Configuring Crypto Officer and FIPS User Identification and Access
- play_arrow Configuring SSH and Console Connection
- play_arrow Configuring MACsec
- play_arrow Configuring Event Logging
- play_arrow Configuring IPsec VPN
- play_arrow Performing Self-Tests on a Device
- play_arrow Operational Commands
Understanding Junos OS in FIPS Mode
Federal Information Processing Standards (FIPS) 140-2 defines security levels for hardware and software that perform cryptographic functions. This Juniper Networks router running the Juniper Networks Junos operating system (Junos OS) in FIPS mode comply with the FIPS 140-2 Level 1 standard.
Operating this router in a FIPS 140-2 Level 1 environment requires enabling and configuring FIPS mode on the devices from the Junos OS command-line interface (CLI).
The Crypto Officer enables FIPS mode in Junos OS and sets up keys and passwords for the system and other FIPS users.
Supported Platforms and Hardwares
For the features described in this document, the following platforms are used to qualify FIPS certification:
MX240, MX480, and MX960 devices with the following Routing Engine and Modular Port Concentrator (MPC) combinations (https://www.juniper.net/us/en/products/routers/mx-series/mx240-universal-routing-platform.html, https://www.juniper.net/us/en/products/routers/mx-series/mx480-universal-routing-platform.html, and https://www.juniper.net/us/en/products/routers/mx-series/mx960-universal-routing-platform.html
- RE1800 and MPC7E
- NGRE and MPC7E
- NGRE and MS-MPC
- RE1800 and MS-MPC
- RE-S-X6-64G and MS-MPC
About the Cryptographic Boundary on Your Device
FIPS 140-2 compliance requires a defined cryptographic boundary around each cryptographic module on a device. Junos OS in FIPS mode prevents the cryptographic module from executing any software that is not part of the FIPS-certified distribution, and allows only FIPS-approved cryptographic algorithms to be used. No critical security parameters (CSPs), such as passwords and keys, can cross the cryptographic boundary of the module in unencrypted format.
Virtual Chassis features are not supported in FIPS mode. Do not configure a Virtual Chassis in FIPS mode.
How FIPS Mode Differs from Non-FIPS Mode
Junos OS in FIPS mode differs in the following ways from Junos OS in non-FIPS mode:
Self-tests of all cryptographic algorithms are performed at startup.
Self-tests of random number and key generation are performed continuously.
Weak cryptographic algorithms such as Data Encryption Standard (DES) and MD5 are disabled.
Weak or unencrypted management connections must not be configured.
Passwords must be encrypted with strong one-way algorithms that do not permit decryption.
Administrator passwords must be at least 10 characters long.
Validated Version of Junos OS in FIPS Mode
To determine whether a Junos OS release is NIST-validated, see the compliance page on the Juniper Networks Web site (https://apps.juniper.net/compliance/).
