Security checks: Runtime and privileges
Security checks: Runtime and privileges
Section titled “Security checks: Runtime and privileges”What runs and as whom: Horizon, the scheduler, root helpers, the web terminal and device targets that point back at this server.
From V8.5.0, these checks run in php artisan rconfig:security-check and on Security Review. Run only this group with:
cd /var/www/html/rconfig8php artisan rconfig:security-check --only=runtimeEach 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 |
|---|---|---|
runtime.worker_user |
Critical | Nothing runs as root |
runtime.scheduler |
High | The scheduler is running |
runtime.queue |
High | Queue workers are running |
runtime.security_check_stale |
Medium | The daily security check is running |
runtime.xftp_helper |
High | xFTP uses the root-owned helper, not open Docker access |
runtime.vector_hub_helper |
High | Vector Hub privileged actions go through the root-owned helper |
runtime.web_terminal |
Low | Web terminal sessions are recorded |
runtime.device_targets |
High | No device points back at the rConfig server |
Nothing runs as root
Section titled “Nothing runs as root”Check ID: runtime.worker_user · Severity: Critical
Horizon workers run queued jobs. As root, any job injection becomes full control of the server, which is how CVE-2026-124079 escalated.
Guards against: rCFG-SA-2026-09
References: NIST AC-6, CIS Controls 5.4, CVE-2026-124079
The scheduler is running
Section titled “The scheduler is running”Check ID: runtime.scheduler · Severity: High
The scheduler runs backups, the daily security check, data purges and advisory refreshes. If it stops, problems stop being detected.
References: NIST SI-4, NIS2 21(2)(c)
Queue workers are running
Section titled “Queue workers are running”Check ID: runtime.queue · Severity: High
Horizon runs backups, notifications (security alerts included) and in-app fixes. Without it, alerts are queued but never sent.
References: NIST SI-4, NIS2 21(2)(c)
The daily security check is running
Section titled “The daily security check is running”Check ID: runtime.security_check_stale · Severity: Medium
Security alerts come from the scheduled daily run. If it stops, a new failure is never reported.
References: NIST CA-7, NIS2 21(2)(f)
xFTP uses the root-owned helper, not open Docker access
Section titled “xFTP uses the root-owned helper, not open Docker access”Check ID: runtime.xftp_helper · Severity: High
Access to the Docker socket is root access. rConfig reaches Docker only through a narrow root-owned helper, so the socket must not be open to all users and the web user must not be in the docker group. /srv/xftp must not be world-writable.
References: NIST AC-6, CIS Docker 3.15 (docker.sock ownership), RCO-1815, RCO-1816
Vector Hub privileged actions go through the root-owned helper
Section titled “Vector Hub privileged actions go through the root-owned helper”Check ID: runtime.vector_hub_helper · Severity: High
Vector Hub needs a few root actions. They must go through the installed root-owned wrapper and its narrow sudo rule, never through a wider sudo grant or a root worker.
References: NIST AC-6, RCO-1794
Web terminal sessions are recorded
Section titled “Web terminal sessions are recorded”Check ID: runtime.web_terminal · Severity: Low
The web terminal gives interactive device access from the browser. Recording every session, with no opt-out, keeps an audit trail of what was typed on each device.
References: NIST AU-2, NIST AU-14, NIS2 21(2)(b), RCO-1900
No device points back at the rConfig server
Section titled “No device points back at the rConfig server”Check ID: runtime.device_targets · Severity: High
A device whose address resolves to this server lets a signed-in user aim rConfig’s connections at its own internal services, such as Redis (rCFG-SA-2026-09, rCFG-SA-2026-11).
Guards against: rCFG-SA-2026-09, rCFG-SA-2026-11
References: NIST SC-7, OWASP ASVS V12.6 (SSRF), GHSA-p5q7-2wwp-q42f
See Hardening guides for the configuration snippets behind these checks, and NIS2 Article 21 mapping for the controls they give evidence for.