Users can't recycle their recent passwords.
What it actually means
Stop users from cycling back to an old password. Configure password history in your identity provider so a defined number of prior passwords can't be reused.
Pass or fail — an assessor needs a "yes" to each
- Password history is enforced for a defined number of generations.
What to have ready
- Password-history setting in the identity provider
Where teams trip up
- No history enforcement
- Users alternating between two passwords
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.9 — Force change of temporary passwords3.5.10 — Protect stored and transmitted passwords3.5.11 — Obscure authentication feedback