Security checks: Devices
Security checks: Devices
Section titled “Security checks: Devices”How rConfig talks to devices: Telnet and SNMP trap authentication.
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=devicesEach 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 |
|---|---|---|
devices.telnet |
Medium | Devices are backed up over SSH, not Telnet |
devices.snmp_community |
Medium | SNMP traps are authenticated |
Devices are backed up over SSH, not Telnet
Section titled “Devices are backed up over SSH, not Telnet”Check ID: devices.telnet · Severity: Medium
Telnet sends the device username, password and enable password in clear text on every backup. Anyone on the path between rConfig and the device can capture them.
References: NIST SC-8, NIST IA-5, CIS Controls 12.2, NIS2 21(2)(h)
SNMP traps are authenticated
Section titled “SNMP traps are authenticated”Check ID: devices.snmp_community · Severity: Medium
Traps can trigger config downloads. Accepting v1/v2c traps without checking a strong community lets anyone on the network trigger them; SNMPv3 authenticates and encrypts traps.
References: NIST IA-3, NIST SC-8, CIS Controls 4.6
See Hardening guides for the configuration snippets behind these checks, and NIS2 Article 21 mapping for the controls they give evidence for.