Sicura Console
  1. Introduction
  2. Installation
  3. RPM Installation
  4. Container Installation
  5. Upgrades
  6. Running Sicura Console
  7. Configuration - Accounts
  8. Configuration - Database
  9. Configuration - Collector
  10. Configuration - Security
  11. Configuration - Plugins
  12. Configuration - Experimental
  13. Sidebar - Administration
  14. Sidebar - Infrastructure
  15. Sidebar - Profiles
  16. Sidebar - Reports
  17. Sidebar - Scheduling
  18. Commands
  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


Configuring the Database connection

There is no default database so you must define a PostgreSQL connection string in sicura-console.yaml using one of the following formats:

main.database: postgres://ip_address:port/database
 user: user
 password: password
main.database: "postgres://"
 user: user
 password: password
 host: ip_address
 port: port
 database: database

You can specify additional general and PostgreSQL specific options using main.database.options.

Migrating from SQLite to PostgreSQL

To migrate a SQLite database to PostgreSQL, use the sicura-console migrate command.

Changing the Database Table Prefix

By default, the Sicura Console configures a table prefix for all database tables it manages. This allows admins the capability to run multiple Sicura Console instances using the same underlying database. For example, one could have tables with the names production, staging, and dev all within the same database.

The default prefix is production, but it can be changed. For example, this creates all database tables with dev_ in front of them.

A table prefix is considered valid if it:

main.database_table_prefix: dev