Accounts unused for a set period are disabled automatically.
What it actually means
Stale accounts are easy targets and nobody's watching them. After a defined period of inactivity, identifiers should be disabled — ideally automatically through your identity provider's lifecycle policy, backed by periodic access reviews.
Pass or fail — an assessor needs a "yes" to each
- A defined inactivity period triggers disablement.
- Disablement is automated or caught by regular review.
What to have ready
- Lifecycle/inactivity policy
- Identity-provider configuration or review records
Where teams trip up
- Dormant accounts left enabled for months
- Disablement that depends on someone remembering
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.7 — Enforce password complexity3.5.8 — Block password reuse3.5.9 — Force change of temporary passwords3.5.10 — Protect stored and transmitted passwords3.5.11 — Obscure authentication feedback