SICURA

Configuring the Database Connection

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

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
main.database.options:
 user: user
 password: password
main.database: "postgres://"
main.database.options:
 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.

main.database_table_prefix: dev

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.