FIPS Configuration

In this section:

  1. User Roles in FIPS Mode
    Configuring FIPS mode on the RUCKUS devices complies with the standards established by the United States government and the National Institute of Standards and Technology (NIST).
  2. Commands Disabled in FIPS Mode
    The device in FIPS mode does not support the following commands:
  3. Hidden Files in FIPS Mode
    Hidden files are not displayed when the device is in FIPS mode. Hidden files are displayed only when the device is in non-FIPS mode.
  4. Cryptographic Algorithms in FIPS Mode
    The device in FIPS mode supports the following FIPS 140-3-approved cryptographic algorithms:
  5. SSH
  6. SSH Clients
  7. Usernames and SSH Public Key Authentication
    The device stores or uses the username that is provided by the SSH client when public-key authentication is used. Therefore, the username is mentioned in the login and logout syslogs.
  8. Protocol Changes in FIPS Mode
    The following table lists the protocols that undergo changes while the device is in FIPS mode with the default policy applied.
  9. System Reset and Boot up in FIPS Mode
    POST testing takes place as the device progresses through the boot sequence.
  10. Debugging in FIPS Mode
    The device reloads automatically when it encounters a system reset and enters FIPS failure state. The cause of failure logs on the console and the device performs a self-reboot.
  11. Placing the Device in FIPS Mode
    Placing the device in FIPS mode is a multiple-step process that begins with enabling FIPS mode on the device.
  12. Disabling FIPS Mode
  13. Running FIPS Self-tests
    Use the fips self-tests command either in FIPS mode or non-FIPS mode to run the Known Answer Tests (KATs) and conditional tests on demand in both FIPS mode and non-FIPS mode.