Sicura Logo


Note: All of the following config options can be set in  /etc/sicura/sicura-console.yaml

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.



This article provides configuration options for the Sicura Console, including disabling remediation, changing cryptographic settings, and configuring SSL termination.

Read Article


This article explains how to configure the Sicura Console Collector, including pruning report data and enabling legacy versions.

Read Article


This article describes an experimental configuration option to improve simultaneous use of the console via request threading.

Read Article


This article provides information on the Sicura Console, including its plugins, configuration options, and instructions for setting up notification and authentication providers.

Read Article

Account Configuration

This article provides instructions on how to configure the administrator account for Sicura Console.

Read Article


This article provides instructions and information on configuring the database connection for the Sicura Console.

Read Article