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

Collector

Pruning Scan Data

To keep the database from storing too many scan results, you can specify the maximum number of scans to store per node using the following setting.

main.max_scans: 3

The default value is 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.