Login messages must not disclose account state
- Risk
- Moderate
- Evidence
- metadata
- Section
- Authentication
- Fix shape
- org
Defence in depth — other controls still give coverage if this one fails.
Decidable from the instance’s own configuration.
Passwords, lockout, sessions, and what the sign-in page gives away.
One instance-level change.
Maps to ISO 27001
Control Statement: The login screen must not disclose whether an account exists, is locked, or was presented with an incorrect password.
Description:
Two system settings control the detail shown on a failed login:
DisplayAccountLockoutMessageAtLogin, which states that the account is locked, and
DisplayIncorrectPasswordMessageAtLogin, which states that the password was incorrect. This control
requires both to be disabled, so that a failed login returns an indistinguishable response regardless
of cause. Creatio’s own guidance recommends false for both.
Rationale: Distinguishable failure messages let an unauthenticated party test which accounts exist. “Incorrect password” confirms the account is real; a generic failure does not. That distinction converts the login screen into an account enumeration oracle, and a confirmed list of valid accounts is the input to every subsequent credential attack — it makes password spraying efficient and gives a phishing campaign a verified target list. A lockout message adds a second signal, revealing which accounts are already under attack and when the lock will lift.
Audit Procedure:
- Open System Designer → System settings.
- Record the configured values of
DisplayAccountLockoutMessageAtLoginandDisplayIncorrectPasswordMessageAtLogin. - Record the instance as non-compliant if either is enabled.
- Confirm the behaviour directly: attempt a login with a known-valid account and an incorrect password, and with an account that does not exist, and confirm the responses are indistinguishable.
Remediation:
- Set both settings to
false. - Re-run the two login attempts in step 4 of the audit procedure and confirm the responses no longer differ.
- Where a support process relies on users reporting the specific message they saw, update it before making the change.
Default Value:
Creatio’s guidance recommends false for both settings, which indicates they are not reliably false
before configuration. Verify the behaviour on the instance rather than assuming disclosure is off.
Cite this control as CSB-AUTH-005, Security Benchmark v0.5.0. Verified against
Creatio 8.x. Published by ctx10; not
affiliated with or endorsed by Creatio.