Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Understanding FIPS Self-Tests

The cryptographic module enforces security rules to ensure that a device running the Juniper Networks Junos operating system (Junos OS) in FIPS mode of operation meets the security requirements of FIPS 140-3 Level 2. To validate the output of cryptographic algorithms approved for FIPS and test the integrity of some system modules, the device performs the following series of known answer test (KAT) self-tests:

  • kernel_kats—KAT for kernel cryptographic routines

  • md_kats—KAT for libmd and libc

  • openssl_kats—KAT for OpenSSL cryptographic implementation

  • openssl-102_kats—KAT for OpenSSL v1.0.2 cryptographic implementation

  • quicksec_7_0_kats—KAT for Quicksec_7_0Toolkit cryptographic implementation

  • octcrypto_kats—KAT for Octeon

The KAT self-tests are performed automatically at startup and reboot, when FIPS mode of operation is enabled on the device. Conditional self-tests are also performed automatically to verify digitally signed software packages, generated random numbers, RSA and ECDSA key pairs, and manually entered keys.

If the KATs are completed successfully, the system log (syslog) file is updated to display the tests that were executed.

If the device fails a KAT, the device writes the details to a system log file, enters FIPS error state (panic), and reboot.

The file show /var/log/messages command displays the system log.

Proceed with normal operation after the reboot is complete. If an error occurs, please contact the Juniper Networks Technical Assistance Center (JTAC).

You must have administrative privileges to configure FIPS self-tests. The device must be running the evaluated version of Junos OS in FIPS mode software.

In this example, the FIPS self-test is executed at 9:00 AM in New York City, USA, every Wednesday.

Note: Instead of weekly tests, you can configure monthly tests by including the month and day-of-month statements.