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

Container Upgrades

As of the 2025.2.0 release, Sicura Console is distributed exclusively as a container image. Container upgrades are straightforward and involve pulling the latest image and restarting your container.

Upgrading Container Installations

1. Pull the latest version of the Sicura Console container:

    docker pull registry.customers.sicura.us/products/sicura-console:latest
   

   For specific versions:

    docker pull registry.customers.sicura.us/products/sicura-console:2025.5.0
   

2. Stop and remove the current container (if it’s running):

    docker stop sicura-console
    docker rm sicura-console
   

3. Start a new container using the same configuration and environment variables as your previous installation.

   Refer to the Running the Console Container section in the Container Installation guide for detailed examples of different deployment options.

Note: For container-to-container upgrades only, the database will be automatically upgraded to support new features when the new container connects to it.

Migrating from RPM Installation to Container

IMPORTANT: The 2025.5.0 release requires a fresh database. Data migration from RPM-based installations to container-based installations is not currently supported. You will need to set up a new database instance for your container installation and reconfigure your environment.

If you’re currently using an RPM-based installation, follow these steps to migrate to the container-based installation:

1. Backup your current configuration for reference:

    mkdir -p /path/to/backup
    cp -r /etc/sicura/ /path/to/backup/etc-sicura
   

2. Set up a new PostgreSQL database for the container installation.

   Refer to the PostgreSQL Server section in the Container Installation guide for detailed instructions.

3. Copy your license key and create a new configuration:

    mkdir -p /path/to/config
    cp /etc/sicura/license.key /path/to/config/
    # Note: Do not copy the old sicura-console.yaml directly
    # Instead, create a new one based on the template but with your specific settings
   

4. Deploy the Sicura Console container with your new configuration.

   Refer to the Running the Console Container section in the Container Installation guide for detailed deployment options.

Note: After migrating to the container-based installation, you’ll need to re-register all your agents and reconfigure your compliance profiles and other settings from scratch.

Cleaning Up RPM Install

To clean up an RPM install, you can do the following, but it is not required:

Uninstall RPMs

For SIMP Enterprise versions 6.5.3 and prior:

yum repo-pkgs simp-enterprise erase
yum repo-pkgs simp-community-simp erase
yum remove simp-release-enterprise

For Sicura Enterprise 6.5.4 and newer:

yum repo-pkgs sicura-console erase
yum remove sicura-release-console

Remove Puppet Modules

On RPM install, Puppet data is installed in /usr/share/simp/modules, and is not removed on uninstall. You can purge the /usr/share/simp directory if you don’t want to keep this data