Sicura Enterprise Edition
  1. Introduction
  2. Licensing
  3. Installing Sicura Enterprise
  4. Server install from RPM
  5. Server install from ISO
  6. Upgrade Sicura Enterprise
  7. Server Installation via Control Repo
  8. Enable SIMP Compliance Engine
  9. Configure SIMP Compliance Engine
  10. Included Compliance Profiles
  11. Console install via Puppet
  12. Agent Install via Puppet
  13. Coverage - CIS, Windows
  14. Coverage - CIS, Linux
  15. Coverage - CMMC, Windows
  16. Coverage - CMMC, Linux
  17. Coverage - DISA, Windows
  18. Coverage - DISA, Linux
  19. Coverage - NIST 800-171 r2, Windows
  20. Linux DISA Module Usage
  21. Windows CIS module usage
  22. Linux CIS Module Usage
  23. Linux SSG Module Usage

Console Install via Puppet

The Sicura Enterprise installation includes a Puppet module to manage the installation and configuration of the Sicura Console. By default, it will install and configure a local PostgreSQL database to hold Console-specific data. See the module REFERENCE file for details on disabling this behavior and configuring a connection to an existing database server.

Configure Prerequisites

Set the sicura_console::license_key parameter to the contents of your Sicura Enterprise license key.

Add the following to the appropriate host data file in /etc/puppetlabs/code/environments/production/data/hosts/:

sicura_console::license_key: |-
 '<contents of license.key>'

If you want to enable SSL, also set the following options:

sicura_console::ssl_enable: true
sicura_console::ssl_key: '<path to SSL certificate private key file>'
sicura_console::ssl_cert: '<path to SSL certificate file>'


To install the Sicura Console, include the sicura_console class on the system you want the Console to be installed on.

Add the following to an appropriate data file in /etc/puppetlabs/code/environment/production/data:

  - sicura_console
sicura_console::license_key: |-
  <contents of your Sicura license file>

To use an existing PostgreSQL server, add the following parameters in hieradata:

sicura_console::manage_db: false
sicura_console::dburi: 'postgres://<DB username>:<DB password>@<DB server>:<DB port>/<database name>'

The Console will by default listen on port 6468. Use the following hieradata to set these to your requirements:

sicura_console::listen_address: '<specific IP address on the Console server, or for all interfaces>'
sicura_console::listen_port: '<port number>'