Identities and credentials are managed for authorized users and devices
Every account that can access your systems is a potential entry point. Managing identities centrally, with a single source of truth for who has access to what, lets you grant access consistently, revoke it immediately when someone leaves, and audit access decisions over time.
Implementation steps
- 1
Centralize identity in a single IdP
Route all application access through one identity provider. Every SaaS tool, cloud console, and internal service should authenticate via your IdP, not via shared passwords or per-app local accounts.
oktagoogle-workspacemicrosoft-entrajumpcloud - 2
Enforce unique accounts per person
No shared accounts. Every user has exactly one identity tied to their work email. Shared credentials make attribution impossible and cannot be revoked individually.
- 3
Implement a joiner-mover-leaver process
Define a documented procedure for provisioning access on day one, adjusting it when roles change, and fully revoking it within 24 hours of departure. Automate where possible via your IdP's lifecycle management.
oktaripplingworkday - 4
Review active accounts quarterly
Run an access review every quarter. For each system, verify that every account with access still needs it. Revoke stale accounts. Document the review.
Evidence required
IdP user directory
Screenshot or export of your identity provider showing all active users.
- · Okta people list export
- · Google Workspace admin users report
- · Entra ID user list
Joiner-mover-leaver procedure
Written document describing the process for onboarding, role changes, and offboarding.
- · IT runbook or wiki page
- · HR onboarding checklist that includes access provisioning steps
Most recent access review
Documentation that an access review was completed in the last 90 days.
- · Signed-off spreadsheet from the last quarterly review
- · Ticket or task marked complete with reviewer name and date
Related controls
Identities are proofed and bound to credentials based on the context of interactions
Identity Management, Authentication, and Access Control
Users, services, and hardware are authenticated
Identity Management, Authentication, and Access Control
Identity assertions are protected, conveyed, and verified
Identity Management, Authentication, and Access Control
Access permissions are defined in policy, enforced, and reviewed using least privilege and separation of duties
Identity Management, Authentication, and Access Control