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



Pruning Report Data

To keep the database from storing too many reports, you can specify the maximum number of reports to store per node using the following setting. The default is 3.

main.max_scans: 3

Configuring Sicura Console Collector

The Collector is the communication point between the Sicura Agent and Sicura Console. The current version of the collector is v3, which all Sicura Agents since Console version 1.8.0 fully support. If, for whatever reason, you want to use an Agent from previous releases, you will need to enable the legacy Collector.

main.legacy_collector: true

Enabling this configuration option will bring back the v2 Collector and the Client Installation page. You can use the registration token as mentioned in the v2 documentation.