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 Security Administrator must zeroize the non-approved mode critical security parameters (CSPs). For SRX5400, SRX5600, and SRX5800 devices, the Security Administrator initiates the zeroization process by entering the request system zeroize from the CLI after enabling FIPS mode of operation. Use of this command is restricted to the Security Administrator.
Perform system zeroization with care. After the zeroization process is complete, no data is left on the device. This command erases all the CSPs, configurations, and the hard disk partitions containing the device image. Hence, the device does not boot up on zeroization and USB reimage is required to recover the device.
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.
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 Security Administrator, 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 non-approved 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 on the device.
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.