Hardening Redis for rConfig
Hardening Redis for rConfig
Section titled “Hardening Redis for rConfig”rConfig’s job queue lives in Redis, and Horizon runs every job it finds there. Access to Redis is access to the workers, which is how CVE-2026-124079 escalated. These settings follow Redis’s own security guidance.
Require a password
Section titled “Require a password”One command sets a password in Redis and in .env together, and restarts the workers (redis.auth):
cd /var/www/html/rconfig8php artisan rconfig:redis-secureSee Redis Authentication for rotation and troubleshooting.
redis.conf
Section titled “redis.conf”/etc/redis/redis.conf or /etc/redis.conf. Restart Redis afterwards.
# Loopback only, with protected mode as a second layer (redis.bind)bind 127.0.0.1 -::1protected-mode yes
# Never silently drop queued jobs under memory pressure (redis.persistence)maxmemory-policy noevictionappendonly yesA remote Redis needs TLS: REDIS_SCHEME=tls in .env (redis.tls_remote).
Run the workers as the web user
Section titled “Run the workers as the web user”Horizon, the scheduler and the SNMP trap receiver must never run as root (runtime.worker_user). Check with:
sudo php artisan rconfig:security-check --only=runtime.worker_userSee Worker Privilege.
Standards: Redis security guidance (requirepass, bind, protected-mode), NIST SP 800-53 AC-3, AC-6, IA-2, SC-7.