Skip to content

Introduction

The Sicura Console is the flagship feature for Sicura Enterprise. It is a web client for monitoring compliance across your infrastructure. Once you register a system using the packaged Sicura Agent, you'll be able to: - Perform scans - Monitor compliance against various compliance profiles - Find failing controls - Receive Puppet remediation data

What's New

See What's New for the highlights of the current release, and Release Notes for the history of previous releases. Starting with the 2025.5.0 release, Sicura Console has a completely rewritten frontend web application and is distributed exclusively as a container image — for details on that transition, see 2025.5.0 in the Release Notes.

System Requirements

Sicura Console is now distributed exclusively as a container image and can be deployed in any environment that supports container runtimes (Docker, Podman, Kubernetes, etc.).

Sicura Console is expected to be fully functional on clients running current versions of modern browsers, including Chrome, Firefox, Safari, and Microsoft Edge.

  • The default unencrypted port is 80 for both the web UI and Agent communication, but we recommend running encrypted. (See our reference SSL configuration for more information.) The configured ports will need to be open between every node you are scanning and every system you need to have access to the Console's tools and reports.
  • For test deployments, we recommend allocating at least 2GB of memory and 2 CPU cores. For production use with a large number of agents, 4GB of memory and 4 CPU cores is recommended.
  • At least 5GB of storage is recommended for logs and operating data. The location of the logs is configurable.
  • A PostgreSQL database (version 15 or newer recommended) is required for storing application data.

Note: You will need a Sicura Enterprise License Key to use any part of Sicura Console.