Study guide

6.4 Provisioning, Deprovisioning, JML, and Access Reviews

CISSP Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CISSP Orientation, CAT, and Official Source Control

1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview

2 Chapter 2: Security and Risk Management

2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab

3 Chapter 3: Asset Security and Data Lifecycle

3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab

4 Chapter 4: Security Architecture, Engineering, and Cryptography

4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab

5 Chapter 5: Communication, Network Security, and Zero Trust

5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab

6 Chapter 6: Identity and Access Management

6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab

7 Chapter 7: Security Assessment, Testing, and Audit Strategy

7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab

8 Chapter 8: Security Operations, Incident Response, and Resilience

8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab

9 Chapter 9: Software Development Security and DevSecOps

9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab

10 Chapter 10: Integrated CISSP Governance Scenario Labs

10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation

11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy

11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review

6.4 Provisioning, Deprovisioning, JML, and Access Reviews

Key Takeaways Explain This Topic AI

Joiner, mover, and leaver processes keep identity and access aligned to employment status, role, and business need.

Provisioning should be automated where possible, but every entitlement still needs ownership, approval logic, and review.

Deprovisioning is a high-priority control because stale access, orphaned accounts, and retained tokens create direct compromise paths.

Access reviews are governance evidence only when reviewers understand the access, challenge exceptions, and remediation is tracked.

Last updated: May 2026

Lifecycle Governance as a Control

The joiner, mover, and leaver lifecycle is one of the most important IAM control patterns. A joiner is a new worker or identity that needs initial access. A mover changes role, department, location, project, or risk status. A leaver exits the organization or no longer has a business relationship. Each event should trigger access changes that are timely, complete, and documented.

Provisioning should start from an authoritative source. For employees, that source is often HR. For contractors, it may be a vendor management or sponsor system. For workloads, it may be a deployment pipeline or cloud inventory. The identity source should create a unique identity, assign ownership, set start and end dates, and provide attributes needed for access policy. Manual account creation outside the lifecycle process creates blind spots.

Birthright access is baseline access granted automatically for a role or population. Examples include email, collaboration tools, time reporting, and required training systems. Birthright access should be limited and reviewed because broad baselines can quietly create excessive privilege. A new employee should not receive access to sensitive applications just because others in the department historically had it.

Additional access should follow a request and approval path. The request should identify the business purpose, data or system involved, role or entitlement needed, duration, and approver. Approval should come from someone who understands the business risk, such as a data owner, application owner, or process owner. Manager approval alone may be insufficient if the manager cannot evaluate the entitlement.

Mover events are often more dangerous than joiner events because old access remains while new access is added. A user moving from accounts payable to vendor management may retain payment approval while gaining vendor creation. That creates a separation-of-duties conflict. A good mover process removes access no longer needed, adds new access only after approval, and checks for toxic combinations before completion.

Leaver processing must be fast and coordinated. The organization should disable accounts, revoke sessions, collect badges, remove VPN and cloud access, recover devices, rotate shared secrets if exposed, and transfer ownership of data or workflows. High-risk terminations may require immediate action before the person is notified. Routine departures still require closure because attackers often find and use orphaned accounts.

Lifecycle event Trigger Required control action Evidence to retain

Joiner New employment, contract, partner, workload Create identity, assign baseline access, require MFA HR record, sponsor, approvals, start date

Mover Role, project, location, risk, department change Remove old access, grant new access, check duty conflicts Change ticket, owner approval, review result

Leaver Termination, contract end, decommission Disable identity, revoke tokens, recover assets Timestamp, systems touched, exception notes

Recertification Scheduled review or risk event Confirm, modify, or remove entitlements Reviewer decision, remediation tracking

Automated provisioning tools can reduce delay and inconsistency, but automation must encode policy accurately. If the role catalog is wrong, automation will grant wrong access faster. If application connectors cannot remove access, the process needs manual compensating tasks with tracking. If deprovisioning only disables the directory account but leaves local SaaS users active, the control is incomplete.

Access reviews are periodic checks that validate whether entitlements remain appropriate. Reviews may be manager based, application owner based, data owner based, role based, or privileged access focused. The strongest reviews provide context: who the user is, why access was granted, what the entitlement allows, when it was last used, and whether it conflicts with other access. Rubber-stamp approvals provide weak evidence.

Review frequency should match risk. Privileged access, sensitive data, regulated systems, and high-risk third parties may need more frequent review than low-risk collaboration tools. Reviews should also occur after incidents, reorganizations, mergers, migrations, and major application changes. Event-driven review is often more valuable than waiting for a quarterly schedule.

Metrics help leadership see whether lifecycle governance is working. Useful measures include time to provision, time to deprovision, percentage of access with an owner, stale account count, orphan account count, review completion, revocation success, privileged access age, and number of separation-of-duties conflicts. Metrics should lead to remediation, not just dashboards.

Access Review Decision Guide

Keep access only when there is a current business need and the entitlement matches the user's role.

Modify access when the need remains but the permission level is too broad.

Remove access when the user changed role, the entitlement is unused, the project ended, or ownership is unclear.

Escalate access when it creates a duty conflict, grants privileged rights, or lacks a business owner.

Track every removal to completion, including systems that require manual action.

The CISSP perspective is that provisioning is not a service desk convenience function. It is a preventive, detective, and corrective control. The organization should know who requested access, who approved it, why it exists, when it expires, how it was used, and how quickly it can be removed. That evidence supports least privilege and gives management a defensible view of access risk.