Security checks: Web exposure
Security checks: Web exposure
Section titled “Security checks: Web exposure”Self-probes of this server’s own web endpoints, over HTTP and HTTPS, on 127.0.0.1, every server address and the APP_URL host. A path counts as exposed only when it is served and its content proves it is the real file.
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=webEach 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 |
|---|---|---|
web.env_exposed |
Critical | The .env file is not served over the web |
web.storage_exposed |
Critical | Storage, logs and saved configs are not served over the web |
web.vcs_exposed |
High | Git metadata is not served over the web |
web.composer_exposed |
Medium | Dependency manifests are not served over the web |
web.config_files |
Medium | Web server config files are not served |
web.dir_listing |
Medium | Directory listings are off |
web.registration_closed |
Critical | Self-registration is closed |
web.phpinfo_guest |
High | phpinfo() is not open to guests |
web.debug_tools |
High | No debug tools are reachable |
web.horizon_guest |
High | The Horizon dashboard is closed to guests |
web.log_viewer_guest |
High | The log viewer is closed to guests |
web.trace_method |
Low | HTTP TRACE is disabled |
web.server_tokens |
Low | Responses do not reveal server and PHP versions |
web.security_headers |
Medium | Browser security headers are sent |
web.https_redirect |
Medium | HTTP redirects to HTTPS, and never back |
web.public_dir_clean |
High | No backups, dumps or keys in the web root |
web.storage_symlink |
High | public/storage exposes only the public disk |
The .env file is not served over the web
Section titled “The .env file is not served over the web”Check ID: web.env_exposed · Severity: Critical
The .env file holds the database password, APP_KEY and every integration secret. On some RHEL-family installs the stock HTTPS site served the whole app folder, .env included (rCFG-SA-2026-15).
Guards against: rCFG-SA-2026-15
References: NIST SC-28, NIST CM-7, CIS Apache 2.4, SEC-EXT-014
Storage, logs and saved configs are not served over the web
Section titled “Storage, logs and saved configs are not served over the web”Check ID: web.storage_exposed · Severity: Critical
The storage folder holds device configs, logs and exports. Served over the web, anyone who can reach the server can list and download them.
Guards against: rCFG-SA-2026-15
References: NIST SC-28, NIST AC-3, CIS Apache 2.4, SEC-EXT-014
Git metadata is not served over the web
Section titled “Git metadata is not served over the web”Check ID: web.vcs_exposed · Severity: High
A served .git folder lets anyone rebuild the deployed source and its history, and find the exact version to attack.
Guards against: rCFG-SA-2026-15
References: NIST CM-7, OWASP ASVS V14.3
Dependency manifests are not served over the web
Section titled “Dependency manifests are not served over the web”Check ID: web.composer_exposed · Severity: Medium
composer.json, composer.lock and installed.json list every PHP package and version, which tells an attacker which known vulnerabilities to try.
Guards against: rCFG-SA-2026-15
References: NIST CM-7, NIST SR-3
Web server config files are not served
Section titled “Web server config files are not served”Check ID: web.config_files · Severity: Medium
Served .htaccess and web.config files reveal rewrite rules and access controls, and a served web.config was reported against rConfig before (RCO-1522).
References: NIST CM-7, CIS Apache 2.4, RCO-1522
Directory listings are off
Section titled “Directory listings are off”Check ID: web.dir_listing · Severity: Medium
Apache’s automatic directory index lists every file in a folder without an index page, so anything left there is easy to find.
References: NIST CM-7, CIS Apache 2.4 (Options -Indexes)
Self-registration is closed
Section titled “Self-registration is closed”Check ID: web.registration_closed · Severity: Critical
rConfig accounts are created by administrators only. An open registration route let anyone create an administrator account (CVE-2026-77915).
Guards against: CVE-2026-77915
References: NIST AC-2, NIS2 21(2)(i), CVE-2026-77915
phpinfo() is not open to guests
Section titled “phpinfo() is not open to guests”Check ID: web.phpinfo_guest · Severity: High
phpinfo() shows the PHP build, loaded modules, paths and server variables. rConfig shows it to signed-in admins only, and without environment values (RCO-1237).
References: NIST CM-7, NIST SI-11, RCO-1237
No debug tools are reachable
Section titled “No debug tools are reachable”Check ID: web.debug_tools · Severity: High
Telescope, Debugbar, Ignition and Clockwork record requests, queries and sometimes secrets, and some versions allow code execution. rConfig ships none of them; this catches one added by hand.
References: NIST CM-7, NIST SI-11, OWASP ASVS V14.3
The Horizon dashboard is closed to guests
Section titled “The Horizon dashboard is closed to guests”Check ID: web.horizon_guest · Severity: High
Horizon shows every queued job with its payload and lets the viewer retry or delete jobs. Only signed-in administrators may open it.
References: NIST AC-3, NIS2 21(2)(i)
The log viewer is closed to guests
Section titled “The log viewer is closed to guests”Check ID: web.log_viewer_guest · Severity: High
Application logs record errors, usernames, device addresses and sometimes device output. Only signed-in administrators may read them.
References: NIST AU-9, NIST AC-3
HTTP TRACE is disabled
Section titled “HTTP TRACE is disabled”Check ID: web.trace_method · Severity: Low
TRACE echoes the request back, headers included, which helps cross-site tracing attacks steal cookies. CIS asks for TraceEnable off.
References: CIS Apache 2.4 (TraceEnable off), NIST CM-7
Responses do not reveal server and PHP versions
Section titled “Responses do not reveal server and PHP versions”Check ID: web.server_tokens · Severity: Low
Version numbers in the Server and X-Powered-By headers tell an attacker which known vulnerabilities to try, without any probing.
References: CIS Apache 2.4 (ServerTokens Prod, ServerSignature Off), NIST CM-7
Browser security headers are sent
Section titled “Browser security headers are sent”Check ID: web.security_headers · Severity: Medium
These headers tell browsers not to guess content types, not to frame rConfig in another site (clickjacking), not to leak URLs to other sites, and to use HTTPS only.
References: OWASP ASVS V14.4, NIST SC-8, NIST SC-18
HTTP redirects to HTTPS, and never back
Section titled “HTTP redirects to HTTPS, and never back”Check ID: web.https_redirect · Severity: Medium
If plain HTTP still serves the app, users and scripts keep sending credentials unencrypted. A redirect from HTTPS back to HTTP silently drops encryption for the next request.
References: NIST SC-8, OWASP ASVS V9.1
No backups, dumps or keys in the web root
Section titled “No backups, dumps or keys in the web root”Check ID: web.public_dir_clean · Severity: High
Every file under public/ can be downloaded by anyone who can reach the server. Database dumps, archives, logs and keys left there are a direct leak.
In-app fix: users with the security.update permission can click Move to quarantine on the finding. rConfig shows what will change first, records the fix in the activity log and runs the checks again.
References: NIST CM-7, NIST SC-28, CIS Apache 2.4
public/storage exposes only the public disk
Section titled “public/storage exposes only the public disk”Check ID: web.storage_symlink · Severity: High
public/storage makes a folder downloadable. Pointed anywhere but storage/app/public, or replaced by a real folder, it can publish configs, logs or exports.
References: NIST AC-3, NIST CM-7
See Hardening guides for the configuration snippets behind these checks, and NIS2 Article 21 mapping for the controls they give evidence for.