1. Introduction
2. Installation
3. Reference Deployment with SSL Termination
4. RPM Installation (Deprecated)
5. Container Installation
6. Upgrades
7. Running Sicura Console
8. Configuration - Accounts
9. Configuration - Database
10. Configuration - Collector
11. Configuration - Security
12. Configuration - Plugins
13. Configuration - Experimental
14. Sidebar - Administration
15. Sidebar - Infrastructure
16. Sidebar - Profiles
17. Sidebar - Reports
18. Sidebar - Scheduling
19. Known Issues
20. How To - Enforce compliance
21. How To - Enforce custom profiles
22. How To - Use the API

Note: All of the following config options can be set in

      /etc/sicura/sicura-console.yaml

Configuring the Administrator Account

Sicura Console creates this default account with full admin privileges:

Username: admin
Password: password

It is highly recommended to change the default username and password. You can also set a default admin token for the default administrative user to better facilitate using the REST API from systems like Puppet.

Changing the Default Password

Passwords in the config file are only stored as crypt(3)-style salted hashes. In order to make it easier to generate, sicura-console contains a helper flag that will take a plain text password and return the hash suitable for the configuration file:

sicura-console -e ‘password’

And then add the output to /etc/sicura/sicura-console.yaml

main.default_admin_password: '$5$7c03659ec01eab77$RB.C4ovajCc9m/JL2.oGX02OlpgMqJmejI72FutgbM5'

Changing the Default Username

It is also best practice to change the default ‘admin’ username to be something site specific:

main.default_admin_username: "sicura_root_admin"

Setting the Default Admin Token

The default authentication token is used to interact with the REST API without an account.

Notice: The default admin token is set to null and will not be usable until set.

main.default_admin_token: "mYxiQo0JCoVdGCZOwLzs"