Security checks: Accounts and sign-in
Security checks: Accounts and sign-in
Section titled “Security checks: Accounts and sign-in”rConfig user accounts: default passwords, multi-factor sign-in through your identity provider, unused and administrator accounts, and LDAP transport.
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=accountsEach 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 |
|---|---|---|
accounts.default_admin |
Critical | No administrator uses a default password |
accounts.mfa |
Medium | Administrators sign in through an MFA-capable provider |
accounts.inactive |
Medium | No long-unused accounts |
accounts.admin_count |
Low | Few people hold the administrator role |
accounts.ldap_tls |
High | LDAP sign-in is encrypted |
accounts.login_throttle |
Medium | Repeated failed sign-ins are locked out |
No administrator uses a default password
Section titled “No administrator uses a default password”Check ID: accounts.default_admin · Severity: Critical
The install docs publish admin@domain.com / admin. An administrator still on it, or on another obvious password, hands the whole install to anyone who can reach the sign-in page.
References: NIST IA-5, NIS2 21(2)(i), CIS Controls 4.7, OWASP ASVS V2.1
Administrators sign in through an MFA-capable provider
Section titled “Administrators sign in through an MFA-capable provider”Check ID: accounts.mfa · Severity: Medium
NIS2 Article 21(2)(j) and most frameworks expect multi-factor sign-in for privileged accounts. rConfig takes MFA from your identity provider: SAML2 or Microsoft SSO, or RADIUS backed by an MFA service.
References: NIS2 21(2)(j), NIST IA-2(1), CIS Controls 6.5
No long-unused accounts
Section titled “No long-unused accounts”Check ID: accounts.inactive · Severity: Medium
Accounts of people who left or never used rConfig are unmonitored ways in. Review and remove them regularly.
References: NIST AC-2(3), NIS2 21(2)(i), CIS Controls 5.3
Few people hold the administrator role
Section titled “Few people hold the administrator role”Check ID: accounts.admin_count · Severity: Low
Every administrator can change credentials, roles and settings. Least privilege means most people get a narrower role from the RBAC templates.
References: NIST AC-6(5), NIS2 21(2)(i), CIS Controls 5.4
LDAP sign-in is encrypted
Section titled “LDAP sign-in is encrypted”Check ID: accounts.ldap_tls · Severity: High
Without LDAPS or StartTLS, every user’s directory password and the bind account’s password cross the network in clear text.
References: NIST SC-8, NIST IA-5(1), NIS2 21(2)(h)
Repeated failed sign-ins are locked out
Section titled “Repeated failed sign-ins are locked out”Check ID: accounts.login_throttle · Severity: Medium
Without a lockout, passwords can be guessed at network speed, and LDAP binds can be driven against your directory.
References: NIST AC-7, OWASP ASVS V2.2
See Hardening guides for the configuration snippets behind these checks, and NIS2 Article 21 mapping for the controls they give evidence for.