Security checks: Integrations
Security checks: Integrations
Section titled “Security checks: Integrations”Email transport and alert delivery.
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=integrationsEach 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 |
|---|---|---|
integrations.smtp_tls |
Medium | Email is sent over verified TLS |
integrations.alert_channels |
Medium | Security alerts reach someone |
Email is sent over verified TLS
Section titled “Email is sent over verified TLS”Check ID: integrations.smtp_tls · Severity: Medium
Alerts and reports can carry config excerpts and device names, and the SMTP login is a password. Without TLS, or without certificate checks, both can be read or altered on the way.
References: NIST SC-8, NIS2 21(2)(h)
Security alerts reach someone
Section titled “Security alerts reach someone”Check ID: integrations.alert_channels · Severity: Medium
A new security failure raises an alert. If nobody receives it by email, chat or webhook, it waits in the in-app bell until someone happens to sign in.
References: NIST IR-6, NIST SI-4(5), NIS2 21(2)(b)
See Hardening guides for the configuration snippets behind these checks, and NIS2 Article 21 mapping for the controls they give evidence for.