Understanding Roles and Services for Junos OS in FIPS Mode of Operation
The Juniper Networks Junos operating system (Junos OS) running in non-FIPS mode of operation allows a wide range of capabilities for users, and authentication is identity-based. In contrast, the FIPS 140-2 standard defines two user roles: Cryptographic 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 of operation (operator, administrative user, and so on) must fall into one of the two categories: Cryptographic Officer or FIPS user. For this reason, user authentication in FIPS mode of operation is role-based rather than identity-based.
In addition to their FIPS roles, both user types can perform normal configuration tasks on the device as individual user configuration allows.
Cryptographic Officers and FIPS users perform all FIPS-related configuration tasks and issue all statements and commands for Junos OS in FIPS mode of operation. Cryptographic Officer and FIPS user configurations must follow the guidelines for Junos OS in FIPS mode of operation.
For details, see:
Cryptographic Officer Role and Responsibilities
The Cryptographic Officer is the person responsible for enabling, configuring, monitoring, and maintaining Junos OS in FIPS mode of operation on a device. The Cryptographic Officer securely installs Junos OS on the device, enables FIPS mode of operation, establishes keys and passwords for other users and software modules, and initializes the device before network connection. The Cryptographic Officer can configure and monitor the module through a console or SSH connection.
We recommend that the Cryptographic Officer administer the system in a secure manner by keeping passwords secure and checking audit files.
The permissions that distinguish the Cryptographic Officer from other FIPS users are secret, security, maintenance, and control. For FIPS compliance, assign the Cryptographic 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).
Junos OS in FIPS mode of operation 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 of operation, the Cryptographic Officer is expected to:
Set the initial root password.
Reset user passwords for FIPS-approved algorithms during upgrades from Junos OS.
Set up manual IPsec SAs for configuration with dual Routing Engines.
Examine log and audit files for events of interest.
Erase user-generated files and data on (zeroize) the device.
FIPS User Role and Responsibilities
All FIPS users, including the Cryptographic Officer, can view the configuration. Only the user assigned as the Cryptographic Officer can modify the configuration.
The permissions that distinguish Cryptographic 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 device and perform other tasks that are not specific to FIPS mode of operation. FIPS users who are not Cryptographic Officers can perform reboots and view status output.
What Is Expected of All FIPS Users
All FIPS users, including the Cryptographic Officer, must observe security guidelines at all times.
All FIPS users must:
Keep all passwords confidential.
Store devices and documentation in a secure area.
Deploy devices 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.