Manage the identity lifecycle
Create, update, review, and remove access as people and systems change.
- Describe joiner, mover, and leaver processes and access reviews.
IAM follows identities and permissions through their lifecycle. When someone or a service joins, grant approved access for its responsibilities. When roles change, update access so obsolete permissions do not accumulate. When an identity leaves or is retired, disable credentials and revoke sessions, keys, tokens, and grants. Periodic access reviews help find permissions that are no longer needed.
Automating lifecycle steps can reduce delays and orphaned access, but automation needs authoritative identity data, approvals, and error handling. Include non-human identities such as service accounts and API credentials in inventory and review processes. Keep evidence of approvals and changes for audit needs.
Practice: run an access review
Try it
Up to 15 XPReview this quarter’s access
You’re reviewing access for your team. Decide what should happen to each one.
“An engineer has production read access and uses it every week.”
“A support agent has admin rights but only ever views tickets.”
“A contractor’s account from a project that ended in March.”
“A service account with no owner, unused for 200 days.”
“A moved employee still has access to their old team’s systems.”
Try it
Up to 15 XPAudit an offboarding checklist
A developer left the company today. Click everything this checklist gets wrong.
Click every suspicious section. There are 3.
Key takeaways
Describe joiner, mover, and leaver processes and access reviews.
Treat access as a lifecycle: grant deliberately, review regularly, and revoke promptly.
Lesson quiz
5 questions · pass with 4 correct · up to 50 XP
Passing this quiz completes the lesson and keeps your streak going. Questions you miss come back in review sessions later.
Questions about this lesson
Stuck? Ask. Figured something out? Share it. Explaining is one of the best ways to learn.
Loading posts…