Entering Common Criteria Operational Mode

When the device is in Common Criteria Administrative mode, perform the following steps to place the device into Common Criteria Operational mode.
  1. Configure the local user accounts as secure and delete non-secure user accounts. A local user account is secure when it has a password with characters from three or more character classes. These character classes are uppercase, lowercase, numeric, and ASCII non-alphanumeric characters.
  2. Configure secure logging by setting up the encrypted syslog server. For details, refer to Encrypted syslog servers in Common Criteria mode.
  3. Use the enable aaa console command to ensure user authentication during the next reload. This also requires that you have enabled AAA authentication with the aaa authentication login default command.
  4. Use logging cli-command to allow you to log all syntactically valid CLI commands from each user session into the system log.
  5. Configure a motd banner using the banner motd command. Refer to CLI banner configuration for more information.
  6. Use the write memory command to save the configuration.
  7. Use the reload command to reload the device.

On successful completion of these steps, the device will be in Common Criteria Operational mode.

Note: FIPS self-tests are executed as part of device bootup. If any of the self-tests fails, the device reloads automatically. If there are continuous reloads, please contact Ruckus technical support.
Note: Use the exit command to terminate a local or remote interactive session.
Parent topic: Enabling Common Criteria Mode