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

Running Sicura Console

By default, the Sicura Console RPM creates a user called sicura-console, and sets permissions on its default files based on the Sicura Console user. Commands for Sicura Console should be run by the sicura-console user.

There is also a Puppet module available for management of the sicura-console service and configuration.

Running Sicura Console Manually

To run sicura-console from the command line run:

sudo -u sicura-console sicura-console

Running Sicura Console at Boot

The Sicura Console RPM sets up a systemd unit file on EL7, or a sysvinit service file on EL6. You’ll need to enable the service, then start it.

EL7

systemctl enable sicura-console
systemctl start sicura-console