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 Security Administrator 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 Security Administrator.
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.
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, the only way to exit from FIPS mode is to zeroize the TOE.
When to Zeroize?
As Security Administrator, perform zeroization in the following situations:
Before Enabling FIPS mode of operation: To prepare your switch for operation as a FIPS cryptographic module, perform zeroization before enabling FIPS mode.
Before repurposing to non-FIPS mode of operation: To begin repurposing your switch for non-FIPS mode of operation, perform zeroization on the switch.
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 a secure 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.