Study guide
Provisioning, Deprovisioning, and Access Reviews
ISC2 Certified in Cybersecurity CC
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
Official 2026 CC Exam Facts and Timeline CAT Format and Beginner Security Judgment Domain Map and Time Allocation 30, 60, and 90 Day Study Plan with Readiness Thresholds
2 Domain 1: Security Principles (24%)
CIA Triad as a Practical Decision Tool Authentication, Authorization, Accounting, and Non-Repudiation Privacy in the CC Outline Beginner Security Decision Scenarios AI Security in Security Principles
3 Domain 1: Risk Management and Security Controls
Risk Identification in Business Context Risk Management Processes Risk Treatment Decisions Security Controls: Technical, Administrative, and Physical
4 Domain 1: Governance, Ethics, Policy, and Privacy
Governance and the ISC2 Code of Ethics Policies, Procedures, Standards, Laws, and Regulations Privacy and AI Governance Due Care, Due Diligence, and Governance Decisions
5 Domain 1: Physical Security Controls
Physical Controls and Their Monitoring Tailgating and Physical Penetration Testing
6 Domain 2: Security Governance - Business Continuity
Business Continuity (BC)
7 Domain 2: Security Governance - Disaster Recovery
Disaster Recovery (DR) Redundancy in Business Continuity and Disaster Recovery
8 Domain 2: GRC Planning
GRC Planning: Purpose, Importance, and Tools
9 Domain 2: Measuring Cybersecurity Effectiveness
Security Metrics, KRIs, and Dashboards AI Security in Governance, Awareness, and Continuity
10 Domain 2 and Domain 5: Security Awareness and Triage
Security Awareness and Organizational Culture Phishing and Password Protection Security Event Triage and Human Review
11 Domain 3: Identity Lifecycle Management
Identification, Authentication, Authorization, and Accountability Multi-Factor Authentication and Password Protection Provisioning, Deprovisioning, and Access Reviews Service Accounts and AI Bots in Identity Management AI Bots and Service Accounts in Identity Management
12 Domain 3: Logical Access Controls
Least Privilege and Separation of Duties DAC, MAC, RBAC, and ABAC
13 Domain 4: Networking Fundamentals
Network Models and IP Addressing Firewalls: Ports and Applications Virtual Private Networks (VPN) Wireless Networks and Embedded Systems
14 Domain 4: Network Security Architecture and Cloud Security
Network Segmentation Defense in Depth and Zero Trust Cloud Characteristics and Shared Security Model Cloud Service Models, Deployment Models, and Shared Security AI in Network Security and Cloud Hosting
15 Domain 5: Incident Response
Incident Response (IR) and the Incident Response Plan Preparing the Incident Response Plan Incident Response Exercises and Tabletops AI in Security Operations and Incident Response
16 Domain 5: Security Monitoring
Logging and Monitoring Security Events
17 Domain 5: Threat Actors and Threat Intelligence
Threat Actors, Threat Intelligence, and Frameworks
18 Domain 5: Data Security
Encryption and Hashing for Data Security Data Handling: Classification, Labeling, Masking, and Sanitization Security of the AI Workspace
19 Domain 5: Asset Protection
Configuration and Change Management Change Management and Asset Protection Asset Lifecycle and End-of-Life Management
20 Domain 5: Data Handling Policy
Data Handling Policy and Classification
21 Domain 5: Security Testing
Security Readiness, Application, and Physical Testing
22 Integrated CC Scenario Labs
Risk and Control Selection Drill Continuity, Recovery, and Response Drill Access Control Design Drill Segmentation and Triage Drill
23 Final 14-Day Review and Exam Readiness
CAT Pacing and 100-125 Item Strategy Missed-Question Notebook and Domain Repair Exam Day Logistics and Rescheduling After Passing: AMF and CPE
Provisioning, Deprovisioning, and Access Reviews
Key Takeaways Explain This Topic AI
Provisioning creates or updates access based on an approved business need, ideally mapped to a role.
Deprovisioning disables or removes access promptly when it is no longer needed, especially at termination.
Joiner, mover, and leaver (JML) processes keep access aligned with employment status and job duties.
Access reviews (recertifications) ask managers or system owners to confirm that current access is still appropriate.
Delayed offboarding, orphaned accounts, and privilege creep from mover events are common identity-lifecycle risks.
Last updated: October 2026
The Joiner-Mover-Leaver Lifecycle
Provisioning creates, enables, or changes access for a subject; deprovisioning disables, removes, or reduces it when it is no longer needed. Together they form most of identity lifecycle management, and the goal is one sentence: the right identities should have the right access at the right time, and stale access should be gone.
Organizations model lifecycle events as joiner, mover, and leaver (JML) :
- Event Trigger Required action Main risk if mishandled
- Joiner New hire, contractor, service account Grant role-based baseline access Over-provisioning a new account
- Mover Role, department, or project change Add new access AND remove old Privilege creep / accumulation
- Leaver Termination or end of need Disable all access promptly Orphaned account, lingering access
Movers are the trickiest event. When a developer transfers from billing to the mobile-app team, the new repositories and tooling get added, but the old billing-deployment rights too often remain. Repeated over years, that produces privilege creep — access far beyond current duties — which violates least privilege and inflates the blast radius of any compromise.
Good provisioning starts with a request and approval from a manager or application owner who confirms business need. Access should map to a role when possible, and any exception should be documented with an end date — for example, temporary access to a project folder that auto-expires.
Deprovisioning Timing and Access Reviews
Deprovisioning timing depends on the scenario, so distinguish the cases:
Voluntary resignation — schedule removal for the final working day, coordinated with HR.
Involuntary termination or insider-risk case — disable access before the employee is notified, to prevent retaliation or data theft.
Contractor end-date — set expiration at provisioning time so access lapses automatically.
At termination, sweep every system: SSO, email, VPN, cloud apps, privileged accounts , building/badge access, and company devices. A single forgotten cloud admin account becomes an orphaned account — an active credential with no valid owner, a prime target for attackers.
Access reviews (recertification)
Access reviews , also called recertifications , are periodic checks where managers, data owners, or application owners confirm that current access is still appropriate. Typical questions: Does this user still work here? Still hold this job? Still need this application? Does this privileged role still have a valid owner? Reviews matter most for privileged access, financial systems, sensitive data, and contractors.
A review must produce action, not just a spreadsheet . If a manager flags access as no longer needed, the identity team or an automated workflow must actually revoke it. If no one can explain why a service account exists, investigate and document its owner and purpose before disabling — or retire it safely. A review that merely collects rubber-stamp approvals becomes a paper exercise.
Automation does not remove responsibility
HR systems can trigger JML workflows, identity-governance tools route approvals and reviews, and SSO centralizes disablement. Even so, business owners must define appropriate access, managers must certify accurately, and security must monitor for gaps. The warning signs are delayed deprovisioning, orphaned accounts, and accumulated cross-role permissions — and the remedy is timely JML execution plus recurring reviews.
Least Privilege, Need to Know, and Provisioning Models
The principles that govern what to provision matter as much as the lifecycle mechanics. Least privilege says a subject receives only the access required to perform its tasks — no more. Need to know is the data-focused companion: even a user cleared to a level only sees the specific information their duties require. A common wrong answer offers "grant access in case they need it later" — always wrong, because it violates least privilege and fuels privilege creep.
Provisioning is most defensible when it is role-based . Instead of hand-granting permissions per person, the organization defines roles (Accounts Payable Clerk, Help Desk Tier 1) and assigns users to them. This makes provisioning consistent, deprovisioning clean (remove the role), and reviews tractable (recertify roles, not thousands of individual grants). Watch for toxic combinations that break separation of duties — for example, one person who can both create a vendor and approve its payments. JML and access reviews should detect and split such combinations.
A mover walkthrough
Consider a developer moving from billing to the mobile-app team:
Add new repository, issue-tracker, and cloud-dev access for the mobile role.
Remove billing test-data access and billing deployment privileges.
Record the change with manager approval and an effective date.
Verify at the next access review that no billing entitlements remain.
A mature mover process performs step 2 as part of step 1. Skip it, and the developer can silently keep both permission sets for years.
Reconciliation and orphan hunting
Beyond scheduled reviews, mature programs reconcile the identity store against authoritative sources. Comparing the HR roster to active accounts surfaces logins for people who already left (orphaned/ghost accounts). Comparing application accounts to the central directory surfaces local accounts that bypass SSO and offboarding. The CC takeaway: lifecycle controls are only as good as the evidence that they actually ran — reviews and reconciliation provide that evidence, and an unremediated review finding is itself a deficiency.
Source: ISC2 CC Exam Outline effective September 1, 2026 (v01/2026), subdomain 3.1 (provision, review, deprovision), checked 2026-10-22.