1. Introduction
2. Installation
3. RPM Installation
4. Container Installation
5. Upgrades
6. Running Sicura Console
7. Configuration - Accounts
8. Configuration - Database
9. Configuration - Collector
10. Configuration - Security
11. Configuration - Plugins
12. Configuration - Experimental
13. Sidebar - Administration
14. Sidebar - Infrastructure
15. Sidebar - Profiles
16. Sidebar - Reports
17. Sidebar - Scheduling
18. Commands
19. Known Issues
20. How To - Enforce compliance
21. How To - Enforce custom profiles
22. How To - Use the API

Note: All of the following config options can be set in

/etc/sicura/sicura-console.yaml

Security

Enable/Disable Remediation from the Console.

To disable the ‘Remediate’ button system wide, set the following option to false.

main.disable_enforcement: true

Setting the Hashing Algorithm for the Database Schema Engine

main.schema_engine.signature_hash: "SHA384"

Changing Cryptographic Settings

Some cryptographic settings used by Sicura Console have configuration options specified in the config file to meet some policy requirements.

To set the hashing algorithm for the web server’s HMAC algorithm use the following setting:

main.rack-session.hmac: "SHA384"

Configuring Listen Address and Port

The address and port can be specified using the following parameters:

main.listen_ip: localhost

Note: In order for the Sicura Console to be discoverable externally (Both LAN and Internet) listen_ip should be 0.0.0.0

main.listen_port: 6468

Using Internal SSL Termination

First, either self-generate or purchase an SSL certificate and key.

Then place them in /etc/ssl/certs and /etc/ssl/private respectively.

In sicura-console.yaml add the following configuration:

main.ssl.enabled: true
main.ssl.key: "/etc/ssl/private/mykey.key"
main.ssl.cert: "/etc/ssl/certs/mycert.pem"

# Enable SSL verify (Insecure if set to false)
main.ssl.verify: true