Security checks: Data at rest
Security checks: Data at rest
Section titled “Security checks: Data at rest”Credentials and configs at rest: encryption with APP_KEY, plain-text secrets left in tables, and file permissions on saved configs.
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=dataEach 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 |
|---|---|---|
data.credentials_encrypted |
Critical | Stored credentials are encrypted and readable with APP_KEY |
data.integration_secrets |
High | Integration secrets are encrypted |
data.failed_jobs_secrets |
Medium | Failed jobs do not hold plain-text secrets |
data.storage_world_writable |
High | Other local users cannot write to rConfig storage |
data.config_folder |
High | Other local users cannot list or change saved configs |
data.config_file_modes |
High | Saved configs are private to rConfig |
data.mask_credentials |
Low | Device credentials are masked in the UI and API |
Stored credentials are encrypted and readable with APP_KEY
Section titled “Stored credentials are encrypted and readable with APP_KEY”Check ID: data.credentials_encrypted · Severity: Critical
Device, enable, SSH key, SMTP, LDAP, RADIUS and integration secrets must be stored encrypted with APP_KEY. Plain text leaks them through any database backup or export; values APP_KEY cannot decrypt mean a key change went wrong; serialized objects were an attack path (SEC-EXT-010).
Guards against: rCFG-SA-2026-10
References: NIST SC-28, NIS2 21(2)(h), SEC-EXT-010, SEC-EXT-003
Integration secrets are encrypted
Section titled “Integration secrets are encrypted”Check ID: data.integration_secrets · Severity: High
Integration API keys and passwords grant access to other systems (NetBox, Zabbix, SolarWinds, clouds). Before 8.4.2 some were stored in plain text alongside the integration settings (RCO-2107).
References: NIST SC-28, NIS2 21(2)(d), RCO-2107
Failed jobs do not hold plain-text secrets
Section titled “Failed jobs do not hold plain-text secrets”Check ID: data.failed_jobs_secrets · Severity: Medium
When a job fails, its whole payload is kept in failed_jobs. Jobs that carried credentials in plain text leave them there, in every database backup (SEC-INT-002).
References: NIST SC-28, NIST AU-9, SEC-INT-002
Other local users cannot write to rConfig storage
Section titled “Other local users cannot write to rConfig storage”Check ID: data.storage_world_writable · Severity: High
A storage folder any local user can write to lets them plant files that rConfig later reads, imports or serves.
References: NIST AC-6, CIS RHEL 9 6.1 (world-writable files), RCO-1790
Other local users cannot list or change saved configs
Section titled “Other local users cannot list or change saved configs”Check ID: data.config_folder · Severity: High
Device configs hold hashed and sometimes clear-text passwords, SNMP communities and network layout. Only rConfig itself should reach the config folder.
References: NIST AC-6, NIST SC-28, RCO-1268
Saved configs are private to rConfig
Section titled “Saved configs are private to rConfig”Check ID: data.config_file_modes · Severity: High
Configs saved before 8.4.1 could be readable by every local account. They hold secrets, so they must be 0440 or 0640 with folders 0750.
In-app fix: users with the security.update permission can click Tighten config permissions on the finding. rConfig shows what will change first, records the fix in the activity log and runs the checks again.
References: NIST AC-6, NIST SC-28, RCO-1268
Device credentials are masked in the UI and API
Section titled “Device credentials are masked in the UI and API”Check ID: data.mask_credentials · Severity: Low
Masking keeps device passwords off screens, screenshots and API responses, so only people who need a credential see it (SEC-EXT-006).
References: NIST AC-3, NIST SC-28, SEC-EXT-006
See Hardening guides for the configuration snippets behind these checks, and NIS2 Article 21 mapping for the controls they give evidence for.