Skip to content

Security checks: Operating system

Operating system settings the web user can read. The root server check script covers the rest.

From V8.5.0, these checks run in php artisan rconfig:security-check and in Security Center. Run only this group with:

Terminal window
cd /var/www/html/rconfig8
php artisan rconfig:security-check --only=os

Each failing check shows the exact fix for your server, including paths, on the page and in the command output. The sections below explain what each check looks for.

Check Severity Checks that
os.selinux Medium SELinux is enforcing
os.firewall High A host firewall is active
os.auto_updates Low OS security updates are applied or reported automatically
os.reboot_required Low No kernel or library update is waiting for a reboot
os.time_sync Medium The clock is synchronised
os.auditd Low The Linux audit daemon is running
os.default_ssl_site High Apache’s stock HTTPS site is not serving
os.server_check_script Low The root server check has run recently

Check ID: os.selinux · Severity: Medium

On RHEL-family systems SELinux confines Apache, PHP-FPM and Redis, so a compromised web process cannot read or write outside its labelled paths. rConfig’s install scripts set the labels it needs.

References: CIS RHEL 9 1.6 (SELinux), NIST AC-3(3), DISA STIG RHEL 9


Check ID: os.firewall · Severity: High

A host firewall limits the server to HTTPS, SSH and the xFTP/SNMP ports rConfig needs, so a database or Redis misconfiguration is not reachable from the network.

References: CIS RHEL 9 3.4 (firewall), CIS Ubuntu 24.04 4.1, NIST SC-7, NIS2 21(2)(i)


OS security updates are applied or reported automatically

Section titled “OS security updates are applied or reported automatically”

Check ID: os.auto_updates · Severity: Low

PHP, OpenSSL and OpenSSH fixes reach rConfig through OS packages. Automatic security updates, or at least automatic notification, keep the gap between a fix and its install short.

References: CIS RHEL 9 1.2 (updates), NIST SI-2(2), NIS2 21(2)(e)


No kernel or library update is waiting for a reboot

Section titled “No kernel or library update is waiting for a reboot”

Check ID: os.reboot_required · Severity: Low

Installed kernel and core library fixes protect nothing until the server restarts into them.

References: NIST SI-2


Check ID: os.time_sync · Severity: Medium

Audit logs, config change times, token expiry and TLS all rely on the clock. A drifting clock makes incident timelines unreliable.

References: NIST AU-8, CIS RHEL 9 2.1 (chrony), NIS2 21(2)(b)


Check ID: os.auditd · Severity: Low

auditd records logins, privilege use and changes to sensitive files at the OS level, which rConfig’s own activity log cannot see.

References: CIS RHEL 9 6.2 (auditd), NIST AU-2, NIST AU-12, NIS2 21(2)(b)


Apache’s stock HTTPS site is not serving

Section titled “Apache’s stock HTTPS site is not serving”

Check ID: os.default_ssl_site · Severity: High

On RHEL-family installs, mod_ssl’s stock ssl.conf adds a default:443 site with the distribution DocumentRoot. On some installs that served rConfig’s whole folder, .env included (rCFG-SA-2026-15).

Guards against: rCFG-SA-2026-15

References: SEC-EXT-014, CIS Apache 2.4, NIST CM-7


Check ID: os.server_check_script · Severity: Low

Some settings (sshd, sudoers, Apache vhosts, pg_hba.conf, redis.conf) are readable by root only. The server check script reviews them and shares its results with this page.

References: NIST CA-7, NIS2 21(2)(f)


See Hardening guides for the configuration snippets behind these checks, and NIS2 Article 21 mapping for the controls they give evidence for.