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

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