Password fields show dots, not the characters typed.
What it actually means
The simplest control in the family: login interfaces must mask authentication input (the classic password dots) so it isn't exposed on screen. Standard on every modern system — the task is confirming no custom login form leaks it.
Pass or fail — an assessor needs a "yes" to each
- All login interfaces mask password entry.
- No custom/legacy form displays credentials in clear text.
What to have ready
- Confirmation across login interfaces (incl. any custom apps)
Where teams trip up
- A homegrown app that shows the password
- A 'show password' default left on in a sensitive context
See where this control puts your score
Run all 110 requirements free in about 10 minutes — or draft your SSP language for this control. No signup.
Calculate your SPRS score →Draft your SSP language →Connected requirements
More in Identification & Authentication (3.5)
3.5.1 — Uniquely identify users, processes, and devices3.5.2 — Authenticate before access3.5.3 — Multifactor authentication (MFA)3.5.4 — Replay-resistant authentication3.5.5 — Don't recycle identifiers3.5.6 — Disable dormant accounts3.5.7 — Enforce password complexity3.5.8 — Block password reuse3.5.9 — Force change of temporary passwords3.5.10 — Protect stored and transmitted passwords