Understanding Zeroization to Clear System Data for FIPS Mode of Operation
Zeroization completely erases all configuration information on the device, including all plaintext passwords, secrets, and private keys for SSH, local encryption, local authentication, and IPsec. To exit the FIPS mode you need to zeroize the device.
The cryptographic module provides a non-approved mode of operation in which non-approved cryptographic algorithms are supported. When moving from the non-approved mode of operation to the approved mode of operation, the Cryptographic Officer must zeroize the non-approved mode critical security parameters (CSPs). The Cryptographic Officer initiates the zeroization process by entering the request system zeroize hypervisor operational command from the CLI after enabling FIPS mode of operation. Use of this command is restricted to the Cryptographic Officer.
Perform system zeroization with care. After the zeroization process is complete, no data is left on the device. The request system zeroize hypervisor command erases all the CSPs, configurations, and the hard disk partitions containing the device image. Therefore, the device does not boot up on zeroization and the USB reimage operation is required to recover the device.
Your device is not considered a valid FIPS cryptographic module until all CSPs have been entered—or reentered—while the device is in FIPS mode of operation.
For FIPS 140-2 compliance, we recommend that you zeroize the device to exit the FIPS mode.
When to Zeroize?
As a Cryptographic Officer, perform zeroization in the following situations:
Before FIPS operation—To prepare your device for operation as a FIPS cryptographic module, perform zeroization to remove the nonapproved mode critical security parameters (CSPs) and enable FIPS mode on the device.
Before non-FIPS operation—To begin repurposing your device for non-FIPS operation, perform zeroization before disabling FIPS mode of operation on the device or loading Junos OS packages that do not include FIPS mode of operation.
Juniper Networks does not support installing non-FIPS software in a FIPS mode of operation, 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.