SICURA

Collector

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.

In this category

Infrastructure

This document provides information on the infrastructure management, node organization, and scan triggering within the Sicura agent, including instructions on accepting/rejecting nodes, creating automation rules, and viewing scan results.

In this category

Plugins

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

In this category

Administration

This article provides an overview of the administration options available in the Console UI of the Sicura platform, including authentication providers, groups, users, and roles.

In this category

Security

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

In this category

Use the API

This article provides an overview of the API usage and Swagger documentation for Sicura Console.

In this category

Scheduling

This article explains how to use the scheduling feature in SICURA to define repeat scheduled tasks for folders and endpoints.

In this category

Reports

This article provides an overview of the report generation system in Sicura Console, including the two built-in report generators and the options available for exporting scan results in various formats.

In this category

Profiles

This article explains how profiles are used in the Sicura console to scan and enforce compliance rules on systems.

In this category

Prerequisites

This article provides instructions for installing and configuring PostgreSQL and creating a user and database for Sicura Console.

In this category

Account Configuration

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

In this category

Experimental

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

In this category

Enforce Compliance

This article explains the steps required to set up automatic compliance enforcement with the Sicura Console.

In this category

Database

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

In this category

Custom Profiles

This article explains how to use Sicura to export subsets of policies in order to customize what is enforced out of any given baseline policy.

In this category

Collector

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