Chapters0/43 ▾
- 1.Security Principles & Control Types0/5
- 2.Risk, Policy Hierarchy & Ethics0/4
- 3.Governance, Risk & Compliance0/4
- 4.Continuity, Disaster Recovery & Awareness0/4
- 5.Identity Lifecycle Management0/4
- 6.Logical Access Controls & Models0/4
- 7.Network Security Concepts0/5
- 8.Network Architecture & Cloud Security0/4
- 9.Data Security & Security Operations0/5
- 10.Incident Response, Assets & Testing0/4
Chapter 5 · Lesson 2 of 4
Access reviews, movers and privilege creep
1 min read
The review stage keeps access matched to the current job. Its biggest trigger is a mover: someone promoted or transferred. The correct handling is to remove the old role's entitlements at the same time the new ones are added.
Simply layering new access on top of old is how privilege creep happens, the slow buildup of rights from every earlier position. Privilege creep is a life cycle failure, not an attack and not a provisioning decision.
The fix is a periodic access review, also called recertification, in which each entitlement is confirmed, changed or revoked. The decision belongs to whoever knows the business need, usually the data or system owner or the person's manager.
The help desk only carries out changes, an auditor tests the control rather than owning it, and letting users certify their own access is weak because they want to keep everything.
Reviews also hunt for orphaned accounts: enabled accounts with no valid owner, often left by a contractor or leaver. Nobody watches them, so reused or guessed credentials go unnoticed. Example: a designer moved from Sales to Marketing a year ago and can still open the Sales pipeline. The quarterly review flags it and her manager revokes it.
Check yourself
1. Which situation is the textbook description of privilege creep?
2. An audit finds that long-serving staff still hold entitlements from roles they left years ago. Which measure actually corrects this finding?
Facts checked 2026-11-15 · Sources: ISC2 Certified in Cybersecurity (CC) Exam Outline
ISC2 Certified in Cybersecurity (CC) cheat sheet: every key fact on one page →