- RPM Installation
- Container Installation
- Running Sicura Console
- Known Issues
- How to - Enforce Compliance
- How to - Custom Profiles
- How to - Use the API
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 of that system against various compliance profiles
- find failing controls
- receive Puppet remediation data
- generate reports against your data
Sicura Console currently requires an EL 7 or 8 (Red Hat or CentOS) Linux Server with network access to your infrastructure.
Access to the Console has been tested on clients running current versions of Chrome, Firefox, Safari, and Microsoft Edge.
- The default unencrypted port is 6468, but we recommend running encrypted on port 443. The configured port(s) 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.
- At a minimum, your Linux server (or VM environment) will need 750MB available to
/etcfor the Console installation, basic logs, and remediation modules. 5GB of storage is recommended for long-term storage of logs. The location of the logs is configurable.
- Your Linux server (or VM environment) should have a minimum dual-core CPU and 2GB of RAM. A quad-core CPU and at least 6GB of RAM is recommended.
- NOTE! You will need a Sicura Enterprise License Key to use any part of Sicura Console.