Security checks: Redis
Security checks: Redis
Section titled “Security checks: Redis”Redis holds rConfig’s job queue, so access to Redis is access to the workers that run jobs.
From V8.5.0, these checks run in php artisan rconfig:security-check and in Security Center. Run only this group with:
cd /var/www/html/rconfig8php artisan rconfig:security-check --only=redisEach 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 |
|---|---|---|
redis.auth |
Critical | Redis requires a password |
redis.bind |
High | Redis listens on this host only |
redis.persistence |
Medium | Redis never evicts queued jobs |
redis.tls_remote |
High | A remote Redis connection is encrypted |
redis.version_eol |
Medium | Redis still gets security fixes |
Redis requires a password
Section titled “Redis requires a password”Check ID: redis.auth · Severity: Critical
rConfig’s workers run jobs from Redis. Without a password, any local process, or a device target pointed at the server, can write a job that the workers run (CVE-2026-124079).
Guards against: rCFG-SA-2026-09, rCFG-SA-2026-11
References: NIST IA-2, NIST AC-3, CVE-2026-124079, Redis security guidance (requirepass/ACL)
Redis listens on this host only
Section titled “Redis listens on this host only”Check ID: redis.bind · Severity: High
A Redis bound to every interface can be reached from the network, so the password is its only protection. Bind it to loopback and keep protected-mode on as a second layer.
Guards against: rCFG-SA-2026-09
References: NIST SC-7, Redis security guidance (bind, protected-mode)
Redis never evicts queued jobs
Section titled “Redis never evicts queued jobs”Check ID: redis.persistence · Severity: Medium
rConfig’s queue lives in Redis. An eviction policy other than noeviction lets Redis delete queued jobs (backups, alerts, compliance runs) under memory pressure without any error.
References: NIST CP-9, NIS2 21(2)(c), RCO-2185
A remote Redis connection is encrypted
Section titled “A remote Redis connection is encrypted”Check ID: redis.tls_remote · Severity: High
With Redis on another host, the Redis password and every queued job cross the network. Without TLS they can be read or changed in transit.
References: NIST SC-8, NIS2 21(2)(h)
Redis still gets security fixes
Section titled “Redis still gets security fixes”Check ID: redis.version_eol · Severity: Medium
An end-of-life Redis release no longer gets security fixes.
References: NIST SI-2
See Hardening guides for the configuration snippets behind these checks, and NIS2 Article 21 mapping for the controls they give evidence for.